DSM/SCM Event Management Programming Manual

Event Messages

DSM/SCM Event Management Programming Manual—529844-003

5-17

DSM/SCM Event Message Generation

DSM/SCM events are generated in response to DSM/SCM activities. Each time a

DSM/SCM activity starts, a sequence of messages is generated. All events for an

activity are identified by the activity-ID token (ZPHI-TKN-ACTIVITY-ID) in the header.

The messages in the sequence vary depending on whether an error occurs and

whether the activity stops or completes processing. The message sequence for an

activity is:

All activities have a 1020 or 1010 event associated with them to report current status:

stopped or completed.

DSM/SCM Event Message Classification

DSM/SCM events are assigned to error ranges, depending on whether they are events

of an informational nature, general events, events issued by a specific DSM/SCM

component, or internal events that primarily assist the developer or analyst in

debugging an internal error.

Within these error ranges, DSM/SCM events are also classified as informational

messages, errors, or warnings, and by the completion or stopped code with which they

are associated. Each message can be associated with more than one of these

categories. (See DSM/SCM Event Message Generation on page 5-17.)

Event Message Generated Reason

1005 ZPHI-EVT-ACT-STARTED An activity has been started.

nnnn ZPHI-EVT-nnnn An error occurred. This message defines the cause

of the error. (If no error occurs, no error message is

generated.)

1020 ZPHI-EVT-ACT-STOPPED The error caused the activity to stop processing.

This message returns the stopped code. (If the

activity completes processing despite the error, this

message is not returned.)

1010 ZPHI-ACT-COMPLETED The activity completed. This message returns the

completion code. (If the activity does not complete

processing, this message is not returned.)