Guardian Procedure Calls Reference Manual

Considerations
• EpTAL callers must set toggle
EpTAL callers must set the toggle _64BIT_CALLS before sourcing the FILE_CONTROLBUF64_
section from EXTDECS.
• Familiar semantics
Unless otherwise described, the semantic behavior of FILE_CONTROLBUF64_ is same as that
of CONTROLBUF.
• Nowait and FILE_CONTROLBUF64_
If FILE_CONTROLBUF64_ is called on a file opened for nowait I/O, then the operation must
be completed by calling either FILE_AWAITIO64_ or FILE_COMPLETEL_.
• Wait and count-transferred
If a waited FILE_CONTROLBUF64_ is executed, the count-transferred parameter indicates
the number of bytes actually transferred.
• Nowait and count-transferred
If a nowait FILE_CONTROLBUF64_ is executed, count-transferred has no meaning and
can be omitted. A count of the number of bytes transferred is obtained by either the
count-transferred parameter of the FILE_AWAITIO64_ procedure or the count-transferred
field of the completion-info parameter of the FILE_COMPLETEL_ procedure when the I/O
finishes.
• When object of FILE_CONTROLBUF64_ is not accepting messages
If the object of the FILE_CONTROLBUF64_ operation is not accepting process CONTROLBUF
messages, the call to FILE_CONTROLBUF64_ completes with an error 7.
You can obtain the process identifier of the caller to FILE_CONTROLBUF64_ in a call to
FILE_GETRECEIVEINFO_ after you have read the process CONTROLBUF message.
• Nonstandard operation and buffer parameters
You can specify any value for the operation parameter, and you can include any data in
buffer. An application-defined protocol should be established for interpreting nonstandard
parameter values.
Messages
• Process CONTROLBUF message
Issuing a FILE_CONTROLBUF64_ to a file that represents another process causes a system
message -35 (process CONTROLBUF) to be sent to that process. For detailed information of
system messages sent to processes, see the Guardian Procedure Errors and Messages Manual.
384 Guardian Procedure Calls (F)