Re: Query on commitment control in SQL scripts

[Charles Wilt <charles.wilt@xxxxxxxxx>]

You realize that those message, particularily #2 mean that your statement
didn't complete.

Charles

On Tue, Mar 3, 2015 at 10:26 AM, Darryl Freinkel <dhfreinkel@xxxxxxxxx>
wrote:

> There are 2 repeating messages:
>
> 1. CPF4328 member "name" not journaled to Journal *N
> 2. SQL7008 "filename" in QTEMP not valid for operation - Code = 3.
>
>
>
> On Tue, Mar 3, 2015 at 10:12 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:
>
> > 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.
> >
> > --
> > Regards, Chuck
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
>
> --
> Darryl Freinkel
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.