BACKUP returns ADSDF102 4106 ADR356E (001)-SB207(01)

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

Sometimes when doing a backup you can get the following messages:

ADSDF102 4106 ADR356E (001)-SB207(01), TASK TERMINATED BY UIM EXIT (06) 
ADSDF102 4106 ADR415W (001)-DTDSC(04), NO DATA SETS WERE COPIED, DUMPED, OR    
RESTORED FROM ANY VOLUME    
ADSDF102 4106 ADR324E (001)-DTDSC(01), THE VOLUME/DATA SET SPECIFIED BY    
DDNAME SYS00032 HAS BECOME UNUSABLE    
ADSDF102 4106 ADR339W (001)-DTDSC(01), I/O ERRORS WERE ENCOUNTERED ON THE FOLLOWING DATA SETS DURING PROCESSING FROM VOLSER    
     SYS1.DATASET  

ADSDF102 4106 ADR020E (001)-DEVSU(01), DDNAME SYS00050 NOT FOUND

Cause

The reason could be that DISK encountered an end-of-volume condition on the tape being written, whereby the data set that is just being backed up is not the first data set on the volume. Since DISK does not spill data sets to follow-up volumes. If they are not the first data set on a volume, the operation will be stopped with the message:
TASK TERMINATED BY UIM EXIT (06)

Resolution

This is correct processing, and does not normally mean that data was lost.

1. For LARGE data sets:
   The following action are then to open a new volume, and backup the dataset. In the continuation of the job, you will most likely find this message:
   

   ADR454I (001)-DTDSC(01), THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED
        SYS1.DATASET

2. For ADR020E message, review the Disk report messages and if you see that one:
   

   ADSDM928 3825 DEVICE TYPE=(3490E,CART) CAPACITY=2,000MB ADJUSTED TO 8,000MB ES 
     T FOOTAGE=2,716 ADJUSTED TO 10,864

It means that CARTPRCT is not at its default value of 100 but more. Here it was at 400. Once this is modified to match the tape size. The job will no longer send the UIM EXIT (06) message and all will work fine.

The reason is that Disk calculates the correct space allocation on tape and will not enter on a multi-volume, which makes DFDSS fail on its ESTAE processing.

In summary, the backup run does not lose any data, and all the data sets get backed up successfully.