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


Article ID: 18161


Updated On:


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



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



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.


Release: DATABB00200-14-Datacom/AD