Re: SYSZMCS Hang
OMG Human Error! In a message dated 9/22/2016 4:31:43 A.M. Central Daylight Time, robert.richa...@opm.gov writes: 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. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSZMCS Hang
> On Sep 22, 2016, at 2:23 AM, Elardus Engelbrecht >wrote: > > Edward Finnell wrote: > >> EREP show anything on the offending LPAR? > > What type of EREP records will be written if there are such events? EOD? OBR? > SFT? or other type? > > Or should I just use PRINT=AL and the scan the output? ———SNIP——— Do a Print=al that will give you and idea what lead up to the issue (hopefully). Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSZMCS Hang
If that is the case, you may have been able to save yourself an IPL using the CMDS console command that allows for cancelling in-process/hung operator commands. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Thursday, September 22, 2016 5:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSZMCS Hang 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 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSZMCS Hang
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
Re: SYSZMCS Hang
Edward Finnell wrote: >The Sample EREP report covers about everything. Think it's a nine step job. >May have to add parms for devices or ranges. Generally look for the outliers >perm, temp and soft just to get in the ball park. If no SAD were taken might >get the abending task and go from there.. Many thanks! That is a relief. I do also basically the same. Getting a full PRINT=AL report to get in the 'ball park'. Get a second report - EVENTS for a chronological overview. Then I go look for the some clues and also in dumps, SYSLOG, etc. Thanks Edward for your kind reply. I really appreciate it much! Sorry to the OP, but I don't know what to do with the event of SYSZMCS hang. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSZMCS Hang
The Sample EREP report covers about everything. Think it's a nine step job. May have to add parms for devices or ranges. Generally look for the outliers perm, temp and soft just to get in the ball park. If no SAD were taken might get the abending task and go from there.. In a message dated 9/22/2016 2:23:36 A.M. Central Daylight Time, elardus.engelbre...@sita.co.za writes: What type of EREP records will be written if there are such events? EOD? OBR? SFT? or other type? Or should I just use PRINT=AL and the scan the output? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSZMCS Hang
Edward Finnell wrote: >EREP show anything on the offending LPAR? What type of EREP records will be written if there are such events? EOD? OBR? SFT? or other type? Or should I just use PRINT=AL and the scan the output? TIA! Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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
Re: SYSZMCS Hang
An IPL of the true ENQ-owning system released the QNAME and other systems immediately responded. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell Sent: Tuesday, September 20, 2016 11:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSZMCS Hang Hard to say w/o more info. Are there any SIM messages logged? My guess is some hardware something failed and XCF signaling is stuck. If you can purge the offender might be able to get by. Found an old 2004 APAR OA05697 but that's about it. MSGCNZMSG4 OA05697 INVALID GEPL DETECTED IN IEAVG603 ON SYSTEM . ISSUING DUMP. PLEASE SEND TO CONSOLE L2. . In a message dated 9/20/2016 8:59:02 P.M. Central Daylight Time, robert.richa...@opm.gov writes: Just got a call from work. Is there a way to free a SYSZMCS hang in a sysplex without IPLs? -- 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
Re: SYSZMCS Hang
Hard to say w/o more info. Are there any SIM messages logged? My guess is some hardware something failed and XCF signaling is stuck. If you can purge the offender might be able to get by. Found an old 2004 APAR OA05697 but that's about it. MSGCNZMSG4 OA05697 INVALID GEPL DETECTED IN IEAVG603 ON SYSTEM . ISSUING DUMP. PLEASE SEND TO CONSOLE L2. . In a message dated 9/20/2016 8:59:02 P.M. Central Daylight Time, robert.richa...@opm.gov writes: Just got a call from work. Is there a way to free a SYSZMCS hang in a sysplex without IPLs? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN