I traced the problem to some suspect information provided through an IBM
API.
Thanks for all the ideas.
Rich
--------------------------------------------------------------------------
On 6/26/2014 3:55 AM, Austin, Mark wrote:
Rich,
Check your code doesn't have a GO TO outside of the section it is in. This causes some very strange results.
Best regards,
Mark
-----Original Message-----
From: COBOL400-L [[1]mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: 25 June 2014 21:31
To: [2]cobol400-l@xxxxxxxxxxxx
Subject: Re: [COBOL400-L] CPF5009/5026?
Joel,
Thanks for the suggestion about removing the UNIQUE statement. I did that and changed the program by adding the WITH DUPLICATES stmt and ran it again and lo and behold there is a duplicate at the end of the file. Now I have to find out how that is happening. In my program, I'm just doing a read- write-read-write so this will be a hassle, but at least I now know where to look.
Rich
-------------------------
Quoting "Stone, Joel" [3]<Joel.Stone@xxxxxxxxxx>:
Are you using "SECTIONS" in the code? Sometimes it can run thru
statements an extra time before ending.
Also, try removing the "UNIQUE" from the file and running the CBLLE
pgm, and see if the last record is a dup.
-----Original Message-----
From: COBOL400-L [[4]mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rich Loeber
Sent: Wednesday, June 25, 2014 2:27 PM
To: COBOL Programming on the iSeries/AS400
Subject: [COBOL400-L] CPF5009/5026?
I have a CBLLE program that is creating a file with a 5 part unique key.
In the program, I have the file set as:
organization is indexed
access is random
record key is externally-described-key.
The file is cleared before starting and is opened as an output file.
There is a single write statement to the file with a check for a
duplicate
key. I have absolutely confirmed that there is no way that a
record with
a duplicate key is getting generated, but after writing the last
record to
the file, it is leaving a CPF5009/CPF5026 in the joblog. The job
goes on
to the next step and produces the right output, but I'm trying to
get it
to stop issuing the error codes. The file is set to reuse deleted
records, but I've tried it by removing that setting and it still
throws
the error codes.
Any ideas?
I'm running IBM's 6.1 version of the OS and am current on PTFs.
Rich Loeber - @richloeber
Kisco Information Systems
[1][5]
http://www.kisco.com
References
Visible links
1. [6]
http://www.kisco.com/
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list
To post a message email: [7]COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [8]
http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: [9]COBOL400-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
[10]
http://archive.midrange.com/cobol400-l.
______________________________________________________________________
__ This inbound email has been scanned for all viruses by the
MessageLabs SkyScan service.
______________________________________________________________________
__
______________________________________________________________________
This outbound email has been scanned for all viruses by the
MessageLabs Skyscan service.
For more information please visit [11]
http://www.symanteccloud.com
______________________________________________________________________
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list
To post a message email: [12]COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [13]
http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: [14]COBOL400-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
[15]
http://archive.midrange.com/cobol400-l.
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L) mailing list To post a message email: [16]COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: [17]
http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: [18]COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at [19]
http://archive.midrange.com/cobol400-l.
________________________________
"**Confidentiality**
The information contained in this e-mail is confidential, may be privileged and is intended solely for the use of the named addressee. Access to this e-mail by any other person is not authorised. If you are not the intended recipient, you should not disclose, copy, distribute, take any action or rely on it and you should please notify the sender by reply. Any opinions expressed are not necessarily those of the company.
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you.
References
Visible links
1. mailto:cobol400-l-bounces@xxxxxxxxxxxx
2. mailto:cobol400-l@xxxxxxxxxxxx
3. mailto:Joel.Stone@xxxxxxxxxx
4. mailto:cobol400-l-bounces@xxxxxxxxxxxx
5.
http://www.kisco.com/
6.
http://www.kisco.com/
7. mailto:COBOL400-L@xxxxxxxxxxxx
8.
http://lists.midrange.com/mailman/listinfo/cobol400-l
9. mailto:COBOL400-L-request@xxxxxxxxxxxx
10.
http://archive.midrange.com/cobol400-l
11.
http://www.symanteccloud.com/
12. mailto:COBOL400-L@xxxxxxxxxxxx
13.
http://lists.midrange.com/mailman/listinfo/cobol400-l
14. mailto:COBOL400-L-request@xxxxxxxxxxxx
15.
http://archive.midrange.com/cobol400-l
16. mailto:COBOL400-L@xxxxxxxxxxxx
17.
http://lists.midrange.com/mailman/listinfo/cobol400-l
18. mailto:COBOL400-L-request@xxxxxxxxxxxx
19.
http://archive.midrange.com/cobol400-l
midrange.com
