×
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 would create a separate table for each library and then do an exception join. The general approach works with one table though.
Try something like this.
With TESTFILES as (
select file_name as TestFile from dspfdoutput where library = <PREFIX>FTEST)
Select file_name from dspfdoutput exception join TESTFILES on file_name = TestFile
where library = <PREFIX>F
Order by 1
HTH,
Rick
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Monday, November 10, 2008 3:11 AM
To: Midrange Systems Technical Discussion
Subject: Today's SQL Brain Teaser
Hi all,
I have several libraries named <PREFIX>F each having a duplicate library named <PREFIX>FTEST.
All files in library <PREFIX>F SHOULD have a file with the same name in <PREFIX>FTEST. However, there are imperfections and now many files don't exist in the library <PREFIX>FTEST.
I have a file named DSPFD resulting from DSPFD *ALLUSR/*ALL to work with.
I want to list the missing files from the libraries named LIKE '%FTEST%'
No prizes, just thanks for the best reply :
Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
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.