Guardian Procedure Calls Reference Manual

timelimit
input
INT(32):value
specifies how long INITIALIZER is to wait on $RECEIVE, as follows:
timelimit specifies the maximum amount of time (in units of 0.01 second) that INITIALIZER is to wait
on $RECEIVE.
>= 0D
DINITIALIZER is to wait indefinitely.= -1
DINITIALIZER calls ABEND.< -1
If this parameter is omitted, the default value 6000D (60 seconds) is used.
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.
Returned Value
INT
One of these status values:
This is a primary process (of a potential process pair).0
This is a backup process, CHECKMONITOR returned (indicating that the primary failed before establishing
a takeover point), and bit 12 of flags is 1.
-1
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. (For information about $RECEIVE, see
the Guardian Programmer's Guide.) 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
728 Guardian Procedure Calls (H-K)