RE: OPNQRYF a flat file?

Have you tried to create a definition using IDDU and then LINK the file to the IDDU definition?  I am still stuck with our aging AR system that was written on a 36.  We have linked the files and can query them.  NOT SQL but Query400.  Another trick is to create a native LF using the SST to define the fields.  Ok they are all character but readable if using zone decimal.  You can even use SQL against the LF.  Just remember to build the selection fields as character fields, mapping packed as hex.

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.  Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: D.BALE@handleman.com [mailto:D.BALE@handleman.com]
Sent: Wednesday, February 28, 2001 9:10 AM
To: MIDRANGE-L@midrange.com
Subject: OPNQRYF a flat file?

Can OPNQRYF be used on a non-externally described flatfile?  The flatfile maps
to a file that is externally described, and will eventually be copied to files
with the externally described format, but first I have to run the flatfile
through OPNQRYF to determine all the unique release numbers found in the file.
 Note that ASNPK is the externally described file and DANBALEZ is the
non-externally described flatfile.  ORRNPK is the Release Number field,
defined as 7-digits, zoned decimal.