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



Thanks everyone.

Good news.
1) Adding the extra space resolved the syntax issue.
AND JOB_TYPE
Never new about this issue, wish I would have.

Bad news.
2) 3 versions of RUNSQL command.
The version currently being used, and working, is in library SYS, supplied by a 3rd party vendor for their application. Creation date/time . . . . . . . . . : 05/23/08.
IBM's RUNSQL has never been used.
IBM's RUNSQL cannot be run from a command line, does not allow Select statement, does not have *print output,
A google search of RUNQSL reveals all the negatives with the IBM version.

RUNSQL *CMD IC08XXPGMS Process SQL commands using Creation date/time . . . . . . . . . : 04/25/04
RUNSQL *CMD QSYS Run SQL Statements Creation date/time . . . . . . . . . : 05/15/14
RUNSQL *CMD SYS Process SQL commands using Creation date/time . . . . . . . . . : 05/23/08

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Friday, January 06, 2017 10:57 AM
To: Midrange Systems Technical Discussion
Subject: Re: Interactive SQL vs RUNSQL REQUEST submitted via AJS - syntax checking different

If your sql statement goes into the parameter REQUEST you have the old homegrown one with the concatenation bug.
If your sql statement goes into the parameter SQL you have the new one supplied by IBM.

This is a caution to be aware of when you upgrade your OS!
It actually came out with some TR so that can be a concern also.

Some people go to great lengths to keep their existing code by renaming the IBM one, etc.
I say sooner or later you are going to trip on your member so it's best to fix your code to either use the IBM one or to rename the homegrown one and redirect your code to use that one.

A stepping stone is to use the command exit point to intercept any use of the "RUNSQL REQUEST" and log it and redirect it. Browse the log on occasion and put that code on your to do list to get fixed.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.