RE: Moving a field and removing blanks

[Kurt Anderson <kurt.anderson@xxxxxxxxxxxxxx>]

If you have a field the following field:
FIELDA = "1234     "

And you want to put 89 at the end to give a value of "1234   89", then saying EVALR FIELDA = '89' is not going to do it. 

All of the substring solutions appear fine.  I was just taking issue with Vern's statement to ignore using the substring functions and simply do plain EvalR (as per his example).

-Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Wednesday, December 01, 2010 9:07 AM
To: 'RPG programming on the IBM i / System i'
Subject: RE: Moving a field and removing blanks

All of these solutions will, as far as I can see.  If they don't the result won't be as sought.  Do you really care that the field is momentarily blank, since there's no chance to intercept it in that condition?  Or maybe I don't understand your objection.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Shin bone: (n) A device for finding furniture in a dark room. 
> However the OP wanted to retain data that is in the result field.  
> Eval or EvalR will clear the field before assigning the value.
>
> -Kurt
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l- 
> bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
> Sent: Wednesday, December 01, 2010 8:09 AM
> To: RPG programming on the IBM i / System i
> Subject: Re: Moving a field and removing blanks
>
> But EVALR trumps them all - as other posts have suggested. No 
> intermediate field - no substring - no length function.
>
> It came out in V4R4, so far as I can tell, so everyone should be able 
> to use it.
>
> Nothing much cleaner than
>
> evalr text = %trim(text);
>
> Vern
>
> On 11/30/2010 9:59 PM, Joe Pluta wrote:
> > On 11/30/2010 5:56 PM, Alan Campin wrote:
> > > VaryingField30 = %Trim(Field30);
> > > %Subst(Field50:
> > >                (%Size(Field50) - %Len(VaryingField30)) + 1:
> > >                %Len(VaryingField30) = VaryingField30       ;
> > Without intermediate field:
> >
> > %Subst(Field50:
> >          (51 - %Len(%Trimr(Field30))):
> >          %Len(%Trimr(Field30)))
> >      = %Trimr(Field30);
> >
> >
> > With an intermediate field, Alan's is probably the best.  And even 
> > overall, I like Alan's because it only trims the field once.  That's 
> > worth the tradeoff of an intermediate field.  Note that either 
> > method will require you to check for a blank string; if Field30 is 
> > all
> blanks
> > either of these will give you an RNX0100 string position error.
> >
> > Joe
> --
> 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.
>
> --
> 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.