RE: %trim

Barbara,

Do you mean that because a VARYING field is usually set to a length that
is at or close to the same length of the data, that the result is that
%trim has to do less work and therefore finishes quicker (typically)
than when it works with a fixed length field?

Bob

> -----Original Message-----
> From: rpg400-l-admin@midrange.com
> [mailto:rpg400-l-admin@midrange.com] On Behalf Of Barbara Morris
> Sent: Wednesday, July 17, 2002 2:21 PM
> To: rpg400-l@midrange.com
> Subject: Re: %trim
>
>
> JJW wrote:
> >
> > We recently had IBM do an analysis of some of our most
> > used programs in terms of CPU usage.  One of the things
> > they mentioned was that %trim was a big user of CPU.  Has
> anyone heard
> > this about %trim before?
> >
>
> %trim searches from both ends of the string to find the
> non-blank data. If the string is long and the data is short,
> repeated trimming can involve a lot of searching.
>
> To eliminate most of your trims -and- make your code nicer,
> consider using varying length fields, or at least varying
> length temporaries. When using varying fields, you normally
> only have to do at most one trim to get trimmed data into the
> field in the first place.
>
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L)
> mailing list To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>