IBM Support

IT37199: Failure data capture (FDC) record header contains the first linefrom mqpatch.dat but it should be the last line

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

  • The record header in each record of a .FDC file contains the
    build level of MQ.
    
    If a fix has been installed using the supplied installation
    program, then a line containing the fix name has been added to
    mqpatch.dat.
    
    The build level in the FDC record header is expected to contain
    the current fix name, if there is one.
    
    The first line from mqpatch.dat was being written into the FDC
    record header.  But it is possible for the level of MQ code to
    be upgraded (by installing a fix pack), or for a second fix to
    be installed, without the earlier line being removed from
    mqpatch.dat.  In that case it is the last line in the file that
    is most appropriate to be written into the FDC record header,
    not the first line.
    

Local fix

  • Manually edit mqpatch.dat to remove the irrelevant lines,
    leaving
    only the last line.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users looking at FDC files (these are written for unhandled
    error conditions) and seeing that the fix named in the top of
    the FDC file is not relevant for the installation.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The last line in mqpatch.dat is most appropriate to describe the
    current state of fixes installed, not the first line (if there
    is more than one line).  So the last line from mqpatch.dat
    should have been used in the FDC records.
    

Problem conclusion

  • The MQ code has been changed to write out the last line from
    mqpatch.dat into the FDC records.
    
    The dspmqver command now also outputs the last line (if present)
    from mqpatch.dat as the 'Level:'.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.11
    v9.2 LTS   9.2.0.5
    v9.x CD    9.3.0.0
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT37199

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-06-09

  • Closed date

    2021-12-21

  • Last modified date

    2022-04-13

  • 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

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0"}]

Document Information

Modified date:
14 April 2022