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
