On Tue, Dec 15, 2015 at 8:41 AM, Sumi, Joseph J. (CMS/CTR) (CTR) < [email protected]> wrote:
> Hello, is there a JES2 exit that will allow us to place the dataset and > member name of the job that was submitted ? The originating dataset/member > would be added as a comment to the JESLOG, MESSAGES, or JCL. I would assume > JES2 would know where the JCL came from but not sure. > No, it doesn't really. In most cases, the JCL is coming in from a "reader" of some sort (local, NJE, RJE, or _most likely today_ the internal reader: INTRDR). In all cases other than the INTRDR case, there is no DSN involved at all. And JES2 does know the origin and writes it in SMF. E.g. R1.RD1 for a card reader attached to "remote 1". If anybody use RJE any more. In the INTRDR case, the JCL is simply written out like it would be to a normal data set, most likely using QSAM or maybe BSAM. JES2 has no idea where the program doing the writing is getting it from. There might not even be a "data set", such as in the case of a CLIST doing a SUBMIT * command (JCL is in-line). Also, keep in mind that if someone is in ISPF EDIT and does a SUBMIT command, that command actually writes the contents of the edit buffer to an ISPF "temporary" (.CNTL) data sets, so even if JES2 somehow knew that DSN, it wouldn't help you with the DSN/MEMBER which was actually submitted by the ISPF SUBMIT edit command. > > Rgrds, Joseph Sumi > > -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
