Vendor response

My Control Language for Files (CLF) product handles this type of situation
quite nicely. The command Read Record using
CLF<> allows
you to read by key using a list of key values with the KEYLIST keyword, a
structure containing the key values with the KEYSTRUCT keyword, the key
relationship desired with the KEYREL keyword, etc.

The READRCDCLF command is provided as part of the no-charge run-time of CLF
(base option) and can be used in conjunction with the Open File using CLF
command (also part of the base run-time). Using only the no-charge option
you would need to provide a structure describing the fields/columns of the
record being read (think program-described here).

Using the CLF precompiler (part of the fee-based option 1 of CLF), your CL
program could simply Declare the file using DCLFCLF (think
externally-described here), Open the file, and then start reading records
(sequentially, randomly, etc).

More information on the product can be found
here<> (and
various articles I've written over the years).

End of vendor response.

Bruce Vining

On Wed, May 30, 2012 at 1:45 PM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:

I have a CL loop as follows:

Load keyValue
goto Top

The OVRDBF positions the file ONLY the first time thru (apparently it only
positions for the NEXT file open).

How can I read the record that I need (using keys) several times in on CL


This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


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

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