|
|
|
|
On Solaris systems, SNAP-IX provides two alternative entry points to the APPC library:
Synchronous entry point, APPC. If the application uses this entry point, SNAP-IX does not return control to the application until verb processing has finished.
Asynchronous entry point, APPC_Async. If the application uses this entry point, SNAP-IX returns control to the application immediately. When verb processing has finished, SNAP-IX uses an application-supplied callback routine to return the results of the verb processing to the application.
On Windows systems, SNAP-IX provides three alternative entry points to the APPC library:
Synchronous entry point, APPC. If the application uses this entry point, SNAP-IX does not return control to the application until verb processing has finished.
Asynchronous entry point, WinAsyncAPPC. If the application uses this entry point, SNAP-IX returns control to the application immediately. When verb processing has finished, SNAP-IX indicates this by posting a message to the application's window procedure.
Asynchronous entry point, WinAsyncAPPCEx. When verb processing has finished, SNAP-IX indicates this by signaling an event handle provided by the application.
For more information about these entry points, see Writing Transaction Programs.
Using the asynchronous entry point enables an application to continue with other processing while waiting for a verb to complete. The application may issue verbs on other APPC conversations, or issue verbs to start new conversations, or it may perform other processing not related to APPC. However, it must not issue other APPC verbs on the same conversation as a previous asynchronous verb, until that verb has completed.
The only exception to this is when the [MC_]RECEIVE_AND_POST verb is outstanding. In these cases, the application can issue a limited range of verbs on the same conversation. For more information, see the following section.
|
|
|
 |
|