Re: RDi Compile and CMD Analyzer

We also have a home made pre compiler to do similar things. But ours is
hooked to a custom compile command which then processes the actual compile
(CRTxxxxx). I always thought hooking the pre compile process into the
command itself by way of a command analyzer exit program would be better.
That way it should fire no matter how the compile is executed.

The only limitation the API documentation for the exit points mentions is
the command may not being used in a program running in system state. The
processing of the command runs through QRSEEXEC in the QDEVTOOLS library.
I don't know why, but a DSPPGM for QRSEEXEC shows Program state as
*SYSTEM. Perhaps Paul's suggestion (see below) to execute the command from
a CL wrapper would alleviate this issue.

I would be very interested to hear what the final resolution to this is.
please post any follow-up details.

Thanks,
Michael Quigley
Computer Services
The Way International
www.TheWay.org

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 01/21/2016 10:18:13 AM:

----- Message from Gad Miron <gadmiron@xxxxxxxxx> on Thu, 21 Jan
2016 14:02:34 +0200 -----

To:

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

Subject:

[WDSCI-L] RDi Compile and CMD Analyzer

Hello everyone

First steps using RDi (9.5) and ran into the following problem with

compile.

We have a home made "Pre compiler" of sorts that scans the source
before compiling and executes CMDs embedded in the source, setting LIBL,
OVRDB etc.
(it does the same after compiling as well)

This is achived by adding a CMD analyzer exit point to CRTBNDRPG and
CRTRPGMOD .
This method works fine in 5250 environment and serves us well.

However,
the Cmd Analyzer is not invoked when compiling a program in RDi studio.

Does the RDI use the same CRTBNDRPG/CRTRPGMOD CMDs as the
"Green screen" or is there other reasons why the Exit point is not

called?

and also, How do I setup RDi to compile "interactively" rather the

Batch?

TIA

Gad


----- Message from Paul Bailey <PaulBailey@xxxxxxxxxx> on Thu, 21
Jan 2016 14:46:10 +0000 -----

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


I'm not sure about the CRTBNDRPG/CRTRPGMOD exit points, but maybe if
you created a CLLE program to call CRTBNDRPG/CRTRPGMOD with the
relevant parameters passed in to the CLLE you could create your own
compile command in RDi and use that instead. This should cause your
exit points to fire as if you'd done it through PDM/cmd-line.

Compile in batch is controlled in windows/preferences (search for
"command execution") and the compile in batch is at the top of that
page. You can also control it for each connection as well (right-
click the connection in the RSE view, select properties, select
"subsystems" and change to the "Commands" tab.


-Paul.