Re: Trigger question

[James Lampert <jamesl@xxxxxxxxxxxxxxxxx>]

Bill Meecham wrote:
> You could test if you are in batch or interactive before calling your interactive programs.
>
> RTVJOBA    TYPE(&INTERACTIV)   /* when var is '1' it is interactive else it is batch /**/

Generally, my rule of thumb for whether it's a good idea to use a 
trigger for a given problem is to apply these questions:

1. Is it a side-effect (or a conditional veto, or an integrity check) 
that needs to happen WHENEVER the file gets changed in a particular way, 
REGARDLESS of how, who, or with what application?

2. Is it something that can happen quickly?

Which is to say, I've written a recursive descent parser for a simple 
scripting language, in ILE RPG (the scanner is in ILE C), that runs as a 
trigger without causing more than a slight performance hit. And I 
routinely write trigger programs to cause the database in one of our 
applications to track changes in the database of some other application.