IBM Support

IT30754: The MQ fix pack installer incorrectly reports resources in use when an authority error is encountered

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

  • An error was seen when installing an MQ Fix Pack:
    
      WebSphere MQ shared resources associated with the
      installation at '/xxx/xxxxxx/xxxx/xxx' are still
      in use. You must stop all MQ processes, including
      applications, Queue Managers, and Listeners, before
      attempting to install, update or delete the WebSphere
      MQ product.
    
    
    But the debug.out file shows:
    
      amqiclen -v -x return code was: '243', output was:
      Failed while executing the mqm.server.rte.pre_u script
    
    243 in decimal is 0xf3 in hex. This is a truncated (single-byte)
    version of 0x7f3, which in decimal is 2035
    (MQRC_NOT_AUTHORIZED).
    
    Therefore the output saying "shared resources associated ... are
    still in use" is not a correct statement of the root cause of
    the problem.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users upgrading or installing IBM MQ, in the rare case where
    there is a problem encountered during installation.
    
    
    Platforms affected:
    AIX, Linux on S390, Linux on x86-64, Linux on zSeries, Solaris
    SPARC, Solaris x86-64, Linux on Power
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    There are places in the installer code where amqiclen is run
    (this is an internal MQ program that runs as part of
    installation/uninstallation).
    
    In most cases this means that shared memory segments are still
    in use by running queue managers or their applications.
    
    But in other (rare) cases where there is some other reason for
    the program to fail, the error text should be different, so as
    not to be misleading.
    

Problem conclusion

  • The MQ installer/uninstaller code has been updated to output
    error text that is appropriate to the failure.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.9
    v9.1 CD    9.1.5
    v9.1 LTS   9.1.0.5
    
    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

    IT30754

  • 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

    2019-10-30

  • Closed date

    2020-02-10

  • Last modified date

    2020-02-10

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2020