HP-UX SNAplus2 R7 APPC Programmer's Guide

Writing Transaction Programs
APPC Entry Points: Windows Systems
• WinAPPCSetBlockingHook (with a different procedure instance address) to specify a new blocking function
or to restore a previous one
• WinAPPCUnhookBlockingHook (see Section 2.4.11,
WinAPPCUnhookBlockingHook), to stop using the
current blocking function and return to the default blocking function
2.4.11 WinAPPCUnhookBlockingHook
The application uses this call to remove its own blocking function, which it has previously specified using
WinAPPCSetBlockingHook, and revert to using APPC’s default blocking function.
Function Call
BOOL WINAPI WinAPPCUnhookBlockingHook (void);
Supplied Parameters
No parameters are supplied for this function.
Returned Values
The return value from the function is one of the following:
TRUE
The blocking function was removed successfully; any further blocking calls will use the default blocking
function.
FALSE
The call did not complete successfully.
2.4.12 GetAppcConfig
The GetAppcConfig function is provided for use by 5250 emulation programs. The function returns information
about the remote LUs that a specified local LU can access, as defined in the 5250 emulation user records in the
SNAplus2 configuration.
To determine the information required by this call, SNAplus2 checks the user name configured for the Windows
client against the 5250 user records defined in the configuration (or, if the user name is not explicitly defined, checks
for a <DEFAULT> record). In the appropriate user record, it matches the local LU alias and mode name supplied
on this call against the session definitions, and returns the remote LU alias for each matching session.
The application supplies a Windows handle to which APPC can post a message when the verb completes asynchro-
nously. Before using GetAppcConfig for the first time, the application must use RegisterWindowMessage
to obtain the message identifier that APPC will use for the message indicating asynchronous completion of the call,
and WinAPPCStartup to register as a Windows APPC application. For more information, see the description of
WinAPPCStartup in Section 2.4.1, WinAPPCStartup and Section 2.4.12, GetAppcConfig.
An alternative method of indicating completion of the call is to supply a pointer to an integer value (the AsyncRetCode
parameter) in which APPC can return values to indicate that the call has failed, is in progress, or has completed.
Windows applications are recommended to use the first method, supplying a Windows handle.
Function Call
HANDLE WINAPI GetAppcConfig (
HWND hWnd,
char far *LocalLU,
char far *Mode,
int far *NumRemLU,
int MaxRemLU,
char far *RemLU,
63