RE: Ignoring error messages in SQL scripts

[Dennis <iseries@xxxxxxxxxxxx>]

Thanks.  But that wasn't quite the point, since ERRLVL(30) will still cause the "procedure" to continue after a(nother) significant error.
++
Dennis
++
 "Whenever science makes a discovery, the devil grabs it while the angels are debating the best way to use it."
     -- Alan Valentine 


 

Sent from my Galaxy tablet phone.  Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++


Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:

> ERRLVL(30) suffices to avoid the DROP error.
>
>
>
> From:   Dennis <iseries@xxxxxxxxxxxx>
> To:     Midrange Systems Technical Discussion
> <midrange-l@xxxxxxxxxxxx>, 
> Date:   10/21/2011 11:14 AM
> Subject:        RE: Ignoring error messages in SQL scripts
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> Agreed, and this has always been a nuisance to me.  The only way I have
>
> found around this (aside from a replacement for RUNSQLSTM, which I did 
> eventually write), was to put the DROP and CREATE into two members. 
> Then:
>   RUNSQLSTM. ...DROP... ERRLVL(40)
>   RUNSQLSTM. ..CRT... ERRLVL(10)
> ++
> Dennis
> ++
> Nobody can outstubborn your mother. 
>
>
>
>
> Sent from my Galaxy tablet phone.  Please excuse my brevity.
> For any grammatic/spelling errors, there is no excuse.
> ++
>
>
> "Morgan, Paul" <Paul.Morgan@xxxxxxxxxxx> wrote:
>
> > Alan,
> >
> > There is nothing in the SQL itself but you can change the ERRLVL
> > parameter on the RUNSQLSTM.  However that will stop throwing an error
> > if your create view errors out.
> >
> > Paul Morgan
> >
> > Principal Programmer Analyst
> > IT Supply Chain/Replenishment
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
> > Sent: Friday, October 21, 2011 10:54 AM
> > To: midrange-l@xxxxxxxxxxxx
> > Subject: Ignoring error messages in SQL scripts
> >
> > Good morning all
> > I have an SQL script run by the command
> > RUNSQLSTM SRCFILE(libname/QSQLSRC) SRCMBR(MBRNAME)
> > Within the script MBRNAME I have
> >
> > DROP VIEW library/viewname
> >
> > Followed by
> >
> > Create view library/viewname
> > Etc.
> >
> > In this particular instance the view library/viewname had already been
> > dropped, so my RUNSQLSTM failed on the drop
> > My question is
> > I knew why the view wasn't there, so I wasn't bothered about the drop
> > in the SQL script, so how would I ignore such an error?
> > Is there the equivalent to a MONMSG  within SQL scripts?
> > Is there a reference manual that I could read regarding SQL scripts
> >
> > As always, any and all responses MUCH appreciated
> >
> > Alan Shore
> > Programmer/Analyst, Direct Response
> > E:AShore@xxxxxxxx
> > P:(631) 200-5019
> > C:(631) 880-8640
> > "If you're going through Hell, keep going" - Winston Churchill
> >
> > -- 
> > 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.
> >
> >
> > -- 
> > 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.
>
> -- 
> 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.
>
>
> -- 
> 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.