Before starting the steps in this topic, you must install the CTC hardware. After installing the CTC hardware, you must define the connections between Barr nodes and adjacent host nodes, configure a CTC node and an NJE node, and start the CTC node.
You must be a member of the local Administrators
group to operate the NJE Configuration Utility. If you are assigned the
Configure - NJE user
access right on the computer to which you are trying to connect, but
are not a member of the Administrators
group, the NJE Configuration Utility will operate in read-only mode.
You can also define
routing tables to route jobs from BARR/SPOOL
and messages from NJE Console
to host nodes on the NJE network.
Before configuring BARR/NJE for the first
time, you must install the
CTC hardware.
Use the NJE Configuration Utility to define and configure CTC connections for communicating with the host. The procedures outlined in this topic are required. Your host programmer can help configure the link settings. Complete the following steps to configure the connection.
Open the NJE Configuration Utility.
Select the Communications
Profile tab. 
Under Connection, click Add. The Add Connection dialog box displays.
Type the connection Name.
In the Type
drop-down list, select CTC. Click
OK. The Connection
Configuration dialog box displays.
Next to CTC
Configuration, click Modify.
The CTC Configuration dialog
box displays. Complete the following steps to configure the CTC node.
Select the Adapter that connects to the host's channel. The CHANNEL adapters that are currently installed appear in the list.
If you are using an ESCON connection, from the Image drop-down list, select a control unit image number. Each image can have up to 256 subchannel addresses.
Select the Channel address. Each CTC NJE node must have a unique channel address (except for differing images), which must match the subchannel address at the host. You can enter an address ranging from 00 to FF.
Under Connection type, specify how the node connection to the mainframe will be made. There is no wrong value for this setting, which may or may not be used. It is simply used to expedite the session initiation.
Click OK to return to the Connection Configuration dialog box.
Next to NJE
Configuration, click Modify.
The NJE Configuration dialog
box displays. Complete the following steps to configure the NJE node.
Under BARR node, type the Barr node Name. This must match the BARR/NJE node name specified during JES2, JES3, or POWER configuration. The Location box is currently unavailable.
Type the host node Name. This must match the host node name specified during JES2, JES3, or POWER configuration.
In the Type drop-down list, select the host node. If you are using JES2 or JES3, select MVS/JES2. If you are using POWER, select VSE/POWER.
Click Advanced.
The Advanced Node Settings
dialog box displays.
If you want to use passwords, specify a Send password and a Receive password. The send password is the password sent to the host to authenticate the BARR node. The receive password is the password the BARR node expects to receive from the host to authenticate the host node. By default, the passwords are blank.
The
Features fields are set for optimal
performance and are compatible with host systems.
Under Streams, enter the number of streams. This must match the number of streams specified during JES2 or POWER configuration. If you are using JES3, skip this step.
The
host's receivers correspond to BARR's transmitters, and the host's transmitters
correspond to BARR's receivers. For example, if the host is configured
for 5 SYSIN transmitters, the SYSIN receivers field must be 5.
Click OK and then Close.
When you click OK to close the NJE Configuration Utility, a message displays asking if you want to restart the BARR NJE service. Click Yes.
After you have completed configuring BARR/NJE, you must start the CTC node. Complete the following steps after the BARR NJE service has restarted.
At the host console, vary the CTC device online Activated and ready for operation; capable of communicating with or being controlled by a computer. using the command:
vary devnumber,online
Where devnumber is the CTC device number used to define lines and streams for the node.
At the host console, issue the JES2 start line command:
$SLN#
Where # is the line number used to define lines and streams for the node.
A message will display on the host console indicating that the node is active. If this message does not appear, use Operator Console to diagnose the problem.
You can now finish testing the NJE connection by sending a job or print data set from the host to your NJE node.
At the host console, vary the CTC device online Activated and ready for operation; capable of communicating with or being controlled by a computer. using the command:
vary devnumber,online
Where devnumber is the CTC device number used to define lines and streams for the node.
Verify that the NJE LU is activated.
At the host console, issue the JES3 start networking command.
+S SNA,NODE=nodename
Where nodename is the BARR/NJE node name set in JES3 configuration.
A message will display on the host console indicating that the node is active. If this message does not appear, use the Operator Console to diagnose the problem.
You can now finish testing the NJE connection and send a job or print data set from the host to your NJE node.
At the host console, vary the CTC device online using the command:
online devnumber
Where devnumber is the CTC device number defined in the CTC host configuration.
At the host console, issue the POWER start line command:
PSTART PNET,NODENAME,,DEVNUMBER
A message will display on the host console indicating that the node is active. If this message does not appear, use Operator Console to diagnose the problem.
You can now finish testing the NJE connection by sending a job or print data set from the host to your NJE node.
No additional configuration is needed for receiving print jobs. Once the NJE connection is operational and the node has been started at the host, jobs will automatically be received into the spool. From BARR/SPOOL, you can reroute jobs to various destinations using a header field.
To send a test print job, request that the job be submitted from the host to BARR/NJE and use the Barr node name as the destination. Anyone on the host can route their job to an NJE node using the DEST= parameter in their JCL. For example, you could specify DEST=barrnode in your JCL where barrnode is the BARR/NJE node name specified during JES2, JES3, or POWER configuration.
//SYSOUT DD SYSOUT=A,DEST=barrnode
You can also route the job to a specific printer in the Barr spooler by adding the printer name to your destination parameter. Enter the Barr node name, followed by a comma, and then the printer name. Because the DEST= parameter contains two parameters, you must use parenthesis as shown in the following example.
//SYSOUT DD SYSOUT=A,DEST=(barrnode,HPLASER)