Work with your host programmer to determine which host NJE nodes BARR/NJE needs to communicate with and the relationship of those nodes to each other, if any. This information determines how many Barr nodes you need to define at the host and on the BARR/NJE computer, how many entries you need to make in the BARR/NJE routing table, and how many PUs you need to define in Microsoft SNA Server, Microsoft HIS, or Microsoft SNA Workstation.
In the following graphic, the BARR/NJE computer will connect directly to the unrelated HOST1 and HOST2 nodes, so two Barr nodes are required. BARR/NJE also needs to communicate with the HOST4 and HOST5 nodes, but can do so through the HOST1 node. In this example, HOST1, HOST2, HOST4, and HOST5 are called destination nodes, because they are destinations for jobs. HOST3 is an intermediate node An NJE node situated between an origin node and a destination node. See node., because it will not process jobs but will be used to reach HOST4.
For each adjacent node that BARR/NJE will communicate with, you need to define one Barr node and specify the name of the host node it will communicate with. In this example:
BARR1 
HOST1
BARR2 HOST2
For each destination node that BARR/NJE will communicate with, you need to make an entry in the Barr routing table. You do not need to list intermediate nodes. For example:
BARR1 HOST4
BARR1 HOST5
For each Barr node, the host programmer needs to enter a VTAM and host definition. In this example, you need definitions for the BARR1 and BARR2 nodes.
For each Barr node, the system administrator needs to define a PU to Microsoft SNA Server, Microsoft HIS, or Microsoft SNA Workstation. In this example, you need two PUs, one each for BARR1 and BARR2.
In the Barr software and at the host, the nodes need to be specified by name. Be sure you obtain the correct Barr and host node names from the host programmer before you enter the definitions in the BARR/NJE software.
