I hear what you say about the incompatibility of the different databases.

Using :somelt is not valid.

If I am not wrong, it seems the only solution would be to open the file and
read each until I find the record I need to validate.

This is not elegant but may be the only solution.

The error reported is it does not like the colon (:) in 'select count(*)
into :someIt where some Column = ?

I am going to try it the long way. I'll let you know the results.


On Fri, Aug 26, 2016 at 12:28 PM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

Ah, hah! I missed it before. The above statement is not allowed
in dynamic SQL. You should code it as follows.

zSqlCmd = 'Values (Select count(*) from AXTRN01..UNITOFMEASURE +
where Symbol = ' + Q + %trim(pUOM) + Q +
') into ?;


Dave Clark

values into is not standard SQL and won't work with diffrent databases.
The one and only problem is sitting in front of the Workstation.
A simple

exec sql select count(*) from whatever
into :someint
where someColumn = :someColumn;

will do it (as stated in the included examples)
there is no need for dynamic sql - if I would absolutely use prepare:

you would prepare 'select count(*) into :someIt where some Column = ?'
and provide :someColumn with execute using.

The other way with a cursor and fetch into, I've posted pefore to this

Once again - and hopefully last time -
Darryl, folllow the examples, I've included with the distribution.
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

Please contact support@xxxxxxxxxxxx for any subscription related

This thread ...


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

This mailing list archive is Copyright 1997-2019 by 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].