|
I've found a number of syntax checking errors in Code. They're a pain sometimes. I'm on V4R5M1. Did they fix the EVAL(H) problem yet? Thanks, Mark Mark Walter Sr. Programmer/Analyst Hanover Wire Cloth a div of CCX, Inc. mwalter@hanoverwire.com http://www.hanoverwire.com 717.637.3795 Ext.3040 "Siegrist, Dawn (CAP, PTL)" To: "CODE/400 List (E-mail)" <CODE400-L@midrange.com> <Dawn.Siegrist@pen cc: ske.com> Subject: CODE edit problem Sent by: code400-l-admin@mi drange.com 08/17/01 04:09 PM Please respond to code400-l 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
As an Amazon Associate we earn from qualifying purchases.
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.