Thanks for setting me straight. The threads I referred to must have focused on 'where did the JCL come from?'. Nice to know that the original submitter is available to a running job.
. . . 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 Walt Farrell Sent: Tuesday, August 16, 2016 5:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Real Userid when specifying USER= On Tue, 16 Aug 2016 22:53:32 +0000, Jesse 1 Robinson <jesse1.robin...@sce.com> wrote: >We've had threads here about the difficulty of associating a running >job with the person/process that submitted it. At submit time-- passing >a job stream to the internal reader--the submitter's userid is known so >as to validate SAF authority to run the job under whatever userid is coded on >the job card, if any. After that the origin of the job is not knowable unless >the 'submitting process' has embedded such information somewhere in the job >itself. Not true. The UTOKEN attached to the ACEE while the job is running records both the submitting user and the execution user. However, if that job submits a second job, the association with the original user who submitted the first job is lost. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
