×
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.
To this point, RUNSQL is a PITA because you need to muck around with any literals' apostrophes. E.g.
Select * from CUSTMAST where CUSTSTATE = 'MI'
in RUNSQLSTM, STRSQL, or iACS Run SQL Scripts becomes
'Select * from CUSTMAST where CUSTSTATE = ''MI'''
in RUNSQL.
- Dan
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Sam_L
Sent: Tuesday, August 20, 2024 1:03 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: RUNSQLSTM or RUNSQL command failed
With RUNSQL you provide the SQL statement as a parameter. With RUNSQLSTMT you provide the SQL statement in a file, which, IMHO, is better for anything remotely complex. If RUNSQLSTMT fails there is a spool file that should show the exact point of failure. (My guess would be that it is a commitment control issue.)
But as others have said, iACS Run SQL scripts is the way to go.
Sam
*** 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. ***
midrange.com
