gtpg2m4kGeneral Macros

TPPCC DEALLOCATE

Use the TPPCC general macro with the DEALLOCATE verb specified to deallocate the specified conversation from the transaction program. An implied FLUSH is executed and the resource ID becomes unassigned when the deallocation is complete.

Format




label
A symbolic name can be assigned to the macro statement.

DEALLOCATE
Directs the TPPCC macro to perform the DEALLOCATE verb function.

RESID
Specifies the symbolic name of a field or a register that points to a field. This is a 4-byte field in which the resource ID is supplied. This resource ID must be the one assigned on the initial ALLOCATE for this conversation or one that was assigned by an incoming ATTACH.

TYPE
Specifies the type of deallocation to be performed. The value must be one of the following:

SYNC
Specifies that either the FLUSH or CONFIRM function should be performed before the conversation is deallocated, depending on the SYNC level specified at ALLOCATE time.

FLUSH
Specifies that the function of the FLUSH verb should be executed, and then the conversation should be deallocated.

CONFIRM
Specifies that the function of the CONFIRM verb should be executed, and then the conversation should be deallocated.

LOCAL
Specifies that the conversation should be deallocated locally. This type of deallocation can be specified only if the conversation is already in end-conversation state.

ABENDP|ABENDS|ABENDT
The 3 abend parameters specify that the conversation should be unconditionally deallocated. Logical record truncation can occur when the conversation is in send state, and data purging can occur when the conversation is in receive state. The only difference among the 3 abend codes is the sense codes used to notify the remote transaction program. ABENDP is intended to be used by the application transaction program to indicate that it is requesting the deallocation. ABENDS and ABENDT are intended to be used by the TPF/APPC support routines when they request the deallocation.

LOGDATA
Specifies whether error information should be logged. NO is the only option supported. TPF does not support the YES option defined by the LU 6.2 architecture.

RCODE
Specifies the symbolic name of a field or a register that points to a field. This is a 6-byte field in which the return code is placed. The return code consists of a 2-byte primary return code followed by a 4-byte secondary return code. The actual values returned are listed in Return Conditions.

Entry Requirements

Return Conditions

Programming Considerations

Examples

SYMB100   TPPCC DEALLOCATE,                        X
                RESID=EBW004,                      X
                TYPE=FLUSH,                        X
                LOGDATA=NO,                        X
                RCODE=EBW010