|
I found a solution to this problem, and wanted to share it with the group. The file I was using for output had two (and later three) LFs over it. Even though the PF was not keyed, and there were no unique keys, just having an LF over a PF sometimes prevent this blocking. Once I removed the LFs, the blocking worked. I set up my pgm to build the LFs in QTEMP after all records were written to the file. If this sounds like a strange workaround, see the 'Memory allocation thread' -- This is the same module. Thanks for all the help!!! On Mon, 8 Nov 2004 16:02:39 -0800, Tony Carolla <carolla@xxxxxxxxx> wrote: > Actually, the file is not created with the unique keyword, nor are any > of the (2) logicals built over the file. There are fields named > uniqueID, but I am not using the unique keyword. > > > > Thanks. > > On Mon, 8 Nov 2004 13:24:00 -0500, cwilt@xxxxxxxxxxxx > <cwilt@xxxxxxxxxxxx> wrote: > > Tony, > > > > If the physical (or any logical over the physical?) has a unique key. The > > blocking is turned off. Otherwise the DB would not be able to ensure > > uniqueness. > > > > HTH, > > > > Charles Wilt > > iSeries Systems Administrator / Developer > > Mitsubishi Electric Automotive America > > ph: 513-573-4343 > > fax: 513-398-1121 > > > > > > > > > > > -----Original Message----- > > > From: Tony Carolla [mailto:carolla@xxxxxxxxx] > > > Sent: Friday, November 05, 2004 1:40 PM > > > To: RPG programming on the AS400 / iSeries > > > Subject: Output record blocking > > > > > > > > > I have written a program that is doing output to a file. The output > > > file is declared as such: > > > > > > FRvp1 O E Disk ExtFile('DMME/RVP1') > > > F Block(*Yes) > > > F UsrOpn > > > > > > When writing to this file, if I look at the 'Display Open Files' > > > display for the job, the I/O Count and Relative Record number for this > > > file stay the same. As I understand, this means that the program is > > > performing one write operation for each WRITE op that is executed in > > > the program (not using blocking). > > > > > > I have no overrides to the file, and I am simply usign the WRITE op. > > > The only two things that might be causing it are: > > > > > > 1) I am writing from a DS, i.e. > > > Write Rrvp1 RvpOut; > > > The DS was defined: > > > D RvpOut DS LikeRec(Rrvp1:*Output) > > > > > > 2) I have the same file opened for input with a different F-spec: > > > FRvp1 O E Disk ExtFile('DMME/RVP1') > > > F Block(*Yes) > > > F UsrOpn > > > > > > 3) I have two logicals over this file opened also, with > > > blocking turned off. > > > > > > When I look in the job log, I get the message: > > > Open of member RVP1 was changed to SEQONLY(*NO). > > > I have never understood that message, or what causes it. I have the > > > file declared with no 'K', so I don't understand why this message says > > > that I opened it in some 'seuqential' way... But it might not be > > > related. > > > > > > I like things to run fast, and without record blocking on this > > > program, I know it could go faster. Has anybody else had this > > > problem? > > > > > > > > > > > > -- > > > "Enter any 11-digit prime number to continue..." > > > -- > > > This is the RPG programming on the AS400 / iSeries (RPG400-L) > > > mailing list > > > To post a message email: RPG400-L@xxxxxxxxxxxx > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l > > > or email: RPG400-L-request@xxxxxxxxxxxx > > > Before posting, please take a moment to review the archives > > > at http://archive.midrange.com/rpg400-l. > > > > > -- > > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > > To post a message email: RPG400-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l > > or email: RPG400-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/rpg400-l. > > > > > > -- > "Enter any 11-digit prime number to continue..." > -- "Enter any 11-digit prime number to continue..."
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.