Why is a DBUTLTY job getting a DB10059E after having migrated to 14.0?

book

Article ID: 18161

calendar_today

Updated On:

Products

Compress Data Compression for MVS Compress Data Compression for Fujitsu Datacom DATACOM - AD Disk Backup and Restore - MVS DISK BACKUP AND RESTORE- ADD-ON OPTIO DISK BACKUP AND RESTORE Ideal 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

Description:

After having upgraded Datacom (AD or DB) to 14.0, a DBUTLTY job, that worked fine with previous release, started failing because of:


 	DB10059E DDNAME RESERVED FOR DATACOM AREA

Solution:

A new check is in place with 14.0, which doesn't allow using DDNAME for the sequential files that can be similar to the DDNAMEs used by Datacom to reference its areas in JCL.

This check is to prevent from accidentally overwriting index or data areas.

Names with the following patterns are not acceptable for DDNAME=:

  • 3-byte names that end with XX, meaning they are reserved as either current or future CA Datacom control areas.

  • 6-byte names that end with what could be a database ID from 001 through 999.

  • 7-byte names that end with what could be a database ID from 1000 through 9999.

Environment

Release: DATABB00200-14-Datacom/AD
Component: