Resolving a RC 72 (004) error from DBUTLTY LOAD

Products

• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

When loading data into a data area, the DBUTLTY process first ensures that the file used to receive the loaded data is valid. If there is a problem with the control block of that data area, the job will fail with this error message in the job log:

DB00501E - OPEN ERROR - RETURN CODE 72 (004) CXX=cxxname  (aaaddddd)

where:
cxxname is the CXX being used to access the data area, 
aaa is the area ID,
ddddd is the database ID 

You might also see this error in the output of the job:

DB13018E - OPEN ERROR, RETURN CODE 72 (4) I/O WLR/NRF/ERR OPEN CTL BLK

Environment

Release: DATABB00200-14.0-Datacom/AD
Component:

Resolution

When receiving this error on a DBUTLTY LOAD function, one of the most common causes is that the data area was not correctly initialized by the DBUTLTY INIT function. If the intent of the LOAD is to replace the contents of the data area, we recommend adding a function to initialize this data area first: INIT DBID=ddd,AREA=aaa

However, if you believe that the area has been previously initialized correctly, it is possible that the control block has become corrupted. In this case, we recommend that you run a CXX report to get the file name for the area having the error, and then run a DBUTLTY report to provide information about the file, taken from the control block. You can use this input to produce the report:

//SYSIN    DD  *
  REPORT TYPE=U,DDNAME=TESTDD
/*

//TESTDD  DD DSN= <<-- your filename from the CXX

Then, please open a support case for this problem and attach the output of this job, along with a screen print of the ISPF 3.2 allocation details for the file, so we can review the information and advise you accordingly. If the above DBUTLTY report does not correctly identify the file as a CA Datacom data area, please run IDCAMS to print the first record in the file and attach that output. You can use JCL like this:

//PRINT    EXEC PGM=IDCAMS            
//SYSPRINT DD SYSOUT=*                
//IF01     DD DISP=SHR,DSN= <<-- your filename from the XX   
//SYSIN    DD *                       
  PRINT   COUNT(1) DUMP INFILE(IF01)  
/*                                    

Additional Information

As always, please contact CA Technologies support for CA Datacom if you have further questions.