IBM Support

PH24865: INCONSISTENT DB2 RESULTS WHEN RECEIVING AN ONTOKENSTATUSCHANGENOTIFICATION

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When Zelle Tokens were previously implemented, their statuses
    were binary.  Either they were active or they were Inactive.
    With the addition of the Restricted state, this is no longer the
    case, and if a Token is activated, deactivated, and reactivated
    multiple times, this can cause the receipt of "interesting"
    results from the current queries and logic being used.
    

Local fix

Problem summary

Problem conclusion

  • Corrected the code logic
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH24865

  • Reported component name

    ACH SERVICES FT

  • Reported component ID

    5725S7630

  • Reported release

    306

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-30

  • Closed date

    2020-08-14

  • Last modified date

    2020-08-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    ACH SERVICES FT

  • Fixed component ID

    5725S7630

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"306","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 September 2020