On Tue, Dec 5, 2017 at 11:00 AM, Charles Mills <[email protected]> wrote:
> Late to this thread -- sorry. > > I am responsible for an STC that is dubbed immediately and that most > customers start early in the IPL. I have never heard any "you fail because > OMVS is not up" problems from customers. Perhaps we have just been lucky > and/or customers have solved it on their own with automation. I have to > think most of our customers use IPL automation. > No, I made a mistake in my code which _appeared_ to be a UNIX problem because I didn't zero out some fields. > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Rob Scott > Sent: Tuesday, December 5, 2017 8:22 AM > To: [email protected] > Subject: Re: STC @ IPL - how to wait for OMVS to be initialized with no > automation product. > > If ENFREQ listen for event code 46 is out of the question, you could call > BPXEKDA for the global OMVS options and wait+retry if you get rc=28 > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
