DB002353 area/page not in DMCL in MERGE ARCHIVE job

Products

• IDMS

Issue/Introduction

MERGE ARCHIVE issues the following message:

DB002353 C-4M353: Area/Page 0:1249975 not found in DMCL

What does this mean?

Environment

Release: All supported releases.

Cause

The main purpose of MERGE ARCHIVE is to take archive journal output from multiple CVs in a data sharing environment and merge them into one archive journal file, in order to use it for manually recovering the areas that are data shared by those CVs.

If the utility encounters a journal record for which the record or area is not in the DMCL being used by the utility, it will issue the DB002353 message.

Resolution

The DB002353 message in MERGE ARCHIVE is a warning only but it raises the question of which DMCL the MERGE ARCHIVE utility should use, because typically there is journal input from more than one CV. Ideally, all of the CVs in the data sharing environment should include all of the areas, but that might not always be the case. Individual CVs may have their own dictionaries or other user defined databases that are not in the data sharing environment.

MERGE ARCHIVE does not access the database so for the purposes of creating the SYS002 output file, it does not matter which DMCL is used. All it does is merge the archive journal records. If it encounters an area or record not in the DMCL, it issues the DB002353 warning message but still writes the journal record to SYS002. The main reasons for the DMCL in MERGE ARCHIVE is for retrieving the blocksize for the SYS002 file from the archive journal definition, and for retrieving messages from the DDLDCMSG area.

Nevertheless, if a MERGE ARCHIVE execution does issue DB002353, it should be considered unusual enough that the user must investigate and understand the reason why.