Did not need to go that far. It is believed that the issue was caused by a 
series of errant VTAM commands issued by a sysprog on the wrong system.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Edward Finnell
Sent: Wednesday, September 21, 2016 6:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SYSZMCS Hang

EREP show anything on the offending LPAR?
 
 
In a message dated 9/21/2016 7:27:03 A.M. Central Daylight Time, 
robert.richa...@opm.gov writes:

An IPL  of the true ENQ-owning system released the QNAME and other systems 
immediately  responded.



----------------------------------------------------------------------
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

Reply via email to