RE: Triming CL stings?

I'm surprised someone hasn't mentioned that REXX could do this with
style and ease..... <vbg> Actually, I haven't a clue if it does or
doesn't, but REXX usually comes up whenever we have these CL kludge
threads.

Just fanning the flames... <g>

Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, January 14, 2009 9:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: Triming CL stings?

If you're concern is only with the one on the left, not the right.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
Nick_Radich@xxxxxxxxxxxxxx
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
01/14/2009 10:28 AM
Subject:
Re: Triming CL stings?
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



But, then couldn't you do the *TCAT thing in your CL to trim the
trailing
blanks off?



Thanx,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/14/2009 08:54 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Triming CL stings?






Adam,

Hey the RPG subprocedure sounds nice but has some implementation issues.

For example if I do
CALLPRC PRC(Trimmer) PARM((&FROMSTRING)) RTNVAL(&TRIMMED)
and Trimmer is a subprocedure in a RPGLE module or service program then
it


still isn't right because CL doesn't support varying length fields. At
best it would just trim off the leading blanks. You would have to add
further logic after the CALLPRC.

Rob Berendt