Guardian Application Conversion Guide

New Guardian Procedures
Conversion Concepts
2–2 096047 Tandem Computers Incorporated
Naming Conventions A D-series procedure name has an underscore (_) after each part, including the last
part. This convention allows you to give your own procedures names that do not
conflict with Tandem procedure names provided that you do not end your procedure
names with an underscore. A D-series procedure name follows one of these format
conventions:
[ module_ ] object_action_ [CHKPT _ ]
module_
is the module or subsystem that owns the object. Examples are MBCS_ and SPI_.
object _
is the object that the procedure acts upon. Examples are FILE_ , PROCESS_ , and
SEGMENT_.
action _
is the action that the procedure takes on the object. Examples are CREATE_ ,
STOP_ , and GETINFO_.
CHKPT_
specifies that the CHECKMONITOR procedure executes the procedure for the
backup process of a process pair. For example, a primary process calls
FILE_OPEN_CHKPT_ to open a file for its backup process.
type-1_ TO_ type-2_
type-1_ TO_ type-2_
specifies the conversion from type-1_ to type-2_ . Examples are
CRTPID_TO_PROCESSHANDLE_ and PROCESSHANDLE_TO_FILENAME_.
Parameter Conventions The D-series Guardian procedures use new input and output parameter conventions,
including:
Variable-length string parameters for file names, node names, and process
descriptors
20-byte process handles that you use to identify processes to process-control
procedures such as PROCESS_ACTIVATE_ and PROCESS_STOP_
The following paragraphs describe these new conventions.