Job Entry Network Considerations

If your complex is part of a job entry network and channel-to-channel adapters are being used to connect your node to adjacent nodes, you must restart the lines with the *CALL,NJE command to resume networking communication with the adjacent nodes after a DSI is performed.

If your complex is part of a TCP/IP job entry network, you must typically not restart z/OS® Unix System Services, z/OS Communication Server TCP/IP, or ACF/VTAM on the new global after a DSI is performed if those components run normally. A Netserv that was active on the old global will continue to be active on the old global after JES3 on that processor is restarted as a local. However, if the old global is now down, and you resume networking communication with the adjacent nodes, you need to change the Netserv to run on the new global or another local (that was not involved in the DSI) and restart the Netserv. You might also need to modify and restart sockets on adjacent nodes to reflect changes in the IP address of the Netserv if, as a result of moving the Netserv, the IP address changes and causes host names on the socket definitions for the adjacent nodes not to resolve to the correct IP address.