Re: Logical file order of records

On Thu, 2009-11-05 at 14:13 -0600, Bob P. Roche wrote:

The order they were entered in the file. Basically the record number.

From my observations, I agree about the record number. However,

REUSEDLT(*YES) can make this different from the order they were entered.

To be safe, specify the sequence any time you care about the sequence.

<horse category="hobby" action="trot">

In 1999, I changed date selection in an OPNQRYF statement to implement
the rule that years from 00 and on up are later than years 99 and on
down. And I added a then-next-year record to the input file and ran
the report. And the results were grossly different!

Investigation showed that the OPNQRYF statement did not specify
sequence at all, and the addition of one record made the results
come in a completely different sequence. This happened same way in
both the orignal and my first-changed OPNQRYF statements.

Like I said, if you care about the sequence, specify the sequence.

</horse>

Cheers,
Terry.

From:
Neill Harper <neill.harper@xxxxxxxx>
To:
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date:
11/05/2009 02:10 PM
Subject:
Logical file order of records
Sent by:
<midrange-l-bounces@xxxxxxxxxxxx>



If I have a unkeyed PF FILEA as follows:



Field1, Field2, Field3, Field4



I then have an LF LFA, with a non unique key of Field1,Field2,Field3



When there is more and one record with identical Field1,Field2 and Field3
columns, what controls the order of the remaining records.



Further to this, if I had 2 copies of FILEA in different libraries with
EXACTLY the same data in would you expect LFA in both libraries to show
the
records in exactly the same order?