× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. October 2011

RE: Ignoring error messages in SQL scripts



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.