DISK - DMSAR - doesn't finish after restore

Products

• Disk Backup and Restore - MVS
• Vantage Storage Resource Manager

Issue/Introduction

During a Restore via DMSAR, the restore is not finished, the database of DISK is held and gets contention with other DMSAR instances and jobs. The following message is displayed on the DISKMUF STC:
DB00311I - LOG AREA IS 100% FULL, SPILLING TRACK NONE, OUT OF 9996

Resolution

When the DB00308I is displayed on the MUF STC  a DBUTLTY should be run using 
 SPILLOPT SPILL=MAX in SYSIN.

Following is the job that needs to be run when the LOG AREA is full and more information : DBSPILL - Spill the LXX to the RXX Recovery Files. When the LXX has reached the reporting percentage that is specified in the LXXSPILL Datacom/AD startup options, the following message is issued:
 DB00308I LOG AREA IS nnn% FULL, nnnnnn BLOCKS SPILLABLE

It is recommended to set up automated operations to run the DBSPILL job when this message is issued.
To create a recovery file, a spill job must be run to remove completed transactions from the database log, the LXX, and write them to the recovery file, the RXX. This process saves the recovery information for forward recovery and frees up space in the LXX. You can find a sample spill job—DBSPILL— in the INSTALL library. The job can be run on a periodic basis or through automation when the LXX reaches a defined threshold. If the LXX is allowed to fill up, the database stops processing until the spill job is run. This causes processing to halt until space is freed in the LXX. The MUF must be up for this job to run.

//DBSPILL  JOB (1),'DISK',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
//*****************************************************************************************
//*                                                                                                                          *
//*    SAMPLE SPILL OF    DATACOM/AD LOG RECORDS TO TAPE                *
//*                                                                                                                          *
//*    PLEASE REFER TO    DATACOM/AD MANUALS FOR THE USE OF LOG*
//*    RECORDS FOR FORWARD RECOVERY.                                                   *
//*                                                                                                                           *
//*    THE MUF MUST BE UP TO RUN THIS JOB.                                                *
//*                                                                                                                            *
//******************************************************************************************
//SPILL         EXEC        PGM=DBUTLTY,REGION=4M
//STEPLIB        DD          DISP=SHR,DSN=CAI.DISK.*.CUSLIB
//                       DD          DISP=SHR,DSN=CAI.DISK.*.CAILIB
//SYSPRINT     DD          SYSOUT=*
//CXX               DD          DISP=SHR,DSN=CAI.DISK.*.CXX
//RXX               DD          DISP=(NEW,CATLG),DSN=CAI.DISK.*.RXX(+1),
//                         UNIT=CART
//SYSIN        DD   *
 SPILLOPT  SPILL=MAX
/*
Consider the following points before customizing the sample:
1. Ensure Datacom/AD MUF is active.
2. Ensure that the RXX DD contains all the RXX data sets created since the DBBKHOT or DBBKSTAT job ran.
3. Since the job is generally a tape or cartridge job, add any site-specific requirements that you may have such as a special job class or SETUP control statements.
4. Run the DBSPILL job.