On Tue, 9 May 2023 19:58:11 +0000, Mark Jacobs wrote: >I opened a ticket with IBM on this. Should be interesting to hear what they >say. > Keep the list posted. I'm taking short odds on WAD in view of Rex's concerns. OMVS remains a second-class citizen; considered expendable. You might be advised to move your submitlib to an old-fashioned PDS.
>------- Original Message ------- >On Tuesday, May 9th, 2023 at 12:21 PM, Pommier, Rex wrote: > >> 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. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
