You define nodes to a network through the NJEDEF and the NODE initialization statements. Use the NJEDEF statement to define your own node characteristics, and the NODE statement to define other nodes. JES2 provides $T commands to modify some of the parameters on these initialization statements.

You can use symbolic destination names to reference nodes, remote workstations, and local devices or workstations and devices attached to a network node. The $ADD DEStid command allows you to dynamically define a symbolic destination name for a node, workstation, or device. You can use the $T DEStid to change a symbolic destination name.

When you have defined nodes to the network, you can start node communications using binary synchronous communication (BSC) lines through VTAM®, which maintains the connection information for SNA NJE application-to-application sessions, or through TCP/IP. You start the three types of connections using different JES2 commands. (For an overview of connecting the network through BSC lines, establishing an SNA session through VTAM, or through TCP/IP, see z/OS JES2 Initialization and Tuning Guide, SA32-0991.)

JES2 allows you to control the VTAM interface for SNA sessions and define new applications dynamically to VTAM. You can also set SNA remote terminals to automatically connect and disconnect. (For a description of controlling remote terminals, see “Remote Job Entry”.) JES2 also allows you to control the TCP/IP interface for TCP/IP sessions, or define new sockets.

You can control NJE lines and devices using the same JES2 commands, regardless of how the NJE connection was established. JES2 also provides networking commands you can use to send requests to any other node in the network. (For a list of all JES2 commands and their RJE restrictions in an NJE environment, see “Remote Entry Restrictions”.)