I remember we had some of IFAPRDxx errors when IPLing zOS 2.1 for the first time.
Some of the error messages I could retrieve: IRR418I RACF PRODUCT DISABLED: IRRSSI00 ENDED. BPXP006E OMVS IS WAITING FOR SECURITY PRODUCT INITIALIZATION We had performed NO changes in IFAPRDxx from 1.13 to 2.1 at this point. To fix this, we've copied SYS1.PARMLIB.CPAC.SAMPLE(IFAPRD00) and added the products that were not already inserted there. There are changes in several products. ------------------------------------------------------------------------------------------------------------------------------- *Lucas Rosalen* Emails: rosalen.lu...@gmail.com / *lrosa...@br.ibm.com <lrosa...@br.ibm.com>* LinkedIn: http://br.linkedin.com/in/lrosalen Phone: +55 19 9-8146-7633 2015-04-30 15:33 GMT-03:00 John Norgauer <jcnorga...@ucdavis.edu>: > Lizette > > When the D/R system was up I issued > > D OMVS,F > BPXO042I 07.54.06 DISPLAY OMVS 546 > OMVS 000F ETC/INIT WAIT OMVS=(00,21) > > And that's all that came back. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Thursday, April 30, 2015 11:21 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: OMVS not starting on my DR LPAR > > John, > > Go to SYSLOG and look for OMVS - see what error message you might find. > Also, you should be able to issue D OMVS and see the status of the task. > > Look for BPX messages. > > Lizette > > > -----Original Message----- > >From: John Norgauer <jcnorga...@ucdavis.edu> > >Sent: Apr 30, 2015 10:42 AM > >To: IBM-MAIN@LISTSERV.UA.EDU > >Subject: Re: OMVS not starting on my DR LPAR > > > >My OMVS proc located in SYS1.IBM.PROCLIB is the vanilla proc from IBM. > > > >-----Original Message----- > >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > >On Behalf Of Dean Montevago > >Sent: Thursday, April 30, 2015 10:37 AM > >To: IBM-MAIN@LISTSERV.UA.EDU > >Subject: Re: OMVS not starting on my DR LPAR > > > >Do you have MEMLIMIT=NOLIMIT on the OMVS proc? I had this problem when I > first brought up zOS 1.13. OMVS has to be initialized prior to TCP/IP > starting. OMVS is one of those address spaces started by the OS itself, > like SMS. > > > >On Thu, Apr 30, 2015 at 1:24 PM, John Norgauer <jcnorga...@ucdavis.edu> > >wrote: > > > >> I have a new z/os 2.1 system and when I IPL'ed it on my DR LPAR, OMVS > >> never started. > >> > >> I noticed that my IFAPRD member in parmlib was obsolete and this > >> caused TCP base not to start. > >> > >> Does TCP base actually start OMVS ASID? > >> > >> If TCP is not the culprit, what actually starts OMVS. > >> > >> My Sandbox 2.1 system had no problem with OMVS starting. > >> > >> > >> --------------------------------------------------------------------- > >> - For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO > >> IBM-MAIN > >> > > > > > > > >-- > > > >Dean Montevago > > > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
