Two ways to shut down NRJE using MPE commands exist:
Stop NRJE using an NRJECONTROL STOP or NRJECONTROL HALT command from MPE.
Issue an SNACONTROL STOP command from MPE. This shuts down the SNA link and NRJE.
A STOPWS issued from within NRJE has the same effect as an NRJECONTROL STOP. A HALT issued from within NRJE has the same effect as an NRJECONTROL HALT. NRJECONTROL HALT and NRJECONTROL STOP as well as the and HALT commands are described in the SNA NRJE Node
Manager's Guide. SNACONTROL STOP is described in the SNA Link Services Reference
Manual or the SNA Link/XL Node Manager's
Guide.
Upon terminating communication with the host, NRJE will set NRJEJCW
in the job stream to indicate the reason for the termination. This
JCW can be used to determine whether to attempt to restart NRJE
in the job stream.
Possible values for
NRJEJCW: | Reason |
|---|
| 2 | | NRJE STOPWS workstation command |
| 4 | | NRJE HALT workstation command |
17 | | The LU is not active on
the host. |
| 1224 | | An unbind was received. |
3000 | | SNACONTROL STOP;type=Q command |
3001 | | SNACONTROL STOP;type=P command |
3003 | | Link failure was detected. |
3005 | | Hierarchical shutdown received. |
These JCW values may vary depending on the version of the
SNA link product installed on the system.
In general, all other values set upon termination are a result
of a potential error condition encountered.
Use of NRJEJCW |
 |
The following example can be used to restart NRJE after the
host system disconnects:
!JOB NRJE,MANAGER>>SYS/password,NRJE;OUTCLASS=,1
!RUN NRJEMON;INFO="wsid"
!IF NRJEJCW = 1224 OR NRJEJCW = 3005 THEN
! CONTINUE << Received unbind or hierarchical shutdown >>
! SNACONTROL START;NODE=nodename
! NRJECONTROL START;WSID=wsid
!ENDIF
!EOJ |
The example below includes SNACONTROL commands, which are the responsibility of the SNA node
manager and are described in the SNA Link Services Reference
Manual or the SNA Link/XL Node Manager's Guide.
In this example, the input entered by the NRJE manager is
shown in the first column, and instructions and explanations are
in the other columns.
Example
Issue a status command before the SNA node
is started.
:snacontrol status;node=ibmnode
NODE SPECIFIED NOT ACTIVE. (SNACIERR 9)
Start the SNA node.
:snacontrol start;node=ibmnode
SNA TRANSPORT VERSION: A.XX.XX
Enter the NRJE subsystem.
:nrje r20
product number version number NRJE (C) HEWLETT-PACKARD CO copyright year
WELCOME TO NRJE Issue DISPLAY INFO command.
R20>display;info
Workstation: R20
GENERAL INFORMATION
State: INACTIVE The workstation is INACTIVE
Jes: JES2 even though the SNA node has
Remote: RMT20 been started.Host command prefix char: $
Allowed console commands:
Formid lookup table: NRJETABL.NRJE
Default print form name: STD
Default punch form name: STD
WELCOME MESSAGE:
WELCOME TO NRJE
Issue STARTWS command. A job number is returned
identifying the file that has been streamed.
R20>startws
#J745
Immediately issue another DISPLAY INFO command.
R20>display;info
Workstation: R20
GENERAL INFORMATION
State: Mon Pending The state is now Monitor
Jes: JES2 Pending, a transient state.
Remote: RMT20 It will soon become ACTIVE.
Host command prefix char: $
Allowed console commands:
Formid lookup table: NRJETABL.NRJE
Default print form name: STD
Default punch form name: STD
WELCOME MESSAGE:
WELCOME TO NRJE
Issue another DISPLAY INFO command.
R20>display;info
Workstation: R20
GENERAL INFORMATION
State: ACTIVE The state is now ACTIVE.
Jes: JES2
Remote: RMT20
Host command prefix char: $
Allowed console commands:
Formid lookup table: NRJETABL.NRJE
Default print form name: STD
Default punch form name: STD
WELCOME MESSAGE:
WELCOME TO NRJE
R20>display lutable
WORKSTATION LU LIST
LU Name Chain Size LU Address Auto Start
LU01 * 99 1 YES
LU02 * 99 2 YES
LU03 * 99 3 YES
LU04 * 99 4 YES
LU05 99 0 NO
LU06 99 0 NO
LU07 99 0 NO
LU08 99 0 NO
* = The LU is active.
Now jobs that have been submitted are
transmitted. Data sets can be received.
Console commands can be sent.
Console messages can be received.
Identify the status of all sessions, PU-SSCP,
LU-SSCP, LU-LU.<F100P12D>
R20>:snacontrol status;node=ibmnode
SNACONTROL commands can be entered from your
configured NRJE prompt by preceding them with
colon ( : ).
For MPE V systems, the following displays:
PU - SSCP STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 1 - SSCP STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 1 - LU 1 STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 2 - SSCP STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 2 - LU 1 STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 3 - SSCP STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 3 - LU 1 STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 4 - SSCP STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 4 - LU 1 STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 5 - SSCP STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 6 - SSCP STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 7 - SSCP STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
LU 8 - SSCP STATE: ACTIVE TRACE OFF USER: MANAGER.SYS
For MPE XL systems, the following displays:
SESSION ID STATE TRACE USER
----------------------------------------------------
PU - SSCP SESS_ACTIVE OFF MANAGER.SYS
LU 1 - SSCP SESS_ACTIVE OFF MANAGER.SYS
LU 2 - SSCP SESS_ACTIVE OFF MANAGER.SYS
LU 3 - SSCP SESS_ACTIVE OFF MANAGER.SYS
LU 4 - SSCP SESS_ACTIVE OFF MANAGER.SYS
LU 5 - SSCP SESS_ACTIVE OFF MANAGER.SYS
LU 6 - SSCP SESS_ACTIVE OFF MANAGER.SYS
LU 7 - SSCP SESS_ACTIVE OFF MANAGER.SYS
LU 8 - SSCP SESS_ACTIVE OFF MANAGER.SYS
Stop the SNA node, and so all workstations,
in a quiescent manner.
R20>:snacontrol stop;node=ibmnode;type=q
Issue an SNACONTROL STATUS command after
the node is closed<F100P12D>.
R20>:snacontrol status;node=ibmnode
NODE SPECIFIED IS NOT ACTIVE. (SNAERR 11)
Issue another DISPLAY INFO command.
R20>display;info
Workstation: R20
GENERAL INFORMATION
State: INACTIVE Workstation is INACTIVE.
Jes: JES2
Remote RMT20
Host command prefix char: $
Allowed console commands:
Formid lookup table: NRJETABL.NRJE
Default print form name: STD
Default punch form name: STD
WELCOME MESSAGE:
WELCOME TO NRJE
R20>exit |
