Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
ATBUNID— Unidentify z/OS MVS Programming: Writing Transaction Schedulers for APPC/MVS SA23-1398-00 |
|||||||||||||||||
Note: The ATBUID1 call is the preferred programming interface for
this service.
Unidentify can be used by a transaction scheduler to reverse the effect of invocation of the Identify service. Unidentify terminates all APPC services for the specified transaction scheduler and its subordinate address spaces. After performing Unidentify, a transaction scheduler can invoke the IXCLEAVE macro to undo the effects of its invocation of Join_Sysappc_Group. APPC/MVS asynchronously shuts down the LU or LUs assigned to the transaction scheduler that called Unidentify. The calling program does not have to wait for this to occur. Once the Unidentify request is accepted, APPC/MVS returns control to the calling program and assumes responsibility for taking down the LU or LUs. Shut down automatically disconnects address spaces currently connected to the issuing transaction scheduler. Shutting down an LU also includes setting the session limits to zero. Conversations that are currently running will run to completion. Any outstanding transaction program allocate requests will not be honored. Upon completion of all of the LU's conversations, the ACB is closed. The LU is then placed in pending state, to await another Identify request. A transaction scheduler must issue Identify if it is to restart. The Unidentify must be issued from the address space that issued the Identify. Environment
FormatFigure 1. ATBUNID
- Unidentify
Parameters
Characteristics and RestrictionsTransaction schedulers that call the Unidentify service should not have any enabled unlocked task (EUT) functional recovery routines (FRRs) established. For more information about EUT FRRs, see the information on providing recovery in z/OS MVS Programming: Authorized Assembler Services Guide. |
Copyright IBM Corporation 1990, 2014
|