IOFTech Maintenance Release8G Newsletters Doc FAQ Contact Home
|
IOF Problem Resolution Problem A05 | ||||
---|---|---|---|---|---|
Previous | Next | ||||
Description |
IOF gets "Expired" error after applying the new expiration
patch. It was running OK or with an "expiring" error message before
applying the new patch.
| ||||
Background |
The correct linklist load module is obviously being patched, because
applying the new patch caused the problem.
The IOF expiration patch should be saved in the A50EXPIR member of the IOF OPTIONS library. The patch is applied by running the M40EXPIR job from the IOF INSTALL library. M40EXPIR runs the IMASPZAP (superzap) program to apply the new patch to two libraries:
| ||||
Solution |
Carefully verify that the value in the REP statement that is saved
in the A50EXPIR member of the IOF OPTIONS library is correct.
The superzap command is "REP". The location starts at 00 and
increments by 08. There should be 16 HEX digits in the patch
itself. Each 4 digits should be separated by a comma.
All statements MUST BE ENTERED IN UPPER CASE. Carefully check to insure that no digits were transposed or entered in error. Be sure that there are no old "REP" statements in the deck behind the new "REP" statement(s). If the new REP statement checks out, then perhaps the patch is for the wrong CPU. The expiration patch message gives the CPU model/serial number for which each patch is valid, as well as the limiting expiration date. Check this information to insure that the current CPU is covered by the new expiration patch. There are two simple ways to verify the CPU model and serial number of the current CPU:
1. From an MVS console, enter the command "D M=CPU". A line like the one below will be displayed for each CPU. Multiple lines will be displayed for MP systems. |
IOFTech Maintenance Release8G Newsletters Doc FAQ Contact Home
Thursday, 22-Jul-2021 11:38:06 EDT
bm40a50 sverp