Datacom error: DB00409E SPILL FOUND POSSIBLE BAD BLOCK, DUMP TAKEN, ERROR 010
search cancel

Datacom error: DB00409E SPILL FOUND POSSIBLE BAD BLOCK, DUMP TAKEN, ERROR 010

book

Article ID: 127069

calendar_today

Updated On:

Products

Datacom Datacom/DB Datacom/AD

Issue/Introduction

DBUTLTY SPILL job ran in a test MUF environment. The SPILL ran fine, but this error message occurred: 

DB00409E - SPILL FOUND POSSIBLE BAD BLOCK, DUMP TAKEN, ERROR 010 

How should I handle this?

Environment

z/OS

Datacom/AD

Datacom/DB

Cause

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 2023/09/05 14.31.43-2024/02/13 14.50.39 

Daylight savings time change was in October 2023 during that spill period causing log records to go back one hour during the SPILL period. It appears that Daylight savings time (DST) instructions were not followed.

To find out where the time sequence error occurred run a DBUTLTY RXX report on the RXX that got the DB00409E error. 
Sample JCL:

//REPORT   EXEC PGM=DBUTLTY,REGION=0M
//STEPLIB  DD DSN=hlq.CUSLIB,DISP=SHR
//         DD DSN=hlq.CAAXLOAD,DISP=SHR
//RXX      DD DSN=hlq.RXX,DISP=SHR
//SYSOUT   DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSPUNCH DD DUMMY
//SYSUDUMP DD SYSOUT=*
//SYSIN    DD *
 REPORT AREA=RXX,LOGPRINT=DETAIL,TSNPRINT=DETAIL
/*

In the report look for the following line:

WARNING:  DATE/TIME STEP DOWN: FROM mm/dd/yyyy 18.40.37 TO mm/dd/yyyy 17.40.46 

This means that at 18.40.37 a log entry was written with a time of 17.40.46. 
The log entry that follows this warning indicates what job wrote the log record.

Resolution

Whenever the operating system time is changed, the Datacom TIME_SYNC console command must be issued to re-synchronize the MUF date/time with the operating system date/time.

If a shadow MUF is active it is not fully enabled so it is not aware of the time change.
It must either be restarted after the TIME_SYNC command is issued on the primary MUF or the TIME_SYNC command needs to be issued again after switching to the shadow MUF.

When changing the time for daylight saving, follow the Datacom DST instructions which can be found in Article 46307 - DST Time Change Instructions for Datacom/DB and Datacom/AD on z/OS.

Additional Information

See documentation on MUF TIME_SYNC command.