|
With CHGPF wouldn't you have to run that against each table with the modified field also? Yes, but what I think you are saying is that you can't run a simple ALTER table and it automatically determine what fields have changed and handle accordingly. That's true. I suppose that you could write a simple program to read SYSCOLUMNS in QSYS2 and ALTER TABLE all those that are different from your reference table. But there's a lot of people still lingering on the edges of the primordial swamp who name their fields different in every file which makes automation difficult. I guess they find IPROD LPROD TPROD much more readable than IIM.ITEMNUMBER ECL.ITEMNUMBER ITH.ITEMNUMBER and think that the S/36 had too many characters allowed (6) for variable names and miss the early versions of PC basic where many people used 1 or 2. Granted you still run into issues with MBM.ParentItem and MBM.ChildItem Rob Berendt
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.