The saga continues...
I restored SYS1.LINKLIB from the ADCD CD. MVS now comes up, but it appears
to hang right about the time that JES2MON and/or WLM is coming up. There is
no disabled wait, no messages on the console, no discernable interesting
messages in SYSLOG from a stand alone dump, it appears that I cannot type
anything into the console after it hangs. It just hangs.
Any ideas? The end of my master trace from my dump is:
IEF404I BLSJPRMI - ENDED - TIME=09.30.08
IEF196I IEF142I BLSJPRMI BLSJPRMI - STEP WAS EXECUTED - COND
IEF196I IEF373I STEP/IEFPROC /START 2010001.0930
IEF196I IEF374I STEP/IEFPROC /STOP 2010001.0930 CPU 0MIN
IEF196I SRB 0MIN 00.01SEC VIRT 300K SYS 248K EXT
IEF196I 10824K
IEF196I IEF375I JOB/BLSJPRMI/START 2010001.0930
IEF196I IEF376I JOB/BLSJPRMI/STOP 2010001.0930 CPU 0MIN
IEF196I SRB 0MIN 00.01SEC
IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL,
IEF196I IEF285I ADCD.ZOSV14S.PARMLIB
IEF196I IEF285I VOL SER NOS= S4RES1.
IXZ0001I CONNECTION TO JESXCF COMPONENT ESTABLISHED, 045
GROUP N1 MEMBER N1$SYS1
And that's where it stops. The dump shows JES2 and WLM as address spaces
where both high level TCBs are in an RB wait. I'm not sure what the next
step is.
David Logan
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
