In 7.1 there is something called EXTDESC (as well as EXTFILE).
EXTDESC can be used in compiling

Try googling
AS400 EXTFILE EXTDESC
And look at the results here
http://publib.boulder.ibm.com/infocenter/iadthelp/v7r1/index.jsp?topic=/com.ibm.etools.iseries.langref.doc/c0925086322.htm


Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Victor Hunt
Sent: Thursday, April 05, 2012 3: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 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.


Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.