IT07304: MQ_SERVER_PID IS NOT BEING SUBSTITUTED CORRECTLY FOR THE SERVICE PROCESS ID WHEN THE SERVICE IS STARTED

APAR status

• Closed as program error.

Error description

• In MQ8.0 when a service is defined and started, the STOPARGS
  parameter is not able to interpret the service process id. A
  null value will be passed for the service process id under the
  STOPARGS. As a result when we attempt to stop the service, the
  service remains in STOPPING state. The following example
  demonstrates the scenario
  DEFINE SERVICE(SLEEP) CONTROL(MANUAL) SERVTYPE(SERVER)
  STARTCMD('/bin/sleep') STARTARG(1000) STOPCMD('/bin/kill')
  STOPARG('-9 +MQ_SERVER_PID+') STDOUT('/dev/null')
  STDERR('/dev/null')
  
  START SERVICE(SLEEP)
  
  DIS SVSTATUS(SLEEP)
  AMQ8632: Display service status details.
     SERVICE(SLEEP) STATUS(RUNNING)
     PID(7798920) SERVTYPE(SERVER)
     STARTDA(2015-02-13) STARTTI(05.03.59)
     CONTROL(MANUAL) STARTCMD(/bin/sleep)
     STARTARG(1000) STOPCMD(/bin/kill)
     STOPARG(-9) DESCR( )
     STDOUT(/dev/null) STDERR(/dev/null)
  
  Here the MQ_SERVER_PID is null which should have been service
  process id.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All MQ v8 users using service functionality and using the
  process ID argument in the STOPCMD
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The variable substitution operation on the stop arguments in the
  service definition were being performed before the service was
  provided with a process id. Hence the process id was being
  assigned a null value and so the service could not be stopped.
  

Problem conclusion

• The product has been modified so that variable substitutions on
  the STOPARGS are performed after a process ID has been assigned.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.3
  
  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 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 BASE MULTIP

• Fixed component ID

  5724H7251

Applicable component levels

• R800 PSY

     UP