DBUTLTY SPILL job ran in a test MUF environment.
SPILL ran fine, but this error message occurred:
DB00409E - SPILL FOUND POSSIBLE BAD BLOCK, DUMP TAKEN, ERROR 010
Action according to the manual:
The error number that replaces the nnn in the message text is meaningful to CA Support. Collect the
documentation, including the console message and the dump, and contact CA Support.
The date-time in the log records should always go forward. The ERROR 010 occurs when the SPILL detects that the date/time in the log records has gone backwards.
For example looking at this SPILL job, the first LXX entry being written to the RXX is from September the previous year:
DB13113I - RECOVERY END 37-1, TIMES 2018/09/05 14.31.43-2019/02/13 14.50.39
Daylight savings time change was in October 2018 during that spill period causing log records to go back one hour during the SPILL period.
Daylight savings time (DST) instructions were not followed.
CA Datacom 15.1 (and older versions)
Whenever the operating system time is changed, the CA Datacom TIME_SYNC console command must be issued to re-synchronize the MUF date/time with the operating system date/time.
When changing the time for daylight saving, follow the CA Datacom DST instructions which can be found in Article id 46307 - DST Time Change Instructions for CA Datacom/DB and CA Datacom/AD on z/OS
See documentation on MUF TIME_SYNC command.