Re: Monitor for SQL error in ACS Run SQL Scripts -- MIDRANGE-L

× 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.

On 9/30/2024 12:15 PM, Steve McKay wrote:

I have an ACS SQL script that is run against multiple partitions. The
script consists of SELECTs against various files, the QSYS2.DATA_AREA_INFO
table, and QSYS2.LICENSE_INFO table.

Because it's running against multiple partitions, the file, data area, or
license program may not exist on every system. This is expected. When this
happens, I receive an SQL error message (SQLstate: 42704, vendor code: -443
or other). If this were a CL program, I would be able to MONMSG each error
and continue with the program. Is there a way within ACS Run SQL Scripts
to monitor for an error message and continue the script without showing the
error message? Or to display the error message in the bottom results panel?

I never use the interactive scripting tool this way.
If I have a repetitive task like that, I put the individual SQL statements into a program; one can pass the remote database/schema/etc as parameters.

Once the code is in a program, you can trap and respond to exceptions as needed. If RPG isn't your favourite (or there's no compiler on that machine) you can do this in an SQL Procedure, ReXX program, or even Python.

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.