Page 1 of 1

Change JES2 Node Name

Posted: Mon Sep 15, 2025 3:43 pm
by robi1a
Hello

I have 3 zOS systems connected via NJE and I want to remove old JES2 settings and also want to adopt the JES2 node names. The node names are decades old and never adopted to a good naming convention. An according example in the small drawing below. Now I want to give them a new name like JES<sysname>.

DEV1 (JNODE1) ----  SYS1 (JESA)  -----  TEST (JES9)

There are several jobs are routed from one system to another system. Too many to have them under easy control. My idea would be to give the JES2 both the old and the new node name for a smooth migration for some time. I took several tries but I never succeeded. Is there a way to do this? And how can I do such smooth migration to the new node name?

regards

Re: Change JES2 Node Name

Posted: Fri Sep 19, 2025 8:14 pm
by Anuj Dhawan
JES2 can’t give a system two primary node names at the same time. For a smooth migration, keep the old local name initially, and on all three systems define both the old and the new names as remote nodes pointing to the same partner. That lets you run old and new routes in parallel. When ready, switch each system’s local NODE(n) NAME= to the new name during a planned window, keep the old remote names for a grace period, then remove them.

I'm not a subject matter expert here, though just adding my two cents here..

Example (JES2PARM):
 

Code: Select all

/* SYS1 during transition: local=JESA, but both names defined on partners */
NODE(1) NAME=JESA, TYPE=TCPIP,HOSTNAME=sys1,RMTPORT=175 NODE(110) NAME=JNODE1, TYPE=TCPIP,HOSTNAME=dev1,RMTPORT=175 NODE(111) NAME=JESDEV1, TYPE=TCPIP,HOSTNAME=dev1,RMTPORT=175 NODE(120) NAME=JES9, TYPE=TCPIP,HOSTNAME=test,RMTPORT=175 NODE(121) NAME=JESTEST, TYPE=TCPIP,HOSTNAME=test,RMTPORT=175

/* Cutover later on SYS1: */
NODE(1) NAME=JESSYS1, TYPE=TCPIP,HOSTNAME=sys1,RMTPORT=175 
Test with:
 

Code: Select all

/*ROUTE XEQ JESA /*ROUTE XEQ JESSYS1