EMS Manual

Standard Events
EMS Manual—426909-005
9-22
Common-Standard Tokens That Subsystems
Provide
Manager
Name
ZEMS-TKN-NAME-MANAGER (ZSPI-TYP-STRING,C)
Identifies the manager process for objects in the event subject. It must be in
\node.$process form.
If this token is present, it is the name of the process where commands can be
sent to inquire or control the object reported in the event subject.
If this token is not present:

If the event subject is a process name, the process name is the
\node.$process part of the event subject name.

If the event subject is not a process name, the location where commands
can be sent or the event subject names can be interpreted must be
documented by the subsystem. The location might be an external command
handler where commands for the subject can be sent or an external
directory service or algorithm that can be used to interpret the event subject
name.
For more details, see Underlying Philosophy of Standard Events
on page 9-10
and Object Name for Event Subject
on page 9-13.
In general, if this process name is the management interface that accepts SPI
commands, the management application must be openable by applications by
appending .#ZSPI to the process name. This process might be the process that
an application issuing a SPI command would actually open. For example, for
PATHWAY, the PATHMON process is both the process named in this token and
the process the management application would open. For EXPAND, the
application would open SCP (Subsystem Control Process), which then routes
the command to the manager process named in this token.
If more than one object is reported in the event subject, all objects must be
managed by the same manager process.
Event
Number
ZEMS-TKN-EVENTNUMBER (ZSPI-TYP-ENUM,U)
Identifies the event number of the event message. Enumerated values are
defined by the subsystem and should have this symbolic or literal name:
subsys-EVT-eventname
where subsys is the 4-character subsystem acronym assigned to this
subsystem (see ZSPI-TKN-SSID token above) and eventname provides
descriptive information for the event number. For example, ZSX1-EVT-PU-NOT-
READY is the symbolic event name for the PU not ready event in the SNAX/XF
subsystem.
An event number identifies the specific situation being reported. It must uniquely
identify the subject type and condition within the reporting subsystem or
application. The values are defined by the subsystem or application. For more
details, see Event Numbers
on page 9-12.