I was just reading this wondering when the writer was going to say that they're in a shared mas.
:-) Rob On Wed, May 20, 2026, 9:52 AM Paul Feller < [email protected]> wrote: > Peter, not sure what you are talking about when you say that the node name > is common for SYSA and SYSB. The last place I worked every JES2 system in > a > MAS had unique names. To take it one step more each JES2 environment in > the > shop had unique names. > > As far as I know it should not matter that PRD1/PRD2 are not in a MAS and > SYSA/SYSB are in a MAS. My first thought is to look see how the different > lpars are connected over the network. > > Again, looking through the JES2 Initialization and Tuning Guide and JES2 > Initialization and Tuning Reference will help you understand what PARMS to > look at depending on network protocol being used to connect the JES2 > systems. > > Here are links to the z/OS 3.1 version of the manuals from the IBM website. > z/OS: z/OS JES2 Initialization and Tuning Guide > <https://www.ibm.com/docs/en/SSLTBW_3.1.0/pdf/hasa300_v3r1.pdf> (z/OS > 3.1) > z/OS: z/OS JES2 Initialization and Tuning Reference > <https://www.ibm.com/docs/en/SSLTBW_3.1.0/pdf/hasa400_v3r1.pdf> (z/OS > 3.1) > > > Paul > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of > Peter > Sent: Tuesday, May 19, 2026 12:31 PM > To: [email protected] > Subject: Re: NJE routing > > I forgot to tell that > > SYSA and SYSB are on MAS. > > PRD1 and PRD2 are not in MAS. > > Being in MAS the adjacency is automatically decided ? Cause the node name > is common for SYSA and SYSB. > > > On Tue, 19 May 2026, 19:20 Paul Feller, < > [email protected] > <mailto:[email protected]> > wrote: > > > Peter, my suggestion is to take a step back and check how the > > different lpars are connected over the network. > > > > Is there an actual network connection between SYSA and PRD1 or does > > the network between SYSA and PRD1 flow through SYSB? > > > > Is the network connection between lpars over SNA or IP? The > > definitions in the JES2 parms are different for SNA compared to IP. > > > > What level of z/OS are you running. I believe there are panels in > > SDSF that can help determine the type of network connection being used. > > > > You might also want to look at the JES2 Initialization and Tuning > > Guide for information around how to setup an NJE connection. > > > > > > Paul > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected] > <mailto:[email protected]> > On > > Behalf Of Peter > > Sent: Monday, May 18, 2026 11:07 PM > > To: [email protected] <mailto:[email protected]> > > Subject: NJE routing > > > > Hello > > > > I must confess that I am not an expert in JES configuration. > > > > Recently I have inherited a system where there are two plexes PLEXA1 > > and > > PLEXB1 > > > > PLEXA1 has two lpars SYSA and SYSB > > > > PLEXB1 has two lpars PRD1 and PRD2 > > > > So, > > If I submit a job from SYSA towards PRD1, it goes VIA SYSB to PRD1. > > > > It was a quite new thing to me. I went through all the JES2 definition > > in every lpars and I couldn't find how the routing is happening VIA SYSB. > > > > Has anyone implemented a similar scenario and which parameter in JES2 > > controls this type of routing? > > > > Under SDSF, I could see SYSA is connected to PRD1 via SYSB > > > > Any pointers would be appreciated. > > > > Peter > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] <mailto:[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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
