SNA Link/iX Node Managers Guide (30291-90507)

Chapter 5 117
SNA Link Troubleshooting
The Logging Facility
— Bad port messages
• CLAS0012: LU-LU activities
— OpenUser/CloseUser
— Session activation/Session deactivation
• CLAS0013: LU-SSCP activities
— OpenUser/CloseUser
— Session activation/Session deactivation
Link-level Logging
Four types of link-level logging are available: SDLC link logging, X.25
link logging, Token Ring link logging, and link trace logging.
SDLC Link Logging
SDLC link logging records informational messages and error messages
generated by the SDLC link. It is controlled through the MPE
commands SHOWNMLOG, SWITCHNMLOG, and RESUMENMLOG. These
commands enable the node manager to determine the number of and
available space in the current NM log file (NMLG
nnnn .PUB.SYS, where
nnnn is a number from 0000 through 9999), close the current NM log
file and open a new one, and activate logging after a recoverable error.
The MPE commands are described in Chapter 6 , “MPE Commands,” of
this manual.
The NM log file can be formatted through the NMDUMP utility. Using
NMDUMP for the SDLC link (including an example of the SDLC link
logging format) is described later in this chapter. More-detailed
information about NMDUMP is contained in Using the Node
Management Services Utilities.
The logging subsystem number for SDLC link is SUB0027, and these are
the class numbers:
• CLAS0010: errors
• CLAS0012: informational messages
X.25 Link Logging
X.25 link logging records logging information generated by the X.25
link. Note that the X.25 link uses the logging facilities of SNA
Transport. So, it does not have a separate logging subsystem number. If
you are using an X.25 link and you want logging information recorded,
logging (console, disk, or both) for SNA Transport (subsystem
var|SUB0001|) class CLAS0010 must be enabled (see “SNA Transport
Logging” earlier in this chapter).