CSV003I REQUESTED MODULE <garbage> NOT FOUND and ABEND806-04 in DBUTLTY BACKUP or EXTRACT

Products

• Datacom
• DATACOM - AD
• Datacom/AD
• Datacom/DB

Issue/Introduction

While trying to run a backup on a database that has never had a problem, error messages appeared:

DB00101I - STARTED JOB-DBBACKUP1 NUMBER-11334 CXX=DBMUFPR1 MUFNAME=DBMUFPR1
CSV003I REQUESTED MODULE 01{{ Ý NOT FOUND
CSV028I ABEND806-04 JOBNAME=DBBACKUP1 STEPNAME=BKPSTEP4

The CXX showed that User Compression was turned on for a table, but the Compression Exit shows corruption: USER COMPRESSION - YES(01{{ Ý.Å)

Environment

Release: All supported releases.

Cause

The cause is currently unknown, but there are several diagnostics to perform, after which a support case should be opened.

1. First, ensure that no one has changed the definition or cataloged a new version of the database since the last good backup.
2. Next, be sure that no one inadvertently changed or updated the CXX data using a non-Datacom utility, by reviewing SMF data.
3. Run a DDUTILTY Detail report for all the tables in the subject database, using this SYSIN:
   //SYSIN        DD *                       
   -USR DATACOM-INSTALL,NEWUSER              
   -DEF PATH,PATH1                           
   -DEF TRACE,DATABASE.AREA,$INTERNAL        
   -DEF TRACE,AREA.TABLE,$INTERNAL           
   -END                                      
   -RPT START,DATABASE,?????,PATH1  
   -RPT DETAIL                               
   -END                                      
   /*
4. A full CXX report should be run for all databases in the MUF, to ensure that no other tables have this same corruption, and a report of the CXX control blocks to show its data. Please use this SYSIN:
   //DD01   DD  DISP=SHR,DSN=your cxx file
   //SYSIN  DD  *
     REPORT TYPE=U,DDNAME=DD01
     REPORT AREA=CXX
   /*
5. An SQL query (using DBSQLPR) can be run to see if the results in the CXX match what is in the internal configuration found in the Datacom System Tables. In the following example, the report can be reduced by adding WHERE DBID = ## to list a single DBID that has a problem. Likewise, if you are using your own compression routines, and want to eliminate these from the report, you can add WHERE COMPRESS_EXIT <> ‘exitname' where exitname is the name of your routine.
   //SYSIN    DD  *                      
   SELECT DBID          AS DBID          
         ,AREA_NAME     AS ARA           
         ,TABLE_NAME    AS TBL           
         ,OCCURRENCE    AS TBL_NAME      
         ,COMPRESSION   AS COMP          
         ,COMPRESS_EXIT AS COMP_EXIT     
     FROM SYSADM.DIR_TABLE;
   /*
6. Along with these reports, if an error occurs, an SVC dump should be taken as soon as possible, to allow support to see the state of the MUF and the internal data elements. To produce this dump from the console, here is a set of commands and responses:
   (you ) DUMP COMM=(1-100 characters of title text)
   (resp) *xx IEE094D SPECIFY OPERAND(S) FOR DUMP COMMAND
   (you ) R xx,JOBNAME=jobname,SDATA=(CSA,SQA,LSQA,SWA,LPA,PSA,RGN,SUM,TRT,GRSQ),END
   (resp) *IEA911E COMPLETE DUMP ON SYS1.DUMP## (note this filename)
7. Once you have gathered this information, please provide the failed job output, the output of the above DBUTLTY, DDUTILTY, and SQL jobs, and the SVC dump to technical support with a new support case.

Resolution

If you have determined that nothing should have changed with this database definition, you have two options:

1. You can reload the CXX definition from a recent backup, or
2. You can run a Datadictionary process to Catalog the current production definition to the CXX and overlay the bad fields.

Note that if you reload the CXX data from a backup and if this is an active database, your record counts could now be incorrect, and you should run a DBUTLTY RETIX DBID=###,AREA=xxx,KEYNAME=*SETR command to recount the records in each area.