IT14047: MQ TRIGGER MONITOR DOES NOT APPEAR TO TRIGGER THE DEFINED PROCESS WHEN RUN AS A SERVICE

APAR status

• Closed as documentation error.

Error description

• When defining a trigger monitor as a service, the trigger
  application is not launched when the trigger event occurs.  For
  example, if trigger  process is to open "notepad.exe", then
  notepad process does not appear to launch. However, the task
  manager shows notepad  in running condition as it has been
  launched as a background process.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All Users of MQ trying to lunch a process using Trigger Monitor
  when run as a service.
  
  
  Platforms affected:
  Windows
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  This behaviour is observed because of the design of how Windows
  service works. When the trigger monitor runs as a service, the
  launched process/application is run under the current user?s
  session. From Microsoft Windows Vista, and later versions,
  services are always run in background and any processes launched
  by the service are also run in the background.
  
  Accordingly, when runmqtrm runs as service ,it runs in the
  background . This means that the process triggered by runmqtrm
  also runs in the background.
  

Problem conclusion

• Clarification of this expected Microsoft Windows behaviour will
  be added to the WebSphere MQ  Information center sections in the
  following link.
  
  http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.
  mq.explorer.doc/e_triggermon_starting.htm
  

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

Applicable component levels