Re: changing keys of a physical file

[rob@xxxxxxxxx]

Paul,

Actually in the DDS world you can use the command CHGPF and it 
automatically recompiles the file and migrates the data.

The problem with DDS vs SQL is that DDS doesn't contain all of the 
physical constraints, referential constraints, etc, and with DDS you would 
need a make program.  And, since DDS doesn't support many of these new 
features, then people get into a habit of not using them.

Once again, it's the use of the tool and not the tool itself that is a 
problem.  If you use a RUNSQLSTM or some such utility against stored SQL 
source then you will be no worse off than using DDS.  And probably better 
off because of the storage of the constraints, etc.

Rob Berendt
-- 
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)




PaulMmn <PaulMmn@xxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/22/2003 09:26 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Fax to

Subject
Re: changing keys of a physical file






Rob--

I want the original source, so when the programmers decide to change 
things around they can start from the last known good point.

I suppose that adding a field to a file using SQL to alter the table 
is 'better' than changing the DDS and recompiling the file, then 
migrating the data...

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx





>Rob Rote (in part):
>
>And who cares if you don't have the original SQL source?  The file should
>never get deleted, if so, you should have a backup of the file itself to
>restore it.  What does the original SQL source tell you that most
>utilities don't?
>
>Rob Berendt
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.