RE: Ignoring error messages in SQL scripts

Still get ERRLVL(30) at v7.1



From: Sue Romano <slromano@xxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx,
Date: 10/21/2011 01:47 PM
Subject: RE: Ignoring error messages in SQL scripts
Sent by: midrange-l-bounces@xxxxxxxxxxxx





Since at least V5R4 (I think it was V5R3), DROP errors in RUNSQLSTM have
been downgraded to error level 20 to help solve this problem. Use ERRLVL
(20) and the DROP errors will be ignored but the errors from other
statements will still cause failures.

Sue Romano
IBM i SQL Development

message: 6
date: Fri, 21 Oct 2011 11:30:04 -0500
from: Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
subject: RE: Ignoring error messages in SQL scripts

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
++