×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Whoa!
Strange indeed.  You get the error on the continuation line by typing
anywhere, including a space in col 7.  It goes away if you type anywhere on
the first line, even a space in col 7.
V4R4 00147
V4R5 00231

EVAL works OK; it's only EVALR that does this.

Buck Calabro
Aptis; Albany, NY
"Nothing is so firmly believed as
 that which we least know" -- Michel Montaigne
Visit the Midrange archives at http://www.midrange.com

> -----Original Message-----
> From: Chris Bipes 
> Sent: Thursday, January 11, 2001 4:04 PM
> To:   RPG400 Help (E-mail)
> Subject:      EVALR & SEU
> 
> Has anyone come across an error in SEU when editing long EVALR
> expressions?  For Example
> c       evalr        result = %trimr(
> c                             %subst(inputfld:found+1:end - found -1))
> 
> When entering all is ok.  Now copy, still ok.  Now edit the sub string by
> changing the name of any of the variables.  SEU says
> "Either a valid Operation Code or Conditioning-Indicator entry must be
> specif..."
> 
> To clear the error, add a "+" at the end of the first line and press
> enter.  Now remove the "+" and press enter again.  No more error.  We are
> at 4.4 one cume back.  I have not been able to find a ptf for this strange
> behavior.  Anyone else run into this?  Know of a PTF to fix?
> 
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2026 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.