Log Files

Event Log

The event log is used to record information and error messages generated by the session manager. It is a useful record of events should problems occur. It can be viewed using standard host utilities (for example, vi or pg on UNIX, or Notepad or Wordpad on Windows).

The location of the event log depends on your host system:

All event log messages contain the following information:

A typical information message appears as follows:

SM> Thu, 15 Jan 1999  16:28:24  ---Warning---
Thread :Server Thread (183), Function: SmServerThread::ThreadProcess
Server timed out
System = Bobdbase, User = bob, Account = BOB
Server = ROSFS, Flags = 0, Timeout = 60

A typical error message appears as follows:

SM> Thu, 18 Dec 1997  14:54:50  ***Exception***
Thread :ClientIn thread (1), Function: SmTcpLink::RawSend, API error in send
[10053] Software caused connection abort

Event Log Size

The size of the event log is limited, by default, to 1MB. When the Session Manager starts, if the event log exceeds this value, it is copied to the file Old_Event.Log. The default maximum size of the event log can be changed by modifying session manager options - for details see Changing the Session Manager Parameters (UNIX) or smanager Options (Windows).

Note

You will need to stop and restart the session manager for any changes to take effect.

Session Log

The session log is used by the session manager to record every incoming and outgoing connection processed. It can be viewed using standard host utilities (for example, vi or pg on UNIX, or Notepad or Wordpad on Windows).

The location of the event log depends on your host system:

There are three types of session message: initialisation, connection and disconnection.

Initialisation Messages

An initialisation message is generated each time smanager is started:

Session Manager Started  Mon, 15 Dec 1997  11:55:47

Connection Messages

The information shown in a connection message depends on the type of connection: DDA, telnet or NET-LOGON.

Note

NET-LOGON messages are generated when you use the Reality NET-LOGON command, and when you use START-DESPOOLER (or START-PRINTER) to start a PTR formqueue. Refer to User's Reference: Operation, for more details.

For DDA connections the message contains the following information:

Note

For security reasons, the user, account and server passwords are not displayed.

The following shows typical incoming connection messages:

Session :4  Mon, 15 Dec 1997  12:02:59  IC
System :, User Id :, Account :, Server :
Client Id :, PLId :INET-98.72.0C.20-1
Class :Terminal, Flags :0, Timeout 2
Session :12 Tue, 16 Dec 1997 15:32:47 IC
System :Bobdbase, User Id :bob, Account :BOB, Server :ROSFS
Client Id :xmp1tcp*bob, PLId :UNIX-200077-ttya0
Class :Process, Flags :0, Timeout 1

For character circuit, telnet LBS and NET-LOGON connections the session log messages contain only the session id, date, connection type and PLId. However, the connection type field includes a description of the type of connection: that is telnet_lbs, or Net-Logon.

The following show typical telnet LBS and NET-LOGON messages:

Session :1  Mon, 15 Dec 1997  13:59:35  IC telnet_lbs
PLId :INET-152.114.12.32-0001
Session :1 Tue, 13 Jan 1999 10:49:54 Net-logon
PLId :UNET-200001-Bobdbase

Disconnection Messages

When the session ends, one of the following messages is written to the session log:

Sessid:20    Mon Apr 22 15:32:23 1996, Session Terminated Normally
Sessid:20 Mon Apr 22 15:32:23 1996, Session Terminated by Death of Process
Sessid:20 Mon Apr 22 15:32:23 1996, Session Terminated by Client Timeout
Sessid:20 Mon Apr 22 15:32:23 1996, Session Terminated by Server Rejection

Note

  • The Session Terminated Normally  message indicates that a client or server process has issued a disconnect and the session has terminated in an orderly fashion. The reason for the disconnect, however, may be due to an application level error.

  • The Session Terminated by Server Rejection  message is accompanied by a text message describing the reason for server rejection.

Session Log Size

The size of the session log is limited, by default, to 1MB. When it exceeds this limit, it is copied to the file Old_Session.Log. The default maximum size of the session log can be changed by modifying the session manager options - for details see Changing the Session Manager Parameters (UNIX) or smanager Options (Windows).

Note

You will need to stop and restart the session manager for any changes to take effect.