RE: Ignoring error messages in SQL scripts -- MIDRANGE-L

Subject: RE: Ignoring error messages in SQL scripts
From: Sue Romano <slromano@xxxxxxxxxx>
Date: Fri, 21 Oct 2011 14:18:38 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

The SQL0204 message didn't change its official severity level. RUNSQLSTM
was changed to treat it as level 20 for DROP.

Sue Romano
IBM i SQL Development

message: 5
date: Fri, 21 Oct 2011 13:49:17 -0500
from: Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
subject: 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

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.