Votos - 0, Puntuación media: 0
(
)
)
|
Otros manuales para este modelo:
Computadoras - HP Integrity NonStop H-Series (16.73 mb)
Computadoras - HP Integrity NonStop H-Series (957.56 kb)
Computadoras - HP Integrity NonStop H-Series (881.66 kb)
Computadoras - HP Integrity NonStop H-Series (965.62 kb)
Computadoras - HP Integrity NonStop H-Series (676.93 kb)
Computadoras - HP Integrity NonStop H-Series (393.72 kb)
Computadoras - HP Integrity NonStop H-Series (776.57 kb)
Resumen del manual
SPI Programming Considerations for OSI/AS
Retrieving and Decoding Event Messages
Error Handling
Each response returned by OSI/AS includes a return token (ZSPI-TKN-RETCODE),
whose value indicates whether an error occurred when OSI/AS attempted to perform
the command. An error is a serious condition that prevents the command from being
completed. If the command completed with no errors, the value of the return token is
ZCOM-ERR-OK. If the command returns an empty response record—a response record
containing no information—the value of the return token is ZCOM-ERR-EMPT-RSP.
The latter situation occurs, for instance, when an application uses ZSPI-TKN-
RESPONSE-TYPE to request only response records for objects on which errors or
warnings occurred, but the command finishes processing without any errors or
warnings. If ZSPI-TKN-RETCODE has any value other than the two just mentioned,
this means that an error occurred. In this case, OSI/AS includes an error list in the
response, providing information about the error.
A warning reports a condition less serious than that of an error. If no errors occurred
but a warning did occur, the return token will have the value ZCOM-ERR-OK, but an
error list will appear in the response, providing information about the warning
condition.
General programming considerations for handling errors and warnings reported in
responses are discussed in the Communications Management Programming Manual.
Error handling considerations for specific commands are described along with those
commands in Section 5. Errors defined by the OSI/AS subsystem, together with the
contents of the error lists returned for them, are described in Appendix A. OSI/AS can
also return common data communications (ZCOM) errors; these errors and their error
lists are described in the Communications Management Programming Manual.
Security
OSI/AS commands are either sensitive or nonsensitive. Sensitive commands can change
the state or configuration of subsystem objects, start or stop tracing, or change the
values of statistics counters; nonsensitive commands cannot. SCP allows sensitive
commands to be issued only by members of the Guardian 90 super group or of the
Guardian 90 user group that owns the OSI manager process. Section 5 identifies each
OSI/AS command as sensitive or nonsensitive.
Retrieving and
The following is a summary of the steps your application must take to retrieve and act
Decoding Event
upon event messages:
Messages
1.
Declare a buffer of appropriate size for the Event Management Service (EMS)
GETEVENT command and its response. (For recommended sizes, see the “Event-
Management Considerations” subsection that follows.)
2.
Start an EMS consumer distributor and open it with the #ZSPI qualifier on the
process name.
3.
Format an EMS distributor CONTROL programmatic command to load a filter
you have written, and to specify the source and destination of event messages, if
desired. (The filter selects which event messages you wish your application to
process. Filters are discussed further at the end of this section.) Send the
CONTROL command to the consumer distributor using the mechanism
3–10
056785 Tandem Computers Incorporated
...Otros modelos de este manual:
Computadoras - HP Integrity NonStop J-Series (390.76 kb)
Computadoras - HP NonStop G-Series (390.76 kb)
Computadoras - HP NonStop L-Series (390.76 kb)