Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Identifying and Deallocating Conversations with Outstanding Asynchronous Requests z/OS MVS Programming: Writing Transaction Programs for APPC/MVS SA23-1397-00 |
|
In some situations, a program might need to determine whether an address space contains any outstanding asynchronous APPC/MVS calls, including calls to ATBxxxx services that have an asynchronous processing specified on the Notify_Type parameter. For example, an authorized command or program cannot be invoked from a TSO/E address space while an asynchronous APPC/MVS call is outstanding. In such situations, you can call the Asynchronous_Manager service to determine whether asynchronous APPC/MVS calls are outstanding, and if necessary, clean up the conversations that hold them. For example, when TSO/E needs to invoke an authorized command or program, TSO/E calls the Asynchronous_Manager service to ensure that no asynchronous calls are outstanding. |
Copyright IBM Corporation 1990, 2014
|