Re: Logical File Access

I suspect that logicals are treated slightly different 
from a low-level DB2 perspective but that should not
affect a higher-level language. Of course, stranger 
things have happened ;-) 

Is this truly a logical and not an SQL index?

Is it possible that you have more than one logical
on the system (e.g. a library list problem) or there
is a CCSID problem?  Maybe your Working storage is 
getting corrupted somehow...

I'm running out of ideas, especially since you've
spent time with the debugger and things appear ok.

Terry Winchester 
Programmer/Analyst
________________________________
The Raymond Corporation
terry.winchester@xxxxxxxxxxxxxxx 

> -----Original Message-----
> From: cobol400-l-bounces@xxxxxxxxxxxx 
> [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Stafford
> Sent: Monday, May 01, 2006 10:42 AM
> To: COBOL Programming on the iSeries/AS400
> Subject: Re: [COBOL400-L] Logical File Access
> 
> It is an X(15).
> No messages in the JOBLOG as it is not erroring out.
> Running the debugger, I can see the field values and all is 
> correct............
> 
> Are logicals treated differently that physical files??  I 
> have this same 
> (generically speaking) code running on several physical files 
> and have never 
> had this type problem.
> 
> 
                  <<code snipped for bandwidth>>

Confidentiality Notice:

The preceding e-mail message (including any attachments) contains information 
that may be confidential, protected by applicable legal privileges, or 
constitute non-public information. It is intended to be conveyed only to the 
designated recipient(s). If you are not an intended recipient of this message, 
please notify the sender by replying to this message and then delete it from 
your system. Use, dissemination, distribution or reproduction of this message 
by unintended recipients is 
not authorized and may be unlawful.