Re: Trigger blocking

[Rory Hewitt <rory.hewitt@xxxxxxxxx>]

Peter,

Actually, you didn't 'describe the mechanism' - you just said it '[...]the
trigger is designed to abort immediately where there is an exemption.'. I
don't know exactly what method you're using, and whether I or anyone on
this list can come up with a method which might be simpler or provide
better performance than what you're currently getting. I don't know whether
you're asking the question because you're simply looking for a supported
system solution or because your current user-defined solution isn't working
as well as you would like.

That all being said, the quick answer is that unfortunately, there is no
'system' means of disabling a trigger at the job-level.

Rory

On Wed, Aug 29, 2012 at 4:57 PM, Peter Connell <Peter.Connell@xxxxxxxxxx>wrote:

> Rory,
> There are always  concurrent apps that must not be blocked so option 1 is
> not possible.
> I've already described the mechanism I use instead of option 2.
>
> What I'm really asking is if IBM have since exposed a method to the user
> domain that can set some switch that they may already deploy within the
> system domain.
>
> Peter