DSM/SCM Event Management Programming Manual

Event Messages

DSM/SCM Event Management Programming Manual—529844-003

5-23

DSM/SCM Event Message Header

DSM/SCM has its own EMS message header, in the format:

"<1> <2> <3>DSM/SCM: *<4>* Server Class <5> of PATHMON <6>

activity id <7>, activity code <8>, planner id <9>.<10>

in stage <11>:<*CR>"

where the tokens used to create this header are:

<1> = ZEMS-TKN-GENTIME, TIME ( "H2 : M2: S2" )

<2> = ZEMS-TKN-GENTIME,DATE ( "M2 D2 Y2" )

<3> = ZEMS-TKN-SENDERID

<4> = ZEMS-TKN-EVENTNUMBER

<5> = ZPHI-TKN-SVR-CLS-NM

<6> = ZPHI-TKN-INT-PMON-NM

<7> = ZPHI-TKN-ACTIVITY-ID

<8> = ZPHI-TKN-ACTIVITY-CD

<9> = ZPHI-TKN-PLANNER-ID.Z-GROUPNAME)

<10> = ZPHI-TKN-PLANNER-ID.Z-USERNAME

<11> = ZPHI-TKN-STAGE-CODE

Tokens associated with the standard EMS message header are in the EMS buffer but

are not written out by EMSTEXT to the DSM/SCM message. Instead, GENTIME time

and date information and process name (SENDERID) information associated with the

standard EMS header appears in the DSM/SCM message header.

Because the standard EMS tokens are still in the EMS buffer, management

applications can still access the set of tokens associated with the standard EMS

message header.

Other Subsystems That Use the DSM/SCM Message Header

Some utilities (BACKUP, DISKGEN, File Manager, SYSGEN, and Tape Reader) use a

DSM/SCM template that includes a SHARED_SSID statement specifying the

DSM/SCM subsystem ID, ZPHI-VAL -SSID. This lets these utilities share use of the

DSM/SCM message header and report their events to DSM/SCM.

The only difference from a standard DSM/SCM event is that the event number and the

event text are defined by the utility in their own subsystem DDL files. For descriptions

of the other subsystem events returned with the DSM/SCM message header, see

Section 6, Event Messages From Other Subsystems.