Re: SQL commands over ODBC: Changing tables triggers inquiry messages

Hello Niels,

Am 18.08.2025 um 11:25 schrieb Niels Liisberg <nli@xxxxxxxxxxxxxxxxx>:

My pleasure !!

The qaqqini table can do a lot of optimization and behaviour of "old"
defaults. Now you can even override it with the qsys2.override_qaqqini
procedure;

https://www.ibm.com/docs/en/i/7.4.0?topic=qaqqini-query-options

You are so welcome Patrik;

Thanks a lot. :-)

Apparently, I was a bit too enthusiastic regarding changing the default behavior. SUPPRESS_INQUIRY_MESSAGES is not contained in the default qaqqini file, so I need to insert a record. This is prevented by triggers for the original file in qsys.

Also, one should not change default files in QSYS. :-)

So, I'm using the procedure on the page linked below to generate a copy of qaqqini, and successfully inserted the record there.

https://www.ibm.com/docs/en/i/7.3.0?topic=qaqqini-creating-query-options-file

Now I see, chgqrya has a default value of qusrsys for qryoptlib. Does that mean that after duplication and insertion of the record above, all (new) jobs now use that default file? If yes, great, that's what I intended.

If no, what would be the correct way to establish qusrsys/qaqqini as system-wide default instead of the one in qsys? Change the LIBL, moving qusrsys to the very top seems not to be desirable for the same reasons, user writable directories are added to the PATH variable on Unix after the global ones: It's relatively easy to place a malevolent command there.

TL;DR: How can I make permanent your proposed change about SUPPRESS_INQUIRY_MESSAGES, instead of temporary only?

Thanks!

:wq! PoC