Thank Alan.  I just want to make sure that I'm not missing some types of
PTF.

However, I'll have to disagree with IBM rpg team on this.  SETLL is
supposed to set cursor to the equal to or next closest value in file.
If I want to position to the eof of a sequential file, I should use *end
to do so.



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Friday, October 20, 2006 9:21 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Using RRN 0 to do Setll on arrival sequence file

Okay Lim, then I have to agree with what Kurt responded with. An RRN of
0, well no record exists, therefore (as per the IBM manual) the file is
set to end-of-file condition, and is positioned AT the end-of-file. From
this, you therefore CANNOT  use an RRN of 0.



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
rpg400-l-bounces+alanshore=nbty.com@xxxxxxxxxxxx wrote on 10/20/2006
10:08:18 AM:

Yes.  The first record has RRN of 1.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Friday, October 20, 2006 9:11 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Using RRN 0 to do Setll on arrival sequence file

Unfortunately you haven't really answered my question.
Can you physically look at the file in question? Is the first record 
rrn of
1 or rrn of 2.
Sounds a stupid question, I know, but please humor me



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx

rpg400-l-bounces@xxxxxxxxxxxx wrote on 10/20/2006 09:53:25 AM:

Yes.  Below is the actual test program.
In debug mode, eof gets set to *on and eof1 gets set to *off.

FBLPCUM    IF   E             DISK

D eof             s               n
D eof1            s               n

C     0             setll     BLPCUM
C                   read      BLPCUM
C                   eval      eof = %eof

C     1             setll     BLPCUM
C                   read      BLPCUM
C                   eval      eof1 = %eof

C                   eval      *inlr = *on

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Friday, October 20, 2006 8:52 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Using RRN 0 to do Setll on arrival sequence file

In your file, do you have a record with rrn of 1?



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx

rpg400-l-bounces@xxxxxxxxxxxx wrote on 10/20/2006 09:26:31 AM:

Yes.  I read the documentation and at that time I thought, and 
still

think, that is a wrong statement because one of the main purpose 
of setll is to set the cursor to the record that has the equal to 
or the next closest key value.

That statement seems to say that if there is no record that has 
the same key value in the file, setll will set the cursor to the 
end of the file position, which I think is a wrong statement.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx 
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of 
vhamberg@xxxxxxxxxxx
Sent: Thursday, October 19, 2006 5:38 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Using RRN 0 to do Setll on arrival sequence file

Yes, I think it is at least recommended - I would not have used 
the %eof to test what is done here. But this from the 
documentation is interesting and answers both the original
question and this one:

"If the SETLL operation is not successful (no records found 
condition), the file is positioned to the end of the file."

--
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.


--
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 thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2020 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].