Specifications

Chapter 3. z/OS notes 51
A1F - Processor controller not available; TOD sync cannot occur (16)
A20 - System found page in FLPA that is not fixed (6)
A21 - Segment table entry for MLPA, PLPA, FLPA, or xFLPA is incorrect (6)
A22 - Error (probably hot I/O) invoked disabled console communication facility (see
manual)
A23 - Program check during machine check handling on only online processor (16)
A24 - Loop while running machine check handler on only online processor (6,16)
A26 - Machine check on only online processor; interruption code incorrect (16)
A27 - Problems during machine check interruption handling
A28 - DAT-off machine check handler cannot start DAT-on machine check handler (6,16)
A29 - Problems stopping processor after program or machine check (6)
A2A - System detected LPA page that is not on paging data set (6)
A2B - Error in extended storage (16)
A70 - Console unavailable during NIP (3)
A71 - Reconfiguration problem (9; see codes manual)
A7A - Service processor interface failed (16,9)
B01-B1D Wait states used by the 3203/3211 utility
B20-B24 Wait states used by the stand-alone IOCP program
CCC - Wait state generated by QUISECE command
D0D - SMF had resource shortage (too much SMF output requested? Memory too small?)
E02 - Should never happen (16)
EC7 - Severe error in Unix System Services (6)
FFx - Non-IBM program created a wait state
The suggested actions provided by the following notes assume you are using z/OS (probably
the AD-CD system) in a normal manner. That is, we assume that:
򐂰 You have not modified the system.
򐂰 You are not working with authorized programs or code.
򐂰 You have not installed middleware that operates as authorized code.
򐂰 You are not actively disrupting the hosting Linux environment for zPDT.
1. Check that your devmap contains the necessary volumes and that they are at addresses
supported by the IODF of your z/OS system. For example, with the AD system have your
3390 volumes addresses in the range A80 -AEF. Restart zPDT and try again. If necessary,
verify your emulated 3390 volumes (using an alcckd xxxx -rs command.)
2. Verify that your IODF points to the correct volumes for SYSRES and the IODF volume.
With the typical AD system these are addresses A80 and A82. Possibly these volumes are
corrupted. Verify your emulated 3390 volumes (using an
alcckd xxxx -rs command),
restart zPDT and try to IPL again.
3. z/OS wants a NIP console. This is address 700 in existing AD systems. Be certain a 3270
session is connected to this address (or whatever NIP console address is specified for
your z/OS system). Also be certain the Linux window you used to start zPDT is open, as
this could provide an alternate, limited NIP console function in some cases. If a 3270
session at address 700 is available, try to IPL again.
4. Have you altered a working system? Changed key PROCLIB members? Changed the
catalog line in the LOADxx member in SYS1IPLPARM? This is not recoverable. You must
IPL another z/OS system (or restore volumes for this z/OS.)
5. Did you IPL the correct volume? Verify your devmap and try again.
6. Internal z/OS problem. Probably not your fault unless the volume is corrupted. Try IPLing
z/OS again. You may need to IPL another z/OS system or restore volumes for this z/OS
system.
7. Someone set a SLIP trap. This is probably a user-caused wait and whoever set the SLIP
trap should know how to proceed. System can be restarted.
8. Typically a system error, but could be an error in a software product. Try IPLing z/OS
again, possibly without starting recently installed middleware.