Does anyone use SET ALL=PASS anymore?

Bonjour,
SET ALL=ON, SET ALL=OFF, SET ALL=PASS made me sweat a great deal, because somebody who didn't have a telephone number was forgotten in my lists of people who owed more than XXXX Francs (at the time).
A nice and easy way not to pay one's debt.
At the time, a specialist of IBF, took the time to explain me everything about those powerful Sets ( Including Useless on SEGTYPE = U )
Those Sets are obviously Focus+ level. It does not at all mean they are Useless.
They are somewhere in the very Heart of Focus and it's way to turn into Procedural Action its Global and Biblic langage ( "Reading and Filtering Data : How the internal Matrix is constituted" - Myownmemory.My-Important-Focuseries.fr )
Cordially and Focusely
PS : Since when are the LEFT Outer Join available in DB2 ? Our Focus Sets are older

I'm not saying I use it every day, but it is certainly not a forgotten setting in my book.
Why do you ask?

In my experience, SET ALL=PASS is a mess with DB2. It does not generate the correct SQL, even with SQL DB2 SET SQLJOIN OUTER ON.

I might be off base and if I am, I apologize. However, the last ferw posting seem to gotten away from the original subject of this posting. Can we get back to the posting's issue, please?

Here is the thrust of the original posting:

01) Create Sunday file
02) On Monday, run program to create a Monday file.
03) Compare Sunday File against Monday file.
04) Pull off unmatching records from Monday file into a "Difference" file.
05) Make an output Excel file of the unmatched records for subsequent FTP-ing to a server.
06) Append the unmatched records from the Monday file to the Sunday file.

07) On Tuesday, repeat the process, this time using the Tuesady file agaisnt the Sunday file.

08) On Wednesday, repeat the process, this time, using the Wednesday file against the Sunday file.

09) On Thrusday, repeat the process, this time using the Thursday file against the Friday file.

10) On Friday, repeat the process, this time using the Friday file against the Sunday file.

11) The following week, DO NOT create a new Sunday file... we're going to utilize the original Sunday file.

12) On Monday of the following week, compare the following week's Monday file against the original Sunday file.

13) On Tuesday, repeat the process.

14) In other words, once an original Sunday file has been created, then each subsequent day's file will be processed against it.

Hopefully this clears up some of the confusions my posting seems to have created.

Thank you to all who have responded.

I wasn't going away from the subject. Example:

-* example sunday file.
TABLE FILE CAR
SUM
     DEALER_COST
     RETAIL_COST
     SALES
BY COUNTRY
BY CAR
BY MODEL
WHERE MODEL OMITS 'AUTO';
ON TABLE HOLD AS SUNDAY FORMAT ALPHA
END

-* example monday file.
TABLE FILE CAR
SUM
     DEALER_COST
     RETAIL_COST
     SALES
BY COUNTRY
BY CAR
BY MODEL
ON TABLE HOLD AS MONDAY FORMAT ALPHA
END

-* join 'em ... note the all
JOIN 
	COUNTRY AND CAR AND MODEL IN MONDAY TO ALL
	COUNTRY AND CAR AND MODEL IN SUNDAY AS J1.
END

-* set all to pass
SET ALL=PASS

TABLE FILE MONDAY
PRINT MONDAY.DEALER_COST MONDAY.RETAIL_COST MONDAY.SALES
BY MONDAY.COUNTRY 
BY MONDAY.CAR
BY MONDAY.MODEL
-* enforce the all=pass with a B/S condition
WHERE SUNDAY.COUNTRY EQ 'NOTHING';
END
  

Understood... actually, it was some of the subsequent responses that seemed to get a bit of the subject. Thanks for replying.