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




Buck,

Maybe that I am missing something, but for me EVFEVENT is always created
in the object library of the compile command. *CURLIB is set to *CRTDFT as
far as I can see.

Regarding to my latest test, I am sure that no one else compiled KS*
modules at the same time.

Thomas.

wdsci-l-bounces@xxxxxxxxxxxx schrieb am 15.01.2014 20:44:53:

Von: kc2hiz@xxxxxxxxx
An: wdsci-l@xxxxxxxxxxxx,
Datum: 15.01.2014 20:44
Betreff: Re: [WDSCI-L] CRTRPGMOD: CPYSRCF: From-file EVFEVENT in
KS01TS0O not allowed.
Gesendet von: wdsci-l-bounces@xxxxxxxxxxxx

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
-
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a criminal
offence. Please delete if obtained in error and email confirmation to the sender.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.