Re: Using global temporary tables -- MIDRANGE-L

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

Marco may have the answer. Probably some difference between the SQL settings in RUN SQL and your RPG.

You didn't tell us what the discrepancy in bindates was. Too many records, missing records, what? Comparing the RUN SQL results from your RPG results would probably throw light on the problem.

And you are checking SQLCODE or SQLSTT after each SQL statement?

Sam
On 12/20/2022 12:17 PM, Howie, Bill wrote:

Hello all,

I have a program where I'm making use of global temporary tables. This is my first experience with them, believe it or not, in a 36-year career. I tested out the queries I wanted to use by putting them in the Run SQL Scripts function in ACS and running them there. All worked fine. I then put them into my RPG application program and tested it and got different results for one of the queries. I've pored over the SQL statements and unless I'm totally blind they are identical. Yet, the query that builds the BINDATES table in my application program yields a slightly different (and inaccurate) result set than the one in Run SQL Scripts.

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.