On Thu, Apr 30, 2015 at 1:33 PM, John Norgauer <jcnorga...@ucdavis.edu> wrote:
> 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. > First, I assume no replies are outstanding. And a light glimmers a bit. The OMVS system, which is actually the BPXOINIT started task, is waiting for something. The first thing that comes to my mind is a mistake in the file: /etc/rc . This file is a "normal" UNIX shell script. It is "sourced" (run in-line, like a COPY) by the initialization process. So everything that it does must complete before the OMVS initialization will complete. What sometimes happens is that someone will make a mistake when trying to use it to initialize UNIX processes at IPL time. The mistake is running something, which does not "daemonize" itself , without a trailing "&" to tell the shell to "start this in the background and continue". This might be something like INETD or HTTPD or ??? . If you have a local TSO terminal (needed because TCPIP won't start without OMVS initialized), you might want see if a PS (ProcesS) display works. If it does, you _might_ be able to see what is holding up the initialization process. No guarantees, of course. Naturally, if you have only the unmodified IBM supplied /etc/rc file, this isn't the problem. In this latter case, you will likely need to do a z/OS console DUMP command to dump the BPXOINIT address space: DUMP COMM=(BPXOINIT STUCK) .. wait for WTOR and then reply (change number) R nn,'JOBNAME=BPXOINIT' And then use IPCS to look at the dump. -- If you sent twitter messages while exploring, are you on a textpedition? He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
