Re: Default user ID in SQL table - trigger

[Alan Campin <alan0307d@xxxxxxxxx>]

Tried that. It will not work unless there are no locks on the table!! That
is what I thought to. Kinda limits it's usefulness doesn't it?

I think IBM reason for putting it on was to allow to disable a trigger at
restore or boot time. Like in our case, we have mirrored copies we don't
want triggers firing on so they disable them.

On Tue, May 19, 2009 at 1:36 PM, Crispin Bates <cbates@xxxxxxxxxxx> wrote:

> Alan, not sure which release, but CHGPFTRG STATE(*ENABLE/*DISABLED) is now
> available and allows the trigger to be disabled without removing it...
>
> ----- Original Message -----
> From: "Alan Campin" <alan0307d@xxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Tuesday, May 19, 2009 3:12 PM
> Subject: Re: Default user ID in SQL table - trigger
>
>
> >   4. The only way to disable triggers is to remove triggers from all
> >   tables.
> >   5. Triggers cannot be disabled except by removing the trigger from the
> >   table and then adding the trigger back.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.