Re: blank variable

["Denis Robitaille" <DRobitaille@xxxxxxxxxxxx>]

Also, you should check the parameters of all the CALL statements. If the 
calling parameters do not match the received parameters, unpredictable result 
may occur (value changed in fields, programs bombed ...). This is caused by the 
fact that pointers are passed ans not the actual values

Denis Robitaille
Cascades inc.
Tel: 819-363-5187
DRobitaille@cascades.com

>>> Chris Rehm <Mr.AS400@ibm.net> 03/26 12:24 am >>>
** Reply to note from Wendy Chandler <wchandle@golden.net> Wed, 25 Mar 1998 
14:55:43 -0500 (EST)


> Using interactive debug, we see fields being populated properly. We break at 
> the write (to a physical file) and one of the fields is blank.  Nowhere in 
> the code is this field being updated between the population and the write.   
>    
> Any suggestions ?? 
>    
> Thanks, 
> wendy

Just the usual, trace the variable, check to see if it is coincident
in a data structure, check to see if the record format is being reset,
check to see if it is duplicated in another input record.

Stuff like that.


Chris Rehm
Mr.AS400@ibm.net 

How often can you afford to be unexpectedly out of business?
Get an AS/400.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com 
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---