Safeguard Management Programming Manual (G06.24+, H06.03+)

Elements of SPI Messages
Safeguard Management Programming Manual422086-012
4-6
Event Numbers
card character in either the subvolume or filename element of the filename, but the
characters will be treated as exact characters, not search characters.
The ZCOM-TKN-SUB must be used to indicate wild cards in a diskfile-pattern
filename are to be treated as search characters. This token cannot be used with
the ADD command.
A "*" must be used to begin filenames that are wild carded in the volume element
in order for the command to operate across all volumes that match the filename.
For example:
1. INFO *$DATA*.*.T* returns the three diskfile and three diskfile patterns:
$DATA2.JATER.TEST
$DATA2.J*.T*
$DATA1.JATER.TEST
$DATA1.JA???.TEST
$DATA.JATER.TEST
$DATA.JATE?.T*
2. INFO $DATA*.*.T* returns only two of the six protection records that you
might expect (There is no "*" specified prior to the filename.):
$DATA.JATER.TEST
$DATA.JATE?.T*
Event Numbers
Event numbers for event messages issued by the Safeguard subsystem are
represented by symbolic names in the form ZSFG-EVT-name, where name identifies
the event. For more information about the Safeguard event numbers and their
associated event messages, see Section 8, Event Management.
Subjects of Event Messages
The Safeguard subsystem reports events for the following objects:
SUBSYSTEM
PROCESS (event-exit process)
NULL
FILESET
LU
For Safeguard event numbers and their associated event messages, see Section 8,
Event Management.
Other Tokens
The Safeguard subsystem uses other tokens as command parameters, results in
responses, and elements of event messages and error lists.