I hate when that happens - divide and conquer - yuck!
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.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Victor Hunt
Sent: Thursday, April 05, 2012 2:14 PM
To: Midrange Systems Technical Discussion
Subject: Question on updating some OLD programs
I do apologize in advance for asking about something most folks dealt with
years and years ago...
I have a large number of programs in our sales reporting system that were
written a very long time ago. We are in the beginning stages of upgrading
them. In most cases, these programs have program defined files. In almost
all cases, the file name is something like SALES. There isn't a file on our
system called SALES. There are however files called SALES2012, SALES2011,
etc. The CL has an OVRDBF command to point SALES to the appropriate
SALESYYYY file for processing. Of course, this is variable as any SALESYYYY
file going back 10 years can be selected by the user.
As part of the upgrade, we'd like to change all program defined files to
externally defined files. Unfortunately, the file SALES doesn't exist so
compiles would fail. I could change them all to SALES2012, but at some
point this file won't exist either. I can create an empty file named SALES
with the same layout and no records, but this still has it's problems
(there are many programs where the file is defined more then once, SALES1
and SALES2, for summary processing).
What is the best way to handle this situation? We are on 7.1 by the way if
it makes any difference in how we would handle this.
This thread ...
RE: Question on updating some OLD programs, (continued)
This mailing list archive is Copyright 1997-2020 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