Guardian Application Conversion Guide

Converting Distributed Systems Management (DSM) Applications
Converting Other Parts of an Application
096047 Tandem Computers Incorporated 8–23
Converting Distributed
Systems Management
(DSM) Applications
This subsection describes how to convert Distributed Systems Management (DSM)
applications that:
Use the Event Management Service (EMS) to receive and interpret event messages
from a Tandem subsystem
Use EMS to generate and report event messages
Use the Subsystem Programmatic Interface (SPI) to communicate with a Tandem
subsystem
Note Except for the examples in TAL, the symbolic names in this subsection are in DDL (or COBOL85) format
with hyphens (-) as separators. If you are writing a TAL program, substitute a circumflex (^) for each
hyphen. If you are writing a C or Pascal program, substitute an underscore (_) for each hyphen.
Using the DSM Definition
Files
If you are converting a DSM application, make sure that it copies D-series versions of
the appropriate DSM definition files that are required for the source language you are
using (TAL = TAL, COB = COBOL85, C = C, PAS = Pascal):
SPI definitions ZSPITAL, ZSPICOB, ZSPIC, or ZSPIPAS
EMS definitions ZEMSTAL, ZEMSCOB, ZEMSC, or ZEMSPAS
Data communications definitions ZCOMTAL, ZCOMCOB, ZCOMC,
or ZCOMPAS
Subsystem definitions ZsssTAL, ZsssCOB, ZsssC, or ZsssPAS (where
sss is the specific subsystem abbreviation)
Receiving and Interpreting
Event Messages
This subsection describes how to convert a DSM application that receives and
interprets event messages from a Tandem subsystem.
If you are converting an application, you also need to refer to the Tandem subsystem
manual that describes the specific event messages that your application receives from
the subsystem. For example, if your application receives event messages generated by
the labeled-tape server ($ZSVR), refer to the Tandem NonStop Kernel Event Management
Programming Manual for a description of the labeled-tape event messages and the
tokens in each message.
You might need to convert a DSM application if it receives event messages from a
converted subsystem on a D-series system. The converted subsystem can generate
event messages that contain D-series tokens, which are unknown to an unconverted
application.
For example, suppose an unconverted application tries to extract the process-ID token,
ZEMS-TKN-CRTPID, from an event message generated by a converted subsystem. If
the event message describes a high-PIN process, the converted subsystem substitutes
the process-descriptor token, ZEMS-TKN-PROC-DESC, for the process-ID token.
Thus, the unconverted application does not find a process-ID token and does not try to
extract the process-descriptor token.