RE: Monitor for SQL error in ACS Run SQL Scripts

AFAIK, the only way to monitor for SQL errors is via a stored procedure which has:
DECLARE CONTINUE HANDLER FOR SQLEXCEPTION
This allows the procedure to continue on its merry way if you do nothing to trap an error and respond to it in some way. Beyond that, I've not yet figured out the "respond to it in some way" part. I'm hoping the SELF guided tour Scott Fortsie is doing on Wednesday will shed some light on what I'm missing.

- Dan

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve McKay
Sent: Monday, September 30, 2024 12:15 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Monitor for SQL error in ACS Run SQL Scripts

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?

Thanks,

Steve McKay

*** CONFIDENTIALITY NOTICE: The information contained in this communication may be confidential, and is intended only for the use of the recipients named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ***