I don't believe so. All the execution node does is look at the NOTIFY statement on the jobcard (if it is there) and sends a message back to the the origin node via JES2 services/RTAM, and the origin JES2 sends a notify to the userid via MVS SEND.
The execution node tries to use the same job number that the originating node allocated provided it's not already in use and it's in the job number range. It's all talked about in the JES2 Init and Tuning Guide. Ant. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of vatsal raicha Sent: Thursday, 14 October 2010 2:21 PM To: [email protected] Subject: JES2 Control Block Hi, I am submitting a job at one lpar with /*route xeq statement to NJE it over to another lpar. Once the Job is received at another lpar, the sending lpar receives a message with the job number assigned at the receiving lpar. Does Jes2 save this Job number( from the receiving lpar) somewhere at the sending lpar? If yes, can it be accessed via any jes2 control blocks? Thanks, Vatsal ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
