3.2.4.17 Local LU Initiated Recovery Sending XLN Confirmation

This event MUST be signaled by the higher-layer business logic with the following arguments:

• A connection object of type CONNTYPE_TXUSER_DTCLURECOVERYINITIATEDBYDTC

• An XLN Response value, which MUST be set to one of the following values:

  • Confirm

  • Log Name Mismatch

  • Cold Warm Mismatch

  • Obsolete

If the Local LU Initiated Recovery Sending XLN Confirmation event is signaled, the LU 6.2 implementation (section 3.2) MUST perform the following actions:

• If the provided connection state is not set to Processing Warm XLN Request:

  • Return a failure result to the higher-layer business logic.

• Otherwise:

  • Send a TXUSER_DTCLURECOVERYINITIATEDBYDTC_MTAG_CONFIRMATION_FROM_OUR_XLN message using the provided connection:

    • The XlnConfirmation field MUST be set to one of the following elements of the DTCLUXLNCONFIRMATION enumeration:

      • DTCLUXLNCONFIRMATION_CONFIRM if the provided XLN Response value is Confirm

      • DTCLUXLNCONFIRMATION_LOGNAMEMISMATCH if the provided XLN Response value is Log Name Mismatch

      • DTCLUXLNCONFIRMATION_COLDWARMMISMATCH if the provided XLN Response value is Cold Warm Mismatch

      • DTCLUXLNCONFIRMATION_OBSOLETE if the provided XLN Response value is Obsolete

    • If the provided XLN Response value is Confirm:

      • Set the connection state to Awaiting Response To XLN Confirmation.

    • Otherwise, if the provided XLN Response value is either Log Name Mismatch or Cold Warm Mismatch:

      • Set the connection state to Awaiting Request Complete.

    • Otherwise:

      • Set the connection state to Ended.