I'm with Joel. This sounds like a good strategy.

(Note that you will need to analyze your files to determine if you have blanks in any packed fields...)

- sjl


Joel wrote:
I hate when that happens - divide and conquer - yuck!

My suggestions:

1) Place all years of data in one SALES-ALL-YEARS file, with added key at end to uniquely identify year (as others suggested)
2) Create a logical file for 2012 named SALES2012, which selects only 2012 records (leave off the YEAR field on these, or level check *NO of you are feeling lucky)
3) Same for other past years that pgms need to touch (SALES2011, SALES1010, etc)
4) Create one empty SALES file for compiling

At this point, all production jobs will still function, because the files will be named as expected

Over the course of days, months, (or years as can happen), you can take your time and modify pgms to handle externalizing the files and setting the selection date criteria.

5) last step, when all pgms have been modified to use the SALES-ALL-YEARS file, delete the LFs.





This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].