Appendix D. SP-AMS Log

The log SP-AMS applies only to SP-AMS. CP-AMS uses the host log of the OS 2200 partition associated with the console for which CP-AMS is providing automation.

SP-AMS Log Contents

The files in the log SP-AMS contain the following types of messages:

Error
Trace
Debug
Warning
Database activation
Database deactivation
Database reactivation

To convey trace and debug information, SP-AMS groups a number of related messages together. The generation of trace and debug messages can be controlled individually for each system using Operations Sentinel Console.

Error Messages

If an error is returned while processing an action in trace or debug mode, the error and resulting messages are added to the current day's SP-AMS log file.

If an error is returned while processing an action in normal mode, SP-AMS automatically generates a complete set of trace messages, including the system message, the database name, group name and number of the pattern, error message, action text, and result of the action.

If an error is returned while processing an action, the action portion of the logged message is preceded by an error message of the form

Error error-#: error-message-text

The action text appearing when an error occurs is the text as specified in the database. This action message is followed by

------------> resulting action

Errors associated with conditional logic actions and actions on variables provide information in addition to the message format just described for error messages. The additional information is in the following format:

Error at operand "operand"

where operand is the operand that is in error.

Errors associated with delayed actions (actions specified with a WAIT clause) provide information in addition to the message format just described for error messages. The additional information is in one of the following formats:

Action delay is nn seconds
Action delay is nn minutes

where nn is the number of seconds or minutes the action was delayed.

Trace Messages

Trace messages are preceded by the system name, the message type TR, the time the message was logged, and the time the message was generated by the host. Trace messages display information about a message matching a pattern and the actions performed by SP-AMS in response to that pattern match.

Trace messages contain

The text of the system message that matched a pattern in the SP-AMS database
The database name, group name, and number of the pattern that matched the message, and the total number of tokens in the message text
Each action and its associated text

Note: Action text for a PASSWORD action is always blank.

Debug Messages

Debug messages are preceded by the system name, the message type DB, the time the message was logged, and the time the message was generated by the host. Debug messages display information about a message matching a pattern and the actions that SP-AMS would have executed in response to that pattern match.

Debug messages contain

The text of the system message that matched a pattern in the SP-AMS database
The database name, group name, and number of the pattern that matched the message
Each autoaction and its associated text

Format of Trace and Debug Information in SP-AMS Log Files

The format of trace and debug information is

Message text : message-text

Match        : database= database-name 
               group= group-name number= pattern#

		  tokens= total-tokens

<level>action-type : action-text

where:

message-text

is the first 80 characters of the message text that the pattern matched.

database-name

is the name of the database that contains the pattern that matched.

group-name

is the group name of the matching pattern.

pattern#

is the number of the matching pattern within its group.

total-tokens

is the total number of tokens in the message text.

level

is the level of conditional nesting. This part of the message appears only for actions specified with conditional logic.

action-type

is the name of the action.

action-text

is the text of the action.

Trace and debug information for delayed actions (specified with a WAIT clause) are provided in addition to the trace and debug information just described. The additional information is in one of the following formats:

Action delayed nn seconds, action queued.
Action delayed nn minutes, action queued.

where nn is the number of seconds or minutes that the action is delayed.

Database Activation

Database activation messages are placed in the current day's SP-AMS log file when a database is activated. These messages are written in any mode (normal, trace, or debug).

The format for this type of message is

I0002: Database name activated by reason.

This is an example of this message:

I0002: Database SPD-Driver activated by Single Point AMS initialization.

Database Deactivation

Database deactivation messages (see Section 7) are placed in the current day's SP-AMS log file when trace and debug are off.

The format for this type of message is

I0004: Database name deactivated by reason.

This is an example of this message:

I0004: Database SPD-Driver deactivated by operator.

SP-AMS Log File Message Examples

In the following example, the database prod1 was activated when the message "Switch to SP-AMS database prod1" matched pattern 1 in group activate in the database named test:

Message text:  Switch to SP-AMS database prod1
Match       :  Database= test  Group= "activate"  Number=1 Tokens= 5
ACTIVATE    :  prod

In the following example, an action error occurred and the message "Switch to SP-AMS database shift#1" matched pattern 1 in group activate in the database named test. After token 5 (\5\ = shift#1) was substituted into the action, action verification determined that the result was not a valid database name. SP-AMS did not activate a new database in this case.

Message text:  Switch to SP-AMS database shift#1
Match       :  Database= test  Group= "activate"  Number=1 Tokens= 5
Error E0002 :  Text "shift#1" is an invalid database name.
ACTIVATE    :  \5\
------------> shift#1

Database Reactivation

The database reactivation messages are written to the log file at the start and end of the reactivate request.

The following message is logged when SP-AMS starts processing the database reactivate request.

Reactivate request for database <database name> by <computer name>.<user name> (<process id>).

where:

<database name>

is the name of database to reactivate.

<computer name>

is the name of system where request was sent from.

<user name>

is the name of the user that initiated the request.

<process id>

is the process identifier of RADB.

The following message is logged when the SP-AMS has successfully completed the reactivate request.

Reactivate request completed successfully.

The following message is logged when the database name specified by the reactivate request is not the active database. This message is also logged when no database is active.

Reactivate request ignored because database <database name> is not the
active database.

The following message is logged when an error occurred while activating the database.

Reactivate request completed with errors.

The following message is logged when a request for deactivating the database is made by Reactivate AMS Database utility.

MI002 : Deactivating <database name> requested by Reactivate AMS
Database utility.

Examples

Reactivate request for database 'spstart' by mycomputer.myuser (14196).

I0002 : Database spstart activated by Reactivate AMS Database
utility.

Reactivate request completed successfully.