Re: Adopted authority and triggers

Is there any recommendation for a duplicate file set? That is, as in our case, there are separate libraries for separate companies. FILEA may have a trigger, but FILEA exists in both LIBA and LIBB.

I'm not a trigger aficionado by any means, so this may be a naive question: What is the problem with having the trigger program in a separate library from the file? That is, I can understand that you want to be sure that the program library is always available when the data library containing the triggered file is present. And I understand that one's restore strategy would have to insure that both libraries are restored. But is there any requirement as to the order of the restore? Data library first, or program library first? I have gathered that the recommendation is to keep one from shooting ones self in the proverbial foot (i.e., restoring only the data library). Corrections to this outlook greatly appreciated.


* Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Winchester Terry wrote:

As I understand it, when the library is saved
the trigger program will also be saved along
with the physical file. This will ensure that
there are no problems when restoring the library...

Terry Winchester Programmer/Analyst
________________________________
The Raymond Corporation
terry.winchester@xxxxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian
Sent: Wednesday, April 04, 2007 10:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: Adopted authority and triggers

Why is it recommended that the trigger program reside in the same library as
the physical file it is attached to?



On 4/4/07, Ed Fishel <edfishel@xxxxxxxxxx> wrote:

Yesterday afternoon I found these recommendations in the information
center.

<snip>

Create the program in the physical file's library.

</snip>

Ed Fishel,

edfishel@xxxxxxxxxx

--
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.

Confidentiality Notice:

The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is not authorized and may be unlawful.