Guardian Application Conversion Guide

Converting Distributed Systems Management (DSM) Applications
Converting Other Parts of an Application
8–30 096047 Tandem Computers Incorporated
Specifying a File-System Error
Your DSM application might include an 8-bit token for a file-system error in an event
message. For example, you might define an error token using token type
ZSPI-TYP-BYTE.
Define file-system error-number tokens as integers using a token type such as
ZSPI-TYP-UINT.
Specifying Sequence Numbers
A sequence number is part of a process handle and of a process descriptor (unless it
has been removed) and usually does not need to be stored in a separate token.
However, if you define a separate token for a sequence number, use a fixed-point
number token with a token type such as ZSPI-TYP-INT4.
Specifying Process Handles and Process Descriptors
Your DSM application might include a process-ID token to identify a process in your
event message. For example, you might define a process-ID token using token type
ZSPI-TYP-CRTPID, ZSPI-TYP-FNAME, or ZSPI-TYP-FNAME32.
Convert your application to define a process-descriptor token or a process-handle
token (or both) to identify a process. Tandem recommends that you do not return a
synthetic process ID in an event message.
Define a process-descriptor token as a variable-length string using a token type such as
ZSPI-TYP-STRING. If you define a process-handle token, use a token type such as
ZSPI-TYP-PHANDLE.
Note Tandem recommends that you use a process-descriptor token because:
It is in external format, which makes it suitable to display or print.
It contains the node (system) and process name, if it exists. After a process pair terminates, you
cannot determine the process name from a process handle.