As you can tell by doing IPLDATA STATUS under IPCS against any dump (or ACTIVE), IEAVNP26 is SMS initialization. No one should be issuing an ABEND with a code of 000, so a standalone dump would be needed to see what is going on.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List" <IBM-MAIN@LISTSERV.UA.EDU> wrote on 03/31/2021 09:57:15 AM: > From: "Schneck, Glenn" <0000038354c41b84-dmarc-requ...@listserv.ua.edu> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 03/31/2021 01:40 PM > Subject: Wait Code on IPL > Sent by: "IBM Mainframe Discussion List" <IBM-MAIN@LISTSERV.UA.EDU> > > We are getting a wait code 040 with abend code 0000 and Reason Code > 00000000. We did see IEA303W message with Abend code 0000 and Reason > Code 00000000 but only with the first IPL attempt. We have not seen > it with subsequent IPLs. We as a group have spent a few days > researching the wait, abend and reason codes and have found nothing > that would indicate the > > problem. There has been no resent changes to parmlib, or i/o > configurations. The module abending is IEAVNP26, it's located in > SYS1.NUCLEUS. The last message on the console is "GRS > initialization completed successfully". The last successful IPL > was 12/13/2020. > > > > We do have a question; would 2700 uninitialized volumes prevent an > IPL and cause a hang/abend after GRS Activates? > > TIA > > Glenn > > Glenn Schneck > USDC Manager 1 - GPS > Deloitte Consulting LLP > 901 International Parkway, STE 100 > Lake Mary, FL 32746 > Tel/Direct: +1 407-438-8809 | Fax: +1 866-396-3121 | Mobile: +1 321-279-3535 > gschn...@deloitte.com| www.deloitte.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
