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

Document ID : KB000018161
Last Modified Date : 14/02/2018
Show Technical Document Details

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.