Guardian Procedure Calls Reference Manual

sync-or-receive-depth
input
INT:value
The purpose of this parameter depends on the type of device being opened:
specifies the number of nonretryable (that is, write) requests whose completion the file system must
remember. A value of 1 or greater must be specified to recover from a path failure occurring during
Disk file
a write operation. This value also implies the number of write operations the primary process in a
primary and backup process pair can perform to this file without intervening checkpoints to its backup
process. For disk files, this parameter is called sync depth. The maximum sync depth value is 15.
If omitted, or if 0 is specified, internal checkpointing does not occur. Disk path failures are not
automatically retried by the file system.
specifies the maximum number of incoming messages read by READUPDATE that the application
process is allowed to queue before corresponding REPLYs must be performed
$RECEIVE
file
If omitted, READUPDATE and REPLY to $RECEIVE are not permitted.
For $RECEIVE, this parameter is called receive-depth, and the maximum number of queued incoming
messages is 4047 in the H06.17/J06.06 and earlier RVUs. From H06.18/J06.07 RVU onwards,
the maximum receive-depth value has been increased from 4047 to 16300.
specifies whether or not an I/O operation is automatically redirected to the backup process if the
primary process or its processor module fails. For processes, this parameter is called sync depth. The
process
pair
maximum value is determined by the process. The value must be at least 1 for an I/O operation to a
remote process pair to recover from a network failure.
If this parameter >= 1, the server is expected to save or be able to regenerate that number of replies.
If this parameter = 0, and if an I/O operation cannot be performed to the primary process of a process
pair, an error indication is returned to the originator of the message. On a subsequent I/O operation,
the file system redirects the request to the backup process.
For other device types, the meaning of this parameter depends on whether the sync-ID
mechanism is supported by the device being opened. If the device does not support the sync-ID
mechanism, 0 is used regardless of what you specify (this is the most common case). If the
device supports the sync-ID mechanism, specifying a nonzero value causes the results of that
number of operations to be saved; in case of failures, the operations can be retried if necessary.
The actual value being used can be obtained by a call to FILE_GETINFOLIST_ or FILEINFO.
primary-filenum
input
INT:value
is the file number returned to the primary process when it opened this file. primary-filenum
must be passed as -filenum.
primary-filenum and primary-process-id are supplied only if the open is by the
backup process of a process pair, the file is currently open by the primary process, and the
checkpointing facility is not used. Both parameters must be supplied.
A negative file number indicates that the same file number must be returned in the backup as
was returned in the primary. If a negative file number is specified and the file number is already
open by the backup process, OPEN returns file-system error 12. In this situation, a process
pair would indicate externally that error 12 (file in use) exists when, in fact, the file is not in
use by the normal definition (open by another process in exclusive mode).
primary-process-id
input
INT:ref:4
is an array that contains the four-word process-id of the corresponding primary process.
OPEN Procedure (Superseded by FILE_OPEN_ Procedure) 899