Thanks Simon, I appreciate your effort. That's pretty much
everything I need to know. ;)
Rick
On 6/19/05, Simon Coulter <shc@xxxxxxxxxxxxxxxxx> wrote:
>
> On 19/06/2005, at 2:23 AM, rick baird wrote:
>
> > When you say the trigger should be restored with the file, do you mean
> > the DB trigger event (TRGLIB parm) , or the trigger program (PGM
> > parm), or both?
>
> The trigger name and event information is stored as an attribute of the
> file.
>
> If the file and trigger program are in the same library and you RSTLIB
> they will be restored together.
>
> If you restore a file with triggers to a library other than the
> original library the triggers will be marked as inoperative unless both
> the file and the trigger are restored to the new library. This has to
> be done as part of the same restore operation.
>
> If they are in separate libraries you should ensure the trigger program
> is restored first although the system doesn't care until the trigger is
> fired so you can do it in a different order.
>
> Of course, the above presumes you are restoring on a system where these
> objects no longer exist or are damaged beyond use. If you are just
> trying to recover the previous state of the file and the trigger
> program is still OK then you do not need to restore the trigger
> program.
>
> Read the Backup and Recovery manual for more information regarding
> restoring files with triggers.
>
> Regards,
> Simon Coulter.
> --------------------------------------------------------------------
> FlyByNight Software AS/400 Technical Specialists
>
> http://www.flybynight.com.au/
> Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\
> Fax: +61 3 9419 0175 \ /
> X
> ASCII Ribbon campaign against HTML E-Mail / \
> --------------------------------------------------------------------
>
>
> --
> 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.
>
>