Re: CPF5090 - unexplicable (or is it)?

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxxxxxxxx>]

Perhaps the physical file was created with UNIQUE?

CPF5090 is not saying the key value you tried to insert is not unique; 
it is saying that there is something wrong (or "broken") with the 
underlying access path, and that it might need to be re-built.

> On 9/26/2011 3:59 PM, Åke Olsson wrote:
> We have a heavily used file with 8 logicals attached. None of the logicals is coded "unique". The system is on v6r1.
>
> DSPDBR shows no other relations than these same 8.
>
> All of a sudden any write operation to the file fails with a CPF5090 (indicating unique key violation). There is plenty of space for more records as the file has been reorged recently.
>
> There have been no restores of the file.
>
> The problem was that the file is very much key in many processes so we had to shut everything down at peak time for half an hour so that we could create a fresh file (compile) and copy data from the old file.
>
> Has anyone else experienced this situation? Explanations?
>
> PS: We know that ops have at times been a bit behind in applying ptf:s for the op.sys. Is there a known ptf for this problem?
>
> Med vänlig hälsning / Best regards
>
> Åke H Olsson