The SET_TRACKING_DATA call

The SET_TRACKING_DATA call function sets the transaction tracking origin data tag for the issuing task.

SET_TRACKING_DATA

DFHMNTDX [CALL,]
      [CLEAR,]
      [IN,
      FUNCTION(SET_TRACKING_DATA),
      {TRACKING_TAG (MOBILE)|TRACKING_TAG_VALUE(name1 | *)},]
      [OUT,
      RESPONSE(name1 | *),
      REASON(name1 | *)]

This command is threadsafe.

Important

There is a restriction in using the XPI early during initialization. Do not start exit programs that use the SET_TRACKING_DATA function until the second phase of the PLTPI. For more information about the PLTPI, see Writing initialization and shutdown programs.

TRACKING_TAG (MOBILE)

Specifies the transaction tracking origin data tag information to be set in the transaction tracking origin data.

MOBILE
The transaction tracking origin data tag is mobile.

RESPONSE and REASON values for SET_TRACKING_DATA

RESPONSE REASON
OK None
EXCEPTION NO_ASSOCIATION_DATA
  TRACKING_TAG_ALREADY_SET
  INVALID_TRACKING_TAG
  INVALID_TRACKING_TAG_VALUE
DISASTER None
INVALID None
KERNERROR None
PURGED None
Note:
  1. For more detail, refer to the explanation of RESPONSE and REASON in Making an XPI call.
  2. NO_ASSOCIATION_DATA means that the transaction under which this XPI call has been invoked has no transaction tracking association data. For more information about association data and transaction tracking, see Introduction to CICS intercommunication.
  3. TRACKING_TAG_ALREADY_SET means that transaction tracking origin data tag for the issuing task has already been set.
  4. INVALID_TRACKING_TAG means that the transaction tracking origin data tag has an invalid value.
  5. INVALID_TRACKING_TAG_VALUE means that the transaction tracking origin data tag value is not in the range of 129 through to 255.