I'll bet the amount of time the OS spends dealing with a duplicate-key error
is greater than the time spent on all failed CHAINs.
Leo
-----Original Message-----
From: RPG400-L On Behalf Of dfreinkel@xxxxxxxxxxxxxxxxx
Sent: Wednesday, June 9, 2021 10:24 AM
To: 'RPG programming on IBM i' <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: How to prevent CPF5026
I have a program that writes records to a file, nothing new. However,
occasionally there is a situation where the record already exists and I need
to add the quantity to the total quantity field. That is nothing new.
I do a WRITE(E) followed by IF %ERROR() and then do a update to the record.
This works well.
However, when the system detects the duplicate record, it sends out a
CPF5026 to the job log with an automatic reply C.
I do not want to chain first and then do a WRITE or an UPDATE as needed as
99% of the records will not exist.
How can I prevent the CPF5026 from being generated?
Darryl Freinkel
A4G
Telephone: 770.321.8562 Mobile: 678.355.8562
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
