SNAP-IX TN3270 Administrator's Guide - 4.3 Format of Log Messages

4.3 Format of Log Messages

This section explains the information given in the log file for each message. The following example shows a typical log message with notes on the information shown on each line:

Log Message Sample

------------------12:17:28 GMT  11 Nov 1996 -----------------  
Timestamp
3270     Message 0-26, Subcode: 0                              
Component, Message #, Subcode
Log category: PROBLEM   Cause Type: Config                     
Log category, Cause type
System: tnbox                                                  
System name
Process ID: 12345 (tn3270)                                
Process ID and name


There are no sessions configured for 3270 user abc.            
Message text, including parameters


Cause:  The user has tried to start the 3270 emulation         
Message cause
program, but no sessions are configured for this user in the
configuration file.
Action: If this user is to be permitted to use the 3270        
Message action
emulation program, at least one session must be configured
for the user.

Each message contains the following information:

Timestamp

The time and date the message was logged.

Component

The SNAP-IX TN3270 component that logged the message. The value

indicates that the TN3270 emulation program logged the message.

Message number

An identifier for the message.

Subcode

A unique identifier that indicates the point within SNAP-IX TN3270 at which the message was logged. This subcode is used only by support personnel.

Log category

The event category of the log message. Possible values are Problem, Exception, or Audit events.

Cause type

A summary of the cause of the message. Possible values are:

Internal: Internal error in the SNAP-IX TN3270 software. Report errors of this type to your SNAP-IX TN3270 support personnel.
System limit: An internal limiting value in the SNAP-IX TN3270 software.
External: A cause external to SNAP-IX TN3270.
Resource: Resource shortage (for example, insufficient memory on the Solaris computer).
User: User error (for example, the user has entered invalid parameters on the TN3270 emulation program command line).
SNA: SNA protocol violation by the host system, or interoperability problem with the host system's SNA implementation.
Config: Error in the SNAP-IX TN3270 configuration, or mismatch between the SNAP-IX TN3270 configuration and the host system.
Audit: A normal event, reported for information only.

System name

The name of the computer where the condition that caused the message was detected.

Process ID and name

The Solaris process ID and executable name of the process that logged the message.

Message text

Text describing the condition being logged. This field may include a number of variable parameters relating to this particular occurrence of the message. For example, a message reporting failure to start a TN3270 session may include the TN3270 user name and the session number.

Message cause

Additional information about the cause of the condition being logged. This field may not be included if the message text contains all the required information. This field is generally not used when the cause type specifies Internal.

Message action

Recommended action as a result of the message. For more information, see Recommended Actions for Log Messages. For audit messages, which provide accounting and progress information instead of reporting error conditions, this field is not included because no action is required.