HP 3000 Manuals HP 3000 Manuals
The Logging Facility
Logging records subsystem events--significant normal events, as well as
error events--for use in problem determination. SNA NRJE logging is
configured through NMMGR (see the SNA Link Services Reference Manual [for
MPE V] or the SNA Link/XL Node Manager's Guide [for MPE XL]), and it is
controlled through the MPE commands SHOWNMLOG, SWITCHNMLOG, and
RESUMENMLOG. These commands enable the node manager to determine the name
of the current log file and the amount of available space in it, close
the current log file and open a new one, and activate logging after a
recoverable error. The MPE commands are described in the SNA Link
Services Reference Manual and in the SNA Link/XL Node Manager's Guide.
SNA NRJE logging records NRJE events, errors, and host job entry
subsystem messages.
When you configure logging, you indicate the level you want logging
configured for by specifying the level's subsystem number. Then, within
each subsystem, you can indicate which events you want logged, by
specifying event class numbers.
The subsystem number for SNA NRJE is SUB0002, and the class numbers are
as follows:
* CLAS0010--workstation events.
* Job transmission.
* Job output reception (including Peripheral Device Information
Records [PDIRs]).
* Noncritical errors.
* CLAS0012--critical events and errors.
* Critical errors.
* LU startup.
* LU shutdown.
* CLAS0013--JES2, JES3, and VSE/POWER console commands and messages.
CLAS0012 logging (at least to disc) should always be on.
Example
An example of SNA NRJE console logging (logging displayed on the HP 3000
console) is shown below. In this example, the user followed the logging
configuration guidelines in the SNA Link Services Reference Manual or the
SNA Link/XL Node Manager's Guide, and turned on logging for SNA NRJE
class CLAS0012.
Note that JES2 is NAU 1 at the host (shown as Remote NAU = 1).
_______________________________________________________________________________________
| |
| SNA/TRANSPORT Logging For SNA NRJE, the user issues an |
| Session Started on node PU3000E NRJECONTROL START command. SNA |
| Local NAU = 3, Remote NAU = 1 NRJE LU-LU sessions are started on LUs 1-4.|
| The remote LU is JES2. Note that the |
| sessions need not be started in order |
| according to the NAUs. |
| |
| SNA/TRANSPORT Logging |
| Session started on node PU3000E |
| Local NAU = 2 , Remote NAU = 1 |
| |
| SNA/TRANSPORT Logging |
| Local NAU = 1 , Remote NAU = 1 |
| |
| SNA/TRANSPORT Logging |
| Session started on node PU3000E |
| Local NAU = 4 , Remote NAU = 1 |
| |
| NRJE Logging LU sessions are active with JES2. |
| THU, MAR 1, 1984, 10:42 AM |
| NRJE (R20 ;LU03 ) - LU ACTIVATION COMPLETED. (SC=1226) |
| |
| NRJE Logging |
| NRJE (R20 ;LU02 ) - LU ACTIVATION COMPLETED. (SC=1226) |
| |
| NRJE Logging |
| NRJE (R20 ;LU01 ) - LU ACTIVATION COMPLETED. (SC=1226) |
| |
| NRJE Logging |
| NRJE (R20 ;LU04 ) - LU ACTIVATION COMPLETED. (SC=1226) |
_______________________________________________________________________________________
Figure 5-1. Console Logging Example
After SNA NRJE-to-host activity, the user issues an NRJECONTROL STOP
command. SNA NRJE sends a TERM-SELF to the host for each LU (class) with
an LU-LU session. For each TERM-SELF received, the host sends an UNBIND
to SNA NRJE. SNA NRJE logs receipt of the UNBIND, SNA Transport logs
LU-LU session termination as SNA NRJE sends positive responses to the
UNBINDS, and SNA NRJE logs LU termination.
______________________________________________________________________________
| |
| NRJE Logging SNA NRJE receives UNBIND |
| THU, MAR 1, 1984, 11:11 AM for LU01. |
| NRJE (R20 ;LU01 ) - RECEIVED UNBIND= 3201 (SC=1224) |
| |
| |
| SNA/TRANSPORT Logging SNA Transport logs session |
| Session terminated on node PU3000E termination. |
| Local NAU = 1 , Remote NAU = 100 |
| |
| |
| NRJE Logging SNA NRJE receives UNBIND |
| THU, MAR 1, 1984, 11:11 AM for LU04. |
| NRJE (R20 ;LU04 ) - RECEIVED UNBIND= 3201 (SC=1224) |
| |
| |
| SNA/TRANSPORT Logging SNA Transport logs session |
| Session terminated on node PU3000E termination. |
| Local NAU = 4 , Remote NAU = 1 |
| |
| |
| NRJE Logging SNA NRJE logs LU (class) |
| THU, MAR 1, 1984, 11:11 AM termination. |
| NRJE (R20 ;LU01 ) - TERMINATED. (LU=1121) |
| |
| |
| NRJE Logging SNA NRJE logs LU (class) |
| THU, MAR 1, 1984, 11:11 AM termination. |
| NRJE (R20 ;LU04 ) - TERMINATED. (LU=1121) |
______________________________________________________________________________
Figure 5-1. Console Logging Example (cont.)
______________________________________________________________________________
| |
| NRJE Logging SNA NRJE receives UNBIND for |
| THU, MAR 1, 1984, 11:11 AM LU02. |
| NRJE (R20 ;LU02 ) - RECEIVED UNBIND= 3201 (SC=1224) |
| |
| |
| SNA/TRANSPORT Logging SNA Transport logs session |
| Session terminated on node PU3000E termination. |
| Local NAU = 2 , Remote NAU = 1 |
| |
| |
| NRJE Logging SNA NRJE receives UNBIND for |
| THU, MAR 1, 1984, 11:11 AM LU03. |
| NRJE (R20 ;LU03 ) - RECEIVED UNBIND= 3201 (SC=1224) |
| |
| |
| SNA/TRANSPORT Logging SNA Transport logs session |
| Session terminated on node PU3000E termination. |
| Local NAU = 3 , Remote NAU = 1 |
| |
| |
| NRJE Logging SNA NRJE logs LU (class) |
| THU, MAR 1, 1984, 11:11 AM termination. |
| NRJE (R20 ;LU02 ) - TERMINATED. (LU=1121) |
| |
| |
| NRJE Logging SNA NRJE logs LU (class) |
| THU, MAR 1, 1984, 11:11 AM termination. |
| NRJE (R20 ;LU03 ) - TERMINATED. (LU=1121) |
______________________________________________________________________________
Figure 5-1. Console Logging Example (cont.)