Re: SETGT *End/*Start -- RPG400-L

Just to add 2 cents here but logically speaking, SETGT doesn't seem to fit
anyway. To me SETGT *START would position to the 2nd record just after
the start of the file. To me this would serve no real purpose. The SETGT
*END would position to the EOF one would think? This is of course if
these were valid options on SETGT. So it makes sense to me that those
special values aren't used with SETGT.

Ron Power
Programmer
Information Services
City Of St. John's, NL
P.O. Box 908
St. John's, NL
A1C 5M2
709-576-8132
rpower@xxxxxxxxxx
http://www.stjohns.ca/
___________________________________________________________________________
Success is going from failure to failure without a loss of enthusiasm. -
Sir Winston Churchill
Freedom is the right of all sentient beings. - Optimus Prime

"OPLink" <as400@xxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
2007/12/06 12:20 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>

To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: SETGT *End/*Start

Kevin, there are no F specs, just one C spec in the entire source file.
The error is focused on just the one line.
C *START SETGT ITEMBL

This one C spec works fine, doesnt draw the error message.
C *START SETLL ITEMBL

JoeM

----- Original Message -----
From: "Kevin Bucknum" <Kevin@xxxxxxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, December 05, 2007 8:59 PM
Subject: RE: SETGT *End/*Start

It is making it's decision based on the K in the file spec.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx

[mailto:rpg400-l-bounces@xxxxxxxxxxxx]

On Behalf Of oplink
Sent: Wednesday, December 05, 2007 8:51 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: SETGT *End/*Start

Mike, the seu message knows nothing about the file at this point, its

the

point of entry when I press enter that the message pops up.

Joe Pluta may be right, its just not acceptable to use *Start/*End

with

SETGT.

I understand its not feasible to list all outcomes that's not

appropriate

but I feel this should have been an exception, I could have lost a
paycheck
on this one!

You can replace with SETLL, or if your not concern with the nulls then

use

*Hival/*Loval along with SETGT.

I just didn't see that one coming. Still, I feel there's something im

not

seeing here.

JoeM

----- Original Message -----
From: "Mike Cunningham" <mcunning@xxxxxxx>
To: "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, December 05, 2007 6:01 PM
Subject: RE: SETGT *End/*Start

Are you files keyed logicals ?

On SETLL *LOVAL repositions at the start of a keyed file *START
repositions at the start of a non-keyed file
On SETGT *HIVAL repositions at the end of a keyed file *END

repositions

at

the end of a non-keyed file

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-

bounces@xxxxxxxxxxxx]

On Behalf Of OPLink
Sent: Wednesday, December 05, 2007 7:16 PM
To: RPG programming on the AS400 / iSeries
Subject: SETGT *End/*Start

We are on 5.3 and I can not use the *END or *START
with SETGT as shown below. In SEU the error message
RNF5318 pops up when enter is pressed. I can not find any
docs on the cause of error or that I can even use the *START/*END
with SETGT. However, they both work fine for SETLL.

Am I missing a PTF??

thanks
JoeM
-----------------------------------

C *START SETGT ITEMBL

Factor 1 entry has a data type that is not allowed for this

operation;

speci...

-----------------------------------
F1 on message line
-----------------------------------
Additional Message Information

Message ID . . . . . . : RNF5318 Severity . . . . . . . :

30

Message type . . . . . : Diagnostic

Message . . . . : Factor 1 entry has a data type that is not

allowed

for

this operation; specification is ignored.
Cause . . . . . : The Factor 1 entry (positions 12 - 25) must have

the

correct data type.
Recovery . . . : Correct the Factor 1 entry (positions 12 - 25).
Compile
again.
--
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.