HP-UX SNAplus2 R7 Administration Guide

Basic Conﬁguration Tasks

Conﬁguring Logging

When you deﬁne the control point, SNAplus2 automatically deﬁnes a local LU with the same name. That

LU can act as a default local LU for the node.

Control point alias

Local alias for the default local LU. Supply this value if the default local LU is used by independent LU 6.2

LUs.

Node ID

Identiﬁer for the PU on the local node. Supply a value only if the node will be used for dependent traf

ﬁc

using the default (control point) LU.

4.2.2 Additional Conﬁguration

After conﬁguring the node, continue with the following conﬁguration tasks:

• Conﬁgure connectivity as described in Chapter 5, Deﬁning Connectivity Components.

• Conﬁgure node resources (LUs) as described in Chapter 7, Conﬁguring APPC Communication or Chapter 8,

Conﬁguring User Applications.

• Conﬁgure applications as described in Chapter 8, Conﬁguring User Applications.

4.3 Conﬁguring Logging

SNAplus2 writes log messages describing abnormal events (and, optionally, normal events) to log ﬁles. When you

try to diagnose a problem, the ﬁrst place to look is in the log ﬁles, because the log messages provide information

about the cause of the problem and the action you should take.

SNAplus2 logs messages for the following categories of event:

Problem

An abnormal event that degrades the system in a way perceptible to a user (such as abnormal termination of

a session).

Exception

An abnormal event that degrades the system but that is not immediately perceptible to a user (such as a

resource shortage), or an event that does not degrade the system but may indicate the cause of later exceptions

or problems (such as receiving an unexpected message from the remote system).

Audit

A normal event (such as starting a session).

SNAplus2 also maintains a usage log ﬁle, which is used to record information about the current and peak usage of

SNAplus2 resources.

To distinguish between logs relating to normal and error conditions, the different message categories are logged to

different ﬁles. Problem and exception messages are logged to the error log ﬁle; audit messages are logged to the

audit log ﬁle.

SNAplus2 provides a backup mechanism to prevent log ﬁles from becoming too large and consuming disk resources.

When a log ﬁle reaches the maximum permitted size, SNAplus2 copies its current contents to a backup ﬁle and

then clears the log ﬁle.

By default, SNAplus2 uses the following log ﬁles:

Error log ﬁle