Re: RDi Compile and CMD Analyzer

On behalf of anyone else who would like to use the command analyzer exit
points, thanks for going through all that.

Here's a thought. What about setting up a User Action instead of a Compile
Command? Or have you tried that, too? That could just do a 'SBMJOB
CMD(CRTxxx)' with the rest of the parameters supplied as needed. Of
course, User Actions aren't as easy to trigger while editing source.

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 01/26/2016 06:48:16 AM:

----- Message from Stuart Rowe <rowestu@xxxxxxxxx> on Mon, 25 Jan
2016 13:29:18 -0600 -----

To:

"Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] RDi Compile and CMD Analyzer

Gad,

I have tried several different ways of compiling from RDi and no matter
what I do, QDEVTOOLS/QRSEEXEC is the program that "runs" the CRTXXX
command. Disappointing.

Even compiling in batch, which submits a separate job, will not help you
because even in that case, IBM does NOT simply submit the command to the
job queue like they should have done, they had to submit a call to their
program which then runs the CRTxxx command. Kinda throws a wrench into
something that should be as simple as submitting a command to be

executed.

So you're down to trying to write a layer between IBM and your
pre-compiler, or altering HOW the pre-compiler is run.

Stu