IBM Support

IT38618: After applying a fix pack to a Developer Edition installation onWindows, dspmqver incorrectly reports production license

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

  • After applying a fix pack (for example 9.2.0.1) to an IBM MQ
    Developer Edition 9.2.0.0 installation on Windows, the dspmqver
    command incorrectly
    reports "LicenseType: Production".
    
    The metadata in the installation directly detected by ILMT
    reports is not affected, and ILMT will continue to correctly
    report the installation as Developer Edition licensed.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    <span style="background-color:rgb(255, 255, 255)">This issue
    affects users who have installed the Trial or Developer Edition
    MQ images on Windows, and then apply fix pack maintenance to
    it.</span>
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Installation metadata was incorrectly defaulted to the
    production license value when applying a fix pack. This affected
    the license type value printed by the dspmqver command, and in
    other internal diagnostics such as failure data capture (FDC)
    file headers.
    
    The issue did not affect the license tag files which are used
    for license entitlement and capacity reporting, which continued
    to report the correct usage and entitlement.
    

Problem conclusion

  • The IBM MQ fix pack installer has been modified to generate
    additional metadata files during installation, based on the
    current license type for the system, to ensure that the license
    type is reported correctly by the dspmqver command.
    
    Please note that if earlier fix packs have been applied to a
    developer edition or trial installation, these earlier fix packs
    must be removed (ie. the installation must be reverted to the
    9.2.0.0 level) prior to applying a fix pack level which contains
    this fix , in order to observe the corrected behaviour.
    
    An equivalent change for the Linux and AIX fix pack installer is
    implemented under APAR IT35023.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.10
    v9.3 LTS   9.3.0.5
    v9.x CD    9.3.2
    
    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

    IT38618

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-10-06

  • Closed date

    2022-11-25

  • Last modified date

    2022-11-25

  • 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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

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

Document Information

Modified date:
26 November 2022