Disabling Local Message Handlers

[ray.wurlod]

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?

[DSguru2B]

If the local message handler is viewable in the message handler manager, then the logs can be suppressed, if this is what you are looking for.

[ray.wurlod]

They're not viewable in the Message Handler Manager.

[DSguru2B]

Ray, Out of curiousity, is this handler custom built or a customized add-in.?

[ray.wurlod]

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.

[ray.wurlod]

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.

[ray.wurlod]

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.

[DSguru2B]

Learnt a new thing
Thanks Ray.

[BIuser]

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

[DSguru2B]

I highly doubt it. Never tried it though. Give it shot.
You will have to explicitly copy the rules from Local.msh of your dev server to the same file on your production box.

[BIuser]

:D Good news. All the files in the RT_SCnnn folder are exported to the dsx, including Local.msh :D :D :D

[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.

[katerina_se]

[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

[ray.wurlod]

I was never able to find any documentation. You can infer usage of these functions by inspection of the generated job control code in a job sequence.