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



It says the following -

If the record number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.

Lim, what it doesn't say is - if the record number is not zero, then this is NOT an OUTPUT operation.

But it is interesting, and could well be related to REUSEDLT(*YES).

Rob,

You said that once the record was deleted, it does not have a RRN. Is that true? I thought that the byte that defines the record as deleted was set so that the DB no longer sees it. But it's still in the file, and can be recovered. And can it's RRN be used if REUSEDLT(*NO) is set?

Just curious...

Crispin.



Okay Lim
why are you EXPECTING the text to say "record number 0"?



Alan Shore
I don't think I explain my question correctly.

It is correct that the system is given me a duplicate key error. I'm
not questioning the system giving such an error. I'm question about the
CPF message TEXT. In the TEXT it said:
"The output or update operation to member number 1 record number 1377
format ORDETR, for member ORDET file ORDET in library APLUS2FMC,
failed."

For a WRITE statement I do not except it to tell me the record number
1377. The TEXT should be
"The output or update operation to member number 1 record number 0
format ORDETR, for member ORDET file ORDET in library APLUS2FMC,
failed."

Clear as mud?




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.