Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (H-K)
Guardian Procedure Calls Reference Manual—522629-013
7-39
INITIALIZEEDIT Procedure
Nowait Considerations
IOEdit always returns to the caller with the operation finished. In this sense, it does not
perform nowait I/O. Note that for write operations, the operation is considered finished
when the data is in the IOEdit buffer and might not yet have been passed to the file
system. The
nowait-option parameter controls how this buffering is done.
•
If nowait-option is set to 0 or is left unspecified, and nowait I/O was specified
when the file was opened, IOEdit calls AWAITIOX after every operation. You do
not need to call the COMPLETEIOEDIT procedure.
•
If nowait-option is set to 1 and IOEdit determines that the file is being
accessed sequentially, IOEdit reads ahead or writes behind when it performs
nowait I/O on the buffers for files that are opened for nowait access.
•
If nowait-option is set to 2 or 3 and IOEdit determines that the file is being
accessed sequentially, IOEdit reads ahead and writes behind for all files, not just
those opened for nowait access.
•
If nowait-option is set to 1, 2, or 3 and the calling process calls AWAITIO[X]
with the file number set to -1 (any file), you must call COMPLETEIOEDIT to let
IOEdit know when the nowait operation on the buffer has finished, even if the
process is accessing nonedit files nowait.
Example
In the following example, a call to INITIALIZEEDIT specifies that the EFS be allocated
on $BIGVOL, and that if the EFS cannot be allocated on $BIGVOL or any other disk
volume on the system, INITIALIZEEDIT should display an error message to the home
terminal and terminate abnormally.
INT .EXT swapvol[0:3] := [ “$BIGVOL” ];
INT errorabend := -1;
.
.
error := INITIALIZEEDIT ( swapvol, , errorabend );
Related Programming Manual
For programming information about the INITIALIZEEDIT procedure, refer to the
Guardian Programmer’s Guide.