|
Rob, an easy test if you have authority to RSTOBJ. i'll have to get someone to do it for me. Thanks, Rick On 6/17/05, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote: > I don't believe it fires the trigger for each record on a restore. But > that would be a simple test. > > Your last paragraph is good. I forget why but we do keep our trigger > programs in the same library as the data files and keeping programs in the > file libraries is normally a no-no in our shop. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > rick baird <rick.baird@xxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 06/17/2005 11:02 AM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > cc > > Subject > Triggers, the library they reside in, and restoring the library > > > > > > > Hey all, > > I want to put a DB trigger on a few files, and have a few questions. > > It's standard operating procedure around here (pre-dates me by many > years) to back up an entire library during a critical posting step, so > that it can be restored and rerun if things go bad. please, no > comment on the efficacy of that particular practice. > > The files I want to trigger are in that library. My questions are: > > if a file is restored, does it fire the trigger for each record > restored? - i.e. should I remove the trigger before and re-add it > after, as part of the process of restoring the file? > > if a file with a trigger is restored, should the trigger be restored > with it - i.e. should the trigger reside in the same library as the > file (TRGLIB on ADDPFTRG command)? or does it matter? > > THanks, > > Rick > > -- > 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. > > > -- > 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. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.