AW: Trigger source or not

Hi,

This is my way to work:

- I use iSeries Navigator for creating almost all database objects (Tables,
Views, Indexes, Triggers, Stored Procedures, UDFs).
- After the creation of the objects, I use reverse engineering (position to
the object in iSeries Navigator, rightclick and generate SQL) to store the
SQL code in a physical source file member.
- Then I delete the database objects and recreate them from the physical
file member using the CL-Command runsqlstm (to make sure the sources belong
to the objects).

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
MKirkpatrick@xxxxxxxxxxxxxxxxx
Gesendet: Friday, September 07, 2007 00:06
An: Midrange Systems Technical Discussion
Betreff: Trigger source or not


To the list:
I have just started to work with triggers and was hoping some of you could
share your change management strategy regarding same. Do you use iSeries
Nav exclusively? Do you keep source members with DDL stmts to drop/create
your triggers? If so, do you keep these in the IFS? I do not have a CMS
so mine is a manual process. Any suggestions are welcome. Thanks.




This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
Unless you are the addressee (or authorized to receive for the addressee),
you may not use, copy or disclose to anyone this email or any information
contained in this email. If you have received this email in error, please
advise the sender by replying to this email, and delete this email
immediately. Please note that any views or opinions presented in this email
are solely those of the author and do not necessarily represent those of
Western Dental Services, Inc. Finally, the recipient should check this
email and any attachments for the presence of viruses. Western Dental
Services, Inc. accepts no liability for any damage caused by any virus
transmitted by this email.