Since, I don't believe you when if you maintain that from an executing job, you can in all cases determine the dataset (if any) that contained the jobs JCL, please do answer publically.
Since it is an easy matter using IEBGENER and the internal reader to piece together JCL from several disparate datasets, determining the single source is not always feasible. Dave Gibney Information Technology Services Washington State University > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Mitch > Sent: Thursday, September 27, 2012 2:10 PM > To: [email protected] > Subject: Re: JCL Source Library Name Available During Execution? > > I had indicated in a previous email that there is a way to do this, but that I > would send the information via private reply. If others want to know this, > please let me know and I will publish the response to the group, instead. > > With Regards, > > Mitch McCluhan, > Legacy Modernization Consultant > > > > -----Original Message----- > From: Steve Horein <[email protected]> > To: IBM-MAIN <[email protected]> > Sent: Thu, Sep 27, 2012 1:58 pm > Subject: Re: JCL Source Library Name Available During Execution? > > > I too have a desire for this same information! I started chasing down > published) IKJ* data areas for when I "sub" a job in ISPF, but know and > nderstand this will fall short when a job is submitted outside of TSO. I'm > oping a positive answer is provided! > On Sep 27, 2012 2:51 PM, "Smith, Sean M" > <[email protected]> > rote: > Is there a way in a batch job running REXX, for the REXX to figure out the > riginal library and member the JCL came from? My experience tells me no > nd my hunch tells me the same thing but I thought I would put it out there > n case someone has been here and seen this...hidden in a JES control block > hich is updated by SUBMIT...I know..stretching here > > ean Smith > ank of America > ---------------------------------------------------------------------- > his message w/attachments (message) is intended solely for the use of the > ntended recipient(s) and may contain information that is privileged, > onfidential or proprietary. If you are not an intended recipient, please > otify the sender, and then please delete and destroy all copies and > ttachments, and be advised that any review or dissemination of, or the > aking of any action in reliance on, the information contained in or > ttached to this message is prohibited. > nless specifically indicated, this message is not an offer to sell or a > olicitation of any investment products or other financial product or > ervice, an official confirmation of any transaction, or an official > tatement of Sender. Subject to applicable law, Sender may intercept, > onitor, review and retain e-communications (EC) traveling through its > etworks/systems and may produce any such EC to regulators, law > nforcement, in litigation and as required by law. > he laws of the country of each sender/recipient may impact the handling of > C, and EC may be archived, supervised and produced in countries other than > he country in which you are located. This message cannot be guaranteed to > e secure or free of errors or viruses. > References to "Sender" are references to any subsidiary of Bank of America > orporation. Securities and Insurance Products: * Are Not FDIC Insured * > re Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are > Not > Condition to Any Banking Service or Activity * Are Not Insured by Any > ederal Government Agency. Attachments that are part of this EC may have > dditional important disclosures and disclaimers, which you should read. > his message is subject to terms available at the following link: > ttp://www.bankofamerica.com/emaildisclaimer. By messaging with Sender > you > onsent to the foregoing. > ---------------------------------------------------------------------- > or IBM-MAIN subscribe / signoff / archive access instructions, > end email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- > or IBM-MAIN subscribe / signoff / archive access instructions, > end email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
