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

Writing CPI-C Applications
Windows Considerations
Chapter 2106
Windows Considerations
For Windows This section summarizes processing considerations you need to be aware
of when developing programs on a Windows client.
Windows CPI-C Files
The header file to be used with Windows CPI-C applications is
wincpic.h, which contains the definitions of all CPI-C entry points, and
the defined constants for supplied and returned parameter values at the
Windows CPI-C interface. This file is installed in the subdirectory /sdk
within the directory where you installed the Windows Client software.
The library used to link Windows CPI-C applications is wcpic32.lib.
Function Prototypes
The function prototypes for CPI-C calls shown in Chapter 3, CPI-C Calls,
are in the format used for HP-UX systems.
• For Win32systems, replace “void functionname ” with “void WINAPI
functionname ” for each call.
Multiple Processes and Multiple Conversations
Multiple processes cannot have the same conversation identifier. Only
the process that issues the Initialize_Conversation or
Accept_Conversation call can use the conversation ID returned by the
call. Another process wanting to use CPI-C must issue an
Initialize_Conversation or Accept_Conversation call to obtain its own
conversation ID.
One program can engage in up to 64 simultaneous conversations.
Windows Function Calls
In addition to the standard CPI-C function calls, and the
Windows-specific CPI-C function call Specify_Windows_Handle, a
Windows application also uses the following functions: