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



Check the following user profile settings for any differences between yours
and his profile:

Sort sequence . . . . . . . . .
Library . . . . . . . . . . .
Language ID . . . . . . . . . .
Country or region ID . . . . . .
Coded character set ID . . . . .
Character identifier control . .
Locale job attributes . . . . .
Locale . . . . . . . . . . . . .

Hth, Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: Re: Is this an SQL problem or quirk

Thanks for your reply Charles
It may seem that either, we both need new glasses, or its some mass
hallucination between us, but the LONG story was
1/. we thought that he had a weird version of the custadrp file (not true)
2/. he was signed onto a different box (not true - the file APTSCAN ONLY
exists in my library on the development box)
3/. we changed the SQL to ONLY look at the files in the named libraries
the result was still the same.
Run the SQL signed on as me - no problems, the results were as expected.
Run the SQL signed on as him (at the same terminal in fact, different
sessions) the weird results are displayed
In all circumstances we copied the SQL statement and pasted the same SQL
statement into each sessions STRSQL
So we can definitely say that the SQL statement is NOT the problem


Alan Shore




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.