Guardian Application Conversion Guide

Converting Distributed Systems Management (DSM) Applications
Converting Other Parts of an Application
096047 Tandem Computers Incorporated 8–31
Specifying Device Numbers and Names
Your DSM application might put a logical device number in an integer token such as
ZEMS-TKN-LDEV or in a token with token type ZSPI-TYP-INT or ZSPI-TYP-UINT.
A D-series logical device number requires 32 bits. Place a logical device number in the
ZEMS-TKN-LDEVNUMBER token or define another 32-bit token using a token type
such as ZSPI-TYP-INT2.
Place a device name in the ZEMS-TKN-XLDEVNAME token or define a variable-
length string token using a token type such as ZSPI-TYP-STRING.
Note Logical device numbers are often unreliable (for example, with Dynamic System Configuration).
Therefore, whenever possible, use a logical device name rather than a logical device number.
Converting Structured Tokens That Contain Obsolete Fields
Your DSM application might define a structured token that contains an obsolete field
(that is, a field that cannot hold the required information). For example, you might
define a structured token that contains an 8-bit field for a PIN value. If you convert
your application, consider the following choices for an obsolete field.
New Structured Token. Define a new structured token with a new field to replace the
obsolete field. If you include the old token in the event message, put data in the
obsolete field only if it is meaningful; otherwise, put a null value in the field.
If you cannot put either meaningful data or a null value in the obsolete field, omit the
old token from the buffer. If a DSM application tries to extract this missing token, it
will receive the missing-token error (ZSPI-ERR-MISTKN).
An extensible structured token cannot contain a variable-length field. Therefore,
define a separate variable-length token to hold an item such as a process descriptor.
Separate New Simple Tokens. Define a new simple token to replace the obsolete field.
For example, you can replace a process-ID field (token type ZSPI-TYP-CRTPID) with a
new simple process-descriptor token. Then, define either a new structured token or
new simple tokens for the remaining fields.