Triggers on files usually call subroutines that do something, update an audit file or check for consistency or add an item to a queue, for example. As long as the trigger subroutines are accessing local files in the test environment and the main trigger subroutines are cataloged globally, you should be fine. You can substitute any other called subroutines within the main subroutine locally and make them 'stub' programs if necessary. There is no reason to remove the triggers on the files with a plain 'cp' command. Just make sure that the subroutines are not updating production data anywhere and that all file opens are to local files in your test environment.
Shaun Ferguson Master Data Systems Analyst/Global Business Applications Wolseley plc - 12500 Jefferson Avenue - Newport News - VA - 23602-4314 T: (757) 989-2916 - F: (757) 989-2801 - E: [email protected] www.wolseley.com _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
