IBM Support

IC72986: The WebSphere MQ user defined queue manager service does not stop a program if the STDOUT parameter is not set

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A WebSphere MQ queue manager service is defined to
    start and stop a .cmd or .bat file, using the default
    value for the STDOUT parameter which is blank.
    
    Starting the service shows:
    AMQ8733: Request to start Service accepted.
    The program being started by the service is started
    as expected.
    
    Stopping the service appears to work:
    AMQ8732: Request to stop Service accepted.
    Upon further review, the program being stopped by the
    service is still running.
    
    ADDITIONAL KEYWORDS
    SERVICE STARTCMD STOPCMD
    

Local fix

  • In MQ we create a new process to stop the program
    provided in the STOPCMD parameter of the Service. If STDOUT or
    STDERR is not set the creation flag for the new process is
    DETACHED_PROCESS and this new process does not execute the
    contents of the .cmd or .bat file. The fix for the defect
    modifies the process creation flag in zxpStopProcess function to
    use CREATE_NO_WINDOW if the program to be stopped is a .cmd or
    .bat file and if the output and error file handle is NULL.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Any users of WebSphere MQ using service object definitions to
    launch batch files (.cmd and .bat).
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    WebSphere MQ launches the program provided in the STOPCMD
    parameter of the Service when the stop service is executed.
    However,  the STOPCMD fails to launch batch files ( .bat
    or .cmd) if the default values for STDOUT/STDERR is specified;
    in other words if the STDOUT/STDERR is not set.
    

Problem conclusion

  • The problem was caused by the fact that WebSphere MQ was
    specifying incorrect options on the CreateProcess call when
    launching a batch file. The WebSphere MQ code has been modified
    to alter the flag passed to the CreateProcess call if the
    program to be started is a .bat or .cmd file.
    
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.5
    --------           --------------------
    Windows            U200324
    
    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

    IC72986

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-03

  • Closed date

    2010-12-17

  • Last modified date

    2011-08-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

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023