Moot point in my case. Because everything in our production environment
has to go through change control, I am creating SQL source for each
create. Any changes to the underlying table will result in all the
being recreated anyway.
I am naming them in such a way that I know they were created for SQL and
not to expect any program references (not that there's anything wrong
You're more disciplined than we were, which is a good thing.
Our difficulty is that JD Edwards knows about the physical and it's own
logicals, but not about the ones added for performance purposes. The
promotion process in EnterpriseOne can involve a file regen, but this does
not recreate anything but E1's files. I haven't had time to dig into the
process to find what they do, and it wouldn't do us any good if we knew.
We have to live with it. You give up a lot of the bells and whistles of
OS/400 when working with an ERP package that supports multiple vendor
Please consider the environment before printing this e-mail.
This message and any attachments should be treated as proprietary to the sender
and confidential to the identified recipients and should not be disclosed to or
used by anyone other than the intended recipient unless pre arranged with the
sender. If you are not an addressee of this communication, have received this
e-mail by transmission error of the sender, recipient or due to another
originator by an error in transmission, you are hereby notified that any
disclosure, copying, use, distribution, or taking of any action in reliance on
the contents of this information is prohibited. In any such event, please
notify the sender immediately by contacting Spirax Sarco Inc., 803 714 2000 or
reply to this e-mail and then delete it from your system. Spirax Sarco Inc.
accepts no responsibility for software viruses and all recipients should check
for viruses before opening any attachments.