× 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.


  1.  Home
  2. RPG400-L
  3. June 2021

Re: How to prevent CPF5026

The typical pattern would be:

Chain key Table ResultDs;
If %found(Table);
// do update here
Update Table ResultDs;
Else;
// do write here
Write Table ResultDs;
Endif;

HTH


date: Wed, 9 Jun 2021 10:23:50 -0400
from: <dfreinkel@xxxxxxxxxxxxxxxxx>
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




As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.