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

Just another side note. When EVFEVENT is created by the RPG compiler, it
has the following format:

Field Type Length Length Position Usage
EVFEVENT CHAR 300 300 1 Both
Coded Character Set Identifier . . . . . : 65535

It contains for module KS001:

Line ....+....1....+....2....+....3....+....4....+....5....+....6....+
EVFEVENT
000001 TIMESTAMP 0 20140115223542
000002 PROCESSOR 0 000 1
000003 FILEID 0 001 000000 020 KS01TS0Z/QSRC(KS001) 20131210104736 0

But it also works, when I create it by hand:

CRTSRCPF FILE(KS01TS0O/EVFEVENT) RCDLEN(312)

After having compiled a module, member KS001 contains:

Line
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
SRCSEQ SRCDAT SRCDTA
000001 3,945.23 147,000 20140115223725
000002 7,963.52 269,000 000 1
000003 6,935.94 0 001 000000 020 KS01TS0Z/QSRC(KS001)
20131210104736 0

Maybe that RDi does not always check the format of EVFEVENT and hence
sometimes uses a wrong command.

Thomas.

wdsci-l-bounces@xxxxxxxxxxxx schrieb am 15.01.2014 22:05:34:

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

On 15-Jan-2014 11:44 -0800, Buck Calabro wrote:

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

<<SNIP>>

Or is the EVFEVENT file historical, i.e. existing from prior and
was not deleted and created anew for that recent compile activity?
<<SNIP>>

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

FWiW: I have one of those files, but created from options on a
green-screen compile, and my file is PF-DTA [i.e. File type
FILETYPE(*DATA)] rather than a PF-SRC [aka FILETYPE(*SRC)]. Does RDi
require exclusively that the file it uses be a SRC-PF, perhaps even
deleting an existing file that is not?

Given a certain anomaly with the file, the error may be both correct
and incorrect at the same time; depends on whence the information for
determining the is-src vs is-dta is extracted. Knowing if that is an
issue pends learning the answers to my questions, or the problem may be
able to be resolved by a DLTF of the file with such an anomaly, *but*
the joblog must be reviewed for any underlying errors logged... because
the Delete File is "tolerant" of errors, to the extent that the noted
anomaly can be a side effect; such that creating a new version of the PF

is not helpful, as the condition will resurface until the file by that
name has been deleted without any errors logged. However as I had also
alluded, that anomaly as origin would seem unlikely, if the issue is not

solid\consistent... though the origin of the temporary-name could also
play a role in how consistent the failure when that anomaly exists.

--
Regards, Chuck
--
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.