HPlogo SNA Link/iX Node Manager's Guide > Chapter 3 Logging Configuration

Chapter 3 Logging Configuration

MPE documents

Complete PDF
Table of Contents
Index

Table of Contents
Configuration File Validation
Configuring Logging
Main Screen
HP-IBM Configuration Screen
IBM Logging Configuration (1)
IBM Logging Configuration (2)
IBM Logging Configuration (3)
Enabling Users for a Specific Subsystem and Class
This chapter describes how to use the NMS configuration manager (NMMGR) to create or modify a configuration file for logging. Basic information about NMMGR is contained in Using the Node Management Services Utilities; if you are not familiar with NMMGR, you should read that manual before continuing. Note that the logging configuration is completely HP e3000 dependent and has no corresponding remote system configuration.

Once you have configured the SNA node, you must configure logging. Logging records events such as errors and console commands, and is configured according to subsystems. Within each subsystem, different classes of events (such as internal errors) exist. You specify where you want logging recorded for each of the classes in the subsystem: to a disk file, the HP e3000 console, or the logon device of a UserName.AccountName. If you configure a logging class so that logging is recorded to a UserName.AccountName, that user will receive logged messages any time that UserName.AccountName has an active session.

These topics are covered in this chapter:

  • Configuration file validation

  • Configuring logging

    • "Main" screen

    • "HP-IBM Configuration" screen

    • "IBM Logging Configuration (1)" screen

    • "IBM Logging Configuration (2)" screen

    • "IBM Logging Configuration (3)" screen

    • Enabling users for a specific subsystem and class

Table 3-1 "SNA Logging Configuration Guidelines" provides a summary of the logging classes for which configuration is described in this chapter, and guidelines for those configurations. For more information about logging, see Chapter 5 "SNA Link Troubleshooting" in this manual.

NOTE: If very high volumes of logging are recorded to the console or a set of users, system performance might degrade. So, the Hewlett-Packard recommended configuration should be followed unless you are advised otherwise by your Hewlett-Packard support contact.

Table 3-1 SNA Logging Configuration Guidelines

Subsystem

Class

Events

Console Logging

Disk Logging
SNA Transport (SUB0001)CLAS0010Node events*YESYES
CLAS0011Protocol errorsYESYES
CLAS0012LU-LU activitiesNOYES
CLAS0013LU-SSCP activitiesNO**YES
NRJE (SUB0002)CLAS0010Workstation eventsNONO
CLAS0012Critical events and errorsYESYES
CLAS0013Console commands and messagesNONO
APPC (SUB0016)CLAS0010Internal errorsYESYES
CLAS0011Subsystem warningsYESYES
CLAS0012Subsystem information messagesYESYES
CLAS0013Conversation information messagesYESYES
CLAS0014Session performance statisticsNOYES
Link trace (SUB0018)CLAS0000 Link trace starting and stopping errors. This does not include link errors.YESYES
DHCF (SUB0020)CLAS0010Serious and internal errorsYESYES
CLAS0011WarningsNONO
CLAS0012Informational messagesYESYES
CLAS0013Diagnostic messagesNOYES
SDLC Link (SUB0027)CLAS0010ErrorsNOYES
CLAS0012Informational messagesNOYES
SNADS (SUB0046)CLAS0010Serious and internal errorsYESYES
CLAS0011WarningsYESYES
CLAS0012Subsystem informationYESYES
Token Ring Link (SUB0061)CLAS0001ErrorsNOYES
CLAS0002WarningsNOYES
CLAS0003Informational messagesNOYES
(SUB0082)CLAS0001ErrorsYESYES
Sync MUXCLAS0002WarningsYESYES
LinkCLAS0003Connect statusYESYES
CLAS0004Informational messagesYESYES
*If you are using an X.25 link and you want logging information recorded, logging (console, disk, or both) for SNA Transport class CLAS0010 must be enabled, because the X.25 link uses the logging facilities for that SNA Transport class.
**If you are using a manual-dial modem, console logging for SNA Transport class CLAS0013 must be enabled, so that pertinent logging messages can be displayed.



Configuring the SNA Node and Link

Configuration File Validation