Guardian Procedure Calls Reference Manual

Table 16 FILE_AWAITIO64_ Action
timelimit <> 0
WAIT for any I/O completion on filenum.
timelimit = 0
CHECK for any I/O completion on filenum.
Particular File
(filenum = a file
number)
COMPLETIONCOMPLETION
File number is returned in filenum.File number is returned in filenum
Tag of completed call is returned in tag.Tag of completed call is returned in tag.
NO COMPLETIONNO COMPLETION
Error 40 is returned.Error 40 is returned.
File number is returned in filenum.File number returned is in filenum.
Oldest I/O operation on filenum is canceled.No I/O operation is canceled.
Tag of canceled call is returned in tag.
WAIT for any I/O completion on any open
file.
CHECK for any I/O completion on any open
file.
Any File
(filenum = -1)
COMPLETIONCOMPLETION
File number of completed call is returned in
filenum.
File number of completed call is returned in
filenum.
Tag of completed call is returned in tag.Tag of completed call is returned in tag.
NO COMPLETIONNO COMPLETION
Error 40 is returned.Error 40 is returned.
The value -1 is returned in filenum.The value -1 is returned in filenum.
No I/O operation is canceledNo I/O operation is canceled.
NOTE: This table assumes that SETMODE function 30 has been set.
Considerations
• EpTAL callers must set toggle
EpTAL callers must set the toggle _64BIT_CALLS before sourcing the FILE_AWAITIO64_
procedure section from EXTDECS.
• Familiar semantics
Unless otherwise described, the semantic behavior of FILE_AWAITIO64_ is the same as that
of AWAITIOXL.
• Completing nowait calls
Each 64–bit nowait operation initiated must be completed with a corresponding call to
FILE_AWAITIO64_
◦ If FILE_AWAITIO64_ is used to wait for completion (timelimit <> 0D) and a particular
file is specified (filenum <> -1), completing FILE_AWAITIO64_ for any reason, except
interruption by an OSS signal, is considered a completion: if the I/O operation did not
complete, error 40 is returned and the oldest I/O operation against the file is canceled.
◦ Queue files
If a nowait FILE_READUPDATELOCK64_ operation is used in conjunction with the
FILE_AWAITIO64_ timelimit > 0D, this occurs:
– If the queue file timeout occurs before the time limit, the read request is completed
with error 162.
– If the time limit expires before the queue file timeout, the FILE_READUPDATELOCK64_
request is canceled. A canceled FILE_READUPDATELOCK64_ can result in the loss
of a record from the queue file. If the time limit expires before the queue file timeout,
the FILE_READUPDATELOCK64_ request is canceled if it was a file-specific call (that
FILE_AWAITIO64_ Procedure 357