Re: Converting Case with a Varying Field

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Do you get the same error with just
Eval      XXXDTA = CvtToUpper(%trim(MYFIELD))

If not, I'd guess that using the same variable for input & return is
the problem...

RPG's CONST can only be enforced when all callees are RPG.  Since the
end caller is an API...that isn't true.

While the compiler will sometimes make a copy of a variable, it only
does so if it has too.  In your case, since the variable types and
size match the prototype, it doesn't have to and will pass the address
of XXXDTA directly; expecting the callee to abide by the CONST option.

HTH,
CHarles


On Mon, Aug 20, 2012 at 1:21 PM, Michael Naughton
<michael_naughton@xxxxxxxxxxxx> wrote:
> I've got an application where I want to convert various strings to (in this case) upper case. I'm familiar with the XLATE method, but I thought I'd try to find something more universal (dealing with accented characters, etc.), and I found CvtToUpper and
> CvtToLower procedures at http://www.iprodeveloper.com/article/rpg-programming/apis-by-example-a-better-case-converter-60657 that seemed to be just what I want.
>
> CvtToUpper seems to work great, except for one thing -- if I pass it a blank field, after it's done some of the fields in my program have (apparently randomly) been filled with blanks (I discovered this because if one were numeric I'd get a decimal data
> error).
>
> I'm using this prototype for the procedure:
>
> D CvtToUpper      Pr         32765    Varying
> D                            32765    Const Varying
> D                              272    Options( *NoPass )
> D                               10I 0 Const Options( *NoPass )
>
> and this definition for the field that I'm passing:
>
> D  XXXDTA         S          32765    varying
>
> and I'm calling the procedure like this:
>
> C                   Eval      XXXDTA = %Trim(MYFIELD)
> C                   Eval      XXXDTA = CvtToUpper(XXXDTA)
>
> I've determined that if I remove "varying" from the definition of XXXDTA, then then everything is fine, but that seems like the wrong way to do it. Can anyone tell me why "varying" causes this problem? Alternatively, is there a better way to do what I'm
> trying to do?
>
> Thanks very much,
>
> Mike Naughton
> Senior Programmer/Analyst
> Judd Wire, Inc.
> 124 Turnpike Road
> Turners Falls, MA  01376
> 413-676-3144
> Internal: x 444
> mnaughton@xxxxxxxxxxxx
> ****************************************
> NOTICE: This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that any use is
> strictly prohibited. If you have received this e-mail in error, please notify us immediately by replying to it and then delete it from your computer.
>
> --
> This is the RPG programming on the IBM i / System i (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.