|
Yes, the file is defined as keyed. To clarify the example scenario, let me add that RRN 950 in my sample file has key 'AC'. You are suggesting that the block of records as shown in RRN order in my original post would appear to the program in a block that looks like this: RRN Key 1 AA 7 AB 950 AC 4 BH 3 EG 5 WY 6 WZ 2 ZZ Did I read your statement correctly? Does IBM clarify this at all? If I wanted to test this, would an RPG DUMP show the number of blocks read, or would I see it somewher in the file's INFDS? --- Steve Landess <sjl_123@xxxxxxxxxxx> wrote: > If you have the file defined as Keyed, as shown in your 'F' spec, the block > of records will be in key order. Otherwise, AFAIK, they will be in RRN > order. > > Steve > > ----- Original Message ----- > From: "Dan" <dbcerpg@xxxxxxxxx> > To: <rpg400-l@xxxxxxxxxxxx> > Sent: Friday, February 27, 2004 10:38 AM > Subject: BLOCK(*YES) questions > > > > BLOCK(*YES) questions: > > > > FCMMASTER IF E K DISK block(*yes) > > > > Does BLOCK(*YES) bring in a block of records in sequential order from the > > file, or in keyed order? > > > > RRN Key > > 1 AA > > 2 ZZ > > 3 EG > > 4 BH > > 5 WY > > 6 WZ > > 7 AB > > > > In this scenario, will the block of records be in RRN sequence or in keyed > > sequence? > > > > RPG documentation is not, IMO, not very helpful in indicating how blocking > > occurs. > > > > The archives has a post that appears to support a block "by keyed > records": > > > > http://archive.midrange.com/rpg400-l/200212/msg00433.html > > > 2. Blocking is done is in sequence that the records are being accessed: > > > keyed or arrival. NBRRCDS is always done in arrival sequence. That's > why > > > the warning. > > > > I have found several posts that imply that blocking is by physical > sequence. > > But nothing that says this. > > > > Is there an IBM reference to this? > > > > TIA, > > Dan __________________________________ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools
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.