IBM Support

PM81779: IMPROVE FIN BEHAVIOUR IN CASE OF INCONSISTENT ASP DATA

A fix is available

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

    PM81779

  • Reported component name

    SN FIN, SN IA,

  • Reported component ID

    5655FIN01

  • Reported release

    11E

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-31

  • Closed date

    2013-05-22

  • Last modified date

    2013-06-04

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

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

    PM82056

Modules/Macros

  • DNF00162
    

Fix information

  • Fixed component name

    SN FIN, SN IA,

  • Fixed component ID

    5655FIN01

Applicable component levels

  • R11E PSY UK94572

       UP13/05/30 P F305

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11E","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 June 2013