my own EXECSQL command, created several years ago, works fine-:)
It only passes a string to an RPGSQLLE which does what CL can't (couldn't)
and throws the SQL**** error as an exception error to be monitored after
the cl command in the clp.

2012/11/13 Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>

My V7 system with the most recent (within two weeks) groups shows the same.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 11/12/2012 6:54 PM, Sam_L wrote:
Got the new IBM RUNSQL command with the cume.

- It doesn't seem to have any help text.
- It doesn't seem to issue escape messages if it fails.
For exzmple, running this:
runsql 'Duh! Totally invalid syntax'
Gives only a SQL0104 diagnostic message.

Anyone else seeing this?

On developerWorks there is what looks like help text. It also says that
it does issue escape messages, right at the bottom.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact