|
Dave - thanks for your responses. Much appreciated. >>> "Kahn, David [JNJFR]" <DKahn1@JNJFR.JNJ.com> 09/13 11:28 AM >>> Alan, In that case another possibility is to use file overrides at compile time and run time. In your program you still define bigfile and weefile. Then you issue an OVRDBF BIGFILE QADSPUPB and OVRDBF WEEFILE QADSPUPB. The problem with doing this is that you either need to compile interactively or write a CL wrapper to execute in batch and create the program. In your run time environment you might as well use the names bigfile and weefile (or more sensible ones) as the actual output file names in QTEMP thereby avoiding run time overrides. If you're planning to put both files in QTEMP they'll need different names from each other anyway. And if you call one of them QADSPUPB you'll need a run time override for that to prevent the system trying to open the memberless one in QSYS. Compared with the effort of having a compile time override the one-time overhead of creating 2 extra files is negligible. These only need to exist for compile purposes and can be empty. At run time you can still put your files into QTEMP as you plan. Dave Kahn Johnson & Johnson International (Ethicon) France Phone : +33 1 55 00 3180 Email : dkahn1@jnjfr.jnj.com (work) dkahn@cix.co.uk (home) -----Message d'origine----- De: alan shore [mailto:SHOREA@dime.com] Date: 13 September 1999 14:56 À: RPG400-L@midrange.com Objet: Re: RE: RE: Duplicate file format Sorry if this caused some confusion. You are right, the example I gave was what I would like to see in RPG. There is no problem as such, but if this was available in RPG, creating other files using the same format would NOT be required, thus saving some overhead. The procedures I am writing may need to be used by different people at the same time, so to circumvent any possibility of duplicate files I am equating ALL files to QTEMP, therefore the external copy is not really required, but the internal copy is Hence my request of one format being used more than once internally within a program. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.