RE: eval varylen = *blanks

I have not run accross this but then I always use the CLEAR optcode to
blank/Zero out a field. 

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

*Note to Recruiters
I nor anyone that I know of is interested in any new and/or exciting
positions. Please do not contact me.


-----Original Message-----
From: Jack Mullins [mailto:jmullins@sundash.com]
Sent: Wednesday, October 06, 1999 8:15 AM
To: RPG400-L@midrange.com
Subject: eval varylen = *blanks


Hello Everybody!

I ran into an odd problem (at least I think it is odd) a couple of days ago.
I was making some program changes using variable length fields in RPGIV.
The changes included using eval and *blanks to initialize the variable.
When I tried to run the program, it crashed.  I used debug to see what was
going on because the code looked good to me and I was surprised to find that
eval  varylen = *blanks resulted in a value of '############## for varylen
instead of '              '.  I modified it to use the move opcode instead
and it worked.  I then tried, unsuccessfully, to see if this "peculiarity?"
is documented anywhere.  Has anyone else run across this before?  Am I the
only one who thinks that this is weird?


73,

Jack Mullins
Sunergoline
P.O. Box 2026
Jonesboro, AR 72402
http://www.sunergoline.com
jackm@sundash.com
+---
| 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
+---