Some of the defects addressed in the readme still have NOT been fixed in
release 5.1.1.
First, although it was addressed in the README that APAR PJ26077 was fixed,
the $T variable now returns a 0 instead of the expected timestamp for when a
trap was sent. Reading the actual APAR is not very much help either,
because it does not explain (in layman's terms) how this apar was to be
resolved. The user is simply expecting a timestamp (in hours, minutes,
seconds, etc...) reflecting either when a trap was generated or received,
not an interval between the time a process was started and the time a
subsequent trap was sent. Can this be resolved?
Second, APAR PJ25237 was not addressed at all in the readme for release
5.1.1, and remains an issue. Although, as indicated in the APAR, only one
nvpager process is created, it does NOT loop through all calls until the
system is compltely recycled, at which time, upon initialization of Netview,
the pages are executed. Can this also be resolved?
Raylon Adams
Computer Specialist
DNE/OTSO/NMPB/NMT
410-965-0410 voice
800-766-3803 pgr
raylon.adams@ssa.gov
Tech Tools.gif
Description: GIF image
|
