Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (H-K)
Guardian Procedure Calls Reference Manual—522629-013
7-43
INITIALIZER Procedure
num^fcbs input
INT:value
specifies the number of FCBs passed in the
fcb^array parameter. This
parameter is required for native mode processes that require FCB processing by
INITIALIZER. It is optional for TNS processes.
fcb^array input
WADDR:ref:*
is an array of addresses, each of which points to an FCB to be modified by
INITIALIZER. This parameter is required for native mode processes that require
FCB processing by INITIALIZER. It is optional for TNS processes.
Considerations
•
$RECEIVE and the INITIALIZER procedure
The INITIALIZER procedure provides a way of receiving startup, assign, and
param messages without concern for details of the $RECEIVE protocol. (Refer to
the
Guardian Programmer’s Guide for information about $RECEIVE.)
INITIALIZER opens and obtains messages from $RECEIVE; calls the user-
supplied procedure, passing the messages as a parameter to the procedure; and
closes $RECEIVE.
The INITIALIZER procedure waits on $RECEIVE for the amount of time specified
by the
timelimit parameter. If a startup message is not received within that
time, or if any other error is detected on $RECEIVE, INITIALIZER calls ABEND.
Except in rare cases, the default
timelimit value (60 seconds) is appropriate
and should be used.
•
Sequential I/O (SIO) procedures and FCBs
If the
rucb parameter is supplied, INITIALIZER modifies FCBs based on the
information supplied by the startup and assign messages. These FCBs are in the
form expected by the sequential I/O procedures and can be used with the SIO
procedures without change. If the application does not use the SIO procedures to
access the files, but needs to use them to get startup information, the information
recovered from the assign messages can be obtained from the FCBs by using the
CHECK^FILE procedure. Refer to the
Guardian Programmer’s Guide for
additional about SIO procedures.