DBUTLTY job getting a DB10059E after migrated to Datacom 14.0

Products

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

Issue/Introduction

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

Environment

Release: From 14.0

Resolution

A new check is in place starting 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.

Additional Information

See the documentation section for message DB10059E