Re: CRTRPGMOD: CPYSRCF: From-file EVFEVENT in KS01TS0O not allowed.

On 1/15/2014 2:17 PM, CRPence wrote:

Is the EVFEVENT file being deleted and re-created for each compile or
even just some compiles? Sometimes as PF-SRC, and other times as
PF-DTA? If object auditing is active, at least the former can be
determined. If the file is being deleted and re-created concurrent to
Copy Source File (CPYSRCF) requests, that would be a likely origin for a
concurrency issue being exposed with that feature.

Or is the EVFEVENT file historical, i.e. existing from prior and was
not deleted and created anew for that recent compile activity? The
creation data from DSPOBJD LIBHTTP/EVFEVENT *FILE *FULL OUTPUT(*PRINT)
would establish that; i.e. if the creation data is long ago. If the
EVFEVENT file is historical, then Start Journal Physical File (STRJRNPF)
of that file might gives some timestamps of future member activity which
might be helpful; [and including data, but] unlikely to significantly
impact the ability to recreate the error.

EVFEVENT is historical. It is a multi-member SRC-PF that contains
compiler feedback intended for RDi. I like your train of thought; the
next stop is understanding that this file is created in the *CURLIB in
effect during the compilation. It is possible that different RDi
connections have different *CURLIBs, and therefore there may be a chance
of creating a new EVFEVENT file in a library that one hasn't looked at
yet...
--buck