Re: RDi 9.1: not getting an error list when using a custom compile command

I got bit by this also. Everything used to work fine, and it still seemed
to work in most things, but not SQL or other compiles where a CRTPGM
command is executed after the *MODULE is created. The key can be found in
the instructions on the midrange wiki at:
http://wiki.midrange.com/index.php/WDSC_tips/Compile#Custom_Compile_Commands

Here's the pertinent part:
"When OPTION(*EVENTF) is specified, WDSC will look in the first 20 bytes
of the *LDA. This must contain the library and member for the compiled
source, so your compiler front end needs to ensure that the *LDA is
correctly populated."

The first 10 bytes should include the library where the event file is
located and the next 10 bytes specifies the member name. Our custom
compile processing sometimes generates a *MODULE in QTEMP and then
executes a CRTPGM afterwards. In these cases, I copy the EVFEVENT file
member from QTEMP to the destination object library with the following
command:

CPYF (QTEMP/EVFEVENT) TOFILE(&OBJLIB/EVFEVENT)
FROMMBR(&OBJ) TOMBR(*FROMMBR)
CRTFILE(*YES) MBROPT(*REPLACE)
MONMSG MSGID(CPF2817)

I monitor for other messages and clean up the job log to remove details
related to the CPYF command. It's not required, but leaves a cleaner job
log. That and we resend completion messages to the user submitting the
compile. I didn't want to confuse junior developers with messages about a
member being copied and/or a file being created.

Hope this helps,
Michael

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 06/05/2014 04:26:27 PM:

----- Message from x y <xy6581@xxxxxxxxx> on Thu, 5 Jun 2014 13:08:
58 -0700 -----

To:

wdsci-l@xxxxxxxxxxxx

Subject:

[WDSCI-L] RDi 9.1: not getting an error list when using a custom
compile command

My use of a custom compile command (apparently) breaks the error message
retrieval/insertion process.

When I compile using an IBM command (CRTBNDRPG, CRTSQLRPGI, etc.), the
error list gets pulled from EVFEVENT and the errors are inserted, all
expected behaviors.

I used a generic object create command (with *EVENTF specified) in RDi

8.5

and I'd get the errors back. But on RDi 9.0 and 9.1, and with the same
command, I'm not getting my errors back, The job log shows the results

but

the error list isn't refreshed--in fact, the previous list isn't even
cleared. EVFEVENT shows the same number of records for a given compile
regardless of the compile command (my object build or the naked IBM
command).

Using Work with Compile Commands, I set up a tailored version of

CRTSQLRPGI

and got errors back. The same command string in a stand-alone CL

program

executed from the the list of compile commands failed to retrieve the
errors. So, it appears the compile part is okay: the object is created
when the compile is successful and the EVFEVENT member has the
warnings/errors. That leads me to think that the message retrieval
behavior is triggered by receiving a message or checking the status of

an

object (message queue or data area?).

I'm stumped and would appreciate any suggestions.

Thank you!