To determine if *disable is useful in triggers, stop thinking like a one person shop, and consider the separation of duties.
If I'm the programmer, I can create applications that add/remove triggers.
For security, I would want CRTPFTRG to be completely locked down, and only usable in the install of software.
The operations staff should only control whether they are enabled or disabled, and then only with good auditing.
CRTPFTRG could be a powerful tool for cracking.
Jim Franz

----- Original Message ----- From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, October 16, 2009 1:10 PM
Subject: Re: Trigger state: *DISABLED -- what the heck is that, and from whatOS revision, and what do I do about it?

Luis Rodriguez wrote:
Use CHGPFTRG File(FileName) TRG(TriggerName) STATE(*ENABLED)

This parameter allows you to activate or inactivate a trigger (instead of
deleting/recreating it).


Something like that MIGHT actually be useful.

IF it could be done while there were users in the file.

Unfortunately, I just found out that it can't. So it's no more useful
than just adding or removing the trigger (indeed, worse, because
PRTTRGPGM doesn't indicate anything about whether a trigger is
deactivated), and looks like the result of somebody in Rochester having
WAAAYY too much time on his or her hands.

And in this case, unless there's something else besides CHGPFTRG that
will put triggers into a disabled state, somebody at the customer went
to a LOT of trouble to turn Workflow off while making it LOOK like it
was still turned on.

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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].