Re: CODE edit problem

["SamL" <lennon_s_j@xxxxxxxxxxx>]

Yes, I've noticed this too.  If you syntax check the file it goes away.
It is annoying and time wasting.

Sam

----- Original Message -----
From: "Siegrist, Dawn (CAP, PTL)" <Dawn.Siegrist@penske.com>
To: "CODE/400 List (E-mail)" <CODE400-L@midrange.com>
Sent: Friday, August 17, 2001 4:09 PM
Subject: CODE edit problem


There appears to be a bug in the syntax error checking within CODE/400.
Here is the lines of code.  It appears to happen when the eval statement
spans more than 1 line of code and you add something to the second line.

     C                   if        not *in19 and dhword = *blanks and
     C                             dhunzs = wwunit and xx = yy
RNF5272E Either a valid Operation Code or Conditioning-Indicator entry
must
be specified.

The code in blue was added to the line.  The code compiles just fine on
the
AS/400.

I am using WDT/400 v5r1 on a W2K machine.

Dawn Siegrist
Sr. Programmer/Analyst
Penske Truck Leasing
610-775-6243
Dawn.Siegrist@penske.com


_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com