|
Charles,About the reply from IBM... That just seems a little lame. Especially in light of the fact that I just Duped a production file with a Trigger to my personal Library; did not dupe the Trigger Program and despite the fact that the Trigger was pointing to a non-existent program, it still showed up as STATE: *ENABLED *OPERATIVE. Then duped the Trigger Program, which does reference files found only in the From Library and the Trigger State remained *ENABLED *OPERATIVE.
So why don't all the same arguments about Test Triggers possibly updating files in Production Libraries apply to DDS Descibed Files? And was there a definitive answer that this behavior was limited to Duping SQL Tables or under the right conditions, could this effect DDS Described Files as well? The Plot Thins....
Thanks, Mike
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.