|
Chapin, I agree that SQL and SQLRPG could be a solution, but as you said, I would like to avoid copying to a second file. How would I avoid that with SQL/SQLRPG? FMTDTA is what we use now, but we've hit the max key length. Your suggestion is valid, and I've seen this technique used in our code, but I'm not sure that constructing the key value for each record is going to be any quicker than OPNQRYF, and I'm still stuck with a second file because the next "step" can't read an LF. I believe the possible solutions at the moment are the QLGSORT API or a QMQRY. Great tip, though! > -----Original Message----- > From: Kaynor@xxxxxxx > > The setup: > 1) Add a new text field called something like "sort field" to > your file. > Make it as big as the concatenated sort keys might need to be. > 2) Add a permanent LF ordered only by this "sort field." > NOTICE: This E-mail may contain confidential information. If you are not the addressee or the intended recipient please do not read this E-mail and please immediately delete this e-mail message and any attachments from your workstation or network mail system. If you are the addressee or the intended recipient and you save or print a copy of this E-mail, please place it in an appropriate file, depending on whether confidential information is contained in the message.
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.