HP-UX SNAplus2 CPI-C Programmer's Guide (June 2003)

Writing CPI-C Applications
Windows Considerations
Chapter 2 107
WinCPICStartup() Registers the application as a Windows CPI-C user,
and determines whether the CPI-C software supports
the level of function required by the application.
WinCPICCleanup() Unregisters the application when it has finished
using CPI-C.
WinCPICIsBlocking() Checks whether there is a blocking call
outstanding for this application. For more information
about the circumstances in which this call may be
required, see “Blocking Calls”.
WinCPICSetBlockingHook() Specifies the blocking procedure that
CPI-C uses while processing blocking calls; this
replaces CPI-C's default blocking procedure. The
blocking procedure is called repeatedly until processing
for the blocking call has completed. For more
information, see “Blocking Calls”.
WinCPICUnhookBlockingHook() Unregisters the blocking procedure
specified by a previous WinCPICSetBlockingHook()
call, so that CPI-C reverts to using the default blocking
procedure.
WinCPICExtractEvent() Provides a method for an application to
determine the Win32 event handle being used for a
CPI-C conversation.
WinCPICSetEvent() Associates a Win32 event handle with verb
completion for a CPI-C conversation.
The application must call WinCPICStartup() before attempting to issue
any CPI-C calls.
“Blocking Calls” provides more information about how blocking calls
operate in the Windows environment, and how the application should
use the WinCPICIsBlocking(), WinCPICSetBlockingHook(), and
WinCPICUnhookBlockingHook() calls.
When the application has finished issuing CPI-C calls, it must call
WinCPICCleanup() before terminating; it must not attempt to issue any
more CPI-C calls after calling WinCPICCleanup().
The Windows function calls are described at the end of Chapter 3,
“CPI-C Calls.”