IBM Support

IT31620: THE INTEGRATION NODE FAILS TO START VIA MQ SERVICE ON AIX ACE V11.0.0.7

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

  • On ACE V11.0.0.7 the runMQService was updated to allow a new
    parameters to be called (i.e. --vault-key). This change is
    working as expected on all platforms apart from AIX. The
    runMQService script runs using a ksh where linux uses a bash
    script. This causes a command argument not to be cleared and
    propogates it into the mqsistart command causing it to fail.
    

Local fix

  • In order to fix the issue it it necessary to set the $@
    variable before calling the mqsiprofile.
    
    In the file at
    //server/bin/runMQService
    add
    
    args=$@
    
    before the line # Run mqsiprofile
    
    and change the
    last line from
    
    . ./mqsistart $broker -1 $@
    
    to
    
    . ./mqsistart
    $broker -1 $args
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    <span
    style="font-size:15px;font-family:slack-lato,applelogo,sans-seri
    f">All users of IBM App Connect Enterprise v11.0 on AIX</span>
    
    
    Platforms affected:
    AIX
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    On ACE V11.0.0.7 the runMQService was updated to allow new
    parameters to be called (i.e. --vault-key). This change is
    working as expected on all platforms apart from AIX. On AIX, the
    runMQService script runs using the ksh shell which has different
    'scoping' for positional parameters in comparison to linux
    (which uses bash script). This different scoping causes the
    positional parameters to be overwritten resulting in invalid
    values being propagated to the mqsistart command causing it to
    fail.
    

Problem conclusion

  • The runMQService script is updated to save the arguments
    supplied to the runMQService script, while the execution
    environment is initialised, and then explicitly pass the saved
    arguments to the mqsistart command.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.8
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31620

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-01-22

  • Closed date

    2020-04-09

  • Last modified date

    2020-04-09

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
09 April 2020