| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Ending runmqldq Dead Letter Handler on AIX |
« View previous topic :: View next topic » |
| Author |
Message
|
| wolstek |
 Posted: Wed Sep 08, 2004 1:55 am Post subject: Ending runmqldq Dead Letter Handler on AIX |
 |
|
Acolyte
Joined: 25 Jun 2001
Posts: 52
Location: Bristol, UK
|
Does anyone know how to bring down a Dead letter Queue Handler GRACEFULLY on an AIX system.
I have found no references to commands that might do this and have therefore resorted to a unix "kill" on the process. However only a "kill -9 processid" actually ends the process, softer kills do not. Any type of kill generates FDC reports and errors in the log
which is not really acceptable in a production environment.
I had originally thought that I could use the WAIT(NO) or WAIT(nn) keyword in the rules table to end it normally and then use triggering to re-invoke when a new message arrived. However I could not get triggering to work and then saw an item in this forum (31st July 2002) than said that triggering doesn't work as runmqdlq doesn't support the MQTMC2 header. I couldn't even get a script to invoke it correctly as suggested in the topic
Any help gratefully received; firstly on ending an existing process or secondly sample scripts and triggering config to enbable a trigger on the DLQ
Many thanks |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Wed Sep 08, 2004 2:09 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The easiest way to end runmqdlq is to set the WAIT attribute.
The next easiest way is to set the GET attribute of the DLQ it is reading to DISABLED. The app will then end. The DLQ can then be reset to ENABLED.
As far as triggering is concerned, runmqdlq does not need to support the MQTMC2 structure.
The command string passed by the trigger monitor to the operating
system is built as follows:
1.The ApplId from the PROCESS definition.
2.The MQTMC2 structure, enclosed in quotation
marks
3.The EnvData from the PROCESS definition
So, set ApplId to 'runmqdlq DLQ QMGR'
and set EnvData to '< rules_table'.
runmqdlq will use the DLQ name and QMGR name passed in ApplId, the MQTMC2 structure will be ignored, because runmqdlq does not read a 3rd argument, and the rules will be read from the redirected stdin. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
