RE: fake out system

["Weatherly, Howard" <hweatherly@xxxxxxxxxxxx>]

Pat,

I'm not sure I am following your intent but from what I think I
understand, I believe you might loose the data.

If you just create your new spec with the new field, then CPYF the
data into it from the old file (you will need to tinker with the
mapping) then delete the old file and rename the new to the old name.

After that all you need to do is recompile programs using the
externally-described-file clause, save your COBOL names and make
whatever changes you need for the new field.

______________________________________________________________________
___
Howard Weatherly

hweatherly@dlis.dla.mil
howard.weatherly@ctg.com
hweath@ibm.net

X4324

 <<fake out system>>

---

• Subject: fake out system
• From: Pat Barber <MBOCEANSIDE@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Date: Thu, 24 Sep 1998 14:23:35 -0400

I have run into a small problem on a system that I have to Y2k
convert...

The system has many program described files, BUT, the one file that
requires
adding a new date format ccyymmdd doesn't have any more
space.....soooooo

I have thought about somthing along these lines:

1. create external specs for file with DDS adding new date field 
2. create a logical with an exact layout of internal described file
less
new field
3. rename external described file to some other name
4. rename logical to original internal described name

I'll still have to modify any program that uses dates but a lot of
them
don't
really use the date,,, so that cuts out a LOT of conversion time.....

As time permits, I'll go back and fix all programs to use new external
description....

Is there some downside to doing the conversion this way ??????
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

---