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



I have an issue where the case of the select verb (SELECT vs select), in an
interactive SQL session, was affecting the
records selected for the result set.

We have since determined that it has something to do with exiting and saving
the interactive SQL session.

After exiting and saving an inteactive SQL session, and then at the command
line, we remove a library from the library list and then restart the saved
sql session, the current library list appears to not be utilized (by the
re-started sql session) but instead, the library list used is from when the
session was ended/saved (it doesn't reflect the new library list after it
was altered).

Then during the restarted sql session, changing the case of the select verb
will result in different record sets being displayed and if we display the
job via sys-req #3 and look at the library list, (in either circumstance)
the library
lists are identical, but the records are from different files in different
libraries (one of which is in a library that is no longer in the library
list, (but it was in the library list in of the saved sql session, before
the session was ended and the library list was changed)).

Is there any way to remedy this annoyance? Is this a bug or a feature?

We are running V5R1, and have all the current ptf's as of 8/2/2002.

Thanks in advance. Jerry Kern




As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.