RE: EVALR & SEU

I have noticed this type of behavior with CX-specs with continuation lines in
the past on VnRn's of several varieties.  And Buck's workaround is what I use,
too.

I chalk it up to coding in a modern language using a tool not built for it.

I wonder who maintains the syntax templates for SEU?  Is it the language labs?
 Or Rochester?

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
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
+---