Controlling NJE lines

This describes the JES2 commands for controlling NJE lines. Many of the commands you issue to control NJE activity are used for controlling remote job entry (RJE) lines as well. For information about controlling the RJE environment, see the “Remote Job Entry” in “Controlling JES2 Devices and Functional Subsystems”. (For a discussion of the RJE and NJE facilities, see z/OS JES2 Initialization and Tuning Reference, SA32-0992.)

Starting a line: To start an NJE line for an SNA remote workstation, you must know how the system programmer defined your NJE network in the JES2 initialization procedure; that is, you must know which workstations can use which lines. Ask the system programmer for this information.
Issue the $S LINE(nnnn) command to start an NJE line. This activates a line to VTAM® for the SNA NJE station, allowing JES2 to begin processing logon requests from remote stations. Use the $S RMT(nnnn) command to cause a remote terminal to logon automatically if you have placed the terminal in automatic logon mode by previously issuing the $T RMT(nnnn) command. (For a description of controlling remote terminals, see “Remote Job Entry” in “Controlling JES2 Devices and Functional Subsystems”.)
Assigning a password to a line: Use the $T LINE(nnnn) command to assign or delete a password for a line. You must make a note of those passwords assigned because there is no facility for displaying the passwords in effect. Assigning and deleting passwords requires system authority. (Use the $T NODE(nnnn),AUTH= command to set node command authority.)
Diagnosing line problems: Use the $T LINE(nnnn) command when you suspect there is a problem on a line. For BSC lines, this command causes the system to issue a diagnostic message on the console with master level authority every time a channel end is detected on the specified line. For SNA lines, this command causes the system to issue a diagnostic message on the console with master level authority for each event detected on the specified line. This command requires system authority and should be used only at the direction of your system programmer. In addition, you can trace I/O activity on a line using this command.
Restarting line activity: Use the $E LINE(nnnn) command to stop the current activity on an NJE line. Any input currently being transmitted over the specified line will immediately stop, and the partial input will be purged. Any output being transmitted over the line will be placed on the hardcopy queue.
The NJE node or JES2 remote workstation currently signed on to the restarted line is disconnected. If the line status was active, new JES2 remote workstations can sign on to the line or it can be used for networking. If the line status was draining, it becomes drained and unusable for JES2 I/O until the operator starts it again. For an NJE line, $E LINE(nnnn) stops attempts to sign on to another node.

Note: If the line status remains draining because of an I/O device missing an interrupt, a second $E LINE(nnnn) command is required to restart the line.
Disconnecting a line: You can disconnect an NJE line immediately using the $T LINE(nnnn),DISCON=I command or when all data set communications over the line cease (DISCON=Q). When the line is disconnected immediately, a sign-off record is sent to a multi-leaving remote workstation or to the connected NJE node. When the line is disconnected after communications cease, the disconnection occurs as though the remote operator or NJE node had signed off.
Stopping a line: Use the $P LINE(nnnn) command to stop an NJE line. The specified line will not start any new activity and will stop upon completion of its current activity.