× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Jeff,

I can't say that I remember seeing this myself.  But it seems to make sense.

When you say
Eval PrintInfo = *BLANKS

Just what do you what PrintInfo to have in it?  How many blanks: 0,1,2,5,10,
100...?  I'd guess it is getting the MAX length number of blanks.

Instead what you want is to set the field empty.  Try the following:
Eval %len(PrintInfo) = 0

HTH,
Charles


> -----Original Message-----
> From: Jeff Crosby [mailto:jlcrosby@xxxxxxxxxxxxxxxx]
> Sent: Monday, February 09, 2004 10:49 AM
> To: 'RPG programming on the AS400 / iSeries'
> Subject: Varying length field issue
> 
> 
> I've got a program where I build part of the print line in a 
> field called
> PrintInfo.  I decided to make this a Varying field (which I have used
> before) to avoid a lot of %Trim.  PrintInfo could be blank on 
> the printout,
> or it could have any number of different possibilities in it.
> 
> The output wasn't coming out right.  What I found is, if a 
> Varying length
> field is blank (because I cleared it first), appending to it 
> with an Eval
> does not work:
> 
> C                   Eval      PrintInfo = *Blanks 
>  * If there was a PO number, add that verbeage                  
> C                   If        MQCSPO <> *Blanks                 
> C                   Eval      PrintInfo = PrintInfo + ' PO#=' + 
> C                                         %Trim(MQCSPO)         
> C                   Endif                                       
> 
> Even though the second Eval statement is executed, PrintInfo 
> is still blanks
> afterward.  I temporarily put an "Eval PrintInfo = '.'" spec 
> in there so the
> field wasn't empty and then it works fine.
> 
> Can someone confirm the same behavior on another iSeries, namely that
> appending data to an empty Varying length field fails?  If this is the
> expected behavior, I'll have to try some other ways to do it. 
>  It doesn't
> make common sense for me to check every time whether the 
> field is blank
> before appending.
> 
> -- 
> Jeff Crosby
> Dilgard Frozen Foods, Inc.
> P.O. Box 13369
> Ft. Wayne, IN 46868-3369
> 260-422-7531
> 
> The opinions expressed are my own and not necessarily the 
> opinion of my
> company.  Unless I say so.
> 
> 
> 
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (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.
> 

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.