Re: Query on commitment control in SQL scripts

[CRPence <CRPbottle@xxxxxxxxx>]

On 03-Mar-2015 08:18 -0600, Darryl Freinkel wrote:
> I am running a series of SQL scripts using iNavigator's script
> option.
>
> Issue:
> I am not using commitment control but when I run the scripts, the
> system is logging messages that the files is not being journaled.

  What messages?  Something like msg SQL7008 rc3 for DML, or perhaps 
instead, msg SQL7905 for DDL CREATE TABLE requests?

> Questions:
> How do I suppress the messages?

  Depends on what are the requests being performed and the messages 
being issued; too little context has been offered for a reader to 
provide worthwhile comment.

> Tell the script to not use commitment control. In SQLRPG I use the
> set OPTION COMMIT = *NONE. Is there something equal to this in
> scripts?

  On DML requests code the WITH isolation clause, e.g. WITH NC, or 
issue the statement SET ISOLATION LEVEL for a dynamic request to 
establish the CmtCtl level similar to how the non-executable SET OPTION 
from the embedded SQL statement in pre-compiled host-language source.

  Otherwise the setting can be established initially in the database 
/connection/; those prior mentioned capabilities to override any one 
statement or the effective /session/.  Vern responded about how the JDBC 
settings can address the issue of the isolation level established for 
the connection that is used by the RunSQL script utility.