By: donethat

donethat — Wed, 06 Jan 2010 16:15:21 +0000

Perhaps this SQL routine I use to fix bad dates would help?
The dates in our legacy system are all CC YY MM DD. I use it to set all invalid dates to 1/1/1950.
You can easily adapt.
FYI: I’m not the original author. Lost the proper attribution.

UPDATE	r091128pe.cusmas AS UCM

SET	UCM.cm_chg_cn  =  19,
	UCM.cm_chg_yr  =  50,
	UCM.cm_chg_mo  =  01,
	UCM.cm_chg_da  =  01

WHERE	
/*  Any TRUE statement is an INvalid date.  */
	(	UCM.cm_chg_cn  NOT IN  ( 19, 20 )
			OR
		UCM.cm_chg_cn  =  19  AND  UCM.cm_chg_yr  NOT BETWEEN  50 AND 99
			OR
		UCM.cm_chg_cn  =  20  AND  UCM.cm_chg_yr  NOT BETWEEN  00 AND 49
			OR
		UCM.cm_chg_mo  NOT BETWEEN  01 AND 12
			OR
		UCM.cm_chg_mo  IN  ( 1, 3, 5, 7, 8, 10, 12 )  AND  UCM.cm_chg_da
							NOT BETWEEN  01 AND 31
			OR
		UCM.cm_chg_mo  IN  ( 4, 6, 9, 11 )  AND  UCM.cm_chg_da
							NOT BETWEEN  01 AND 30
			OR
		UCM.cm_chg_mo  =  2  AND  UCM.cm_chg_mo  NOT BETWEEN  01 AND 28
			OR
		UCM.cm_chg_mo  =  2  AND  UCM.cm_chg_yr  =  00  AND  UCM.cm_chg_mo
							NOT BETWEEN  01 AND 28
			OR
		UCM.cm_chg_mo  =  2  AND  UCM.cm_chg_yr  IN  ( 4, 12, 16, 20,
				24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64,
				68, 72, 76, 80, 84, 88, 92, 96 )  AND  UCM.cm_chg_mo
							NOT BETWEEN  01 AND 29
	)

WITH	NC;

Gary

Comments on: SQL0181 error when sending PF from iSeries to PC

By: donethat