Thanks Jim. I was hoping to avoid digging through a dump but I may be
faced with that fact. Thanks for the reason for the enque, which is
more then I could pull from the Diagnosis Reference of z/OS. I will
take a look to see if one of the subsystems is not starting.
Cheers,
Tom
On 1/3/2014 10:57 AM, Jim Mulder wrote:
I am trying to start a second copy of z/OS under a sysplex and am having
trouble early into the IPL process. It seems that *MASTER* address
space owns an enque SYSIEFSD STCQUE and VTAM, JES2, zFS are waiting on
the same enque. I have been through the documentation and cannot find a
good description about what the enque is for. Any help would be greatly
appreciated. I would like to find a description of why the enque
occurs or an idea what might impact this enque during IPL.
SYSIEFSD STCQUE is obtained by IEEMB860 at the beginning of its
phase of Master Scheduler Initialization, and released when
subsystem initialization completes. It may be that you have
a subsystem whose subsystem initialization routine has not
completed. I would start with a standalone dump.
Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
--
_______________________________________________________________
Regards,
Thomas Dunlap Chief Technology Officer [email protected]
Themis, Inc. http://www.themisinc.com 1 (800) 756-3000
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
