The network illustrated in Figure 1 shows how you can extend the capability of basic BSC and SNA NJE configurations. These initialization statements enable an installation to determine the security access one node has to another, the job numbers specified at each node, and the destinations for all output jobs and SYSOUT. Individual nodes must share definitions for the capabilities defined through these initialization parameters to ensure the regular flow of traffic throughout a network.

See Figure 1 as you read through the following explanation of the various initialization statements that control the networking connections between NEWYORK and WASHDC. Preceding each of the following statements is a highlighted number that correlates to a number in parentheses in the figure.

 1  NODE(1) NAME=NEWYORK, PASSWORD=SECRET

This statement assigns the name NEWYORK to this node. When node 1 attempts to sign on to another node in the network, it will identify itself as NEWYORK. The receiving node will look up the name NEWYORK to determine if NEWYORK is a member of the network. If the receiving node does not find an entry for NEWYORK, the receiving node will reject the signon.

PASSWORD=SECRET specifies that if no SEND= password value is specified for NODE(1) to send to another node to which it is signing on, NODE(1) will send this password to that node instead. Note that this option is less secure than two passwords. If you have defined all your nodes using PASSWORD=(SEND=word1,VERify=word2), then it would not be necessary to specify a PASSWORD= parameter on the NODE(1) definition in this initialization data set.

 2  NODE(2) NAME=WASHDC, PASSWORD=(SEND=SECRET,VER=HIDDEN)

PASSWORD=(SEND=SECRET,VER=HIDDEN) specifies that the password that NEWYORK will send to WASHDC is SECRET. The node WASHDC will use this password for verification during signon. In WASHDC's initialization data set, the NODE(1) initialization statement must specify PASSWORD=(SEND=HIDDEN,VER=SECRET).

Figure 1. An Expanded Network

 3  AUTH=(NET=YES)

Specifies one of the four authority categories. In the example, the specification of NET=YES in the AUTH= parameter on the NODE(2) initialization statement on NEWYORK for WASHDC indicates WASHDC has the same authority as consoles attached locally to NEWYORK. WASHDC also has (by default) the ability to affect jobs (JOB=YES), the ability to affect devices (DEVICE=YES), and the ability to affect system function (SYSTEM=YES) at NEWYORK. You can override these defaults. For example, NODE2's initialization data set restricts NEWYORK from affecting system function (AUTH=SYS=NO) at WASHDC.

 4  LINE(1) PASSWORD=LINEPSWD

Specifies the password associated with the line connecting nodes 1 and 2. Notice that both nodes include the password specification in their line definition initialization parameters. NEWYORK will include the line password in the initial signon record sent to WASHDC. WASHDC verifies the line password and sends a response record to NEWYORK that also includes the line password that NEWYORK verifies before continuing signon record processing.

 5  JOBDEF RANGE=(1-499)

Node 1 will assign job identifiers beginning at 1 and assign no identifier greater than 499 for jobs originating locally. For jobs received from node 2 for execution at node 1, node 1 attempts to assign the JOBID that appears in the NJE header received from node 2. Because of the JOBDEF RANGE= specification at node 2, jobs originating at node 2 will have job identifiers beginning at 500 up to and including 999999. Because node 1 does not assign identifiers higher than 499, it can assign numbers beginning at 500 and ending at 999999 (the JES2 system default for job identifiers) to jobs received from node 2. Consequently, each job identifier is unique, and a job transmitted from node 1 to node 2 will have separate job identifiers at each node.

 6  RDR(1) PRTDEST=NEWYORK

Indicates that NEWYORK will print normal print output produced by jobs read in at RDR1 in WASHDC. The PRTDEST=NEWYORK specification corresponds to the NODE 1 node definition statement as defined at node WASHDC. If no NODE 1 statement has been specified at node WASHDC, a printer attached to the system specified by OWNNODE= is the default printer (WASHDC in this example).

 7  DESTID(BRONX)

The statement assigns the name BRONX to the remote workstation numbered 1 (RMT1) attached to NODE1. You can now use BRONX to send jobs or data to the remote workstation.