Nathan, It helps the list to help you when you provide the complete messages or summary dump. There are subtleties based on reason codes and registers.
Since you are looking at the XCF, have you opened a SR/PMR with IBM? They can probably expedite your resolution. Since IBM has the source code, they can review the sections and see what is going on with your environment. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Nathan Astle > Sent: Friday, December 18, 2015 10:22 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: S00C Slip trap for any Stc > > Hi Group > > Basically I am trying to capture the SLIP for the XCF signal failure in our > base sysplex > environment. > > Our SMF logstream has been defined in IXGLOGR with dasdonly. Does that mean > IXGLOGR will Buffer SMF records in memory if it cannot write to DASD ? > > What might be happening here, is that the S00C abend affects XCF services, > which in > turn effect the users of XCF which are: WLM, JES2, GRS, and MASTER. At this > point > GRS becomes unresponsive, and won’t permit the ENQ of a dataset, if that > dataset is > the IFASMF logstream, the records start to backup, where does IXGLOGR put > them. > Would allowing IXGLOGR to use structures in the CF help prevent IXGLOGR from > stealing real storage to buffer SYS EVENTs in the event of the S00C abend of > XCF? > > Any suggestions ? > > Regards > Nathan ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
