MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » April 2014

Re: MIDRANGE-L Digest, Vol 13, Issue 525



fixed

Yep, Eric - I shoulda mentioned both posts.

I was just responding to the unnecessary (in my mind) idea of going into RPG when he already had a couple SQL-only solutions.

Cheers
Vern

On 4/7/2014 4:52 PM, DeLong, Eric wrote:
My reply also had a function in SQL to reformat the field data...

I guess I'm still not sure what problem Buzz needs to solve.

-Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Monday, April 07, 2014 3:21 PM
To: Midrange Systems Technical Discussion
Subject: Re: MIDRANGE-L Digest, Vol 13, Issue 525

Buzz

One of the other replies gives you a solution without going to RPG - I
think - the one with the REPEAT function.

That one gets the length of the fully-trimmed value and uses that to get
the number of leading blanks you need.

Good luck!
Vern

On 4/7/2014 3:17 PM, Buzz Fenner wrote:
On Mon, 7 Apr 2014 16:50:41, Eric DeLong wrote:

How did you define "field"? If it is NOT varchar (or DDS Varying), then
the trim will be ineffective, due to >the fixed length default behavior of
padding blanks.

Hmm, unfortunately it's not Varying so I may have to resort to a small rpg
program where I can get the data into a varying field and do the string
manipulation.

Thanks...









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact