Re: Compile error list

[Buck <kc2hiz@xxxxxxxxx>]

On 3/18/2010 5:22 AM, David FOXWELL wrote:

> I use a custom compile pgm on the i. I don't see what instructs this program to create a file named EVFEVENT, but it's there with the error messages in it.
>  
> In RSE, I've added a compile command : 
> CALL PGM(MyCompilePgmOnThei) PARM(&N &L &L &F) /* OPTION(*EVENTF) SRCMBR(&N) */
>
> This works. 
>
> Now, how do I get the error list view to show up? It does if I use CRTRPGMOD. Eventually.

It sounds like you already followed instructions similar to
http://wiki.midrange.com/index.php/Custom_Compile_Commands but
something's still missing.  That something is the RPG compiler
populating EVFEVENTF.  It won't do that unless you tell it to.
Somewhere in your custom compile command, you must be calling the
compiler.  Wherever that is, you need to set OPTION(*EVENTF) SRCMBR(&N).

There lies the tricky part - I assume you want your PDM-using companions
to use the same command without an event file, so there needs to be some
way for the custom compile program to distinguish when it's being called
by WDSC vs PDM.

You might go the somewhat ugly route of inspecting the call stack, but
before you do that, what are the chances you can make your custom
compile program into a command that everyone will use?  Then you can put
on a optional parameter that you can pass to the compiler...

Another idea (maybe even uglier!) is to ALWAYS produce an event file.
The PDM-users won't know it's there, but it shouldn't cause any harm either.
  --buck