Re: RDi Compile and CMD Analyzer

On 1/26/2016 9:32 AM,
MichaelQuigley@xxxxxxxxxx wrote:

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.

I like that thought!

I created a copy of the 'regular' RDi CRTBNDRPG compile command and
changed it to:
SBMJOB CMD(CRTBNDRPG PGM(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) REPLACE(&R)
OPTION(*EVENTF) DBGVIEW(*SOURCE)) JOB(&N) JOBQ(QS36EVOKE)

I was a little surprised that this returned the feedback just as it did
before it was wrapped in SBMJOB. That was interesting to me because it
could be used with the regular compile shortcut key - Ctrl-Shift-C.

So then I tried a user action with the exact same command and that
worked as well. So there may be two other choices for getting around
the system state issue.