Re: Triggers

[boothm@xxxxxxx]

well... I think so too.  The issue of course (in my mind at least) is that
the trigger may be fired in the future by some unplanned and unexpected
change.  Currently the data is not updated via batch, sql or access, but
who knows what others may choose in the future.  What seems like a good
choice now could become a nightmare.
 

In <35E067BA.5A2FE57B@wt.net>, on 08/23/98 
   at 12:04 PM, Bob Larkin <blarkin@wt.net> said:

>Dave's comment makes sense. (I think)  The job that does the update in
>our environment is a batch job, one is started for each PC session. IThe
>one gotcha might be if you want to treat a PC job differently than a
>regular batch job. I do believe you get the updating program name in the
>trigger data. It would be possible to further identify the updating jobs
>attributes.

>Keep us informed as to your findings!
>Bob

>David Gibbs wrote:

>> Should be able to ... a trigger program runs in the same job as the program
>> that caused the trigger, doesn't it?

-- 
-----------------------------------------------------------
boothm@ibm.net
Booth Martin
-----------------------------------------------------------

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---