× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 23 Aug 2012 11:42, Stone, Joel wrote:
I am not insisting, but the project manager is :)

rob@xxxxxxxxx on Thursday, August 23, 2012 1:26 PM wrote:

Well, if you aren't insisting on being able to read it in RPG with
CHAIN or READ <<SNIP>>


Although possibly not a valid representation per the example not being "a product file nor UPC but it is simple to explain", given the representation of the file and data from the DDS MFLF example in a prior message at http://archive.midrange.com/midrange-l/201208/msg00846.html , a SQL derived INDEX could achieve the single record format, but not a Record Format that is the "same" as the physical file stated as desirable in that same message. The format may possibly be sufficiently compatible when using [note: I am not recommending use of] LVLCHK(*NO). The following assumes the given data will always be a zero-value in one field and a non-zero positive value in the other field for each row:

create index ProductByUPC1or2
on ProductByItem#
( abs( UPC1field - UPC2field ) AS upc )
/* the above key expression, perhaps best CAST; e.g. in DEC() */
rcdfmt ProductRec ADD ALL COLUMNS

A SQL UNION [ALL] VIEW as the QRYFILE() of an OPNQRYF with both the desired KEYFLD() and FORMAT() specified for the ODP could also suffice.

Very possibly, the sample scenario given does not accurately enough describe the actual scenario, such that the above is worthless.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.