Disabling Local Message Handlers
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Disabling Local Message Handlers
Is there any convenient way (that is, without hacking the Repository) to disable a local message handler for a job? That is, if one has created a local message handler (one that is not stored in the MsgHandlers directory), how can one disable its effect?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's created by right-clicking on the warning message in the job log, and selecting "Add rule to message handler..." then, in the dialog thus opened, choosing "add rule to local runtime handler for job jobname." Apparently the message handler is stored with the job (or log) properties, not with the global message handlers.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Solved
They DO show up in the Message Handler Manager if you've got the right job open in the log and with the "messages handled" event selected.
So much for multi-tasking.
Still to figure out where in the Repository these are stored, but that's a question for another day.
![Embarassed :oops:](./images/smilies/icon_redface.gif)
So much for multi-tasking.
Still to figure out where in the Repository these are stored, but that's a question for another day.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
OK, managed to track it down (by accident, since I was looking at the generated OSH from UNIX level. There's a file called Local.msh for storing local message handlers for the job, in the RT_SCnnn directory, where nnn is the job number. ![Cool 8)](./images/smilies/icon_cool.gif)
![Cool 8)](./images/smilies/icon_cool.gif)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I have found that message handler files are not exported to the dsx file.
When moving from development to production, the message handler files have to be copied to the production server.
Seeing that local message handlers are part of the RT_SCnnn directory, will they be exported to the dsx![Question :?:](./images/smilies/icon_question.gif)
When moving from development to production, the message handler files have to be copied to the production server.
Seeing that local message handlers are part of the RT_SCnnn directory, will they be exported to the dsx
![Question :?:](./images/smilies/icon_question.gif)
-------------------------
https://www.ssa.co.za
https://www.ssa.co.za
:D Good news. All the files in the RT_SCnnn folder are exported to the dsx, including Local.msh :D :D :D
-------------------------
https://www.ssa.co.za
https://www.ssa.co.za
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
OK, the answer to the original question is that it IS possible. There is a check box in the Job Run Options dialog. In the API there are two functions for enabling/disabling message handlers, named something like DSSetEnableGlobalMsg and DSSetEnableLocalMsg. Still trying to track down some documentation on these, but they can be found in job control code generated by a job activity for a job that has a message handler defined.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 9
- Joined: Thu Jan 15, 2004 8:49 am
DSSetEnableGlobalMsg and DSSetEnableLocalMsg
[quote="ray.wurlod"]OK, the answer to the original question is that it IS possible. There is a check box in the Job Run Options dialog. In the API there are two functions for enabling/disabling message handlers, named something like DSSetEnableGlobalMsg and DSSetEnableLocalMsg. Still trying to track down some documentation on these, but they can be found in job control code generated by a job activity for a job that has a message handler defined.[/quote]
Hi Ray,
You mentioned that it is possible to enable/disable message handlers using DSSetEnableGlobalMsg and DSSetEnableLocalMsg.
Would you please provide more information how to use them. In my case, I need to disable Project level message handler for a job.
Thank you,
--Katrin
Hi Ray,
You mentioned that it is possible to enable/disable message handlers using DSSetEnableGlobalMsg and DSSetEnableLocalMsg.
Would you please provide more information how to use them. In my case, I need to disable Project level message handler for a job.
Thank you,
--Katrin
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: