IBM Support

IT27005: Indirect runmqsc to a remote z/OS queue manager gives reason code 10 on exit

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

  • A runmqsc session used to run the MQSC command:
    
      dis qmgr
    
    incorrectly on a remote z/OS queue manager exits with return
    code 10 even though the command completes successfully.
    
    For example:
    
    $ runmqsc -w 30 -m QM1 -x MQ0A
    5724-H72 (C) Copyright IBM Corp. 1994, 2018.
    Starting MQSC for queue manager MQ0A.
    
    dis qmgr
         1 : dis qmgr
    
    CSQN205I   COUNT=       3, RETURN=00000000, REASON=00000000
    
    CSQM409I +MQX1 QMNAME(MQ0A)
    
    CSQ9022I +MQX1 CSQMDRTS ' DIS QMGR' NORMAL COMPLETION
    
    end
         2 : end
    One MQSC command read.
    2 command responses received.
    
    $ rc=$?
    $ echo $rc
    10
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects runmqsc users who issue MQSC commands that
    are executed on remote z/OS queue managers.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    After invoking runmqsc to run commands indirectly on a remote
    z/OS queue manager, runmqsc was ending with return code 10
    (meaning the MQSC commands processed with errors) despite the
    successful completion of all the MQSC commands issued.  The
    return code was incorrectly updated from 0 to 10.
    
    In addition, if an invalid MQSC command was issued to a remote
    distributed queue manager, for example:
    
      dsi qmgr
    
    instead of:
    
      dis qmgr
    
    runmqsc would have continued to end with 0, despite the return
    code of 10 being expected in this case.
    

Problem conclusion

  • Runmqsc has been updated such that it exits with return code 0
    after the successful completion of all issued MQSC commands to a
    z/OS queue manager.  It has also been updated to exit with
    reason code 10 if MQSC commands failed to be executed against
    remote distributed queue managers.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.6
    v9.1 CD    9.1.2
    v9.1 LTS   9.1.0.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

    IT27005

  • 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

    2018-11-16

  • Closed date

    2019-01-03

  • Last modified date

    2019-01-03

  • 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":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
03 January 2019