It is astonishing how many words this group needs to reply: "No".
Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elardus Engelbrecht Sent: 16 December, 2015 10:37 To: [email protected] Subject: Re: JES2 - originating jcl Paul Gilmartin wrote: >I also submit many jobs via FTP; there's a file, but it's pretty far away. First one mentioning FTP! ;-) And JES2 can't certainly find out from WHERE your JCL is coming from. As Shmuel said, JES2 is NOT reading the member, it is the SUBMITTER who reads in the SOURCE of the JCL, not JES2. You setup JES2 own INTRDR and the submitter selects the right INTRDR for submitting JCL using the original sources of JCL. >I have such; I use it primarily to escape the dreadful Fixed-80 burden. zSecure can escape that burden. I had to shorten my lines if I want to re-submit a failed job it from SDSF... zSecure uses its own version of SUBMIT instead of TSO submit. That is just one example overcoming of that limit. There are many other examples. > ... Self-tailoring -- allows incorporating current date and time in data set > names. >Lizette had a good idea; I'll go further. Couple a code control system with a >scheduler. Some [commercial] schedulers do that. So you can always know from WHERE that job was coming from. >Most shops discourage submitting production jobs from uncontrolled data sets. Indeed. With RACF class STARTED, you can also stop any unknown procs from running at all in the first place. To the OP: the answer is simple: There is NO method in JES2 to discover the source of the JCL. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
