Tuxedo 6.5.3 tuxhandleio

tuxhandleio
Name
tuxhandleio - arrange to be notified of asynchronous i/o completions detected by NonStop Tuxedo
Synopsis
#include <atmi.h>
int tuxhandleio (int (*handler) (short filetype, short fileid, long error, long
iotag,
long count)
Description
tuxhandleio() is used to register a function that handles completions of asynchronous input/output operations initiated
outside of the NonStop Tuxedo system, but detected within NonStop Tuxedo. The registered function is called
whenever AWAITIOX() or FILE_COMPLETE_() returns an operation completion to NonStop Tuxedo, and the
operation is not one that was initiated by NonStop Tuxedo.
The completion handler function has the same parameters as the tuxpostio() Nonstop Tuxedo ATMI function. More
specifically, NonStop Tuxedo passes the file type, file number, error code, input/output tag, and transfer count of the
completed operation to the handler function. Currently in application processes, NonStop Tuxedo calls only
AWAITIOX(), which returns only Guardian file operation completions, so a file type of zero, indicating a Guardian
file, is always passed to the handler function. The handler function should return a non-zero value if it recognizes the
completed operation, or zero if it does not recognize the operation.
Currently, no more than one handler function in a process can be registered with NonStop Tuxedo. When NonStop
Tuxedo receives an operation completion that it does not recognize, it will call each registered handler function in
turn, until one of them indicates that it recognizes the operation.
tuxhandleio() returns 0 if it successfully registered the handler function. It returns -1 and sets the tperrno variable if a
different handler function has already been registered.
Portability
The tuxhandleio() function is available on Compaq NonStop TUXEDO for NonStop Himalaya systems. The function
is supported for native NonStop TUXEDO client and server programs, but not for NonStop TUXEDO OSS
workstation client programs.
Limitations
The completion handler function should not initiate any asynchronous input/output operations, nor should it begin,
complete, or switch the process current transaction.
tuxhandleio
file:///C|/READMEs TUXEDO/Release 6.5 V3 white/NSTux65v3tuxhandleio.htm (1 of 2) [7/6/2004 9:36:34 AM]