I see a problem with this scenario. It appears to me that there is a call (not necessarily by Shmuel) to potentially have JES2 wait for OMVS to be up before it does its startup (or at least completes the startup). Due to a self-inflicted screw-up on one of our LPARs, OMVS decided it had to do a filesystem check on every filesystem on the system. This took a good half hour where it simply appeared our LPAR was hung. JES2 had come up and I was able to start a few address spaces that are dependent on JES so I could figure out what was going on. Had JES been waiting for OMVS we would have been completely in the dark on this issue.
I could see there being communication between JES and OMVS so that when OMVS gets initialized it signals JES to redrive any failed zFS allocations, but don't force JES to wait until zFS is available. My $.02. Rex -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Seymour J Metz Sent: Tuesday, May 9, 2023 10:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: JES2 Submitlib Bootstrap problem Yes, IBM absolutely should take startup sequence into account and should provide mechanisms to ensure that things occur in the proper order. This goes beyond OMVS. -- Shmuel (Seymour J.) Metz https://urldefense.com/v3/__http://mason.gmu.edu/*smetz3__;fg!!KjMRP1Ixj6eLE0Fj!oLVba7cIWA-HvwL4aaVssbMaEZeCG3m_dnLPJgpEL8DOiFs5DAJaoVf27kYVUZyYy_Nw7UxsOVp6sogwmA$ ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul Gilmartin [0000042bfe9c879d-dmarc-requ...@listserv.ua.edu] Sent: Tuesday, May 9, 2023 11:01 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2 Submitlib Bootstrap problem On Tue, 9 May 2023 12:18:11 +0000, Mark Jacobs wrote: >I defined several submitlibs in my JES2PARM to use directories in a ZFS >filesystem. When I hotstart JES2, JES2 can find everything and is happy. >During IPL/JES2 startup it's not. It doesn't seem like OMVS is initialized yet >and so the file systems aren't accessible for JES2 to resolve. I haven't fully >analyzed the system log to confirm it yet, but it seems like a reasonable >assumption. Has anyone else run into this? > WAD? z/OS UNIX appears to be a second-class citizen in that operations that require UNIX facilities are allowed to begin before UNIX is available, then simply fail. Should design give more attention to the order of startup operations? Should there be an implied WAIT (not explicit) for any operation which requires UNIX? Would that be likely to result in a deadlock? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
