When you enter a "submit" command while in ISPF edit, ISPF saves the current data in the "edit buffer" to a data set, then does a TSO SUBMIT against that. So, even if you could log the name of that "temporary" dataset, it wouldn't tell you the name of the member you were editing. And what use would it be? I regularly edit PDS.CNTL(JUNK). COPY the data I want into it. Then do a SUBMIT. Then do a CANCEL.
And, departing from TSO oriented stuff, I use a z/OS UNIX shell quite a bit. There is a submit command for that environment as well. I sometimes write programs which read data; use it to create JCL; write that to "stdout" which is "piped" into the "submit" command. There is no way to "backtrack" that sort of thing. Is there any other interactive editing facilities? How about RDz? It can submit jobs. IBM is promoting that. Is ROSCOE still available? What about jobs submitted over NJE? Yes, I'm getting far afield. But once you give somebody a report on "where a job came from" in TSO, they will end up wanting to know (required for auditing and so MUST BE DONE!) where every job came from. And I don't see where it is really of any use. Perhaps the OP could help me on this point. I really am stumped about why anybody would care. Now, being able to log the entire "job stream" (JCL and data images) might be of some interest to somebody. But not to me. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Steve Horein > Sent: Thursday, September 27, 2012 3:58 PM > To: [email protected] > 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 > understand this will fall short when a job is submitted outside of TSO. > I'm > hoping a positive answer is provided! > > On Sep 27, 2012 2:51 PM, "Smith, Sean M" > <[email protected]> > wrote: > > Is there a way in a batch job running REXX, for the REXX to figure out > the > original library and member the JCL came from? My experience tells me > no > and my hunch tells me the same thing but I thought I would put it out > there > in case someone has been here and seen this...hidden in a JES control > block > which is updated by SUBMIT...I know..stretching here > > > Sean Smith > Bank of America > > ---------------------------------------------------------------------- > This message w/attachments (message) is intended solely for the use of > the > intended recipient(s) and may contain information that is privileged, > confidential or proprietary. If you are not an intended recipient, > please > notify the sender, and then please delete and destroy all copies and > attachments, and be advised that any review or dissemination of, or the > taking of any action in reliance on, the information contained in or > attached to this message is prohibited. > Unless specifically indicated, this message is not an offer to sell or > a > solicitation of any investment products or other financial product or > service, an official confirmation of any transaction, or an official > statement of Sender. Subject to applicable law, Sender may intercept, > monitor, review and retain e-communications (EC) traveling through its > networks/systems and may produce any such EC to regulators, law > enforcement, in litigation and as required by law. > The laws of the country of each sender/recipient may impact the > handling of > EC, and EC may be archived, supervised and produced in countries other > than > the country in which you are located. This message cannot be guaranteed > to > be secure or free of errors or viruses. > > References to "Sender" are references to any subsidiary of Bank of > America > Corporation. Securities and Insurance Products: * Are Not FDIC Insured > * > Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are > Not > a Condition to Any Banking Service or Activity * Are Not Insured by Any > Federal Government Agency. Attachments that are part of this EC may > have > additional important disclosures and disclaimers, which you should > read. > This message is subject to terms available at the following link: > http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender > you > consent to the foregoing. > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
