Re: RUNSQLSTM or RUNSQL command failed

[Sam_L <lennon_s_j@xxxxxxxxxxx>]

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

On 8/19/2024 5:46 PM, Shane Reeves wrote:

> I have a somewhat complex SQL statement (for me) that I was looking to run in a program.  Normally we use SEQUEL by Fortra but from what I've found so far it doesn't support the statement I'm attempting (I've contacted their support to find out for sure).  So, I started looking at RUNSQL to see what I could use it for, as we've not used it very often.
>
> Starting with a simple insert statement to test it out it came back with 'RUNSQLSTM or RUNSQL command failed'.  After many different small tests that was all that I could get for RUNSQL to return  (when running from the command line).  So, I tried putting the same statement in a CLLE program using RUNSQL, and it worked fine.  Why would the same statement work in the CLLE program, but not from the command line?  It makes testing statements so much more difficult.