PSW 00020000 80000000 00000000 0C0D0030 The low order 3 nibbles (x'030') are the wait state code.
An SAD would provide more information, however with looking at a dump, this is commonly seen when there is insufficient SQA/LSQA during system initialization. Check the values for SQA and CSA in IEASYS00. Also check INITSQA in LOADxx Also found some info via google that indicates it may be a 106 abend earlier (possibly also due to lack of storage). Google search " zos wait030." >From MVS SYSTEM CODES (WAIT STATE CODES): 030 Explanation: The system abended a task during nucleus initialization program (NIP) processing. The hexadecimal abend code ccc appears in the right-most four bytes of the wait state program status word (PSW). The wait state PSW can appear in either of the following formats: x0cccwww xccc0www System action: The system abends the task and enters a non-restartable wait state. Operator response: Record the wait state PSW and notify the system programmer. If the system programmer requests it, obtain a stand-alone dump. System programmer response: See the system programmer response for the abend code. The abend SVC entry in the system's SVC table contains the address of a trap routine in NIP and not the address of the abend SVC. The registers at the time of the abend SVC request are found in the Type I SVC save area. If the problem persists, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM support Center. Provide the contents of the wait state PSW. Source: Nucleus initialization program (NIP) HTH, <snip> Just applied some maintenance and at IPL. I believe I researched all the ACTION items before IPL and did not find any that applied disabled wait PSW 00020000 80000000 00000000 0C0D0030 </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
