Re: SQL options precedence for SQLRPGLE

On 6/19/2013 12:01 PM, Josh Diggs wrote:

I am trying to determine If there is any interaction between a third party application and my program with regards to the SQL options.

As programmers, we tend to see problems as technical issues but very
often describing the actual business problem (for example, '3rd party
program complains about journaling') will trigger more replies than the
more generic description of the hypothetical problem space.

My understanding is that these options can be set with a QAQQINI entry, at compile time via the command, or at compile time via a SET OPTION statement in source.

What makes sense to me is that QAQQINI would provide defaults, the compile command could override those defaults, and the SET OPTION would be the final word. Is that correct?

I can't think of many QAQQINI options that can be overridden by SET
OPTION or compile time settings and I'm on 7.1. So the only real
hierarchy is between the compiler defaults and SET OPTION.

Also, can anyone describe how I might see the SQL options that are active during a debug session, and the SQL options that were specified at compile time (something along the lines of DSPPGM)?

DSPPGM doesn't store any compile time options, not even for OPM RPG
programs. For instance you can't tell if the program was compiled with
IGNDECERR or FIXDECERR or not.

I don't think any of the debuggers have a special command to expose SQL
information; PRTSQLINF is probably the only thing available.
--buck