Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
NJE file duplication
4 views
Skip to first unread message
Paul Coyne
Nov 6, 2012, 7:05:20 AM11/6/12
to
I am trying to determine if there is some way of creating a copy of a file sent via NJE to RMTy to allow for processing on RMTz also. This is to allow parallel processing without the client having to change any JCL. I have looked at DESTID definitions but it looks as if this is not possible. If anybody has any ideas they would be appreciated.
Thanks, Paul
Thanks, Paul
Tom Wasik
Nov 6, 2012, 11:35:44 AM11/6/12
to
If you have the ability to alter the JCL, you can also add OUTPUT statements to create instances of the data set for both RMTx and RMTy. Use DEFAULT=YES and/or JESDS=ALL to get the OUTPUT statement to apply to the appropriate SYSOUT data sets.
If you do not want to alter the JCL there are some other options. Are you really talking NJE or RJE? You stated RMTy and RMTx so let me presume RJE. There are 2 schemes that I can think of to do this. Both are a bit tricky.
The first takes advantage of OUTDISP to maintain a copy of an output group after it has been processed. If you can get the SYSOUT created with an OUTDISP=KEEP (or use EXIT 40 to set this as the OUTDISP) and set the destination to RMTy, then RMTy will print it and the output will not purge but be placed in hold status (the OUTDISP will change to LEAVE). You can then issue a command such as
$TOJ(*),/OUTDISP=LEAVE,/DEST=RMTy,OUTDISP=WRITE,DEST=RMTx
This will reroute all the output going to RMTy that has been processed (has an OUTDISP=LEAVE) to RMTx and set the new OUTDISP to WRITE.
This scheme will not work for NJE since OUTDISP only applies at the destination.
Another scheme would use an exit to create a clone JOE. You can code an exit 1 that detects it is processing a JOE for RMTy. It can then take the existing JOE and pass it into a $#ADD macro call. This will create a clone JOE that is an exact copy of the original JOE. It passes back the new JOE to the caller and you can then alter the destination of then new JOE and do a $#MOD to put it back in the queue.
Now this second scheme can be used for NJE if you use a different exit (say exit 46/56 for NJE selection). The processing is effectively the same to create a clone JOE and queue it to another NJE node.
Tom Wasik
JES2 Development
If you do not want to alter the JCL there are some other options. Are you really talking NJE or RJE? You stated RMTy and RMTx so let me presume RJE. There are 2 schemes that I can think of to do this. Both are a bit tricky.
The first takes advantage of OUTDISP to maintain a copy of an output group after it has been processed. If you can get the SYSOUT created with an OUTDISP=KEEP (or use EXIT 40 to set this as the OUTDISP) and set the destination to RMTy, then RMTy will print it and the output will not purge but be placed in hold status (the OUTDISP will change to LEAVE). You can then issue a command such as
$TOJ(*),/OUTDISP=LEAVE,/DEST=RMTy,OUTDISP=WRITE,DEST=RMTx
This will reroute all the output going to RMTy that has been processed (has an OUTDISP=LEAVE) to RMTx and set the new OUTDISP to WRITE.
This scheme will not work for NJE since OUTDISP only applies at the destination.
Another scheme would use an exit to create a clone JOE. You can code an exit 1 that detects it is processing a JOE for RMTy. It can then take the existing JOE and pass it into a $#ADD macro call. This will create a clone JOE that is an exact copy of the original JOE. It passes back the new JOE to the caller and you can then alter the destination of then new JOE and do a $#MOD to put it back in the queue.
Now this second scheme can be used for NJE if you use a different exit (say exit 46/56 for NJE selection). The processing is effectively the same to create a clone JOE and queue it to another NJE node.
Tom Wasik
JES2 Development
Coyne, Paul
Nov 7, 2012, 9:29:38 AM11/7/12
to
Tom, thanks for the detailed information. I thought it would come to coding an exit but maybe I can convince our application team to change the JCL.
Paul Coyne
z/OS Systems Programmer
Global Technology Services
Experian
Information in this e-mail and any attachments is confidential, and may not be copied or used by anyone other than the addressee, nor disclosed to any third party without our permission. There is no intention to create any legally binding contract or other binding commitment through the use of this electronic communication unless it is issued in accordance with the Experian Limited standard terms and conditions of purchase or other express written agreement between Experian Limited and the recipient. Although Experian has taken reasonable steps to ensure that this communication and any attachments are free from computer virus, you are advised to take your own steps to ensure that they are actually virus free.
Companies Act information: Registered name: Experian Limited. Registered office: Landmark House, Experian Way, NG2 Business Park, Nottingham, NG80 1ZZ, United Kingdom. Place of registration: England and Wales. Registered number: 653331
Paul Coyne
z/OS Systems Programmer
Global Technology Services
Experian
Companies Act information: Registered name: Experian Limited. Registered office: Landmark House, Experian Way, NG2 Business Park, Nottingham, NG80 1ZZ, United Kingdom. Place of registration: England and Wales. Registered number: 653331
0 new messages