Gad, MichaelQ, et al,
A program running in system state has naught to do with CALLING the exit
program, only what you can do to the command string DURING the exit program.
The exit program is called, but the command *cannot be changed* if any of
the following occur:
- The command was qualified with a specific library name.
- The command has a parameter defined as RTNVAL(*YES), which allows the
command processing program (CPP) to return a value to the calling program.
- The command has a parameter defined as either DSPINPUT(*NO) or
DSPINPUT(*PROMPT), which does not allow the value to be shown in the prompt
display or joblog.
- The command was used in a program running in system state.
Gad:
What you are doing should work just fine. Do not give up.
I just registered a little "tattle-tale" program to that exit point and ran
some compiles through RDi -- it triggered the exit program EVERY TIME.
There was no difference in the parameters passed to the called program
whether I compiled in batch or inline (in RDi, the opposite of BATCH is
INLINE, not INTERACTIVE), the exit program was triggered with the same data
every time. I registered QSYS/CRTRPGMOD, QSYS/CRTBNDRPG, etc. I also
tried it with QDEVTOOLS/CRTRPGMOD and it worked just fine every time. I
cannot imagine what your problem is.
Have you set a service break in the pre-processor program to be SURE it is
not being called (and not just doing nothing)? You should, first thing,
and let us know if it IS being called. Don't just judge by end results.
Other stuff to check:
1. If your exit program is checking the command name and/or library
before doing its job, make sure it is checking for the correct command name
and/or library. When I get the exit point triggered (either by RDi or
PDM), the "command being executed" (in the command information structure
passed as paramter 1) is QDEVTOOLS/CRTRPGMOD while the proxy chain
indicates it really started with QSYS/CRTRPGMOD.
2. There are settings on each Connection in RDi that specify which *JOBD
is used for batch compiles -- make sure that if the jobd specifies a user
profile that it has authority to call the pre-processor program or make
sure your pre-processor has PUBLIC *USE authority on it.
3. Check the joblog of your compile job for errors in calling or while
running your pre-compiler.
1. if in batch, it will be named after your job description,
2. if inline it will be in the remote command server job that is
processing your requests (QZRCSRVS with your user ID on it)
Recently (the past year or so) I have had several issues with the Command
Analyzer not working correctly when using the QIBM_QCA_CHG_COMMAND exit
point wikth proxy commands (several bugs were introduced in V5R4 with the
proxy command implementation). When a proxy command is used (CRTBNDRPG,
CRTCPPMOD, etc are PROXY commands in QSYS), I find it wise to register the
root command (QDEVTOOLS/CRTBNDRPG) instead of the more obvious
QSYS/CRTBNDRPG (I believe Bruce Vining pointed this out to you last
August). Not saying this is your issue, just pointing out that if you
register QSYS/CRTRPGMOD, someone can dodge your exit program by executing
QDEVTOOLS/CRTRPGMOD.
One of the issues I had fixed lately was the exit program would just STOP
BEING CALLED until you de-registered and re-registered the exit program.
We never figured out exactly why it sould stop being called, even after a
couple hours on the phone with China (the command analyzer is maintained by
Chinese contractors now). At any rate, here is a PTF that may (or may not)
help:
V6R1 = SI58104
V7R1 = SI58105
V7R2 = SI58106
Good luck.
Stu
On Mon, Jan 25, 2016 at 4:04 AM, Gad Miron <gadmiron@xxxxxxxxx> wrote:
Hello Mike
I've cheked,
The Library list is correct and the (prompted) invoked compile request is
correct
CRTBNDRPG PGM(GAD/BB) SRCFILE(GAD/QRPGLESRC) SRCMBR(BB) OPTION(*EVENTF)
DBGVIEW(*SOURCE) REPLACE(*YES)
*But*
the CMD Analyzer PGM is not invoked
Gad
On Sun, Jan 24, 2016 at 8:07 PM, Mike Hockings <hockings@xxxxxxxxxx>
wrote:
RDI does not do anything special, it just invokes the compile command so
I
would expect that any exit programs should run. Make sure that the
library
list is as expected and you could try prompting the compile command to
make
sure that any specific settings are defined the way you expect as well.
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
midrange.com
