|
Ok, "If the SETLL operation is not successful (no records found condition), the file is positioned to the end of the file." SetLL 0 finds no record, as there is no such thing, so the file is positioned to EoF. In a file where the first RRN is 2, SetLL 1 positions to the deleted RRN 1 record, not to EOF. (I'm guessing it positions to the deleted record, though I know it doesn't position to EoF.) SetGT 0 will accomplish, Lim, what you're looking to do with SetLL 0. Kurt Anderson Application Developer Highsmith Inc -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore Sent: Friday, October 20, 2006 2:06 PM To: RPG programming on the AS400 / iSeries Subject: RE: Using RRN 0 to do Setll on arrival sequence file Lim - the simple answer is that 0 (zero) is NOT a relative record number, so how can it position. Alan Shore NBTY, Inc (631) 244-2000 ext. 5019 AShore@xxxxxxxx rpg400-l-bounces@xxxxxxxxxxxx wrote on 10/20/2006 02:47:31 PM:
Read will fail after setll with rrn 0, which take us back to the original question of why would setll with rrn 0 set the cursor to end of file. It should set to the beginning of file according to setll documentation. -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles Sent: Friday, October 20, 2006 1:36 PM To: RPG programming on the AS400 / iSeries Subject: RE: Using RRN 0 to do Setll on arrival sequence file Ah, but did you try doing a read after the setll with 0? It'd be interesting if the read works. Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121-----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai Sent: Friday, October 20, 2006 2:24 PM To: RPG programming on the AS400 / iSeries Subject: RE: Using RRN 0 to do Setll on arrival sequence file Uummm. For a non empty file, READ will be successful when cursor is at BOF. READ will failed when cursor is at EOF. The opposite applies for READP. So, for me, technically, they are not the same. -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche <clip> technically the begiining of the file is and "end of file" You can set on EOF from READP also. </clip> -- 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. -- 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.
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.