Re: Monitor for SQL error in ACS Run SQL Scripts

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

SQL scripting and/or stored procedures generally follow a different
philosophy than CL.  Instead of MONMSG type trapping you catch it before
hand.
Check for the file or data area with object_statistics prior to acting upon
them.
Check for the software product with software_product_info prior to acting
upon them.

This being said, I do have some RunSQLScripts I run on multiple systems.
One has a bunch of CHGJRN JRN(.../...) JRNRCV(*GEN) and I just tell it to
run to the end.  Failed lines are flagged with red but it does continue
on.  Messages are at the bottom.  If you can't duplicate this let me know
and I'll check settings in Run SQL Scripts.

On Mon, Sep 30, 2024 at 12:16 PM Steve McKay <samckay1@xxxxxxxxx> 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?
>
> Thanks,
>
> Steve McKay
> (205) 585-8424
> samckay1@xxxxxxxxx
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.