Re: Table Definitions DDS or SQL?

I use the integrity features, triggers, etc.  Some people have experienced 
issues with duplicating objects to test libraries, like david gibbs of 
this list.  You may want to search the midrange-l archives for what issues 
he was having.

Now, I am probably going to regret this because the DDS naysayers will 
latch on to this with a death grip.  And a grip they would quickly dismiss 
if it was DDS files that were having the issue and not SQL created files. 
Then again it may not be a DDS vs SQL issue but more of a use of the 
integrity features issue.  But here goes...
I have a constant battle with the files in QMGTC2 getting corrupted. 
Happens an awful lot.
DSPOBJD OBJ(*ALL/*ALL) OBJTYPE(*ALL) OUTPUT(*OUTFILE) 
OUTFILE(*CURLIB/OBJLIST)
...
MCH3402-Tried to refer to all or part of an object that no longer exists.
CPD32BF-File is logically damaged.
File AUTH_00001 in library QMGTC2 with constraint AUTH_CONSTRAINT_PKG_FK 
is logically damaged.

Happens so often that I've put procedures in place to save that library to 
a save file and just delete all damaged objects just prior to doing a GO 
SAVE-21.  Tired of that save blowing up on this library.


Rob Berendt