Types of nodes

In JES3 terminology, a node is called either a home node or a remote node. What you call a particular node depends on your point of reference.

The view from any given node is that node is the home node and other nodes are remote nodes. Thus, you always view your node as the home node and other nodes as remote nodes. However, a system programmer at another node views that node as the home node and other nodes (including yours) as remote nodes.

There are two kinds of remote nodes: directly-connected and indirectly-connected. A directly-connected remote node is adjacent to your node, and is connected through a direct BSC or SNA link. An indirectly-connected remote is not adjacent to your node, but is connected to your node through one or more other nodes.

There are two kinds of remote nodes: directly-connected and indirectly-connected. A directly-connected remote node is adjacent to your node, and is connected through direct BSC, SNA, or TCP/IP links. An indirectly-connected remote is not adjacent to your node, but is connected to your node through one or more other nodes.

In the following diagram, A and B are directly-connected nodes as are B and C. Nodes A and C are indirectly-connected through node B.
Types of nodes

You must define the home node and all remote nodes with which the home node communicates. To define a node, use the NJERMT initialization statement.

Note: When defining an indirectly-connected remote node, you might want to include parameters that would allow this node to become directly-connected at some future time. By doing so during initialization, you need only use the *F,NJE command to change the communication path from indirect to direct.
Table 1 identifies required and optional parameters for the home node and for each type of remote node. If you code the other parameters, those that are not indicated as required or optional for the type of node you are defining, JES3 ignores them.
Table 1. Parameter requirements for the NJERMT statement
NJERMT Parameter Type of Node
  Home Node Alias Directly Connected Remote Node Indirectly Connected Remote Node
ALIAS   R    
AUTO     O (BSC)  
BDTID O (SNA)      
BFSIZ     O (BSC)  
CTC     O (BSC)  
DEFCLASS O O    
EXPWD     O (BSC,TCPIP)  
EXSIG     O (BSC)  
HOME (See Note 1)   (See Note 2) (See Note 2)
JOBRECV     O (TCPIP)  
JOBTRANS     O (TCPIP)  
LINE     O (BSC)  
MAXLINE (See Note 3)   (See Note 4) (See Note 3)
NAME R (BSC,SNA,TCPIP) (See Note 6) R (BSC,SNA,TCPIP) R (BSC,SNA,TCPIP)
NETHOLD O      
NJEPR O (BSC)      
NJEPU O (BSC)      
OUTRECV     O (TCPIP)  
OUTTRANS     O (TCPIP)  
PATH     (See Note 5) R (BSC,SNA,TCPIP)
PRECHECK O      
PRTDEF O (BSC,SNA,TCPIP) O (BSC,SNA,TCPIP)    
PRTSO O (BSC,SNA,TCPIP) O (BSC,SNA,TCPIP)    
PRXWTR O (BSC,SNA,TCPIP) O (BSC,SNA,TCPIP)    
PUNDEF O (BSC,SNA,TCPIP) O (BSC,SNA,TCPIP)    
PWCNTL     O O
PWD     O (BSC,TCPIP)  
RDLY     O (BSC)  
SECSIGNON     O (TCPIP)  
SIG     O (BSC)  
STREAM     O (BSC)  
TLS     O (TCPIP)  
TYPE     O (BSC,SNA,TCPIP)    
VFYPATH O   O O
XNAMEREQ O O    
Notes:
  1. Specify HOME=YES (BSC,SNA,TCPIP).
  2. Specify HOME=NO (BSC,SNA,TCPIP).
  3. Specify MAXLINE=0 (BSC)
  4. Specify MAXLINE=1, 2, or 3 (BSC).
  5. Do not specify for directly-connected nodes.
  6. NAME and ALIAS cannot be specified on the same NJERMT statement.
Legend:

R - Required parameter
O - Optional parameter