Re: Setting up a compile in WDSC...Another Try

Rod,

I had followed your thread with great empathy. I was too busy to dig up
the details and still am. We use a custom compile command all the time.
Here's our command:

COMPILE OBJECT(&O/&N) DELETE(&R) SRCF(&L/&F) SRCMBR(&N) OPTION(*SRCDBG)
REPLACE(&R)

It has both the SRCMBR(&N) and OPTION(*SRCDBG) parameters. Our system
administrator changed the command processing program (CPP) to send all the
messages generated by the compiler back to the *PRV program. (He has
another utility command so it was pretty easy to add it to the CPP. The
process basically involves a loop with RCVMSG and a corresponding
SNDPGMMSG.) I don't recall for certain, but I think he added this
function to our CPP when speaking with someone on SupportLine specifically
regarding getting compile errors, etc. back to WDSC. Anyway, we receive
our compile errors on everything that produces an event file (with the
troublesome exception of SQLCBL compiles).

wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/27/2008 05:52:55 PM:

date: Wed, 27 Feb 2008 15:03:15 -0600
from: Rod Verity <rod_verity@xxxxxxxxxxxxxx>
subject: [WDSCI-L] Setting up a compile in WDSC...Another Try


I had asked this question before but I believe part of the problem was

due

to too many call layers. I have set up a new "chopped down" version of a
compile procedure for Cobol programs. The reason I want to call a

procedure

instead of using the supplied CRTCBLPGM is because the input library

sets

the library list so the copybooks will be found according to the correct
library list. Also, the compiled object is placed in a different

library.

eg. If person is compiling out of ISPS56A, the CL program will put this
library plus a couple of other default libraries in the library list,

sets

the output library for the PGM parameter to be ISPO56A and then runs
CRTCBLPGM.

When I run this, the compile is run but the errors are not returned to
iSeries Error List. I have looked at all comments and references from

last

time which includes putting /* OPTION(*EVENTF) SRCMBR(&N) */ at end of
command. There was another listing that said to use /* *EVENTF

SRCMBR(&N)

*/ which I tried also. The entire command is WDCBLCOMP PGM(&N)

SRCLIB(&L)

SRCFILE(&F) /* *EVENTF SRCMBR(&N) */. I set up a command call

WDCBLCOMP

as well as a CL program. The CL program calls an in-house routine to set
the library list and the output library and then runs CRTCBLPGM as
following:

CRTCBLPGM PGM(&OBJLIB/&PGM) SRCFILE(&SRCLIB/SRCE) OPTION(*SOURCE

*LSTDBG

*APOST *XREF *MAP).

I also went into preferences for iSeries Command Execution and unchecked
"Compile in batch".
I read some info written by Bruce Guetzkow and Kushal Munir regarding
running a command. It says you have to write the events file location to
the local data area. How do I do that? And where would I find the data
area that is used by my WDSC session? I tried adding following two

commands

after the CRTBLPGM call but nothing happened:
CHGDTAARA DTAARA(*LDA (1 10)) VALUE(&OBJLIB)
CHGDTAARA DTAARA(*LDA (11 10)) VALUE(&PGM)

Thanks in advance,
Rod Verity