DSM/SCM Event Management Programming Manual

Introduction

DSM/SCM Event Management Programming Manual—529844-003

1-5

How EMS Handles DSM/SCM Event Messages

DSM/SCM components report informational, warning, and error event messages to

EMS in response to DSM/SCM batch activities. In addition, events generated by some

utilities are included within DSM/SCM events and are also reported to EMS.

DSM/SCM records these events in two EMS collectors:

•

DSM/SCM Alternate Collector ($ZPHI)

All DSM/SCM events are sent to this collector. The alternate collector stores

DSM/SCM event messages in a special log file. The alternate collector is

dedicated to DSM/SCM information and tracks the progress and status of requests

as well as determining whether any errors have occurred. You can view events

sent to this collector through the Planner Interface and the Target Interface. The

alternate collector for DSM/SCM is named $ZPHI.

•

Primary Collector ($0)

No DSM/SCM events are sent to the primary collector unless communication with

the alternate collector is unavailable. If the alternate collector is down, all event

messages are sent to the primary collector. The primary collector stores the

DSM/SCM event messages (along with event messages from other subsystems) in

a disk file called the event log file. The primary collector provides a central

collection point for all events from all subsystems in a system (or node). Each

system (or node) has only one primary event message collector, named $0.

Once the DSM/SCM events are collected in a log file, you can use one of these

distributors to retrieve them. (See Figure 1-2 on page 1-6.)

For detailed descriptions of each DSM/SCM event message, see Section 5, Event

Messages.