Datacom EXTEND IEC145I 413-1C, 13 (005), 76 (009)

Products

• CA Datacom - DB
• CA Datacom
• CA Datacom - AD
• CA Datacom - Server
• CA CIS
• CA Common Services for z/OS
• CA 90s Services
• CA Database Management Solutions for DB2 for z/OS
• CA Common Product Services Component
• CA Common Services
• CA Datacom/AD
• CA ecoMeter Server Component FOC
• CA Easytrieve Report Generator for Common Services
• CA Infocai Maintenance
• CA IPC
• Unicenter CA-JCLCheck Common Component
• CA Mainframe VM Product Manager
• CA Chorus Software Manager
• CA On Demand Portal
• CA Service Desk Manager - Unified Self Service
• CA PAM Client for Linux for zSeries
• CA Mainframe Connector for Linux on System z
• CA Graphical Management Interface
• CA Web Administrator for Top Secret
• CA CA- Xpertware

Issue/Introduction

Doing a  CA Datacom DBUTLTY EXTEND is getting the following errors:

IEC145I 413-1C,IFG0193A,jobname,stepname,ddname,device,volser,dsn
DB02405I - PXX START jobname nnnnn 13(005) XXXXB-nnn-    D-1 DBUTLTY EXTEND
DB02406I - PXX END - INVALID DASD TRACK OUTSIDE EXTENTS
IEF450I jobname  stepname - ABEND=S000 U0004 REASON=00000000  159

A second EXTEND, an EXTRACT or any attempt to open the file gets error:

DB02405I - PXX START jobname nnnnn 76(009) OPEN -nnn-    D-1 DBUTLTY EXTEND
DB02406I - PXX END - OPEN, NOT ENOUGH TRACKS
DB00501E - OPEN ERROR - RETURN CODE 76 (009) CXX=xxxxxx  nnnnnn

Cause

This was found not to be a Datacom issue. 
The problem is due to a z/OS problem with managing the VTOC. Currently there is no IBM PTF to fix the problem. It causes the last volume of a multi-volume dataset to have a VTOC entry that does not have the "last volume" bit set on.  

Environment

Release: DATABB00200-14.0-Datacom/AD
Component:

Resolution

Normally to recover from these errors you would need to reallocate the file, run a DBUTLTY INIT and LOAD from a backup or restore the file using system utilities.
In this case you may be able to resolve this by contacting IBM. They can provide instructions to manually zap the "last volume" bit into the VTOC entry of the last volume of the data set.  All the extents would then be accessible and you would not need to restore the file.

 

Additional Information

See DocOps Return Code 76 - OPEN ERROR and Return Code 13 - INTERNAL ERROR