If for whatever reason the utility blows up (ran out of space, whatever) and I choose to RESTART it I want it to skip processing those records in the SYSREC that were already inserted successfully.

But in my testing I am finding that the utility clutters up my SYSDISC with the records that were inserted before the abend (which I don’t want to process) in addition to the ones caused by there being duplicates to begin with (which i do want to process).

Is there a way to force the utility to RESTART in such a way that it will start reading teh SYSREC only from the last commit? I tried UTILID=’RESTART(CURRENT)’- no good.

I have RESUME YES, SHRLEVEL CHANGE.

Thanks a lot for your time

SELECT COUNT(*), DAYS(TMSTP_COL)
FROM MYTAB A
GROUP BY DAYS(TMSTP_COL)
HAVING COUNT(*) > 1
ORDER BY COUNT(*) DESC

I get an error
DSNT408I SQLCODE = -104, ERROR: ILLEGAL SYMBOL “(“.

I know it is complaining about the DAYS function since the moment I remove it, the error goes away

Thanks

Our automated utilities is now draining us with heavy maintenance and since V7, there are still a few holes that could cause us some serious damage if not fixed in the near future. However, with V8, we would definitely have problems and we have justified the evaluation of an Automated Utility toolset. This would need to be in place before we go to V8.

I am of the opinion that we should have one suite for the purpose of DB2 maintenance, backup and recovery, thinking that multiple vendor support here would become a ‘mare.

We are also well vested in IBM’s utilities across development staff who maintain their own data in the development subsystems.

Has anyone done this excercise – if so, which product did you select? and a any additional comments would be great.
thank you.