OSI/AS Management Programming Manual

Message Elements for the OSI/AS Subsystem
SPI Programming Considerations for OSI/AS
3–6 056785 Tandem Computers Incorporated
Table 3-1. Wild-Card Support for OSI/AS Programmatic Commands (Page 2 of 2)
For This Wild-Card Character...
This Command... Supports Wild-Cards for This Object-Type... ? *
INFO ENTRY OSI manager entry-name XX
INFO PROCESS NSP indirect-process-name ,
TSP indirect-process-name , or
TAPS indirect-process-name
XX
INFO PROFILE OSI manager profile-name XX
INFO SERVICE TAPS service-name , or
OSI manager service-name
XX
LISTOPENS SU TAPS su-name XX
LISTOBJECTS ENTRY OSI manager entry-name X
LISTOBJECTS PROCESS NSP indirect-process-name ,
TSP indirect-process-name , or
TAPS indirect-process-name
X
LISTOBJECTS PROFILE OSI manager profile-name
LISTOBJECTS SERVICE TAPS service-name , or
OSI manager service-name
X
LISTOBJECTS SU TAPS su-name X
RESETSTATS SERVICE TAPS service-name XX
RESETSTATS SU TAPS su-name XX
START PROCESS TSP indirect-process-name or
TAPS indirect-process-name
XX
STATISTICS SERVICE TAPS service-name XX
STATISTICS SU TAPS su-name XX
STATUS PROCESS NSP indirect-process-name ,
TSP indirect-process-nam e, or
TAPS indirect-process-name
XX
STATUS SU TAPS su-name XX
STATUS SU TAPS su-name XX
STOP PROCESS TSP indirect-process-name or
TAPS indirect-process-name
XX
STOP SU TAPS su-name XX
SUSPEND PROCESS TSP indirect-process-name or
TAPS indirect-process-name
XX
How wild cards are supported for each object type is described in Section 4.
Event Numbers All event messages contain a header token identifying the event by number. This event
number, in combination with the subsystem ID header token, uniquely identifies the
kind of event being reported. Event numbers for event messages defined by OSI/AS
are identified in programs by symbolic names of the form ZOSI-EVT- name , where
name gives a brief verbal identification of the event being reported.