RE: runsqlstm

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
There is also a related limitation that you cannot have a SELECT statement
be a prepared SQL statement.  For example, I had a remote system without
SQL so I wrote a SQLRPGLE program to run sql statements.  Works great on
many sql statements but you cannot use it to run the SELECT statement.
Thus we use it for UPDATES, etc but use another (RUNSQL) for the select
statement.  We just didn't like the RUNSQL because of some strange bugs.

RUNSQL came out of an ancient issue of news/400 and utilizes STRQMQRY,
which all 400's have.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




James Rich <james@eaerich.com>
Sent by: midrange-l-admin@midrange.com
07/19/2002 10:39 AM
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Fax to:
        Subject:        RE: runsqlstm


On Thu, 18 Jul 2002, Buck Calabro wrote:

> >It seems that no matter what I do,
> >it fails with the message (in my
> >spooled file result):
> >
> > SQL0084 Position 7 SQL statement not allowed.
>
> I looked at the documentation but could not find the restriction.  You
> cannot run a SELECT statement.  That's my guess.

It turns out that the select limitation is what I was running into (I did
finally find the docs that say this).  Anyone know why there is this
(stupid) limitation?  Why wouldn't I be able to do a select?

James Rich

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