Re: STRDBG giving wrong data

Rajeev,

In a message dated 2/9/00 2:03:28 PM Eastern Standard Time, 
rajeevasthana@yahoo.com writes:

> I have a RPGLE program with 2 *entry parameters with lengths 256 and 512 
> respectively.
>  I'm debugging it to see their contents after the proper values are moved 
> into these *entry parms.   Now weird thing is happening.
>  When I see Parm1 (by F11) it shows the correct value. Now some value is 
> moved into Parm2. 
>  I see Parm2 now (by F11). It's Okay. But if I see Parm1 again, it's NOT 
okay.
>  It shows a value which is a overlap of Parm2 on it.  Why?

Perhaps Hans can expound on the underlying technical reasons for this 
long-time and _ABSOLUTELY RIDICULOUS_ behavior of long RPG parameters passed 
from CL (an explanation of 15 and 5 numerics would be nice, as well).  It's 
been going on since the advent of the AS/400, and the only way to fix it is 
to check the last position of the first parameter in the CL program prior to 
building the second, and inserting an "X" or some such in that position if it 
is blank...

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"Anyone who is not liberal in their youth has no heart.  Anyone who is not 
conservative in their adulthood has no brain." -- Winston Churchill
+---
| 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
+---