HP-UX SNAplus2 R7 APPC Programmer's Guide

Writing Transaction Programs
APPC Entry Points: Windows Systems
APPC_CFG_ERROR_NO_APPC_INIT
The application has not issued the WinAPPCStartup call. This call must be issued before GetAppc-
Config is used.
APPC_CFG_ERROR_INVALID_HWND
The application supplied a Windows handle that was not valid.
APPC_CFG_ERROR_BAD_POINTER
The application supplied a null pointer to a Windows handle, to use the alternative method for indicating
completion, but supplied a pointer for the
AsyncRetCode parameter that was not valid.
APPC_CFG_ERROR_UNCLEAR_COMPLETION_MODE
The application supplied both a Windows handle (in the hWnd parameter) and a non-null pointer to the
AsyncRetCode parameter, so APPC could not determine how to indicate asynchronous completion.
APPC_CFG_ERROR_TOO_MANY_REQUESTS
Too many GetAppcConfig requests are already outstanding. The application should yield, to allow other
processes to run, and retry the call later.
APPC_CFG_ERROR_GENERAL_FAILURE
A system error occurred.
Usage
Before using GetAppcConfig for the first time, the application must use the RegisterWindowMessage
call to obtain the message identifier that APPC will use for messages indicating asynchronous completion.
RegisterWindowMessage is a standard Windows function call, not specific to APPC; refer to your Windows
documentation for more information about the function. (The application does not need to issue the call again before
subsequent GetAppcConfig calls; the returned value will be the same for all calls issued by the application.)
The application must pass the value
WIN_APPC_CFG_COMPLETION_MSG to the function; the returned value is a
message identifier.
An application can indicate completion by using a Windows handle or by using an alternative method, as follows:
• If the application is using a Windows handle to indicate completion, APPC posts a message to this Windows
handle when the call completes asynchronously. The format of the message is as follows:
• The message identifier is the value returned from the RegisterWindowMessage call.
• The wParam argument contains the handle that was returned to the original GetAppcConfig call.
• The lParam argument contains one of the following asynchronous return codes:
APPC_CFG_SUCCESS_NO_DEFAULT_REMOTE
The configuration was retrieved successfully. No default remote LU is configured for the specified
local LU and mode.
APPC_CFG_SUCCESS_DEFAULT_REMOTE
The configuration was retrieved successfully. A default remote LU is configured for the specified local
LU and mode. (SNAplus2 does not return this value, because it does not have a concept of configuring
default remote LUs; however, the application should allow for this return code to ensure compatibility
with other APPC implementations.)
APPC_CFG_ERROR_NO_DEFAULT_LOCAL_LU
The application supplied a blank local LU alias, indicating the default local LU, but no default local
LU is configured.
APPC_CFG_ERROR_BAD_LOCAL_LU
The supplied local LU alias did not match any configured local LU alias used for 5250 emulation.
APPC_CFG_ERROR_GENERAL_FAILURE
65