PM82056: IMPROVE FIN BEHAVIOUR IN CASE OF INCONSISTENT ASP DATA

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When ASP data are not updated in the system or the data is
    inconsistent, and a FIN message type is detected which is not
    defined in an ASP, FIN should act as follows:
    - in addition to the "failed" response DNFH3713E , an event
    needs to be issued on both, sending and receiving site.
    - if exception queues are used, messages failing with DNFH3713E
    need to be routed to a seperate exception queue, not to the
    queue where messages with regular validation errors are routed
    to (sending side)
    - on the receiving site, the available exception queue needs to
    be kept only for such kind of problems.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: IMPROVE FIN BEHAVIOUR IN CASE OF        *
    *                      INCONSISTENT ASP DATA                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    FIN behaviour has been improved in case of inconsistent ASP
    data.
    

Problem conclusion

  • Now, when ASP data is not updated in the system, or the data is
    inconsistent, and a FIN message type is detected which is not
    defined in an ASP, FIN acts as follows:
    * On the sending side:
      - An error response with code Failed and MPU DNFH3713E is
        sent back to the sending application.
      - If exception queues are configured, messages failing with
        DNFH3713E are sent to distinct queue AspSndExceptionQueue.
    * On the receiving side:
      - The message is enriched with error indication DNFH3713E
        and passed to the receiving FIN application queue with
        reason code Failed.
      - If exception queues are configured, messages failing with
        DNFH3713E are sent to distinct queue
        MsgValRcvExceptionQueue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM82056

  • Reported component name

    SW FIN, SW IA,

  • Reported component ID

    5724D9631

  • Reported release

    311

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-05

  • Closed date

    2013-07-01

  • Last modified date

    2013-07-01

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

    PM81779

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

Fix information

  • Fixed component name

    SW FIN, SW IA,

  • Fixed component ID

    5724D9631

Applicable component levels

  • R311 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Business Integration for Financial Networks

Software version:

311

Reference #:

PM82056

Modified date:

2013-07-01

Translate my page

Machine Translation

Content navigation