× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Here's a long shot, try creating the file again.  Maybe the index didn't
get created properly the first time around.

I have similar code for logical files running without a problem.



Basil Zangare
Applications Specialist
Nikon Inc
1300 Walt Whitman Road
Melville, New York 11747
phone: (631) 547-4389
fax: (631) 547-4026
bzangare@xxxxxxxxx


-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Stafford
Sent: Monday, May 01, 2006 11:26 AM
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] Logical File Access

Yes, it is a true logical
No, not multiple logicals........

----- Original Message ----- 
From: "Winchester Terry" <terry.winchester@xxxxxxxxxxxxxxx>
To: "COBOL Programming on the iSeries/AS400" <cobol400-l@xxxxxxxxxxxx>
Sent: Monday, May 01, 2006 11:11 AM
Subject: Re: [COBOL400-L] 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.
>
>
>
>
> -- 
> This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)
mailing 
> list
> To post a message email: COBOL400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
> or email: COBOL400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/cobol400-l. 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.