Is there a network connection between SYSA and PRD1? Is there any commands issued to try to start a JES2 connection between SYSA and PPRD1?
If there is no direct connection between SYSA and PRD1 then SYSA will look for a different route. The route it finds to PRD1 is to go through SYSB. Paul -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Peter Sent: Tuesday, May 26, 2026 11:38 AM To: [email protected] Subject: Re: NJE routing Here Even though SYSA wants to execute directly on PRD1 but it takes a route to SYSB and goes to PRD1. Is the EXIT responsible for this type of thing? On Tue, 26 May 2026, 20:37 Ituriel do Neto, < [email protected] <mailto:[email protected]> > wrote: > Hi all, > > Twenty years ago, I led a JES3-JES2 migration in my previous employer, > and we had a similar situation. > Some batch jobs were automatically sent for execution in other nodes, > and some sysouts should also be directed to different nodes. > IIRC, it was done by using JES2 exit 6, which assigned the execution > node based on jobname pattern or execution CLASS= parameter. > For the sysout reassignment, JES2 exit 40 was coded, changing the DEST > and the OUTDISP of the sysouts. > > > > Best Regards > > Ituriel do Nascimento Neto > z/OS System Programmer > > > > > > > Em segunda-feira, 25 de maio de 2026 às 16:00:58 BRT, Peter < > [email protected] <mailto:[email protected]> > escreveu: > > > > > > Hello Steve > > That helps a lot. Could you please share on how auto route works ? > > On Mon, 25 May 2026, 18:03 Steve Estle, < > [email protected] <mailto:[email protected]> > wrote: > > > Hello, > > > > We recently completed a JES3 to JES2 migration - the production > > environment was a two node MAS JES2 setup where we had to "auto" > > route select jobclasses between the two nodes automatically to match > > up with > what > > JES3 was doing - it is a bit tricky to code in JES2PARM config and > > needed IBM's help to complete. Also involved some JES2 commands be > > executed as ending part of JES2PARM setup on each node. > > > > If want I can share how that was done via JES2PARM - this was ZOS / > > JES2 2.5. > > > > Thanks, > > Steve Estle > > CDW > > > > -------------------------------------------------------------------- > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] <mailto:[email protected]> with the message: INFO > > IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] <mailto:[email protected]> with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] <mailto:[email protected]> with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] <mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
