IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> wrote on 09/18/2009 04:41:28 AM: > Re: Curious about ATTACH and 'SVCR 0' > Steve Austin > > This is occuring on z/OS 1.10. Is there specific maintenance required? > What type of entry will I see when the anomaly is addressed?
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On > Behalf Of Peter Relson > Sent: 17 September 2009 19:38 > To: IBM-MAIN@bama.ua.edu > Subject: Re: Curious about ATTACH and 'SVCR 0' > > I believe that this anomaly has been addressed in z/OS 1.10. > > Peter Relson > z/OS Core Technology Design I had forgotten the specific case that was addressed in z/OS 1.10, but after a bit of research, it turns out that it was for an IRB exiting. >From some comments in the changed code: /* OTHERWISE IF IRB EXITING THEN */ /* TERMINATE IRB */ /* This return address will perform exit prologue and return to the dispatcher, but not create a System Trace SVCR record. Previously IEAVEXP1 was called which creates an SVCR record using SVC # in the current top RB (oftentimes Wait), but that is unrelated to the IRB and the current flow. Consideration was given to creating a SVCR record for SVC3 but this was deemed unnecessary as any SSRV System Trace records could be correctly identified as coming from this routine, and the next System Trace entry for this task will generally be a DSP record. @LHA*/ Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
