IBM Support

IT38022: Log more possible error conditions from amqiclen during installer/uninstaller processing

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

  • Output from amqiclen (a program that runs during installation to
    check and clean up unneeded MQ shared memory segments) has been
    improved so that more information is logged to support a future
    investigation to find the reason why after an upgrade from 9.1
    to 9.2 on AIX a customer can not start the queue manager, with
    these errors.
    
    The queue manager is associated with installation
    'Installation1'.
    The queue manager is associated with a different installation.
    
    But in those cases, there was in fact only one installation.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who install or uninstall IBM MQ will potentially benefit
    from the additional error checking and outputs, if there is in
    fact an error.
    
    
    Platforms affected:
    AIX, Linux on Power, Linux on x86-64, Linux on zSeries
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The shared memory segments belonging to the MQ processes ought
    to be removed successfully during uninstallation/installation
    processing, but there have been support cases opened with IBM
    Support where they were not.
    
    The root cause could not be found, but it seemed that amqiclen
    might have had an internal error, preventing normal processing
    from taking place.  However, in these support cases there were
    no errors output from amqiclen, so it could not be determined if
    this was truly the case.
    

Problem conclusion

  • Some extra error checking and output has been added into
    amqiclen, to be sure there is something recorded from the time
    it was run, if errors occurred.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.25
    v9.3 LTS   9.3.0.20
    v9.x CD    9.3.6
    
    The latest available maintenance can be obtained from
    'IBM MQ Recommended Fixes'
    https://www.ibm.com/support/pages/recommended-fixes-ibm-mq
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'IBM MQ
    Planned Maintenance Release Dates'
    https://ibm.biz/mqplannedmaintenance
    
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT38022

  • 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-08-16

  • Closed date

    2024-03-26

  • Last modified date

    2024-03-26

  • 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":"BU048","label":"IBM Software"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
04 April 2024