Transaction manager domain’s generic format

Table 118 shows the generic format owned by the transaction manager domain, and shows the function performed on the call.

Table 118. Generic format owned by the transaction manager domain
Format Calling module Function
XMNT
DFHXMSR
DFHXMAT
DFHXMTA
DFHXMCL
MXT_NOTIFY
MXT_CHANGE_NOTIFY
XMDN
DFHXMXD
DFHXMQD
DFHXMDD
TRANDEF_NOTIFY
TRANDEF_DELETE_QUERY
XMPP DFHXMIQ
FORCE_PURGE_INHIBIT_QUERY

In the descriptions of the format that follow, the "input" parameters are input not to the transaction manager domain, but to the domain being called by the transaction manager. Similarly, the "output" parameters are output by the domain that was called by the transaction manager domain, in response to the call.

Format XMNT, MXT_NOTIFY function

The MXT_NOTIFY function of XMNT format is used to notify other domains when CICS® is at, or no longer at, the maximum task limit for user tasks.

Input parameters

MXTQUEUING
Indicates whether queuing for MXT has just started or just stopped. It can have either of these values:
STARTED|STOPPED

Output parameters

RESPONSE
is the domain’s response to the call. It can have any of these values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED

Format XMNT, MXT_CHANGE_NOTIFY function

The MXT_CHANGE_NOTIFY function of XMNT format is used to notify other domains of a change to the MXT limit. The called domains indicate whether they can cope with the new limit.

Input parameters

REQUESTED_MXT
The new limit requested for MXT.

Output parameters

ALLOCATED_MXT
Indicates the limit that the called domain can cope with when the LIMIT_TOO_HIGH exception is returned.
RESPONSE
is the domain’s response to the call. It can have any of these values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
[REASON]
is returned when RESPONSE is DISASTER, EXCEPTION, or INVALID. Possible values are:
RESPONSE Possible REASON values
EXCEPTION LIMIT_TOO_HIGH
DISASTER
LOGIC_ERROR
ABEND
LOOP
INVALID INVALID_FUNCTION

Format XMDN, TRANDEF_NOTIFY function

The TRANDEF_NOTIFY function of the XMDN format is used to notify other domains that a transaction definition has been installed, changed, or deleted. The called domain's can then modify any transaction definition related data they are keeping for that definition.

Input parameters

EVENT
Indicates the event that has caused the notify to be sent. It can have any of the following values:
INSTALL|CHANGE|DELETE
TRANDEF_TOKEN
Token identifying the transaction definition instance subject to the above event.

Output parameters

RESPONSE
is the domain’s response to the call. It can have any of these values:
OK|DISASTER|INVALID|KERNERROR|PURGED
[REASON]
is returned when RESPONSE is DISASTER or INVALID. Possible values are:
RESPONSE Possible REASON values
DISASTER
LOGIC_ERROR
ABEND
LOOP
INVALID INVALID_FUNCTION

Format XMDN, TRANDEF_DELETE_QUERY function

The TRANDEF_DELETE_QUERY function of the XMDN format allows other domains to object to the deletion of the named transaction. definition.

Input parameters

TRANSACTION_ID
The transaction definition subject to the delete request.

Output parameters

INHIBIT_DELETE
Indicates whether the called domain wants to inhibit the deletion of the named transaction definition. It can either of the following values:
YES|NO
INHIBIT_REASON
Indicates the reason why the called domain wants to inhibit the deletion of the named transaction definition. It can have any of the following values:
AID_PENDING|ICE_PENDING|SIT_PARAMETER
RESPONSE
is the domain’s response to the call. It can have any of these values:
OK|DISASTER|INVALID|KERNERROR|PURGED
[REASON]
is returned when RESPONSE is DISASTER or INVALID. Possible values are:
RESPONSE Possible REASON values
DISASTER
LOGIC_ERROR
ABEND
LOOP
INVALID INVALID_FUNCTION

Format XMPP, FORCE_PURGE_INHIBIT_QUERY function

The FORCE_PURGE_INHIBIT_QUERY function of the XMPP format allows other domains to object to the force purge request for the specified transaction.

Input parameters

TRANSACTION_TOKEN
Token identifying the transaction that is subject to the force purge request.

Output parameters

INHIBIT_PURGE
Indicates whether the called domain wants to inhibit the force purge of the transaction. It can have either of the following values:
YES|NO
RESPONSE
is the domain’s response to the call. It can have any of these values:
OK|DISASTER|INVALID|KERNERROR|PURGED
[REASON]
is returned when RESPONSE is DISASTER or INVALID. Possible values are:
RESPONSE Possible REASON values
DISASTER
ABEND
LOOP
INVALID INVALID_FUNCTION
[[ Contents Previous Page | Next Page Index ]]