G06.26 ReadMe

1. VDP catalog files are dumped and the VDP is deleted
2. A VDP with the same name is created and the catalog files are
recovered
only the ANT catalog location is updated when using the SMFIXUP
USECATALOG command. A %4072 CPU halt will occur when starting the
VDP in noisy mode.
Recovery
Reload the halted CPU.
Workaround
Do a TMFCOM RECOVERY of all the VDP catalog files. If only the ANT
catalog file is to be recovered, do a RECOVERY of the PENDOPS file
along with the ANT file and use SMFIXUP USECATALOG command for those
catalog files.
Alternatively, start the VDP in quiet mode.
o SMMASTR (T8465)
Solution 10-050309-5442
An error 5214 may occur and Event 5214 EMS messages may also be
reported when adding more than 700 VDPs using SCF.
Recovery
1. Restart the master process ($ZSMS).
2. After restarting, you can add more VDPs.
Note that during the time period that $ZSMS is stopped and
restarted, VDPs already created will not be accessible.
Workaround
None.
o SNAX/XF (T9064)
Solution 10-050113-3540
Under the following circumstances in a SNAX/APN LEN node
configuration, the backup SNAX Line Handler process will trigger
a self-asserted halt with code %47277:
1. SNAX/APN LEN node configuration is used to connect to an IBM
machine.
2. A TLOG-ILOG session has been established.
3. The Creator process which has been configured to the SNAX
subsystem has not been started.
4. A LOGON request is received from the remote IBM machine.
5. SCF STOP and DELETE commands are executed over the LU, whose
SNANAME matches to the SNANAME received in the LOGON request.
6. The above deleted LU is readded to the SNAX subsystem using an
SCF ADD LU command.
Recovery
Bring up the processor over which the backup SNAX Line Handler was
running, and reconfigure the LU using SCF commands.
Workaround
None.
Page
5
of
10