×
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.
Here's my query (field and file names obfuscated due to company policy).
SELECT FIELD1, FIELD2, FIELD3, FIELD4
FROM FILE1
LEFT OUTER JOIN FILE2
ON FIELD1 = FIELDA
ORDER BY FIELD1 ASC, FIELDB ASC
Prior to upgrading this was run from a CLLE program using the STRQMQRY command and used 'FILE1' and 'FILE2' from the user's library list. Since upgrading (which I know may just be coincidence), the STRQMQRY command fails. A check of the user's job log reveals the following:
FILE1 in WEIRDLIB type *FILE not found
RUN QUERY command failed with SQLCODE -204.
What I can't figure out is where WEIRDLIB is coming from. It isn't hard-coded in the query. The library does exist, but is not anywhere in the users library list. I've also verified that WEIRDLIB isn't set as the users CURLIB.
If I run the STRQMQRY command myself from a command line it also fails trying to find FILE1 in WEIRDLIB. However, it runs to completion with no errors if I run the query using option 9 from 'Work With Query Management Queries'.
What am I missing?
Emily Smith
CONFIDENTIALITY NOTICE: This email message is private, confidential property of the sender, and the materials may be privileged communications intended solely for the receipt, use, benefit, and information of the intended recipient, you are hereby notified that any review, disclosure, distribution, copying, or taking of any other action in reference to the contents of this message is strictly prohibited, and may result in legal liability on your part. If you have received this message in error, please notify the sender immediately and delete this message from your system. We believe that this email and any attachments are free of any virus or other defect that might affect any computer system that it is received and opened in, however, it is the responsibility of the recipient to ensure that it is virus free and the sender accepts no responsibility for any loss or damage.
As an Amazon Associate we earn from qualifying purchases.
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.