RE: %subst problem

Peter, you may be right but I think they knew that the inv. Number will
'always' be 10 pos. but I will check out your idea.
Thanks,
Phil

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Peter.Colpaert@xxxxxxxxx
Sent: Monday, June 04, 2007 9:01 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: %subst problem

Phil,

your problem is obvious:

the parameters of %subst are

String
start position
length

whereas you have end position as the last parameter.

I assume you want %subst(J8_Comment::30:10) instead of
%subst(J8_Comment::30:39)

HTH,

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we. Futile is resistance, assimilated will you be.
-----



"Phil Kestenbaum" <pkestenbaum@xxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
04/06/2007 14:57
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


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

Subject
%subst problem






This statement is blowing up. However during a debug, I have values in
both nStartPos anf nEndPos and they appear to be correct, 30 and 39,

This is where we get an invoice number. J8_Comment has contents and they
are what they should be. I am not sure what is wrong at this point.



eval J8_Comment = %subst(J8_Comment : nStartPos

nEndPos)





Yet I am getting this fatal error:



Message ID . . . . . . : RNX0100 Severity . . . . . . . : 50


Message type . . . . . : Diagnostic


Date sent . . . . . . : 06/04/07 Time sent . . . . . . :
08:52:03




Message . . . . : Length or start position is out of range for the
string

operation.


Cause . . . . . : One of the following has occurred in RPG procedure


in program xxx/yyy:


- A numeric length or start position is less than 1 or too large for
the

string operation.


- The search-argument parameter of the %SCAN built-in function has
zero

length or is longer than the source-string parameter.


- The maximum-length parameter of the %STR built-in function is not a
value

between 1 and the maximum size of a character field.



This message contains information proprietary to our company. It is
intended to be read only by the individual or entity named above or
their
designee.
Any distribution of this message or the information contained herein
without written permission from our company is strictly prohibited. If
the
reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are hereby
notified that you have received this document in error and that any
review, dissemination, distribution, or copying of this message is
strictly prohibited. If you have received this communication in error,
please notify us immediately by e-mail, and delete the original message.