Guardian Application Conversion Guide

Using Sequential I/O (SIO) Procedures
Converting Other Parts of an Application
8–18 096047 Tandem Computers Incorporated
Allocating FCBs Using the
INITIALIZER
The D-series INITIALIZER procedure supports creator processes that are running at a
high PIN. If your existing program calls the INITIALIZER only to read its STARTUP,
ASSIGN, or PARAM messages and not to set up its required FCBs, you do not need to
make any changes. However, if your program calls the INITIALIZER to allocate its
required FCBs, convert the program as follows.
Your existing program might call the INITIALIZER to allocate the run-unit control
block (CBS) and the common FCB using the ALLOCATE^CBS DEFINE. In this
example, ALLOCATE^CBS allocates a run-unit control block for three I/O files:
ALLOCATE^CBS (rucb, ! Run-unit control block.
common^fcb, ! Common FCB.
3); ! Number of files.
Convert your program to allocate the run-unit control block (CBS) and the common
FCB using the ALLOCATE^CBS^D00 DEFINE:
ALLOCATE^CBS^D00 (rucb, ! Run-unit control block.
common^fcb, ! Common FCB.
3); ! Number of files.
Your existing program might call the INITIALIZER to allocate an FCB for $RECEIVE:
ALLOCATE^FCB (rec^file,
"$RECEIVE ");
If you want your process to receive D-series system messages then you should use the
ALLOCATE^FCB^D00 DEFINE instead if the ALLOCATE^FCB DEFINE, otherwise
your process will receive C-series system messages:
ALLOCATE^FCB^D00 (rec^file,
"$RECEIVE ");
You do not need to change the DEFINE for other files. It does no harm to use
ALLOCATE^FCB^D00 for other files except to use additional space.