RE: %CHAR()

Sure, Ken that's just what we do.  10-15 'free format' eval statements
followed by a an EVALR and XLATE (set) or a MOVE followed by more evals.
Either way we are stuck with columnar RPG400 lines in the midst of RPGIV
code, not helping readability or maintenance one bit.

I'll try the edit code to put the zeros back in, but I never asked to have
them suppressed just converted to character format.

Tom Westdorp
AS/400 Senior Programmer/Analyst 
  
IBM Certified Specialist - RPG IV Programmer
IBM Certified Specialist - RPG IV Developer 
Certified Master RPG IV Programmer 
Internal Telephone # 04-6859
Voice: (702) 221-6859
Fax:    (702) 221-6881
tom.westdorp@stationcasinos.com 



-----Original Message-----
From: Ken.Slaugh@cm-inc.com [mailto:Ken.Slaugh@cm-inc.com]
Sent: Monday, November 20, 2000 2:52 PM
To: RPG400-L@midrange.com
Subject: RE: %CHAR()



If you got a proven set of calc that produce leading blanks then follow
them with XLATE opcode

' ':'0'   XLATE     YourField YourField

Ken Slaugh  (707) 795-1512 x118
Chouinard & Myhre, Inc.
AS/400 Professional Administrator/MSE
Client Access Specialist
http://www.cm-inc.com/


 

                    bmorris@ca.ibm.co

                    m                        To:     RPG400-L@midrange.com

                    Sent by:                 cc:

                    owner-rpg400-l@mi        Subject:     RE: %CHAR()

                    drange.com

 

 

                    11/20/00 01:40 PM

                    Please respond to

                    RPG400-L

 

 





> Date: Mon, 20 Nov 2000 11:10:27 -0800
> From: "Westdorp, Tom" <tom.westdorp@stationcasinos.com>
>
> This certainly seems to be an error to me, and it is the source of a lot
of
> remaining MOVE and/or XLATE statements in otherwise all eval form code.
> This surely does not improve readability to anyone's eye, although it
does
> require some documentation in the form "Do NOT change the following
MOVE(s)
> to Eval's or necessary leading 0's will be lost."
>>
>> - -----Original Message-----
>> From: M. Lazarus [mailto:mlazarus@ttec.com]
>> Sent: Saturday, November 18, 2000 4:10 PM
>>>
>>> Remove the blanks of with %trim
>>>
>>> %trim(%char(xxxxx))
>>> %trim(%editc(xxxxx:yyy))
>>> %trim(%editw(xxxxx:yyyy))
>>  There's no need to do that.  These BIFs do it for you already.

"This certainly seems to be an error to me ..."

Tom, what "this" do you mean?  I don't think you're talking about
%trim since that only deals with leading blanks, not leading zeros.

If you can't find an edit code or edit word to return leading zeros,
you might consider a subprocedure that returns the input value with
leading blanks changed to zeros.  Then you could remove those MOVEL
and XLATE lines, and just code this:

C         eval      x = leadingBlanks (%editc(num : 'N'))

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---