Hi Sean
I replied to Shane earlier - SEQUEL can be set to use native IBM i syntax - you set the server to *LOCAL instead of *SEQUEL to get IBM i syntax with a dot qualifying separator, *LOCALSYS to get the same with the slash qualifying separator.
Interesting suggestion, to use an IBM i view as the table in a statement in *SEQUEL syntax - might have to try that sometime.
But all manner of joins and CTEs and all are fine directly in SEQUEL with the server set correctly.
Cheers
Vern
On Tue, 20 Aug, 2024 at 12:09 PM, Mcgovern, Sean via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: sean.mcgovern@xxxxxxxxxxxxx
SEQUEL doesn't support a lot of DB2 SQL functionality.
If you want to continue to use SEQUEL, you can create a SQL View of your SQL statement, then just refer to that in SEQUEL.
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> on behalf of Shane Reeves <SReeves@xxxxxxxxxxxxxxxxxx<mailto:SReeves@xxxxxxxxxxxxxxxxxx>>
Sent: Monday, August 19, 2024 22:46
To: midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx> <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
Subject: [EXTERNAL] RUNSQLSTM or RUNSQL command failed
Hello, 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
Hello,
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.
Shane Reeves
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://urldefense.com/v3/__https://lists.midrange.com/mailman/listinfo/midrange-l__;!!NFcUtLLUcw!XTmE24VIbADewFItMxC86671SvAtxY68nRbiNY7FBhqCEAWabQgq2mgHmX-FHY7g8Uqgvmb1EIaR1hDSdHNbCWFT4DY$
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://urldefense.com/v3/__https://archive.midrange.com/midrange-l__;!!NFcUtLLUcw!XTmE24VIbADewFItMxC86671SvAtxY68nRbiNY7FBhqCEAWabQgq2mgHmX-FHY7g8Uqgvmb1EIaR1hDSdHNb7OPAnQw$.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
[CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser:
http://emaildisclaimer.medtronic.com
midrange.com
