I think tracking a job back to a JCL source file is hopeless. Besides the submit methods mentioned, we get jobs submitted via NDM (Connect Direct) or FTP/REXEC. You could insist on some kind of doc format, but ad hoc submissions would be an endless guessing game. I don't think anyone would try to circumvent a standard; there would just be too many omissions in practice.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Monday, June 06, 2016 2:30 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Determine the PDS a job was submitted from? Or copied to INTRDR from a non-PDS or (gasp!) a UNIX file. IIRC FTP will submit a job from either of those sources also. I am no JES or job exit expert. Could an exit limit INTRDR to specific sources or stick a PDS name somewhere? A member name would fit in SMF30UIF. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, June 06, 2016 5:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Determine the PDS a job was submitted from? On Mon, 6 Jun 2016 14:08:33 -0500, Peter Ten Eyck wrote: >Does anyone have suggestions on how to determine the PDS a job was submitted >from? In this case the ZEKE scheduler was used. I would interested in comments >with and without scheduler. > Without scheduler? Not a chance. In the extreme, a programmer might have typed JCL from scratch in an editor then SUBMIT on the command line. Is it possible to prohibit all use of INTRDR except by an authorized scheduler? (Is it practical?) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
