Re: RUNSQLSTM or RUNSQL command failed

RUNSQL has not been touched other than to verify it works as it did on
previous systems in several releases. Like PDM it's
"functionally stabilized", short for dead at some point in the future.
(usually a release boundary)

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Tue, Aug 20, 2024 at 9:15 AM Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
wrote:

RUNSQL is to all intents deprecated.

Um, what? Was there an official statement from IBM?

- Dan

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jon
Paris
Sent: Monday, August 19, 2024 6:11 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: RUNSQLSTM or RUNSQL command failed

You are testing in the wrong place.

RUNSQL is to all intents deprecated.

The way to test SQL is via ACS or via the Db2 feature of Code for i.
There are many SQL features that will not work in RUNSQL

Jon P.

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