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 http://mason.gmu.edu/~smetz3 ________________________________________ 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
