PM79389: INSUFFICIENT DIAGNOSTIC INFORMATION FOR A ZERO LENGTH QUEUE ELEMENT

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

  • Transaction IMRF retrieves an invalid queue element. Error
    message IMR223E is issued showing DSLMMFS error 025
    (hexadecimal). Dump analysis shows that the queue element has no
    data at all, its length is zero. The provided information is not
    sufficient to identify the invalid queue element in a queue.
    Thus it is not possible to locate the invalid queue element for
    further processing (deleting or moving to an error queue).
    

Local fix

  • Improve error diagnostic for transaction IMRF.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of Traffic Reconciliation SWIFT    *
    *                 message monitor.                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: INSUFFICIENT DIAGNOSTIC INFORMATION FOR *
    *                      A ZERO LENGTH QUEUE ELEMENT.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When transaction IMRF retrieved a queue element of length 0
    IMR223E error message was issued and two snap dumps with
    identical dumpids were taken.
    Now error message IMR223E was improved to show the MFS return
    code in decimal (as usual in Merva Esa) and an additional error
    message IMR229E is issued.
    IMR229E issues the QSN of the erroneous message and the name
    of the function which was processed by IMRF.
    So the erroneous message can easily be identified and deleted
    or moved to another queue.
    A snap dump with dumpid 30 (queue buffer) and another one with
    dumpid 127 (TOF) are taken.
    

Problem conclusion

  • Improved error diagnosis when transaction IMRF retrieved
    an erroneous queue element of length zero.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM79389

  • Reported component name

    MERVA COMPONENT

  • Reported component ID

    5648B3000

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-18

  • Closed date

    2013-03-12

  • Last modified date

    2013-04-02

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

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

    UK92433

Modules/Macros

  • IMRCSD41 IMRMSGTC IMRSWFF  IMRYCWFF IMRYIWFF
    IMR223E  IMR229E  J0B1410J
    

Publications Referenced
SH12639208        

Fix information

  • Fixed component name

    MERVA COMPONENT

  • Fixed component ID

    5648B3000

Applicable component levels

  • R410 PSY UK92433

       UP13/03/14 P F303



Rate this page:

(0 users)Average rating

Document information


More support for:

MERVA

Software version:

410

Reference #:

PM79389

Modified date:

2013-04-02

Translate my page

Machine Translation

Content navigation