CPYF giving locks

Thanks Jim & Tom, I was almost giving up hope of getting a reply.
Additional information as requested:-
Try this:-
 CRTPF FILE(FILEA) RCDLEN(80)
INZPFM FILE(FILEA) TOTRCDS(1)
CL program:-
 START:      CPYF       FROMFILE(SHEEHP/FILEA) TOFILE(SHEEHP/FILEB) +
                          MBROPT(*REPLACE) CRTFILE(*YES)
             GOTO       START
Work with member locks (F6 from WRKOBJLCK) :-
 Member      Job         User        Type    Lock     Status
 FILEA       QDFTJOBD    SHEEHP      MBR     *SHRRD    HELD
                                     DATA    *SHRRD    HELD
                                     DATA    *EXCLRD   HELD
                                     DATA    *EXCLRD   HELD
This gives  CPF4128       40     Not able to allocate objects needed for
file
 for any program opening FILEA for update.
Curiously, the two *EXCLRD lines do not appear after:-
 CHGPF FILE(FILEA) REUSEDLT(*YES) so the file can be opened for update.
And curiouser still, the above does not have the described effect if FILEB
exists as a result of CPYF from FILEA when REUSEDLT = *NO.
i.e. to re-test with REUSEDLT = *NO, FILEB must be deleted first.
In fact, vice versa, also. What's really strange is that the presence or
otherwise of the EXCLRD locks on the input file depends on REUSEDLT on the
output file!
Simple enough? But what's the answer to the question Why?

----- Forwarded by Peter Sheehan/EU/FiservCBS on 31/10/01 08:38 -----


                                         To:
                                         midrange-l@midrange.com
                                         cc:
                    Peter Sheehan        Subject:     CPYF giving locks

                    24/10/01
                    10:05





We had a problem the other night when a program attempted to open a small
file, only 2 records, at the same time as a CPYF was starting in another
parallel job. This caused CPF4128. Its easy to replicate. Create a looping
CLP to copy a small file and create/run a program to open that file  for
update. You can also watch the looping job putting EXCLRD members locks on.
Funnily enough, the problem goes away if the file is changed to re-use
deleted records. Why does the CPYF put EXCLRD member locks on? Why doesn't
it, if REUSEDLT = YES?

***********************************************************************
Fiserv CBS Division - Banking Technology for the Future.
************************************************************************
This e-mail should be considered confidential between Fiserv and the
addressee organisation(s), and may be covered by legal, professional or
other privilege (or other similar rules or laws). It should not  be
circulated to any third party without the prior written consent of the
original author. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are not
authorised to and must not disclose, copy, distribute, or retain this
message or any part of it. Nor should you take any action with reference to
it. If you have received this email in error please notify the sender
immediately

Fiserv (Europe) Limited - Registered in England & Wales No. 2467435.