ADSDM083 9999 SEVERE ERROR ENCOUNTERED PROCESSING FILES
search cancel

ADSDM083 9999 SEVERE ERROR ENCOUNTERED PROCESSING FILES

book

Article ID: 442354

calendar_today

Updated On:

Products

Disk Backup and Restore - MVS

Issue/Introduction

The Following messages have been encoutered during a backup of the files:

IOS000I A552,61,IOE,92,0E40,,0798000D,SYT042,BACKDMSD,  459                                                      
  0000100052FFFFF0060000000000000000000000A500FEF0001E60820007980E                                                
 ADSDM083 9999 SEVERE ERROR ENCOUNTERED PROCESSING FILES xxxxxx ON VOLUME NNNNNN                 
                                                                                                                  
 ADSDM083 9999 FDS WRITE-ERROR: EVENT=IOE,CC=41,SENSE=0000,CSW=0015E358 0E400008,@CP=15E338,SEEK=00000007 98000D01
 ADSDM083 9999 FDS WRITE-ERROR: @IOB=0015E860,@DCB=0015E8A8,@DEB=AB0844                                           
 ADSDM083 9999 FDS WRITE-ERROR: EXTENT NUM=000,STR-CC.HH=077A.0000,END-CC.HH=07DD.000E,NUMBER-OF-TRACKS= 1,500    
 ADSDM083 9999 PERMANENT I/O ERROR CONDITION DETECTED.                                                            

Resolution

 

To have more informations why the the following message

 ADSDM083 9999 SEVERE ERROR ENCOUNTERED PROCESSING FILES xxxxxx ON VOLUME NNNNNN   

is displayed, a DSETMAP, found in the CCUWJCL library of CA DISK, is advised to run and analyze it. 

To prevent a reoccurrence of this problem a FDS Unload/reload is usually suggested.

 Stop all the other CA-Disk jobs (like backup or archive) from running.
 Place them on hold and stop any job that may update the FDS). 
Then  the following steps can be run to unload / reload the FILES:
1. First execute the UNLOAD utility and unload the FDS to a seq file.
      UNLOAD ALL
 
 2. Rename the FDS to 'old'.
 
 3. Execute a FILEINIT job to initiate a new FDS, you can find a sample JCL
    of FILEINIT in your CA DISK CCUWJCL library, or hopefully the old JCL from
    your predecessor is still around.
 
    The FILEINIT job will call in member FILEDEFN located in CA-Disk PARMLIB
 
 4. Then execute a RELOAD into the new FDS, using the output from step one
     (UNLOAD) as input.
 
     RELOAD ALL,FORMAT

   
 As for Vantage and Allocate, there is no need to stop them. although if the Vantage ARM is used to control your DMSARs, it should be suspended from submitting any request until the unload / reload of FILES is done.