[WDSCI-L] Re: Compile commands

[David Gibbs <david@xxxxxxxxxxxx>]

Alan Campin wrote:
> Anyway, in order to get it to work, I issue the command COMPILE
> though WDSC but like you, I did not get anything back. I notice below
> that David says OPTION(*SRCDBG). I think he meant to say
> OPTION(*EVENTF) but that still did not work. You always have to use
> OPTION(*EVENTF) and I could see the Event file being built but not
> being returned to me. 

Actually, I did mean OPTION(*SRCDBG) :)

What I did, for our compile commands (part of the Implementer SCM 
product) is put a dummy parameter on the compile command where I put the 
'SRCMBR(&N) OPTION(*SRCDBG)'.  Neither parameter is actually used by 
anything, but WDSC notices them and is able to return the compile 
information.

The actual compile command needs to have either the OPTION(*EVENTF) or 
OPTION(*SRCDBG) parameter.

> Finally found that the only way I could get it
> to work was to compile interactively and that would work. I, also,
> got the free plug-in from Softlanding to retrieve messages from the
> message queue to show me the result messages.

Make sure the compile is not submitted within the batch compile.  WDSC 
submits the compile, and keeps track of the submitted job.

Also, make sure you don't compile the object into QTEMP ... if you do, 
the event file will be written to QTEMP and WDSC won't be able to 
retrieve it.

david

--
David Gibbs
david@xxxxxxxxxxxx

Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email