|
Charles, I guess I didn't make myself clear. I must use the same program. Embedded SQL requires mods to the rpg code and that's not an option. Valerio Vincenti IT Business Analyst County of Spotsylvania, I.S. Department Spotsylvania, VA 22553 Phone (540) 582-7055 Ext. 233 Fax (540) 582-9841 e-mail: vvincenti@xxxxxxxxxxxxxxxxxx >>> CWilt@xxxxxxxxxxxx 05/04/05 02:44PM >>> If all you're doing is reading a subset of the records. You'd be better off using embedded SQL. Charles Wilt iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Valerio Vincenti > Sent: Wednesday, May 04, 2005 2:10 PM > To: midrange-l@xxxxxxxxxxxx > Subject: Alternatives to build a LF on the fly > > > Hi group, > > I have a CASE tool (2E) generated rpg program that reads a > logical file > as input primary (READ loop). In some instances I need to run this > program against a subset of records only. I'm thinking of doing the > following at runtime in a CL program: > > 1) duplicate the physical file in QTEMP > 2) populate with the records that I need to process > 3) move QTEMP on top of the lib list > 4) build another versionof the logical file in QTEMP (based on the > physical in QTEMP) using the CRTLF command > CRTLF FILE(QTEMP/LOGICAL1) SRCFILE(SRCLIB/QDDSSRC) > 5) setup an OVRDBF for extra safety and invoke the rpg program > > I tested this and is working fine, but, I'm concerned with someone > making changes to the source file of the logical. Can anyone suggest a > method to create the logical without using the DDS? If > someone wants to > propose a different approach, I'm open to suggestions. > > TIA > > Valerio Vincenti > IT Business Analyst > County of Spotsylvania, I.S. Department > Spotsylvania, VA 22553 > Phone (540) 582-7055 Ext. 233 > Fax (540) 582-9841 > e-mail: vvincenti@xxxxxxxxxxxxxxxxxx > -- > 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. > > -- 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.
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.