Fair point, although it does what I do. I suspect THAT is the answer to the question "where did I get this logic from?" It starts from the TCB if any, which is probably a good idea, even though my situation does not always have a TCB.
Still leaves at least the first question: Out of curiosity, what kind of A/S has no JSAB? But the fact that IAZXJSAB is the party line implies that the answer to my second question is "no better way." Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: Friday, October 12, 2018 7:26 AM To: [email protected] Subject: Re: Reasons for address space with no JSAB/other sources of job name On Fri, Oct 12, 2018 at 9:15 AM Charles Mills <[email protected]> wrote: > I've got code -- and it works without problems -- that chains > ASCBASSB->ASSBJSAB and then loops through JSABs until it finds one with > JSABNVAL not set. I don't recall where I originally came up with the logic. > I note two things about the code: it allows for the possibility that > ASSBJSAB is zero, and for the possibility that it gets to the end of the > JSAB chain without finding a "valid" JSAB (which the application can > tolerate). > > As I said, the code works. I am just trying to understand the situation a > little better. My questions are these: > > - What are the reasons that an address space would not have a JSAB? > *MASTER*? Address spaces started under *MASTER* rather than by JESx? > - Is there a better source of job name and any userid than the JSAB? I see > that SDSF has a jobname for every A/S. I note the existence of ASCBJBNI/S > but don't know much about them. > > Charles > > I vote the GUPI party line: IAZXJSAB READ,JOBNAME=JOBNAME ... JOBNAME DS CL8 ref: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa200/zxjsab.htm ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
