Disconnect

The Disconnect service can be used by a transaction scheduler to inform APPC/MVS that an address space is no longer one of its subordinate address spaces.

An address space remains connected to a particular transaction scheduler until the address space is terminated or issues an explicit Disconnect. Address space termination is an implicit Disconnect. Normally address space termination is all that is required to disconnect an address space from a transaction scheduler.

Environment

Authorization:

Supervisor state or PSW key 0-7

Dispatchable unit mode:

Task mode

Cross memory mode:

Any PASN, any HASN, any SASN

AMODE:

31-bit

ASC mode:

Primary or access register (AR)

Interrupt status:

Enabled for I/O and external interrupts

Locks:

Unlocked

Control parameters:

All parameters must be addressable by the caller and in the primary address space.

Format

Figure 1. ATBDCON - Disconnect

CALL ATBDCON (ASCB_Ptr, 
              Return_Code
             );

Parameters

ASCB_ptr

Supplied parameter

Type: Pointer
Char Set: N/A
Length: 32 bits

Specifies the pointer to the address space control block (ASCB) of the address space being disconnected from the transaction scheduler.

Return_code

Returned parameter

Type: Integer
Char Set: N/A
Length: 32 bits

Disconnect might return one of the following decimal values in the return code parameter:

Decimal: Meaning
0: Address space was successfully disconnected.
4: The value specified on the ASCB_ptr is not valid.
8: The address space specified was not a subordinate address space connected to the transaction scheduler.
32: The requested service is not supported in the caller's environment. For example, this return code will be given if the caller invokes any of the transaction scheduler services while holding a lock.
34: The requested transaction scheduler service must be invoked from a transaction scheduler address space.
44: APPC/MVS is not active.
48: APPC/MVS services failure.

Characteristics and Restrictions

Transaction schedulers that call the Disconnect 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.