avoid DB347011 error

book

Article ID: 35784

calendar_today

Updated On:

Products

CA IDMS CA IDMS - Database CA IDMS - ADS

Issue/Introduction

Question:

Is there any way to catch a DBTABLE issue during the GENERATE? 

This morning a DBA made the following change. 

MODIFY 
DBTABLE GLBLDBTB 
; 
Status = 0 SQLSTATE = 00000 
MODIFY 
DBNAME GLBLDBTB.DBNAM01 
INCLUDE SEGMENT EMPSEG
; 
Status = 0 SQLSTATE = 00000 
GENERATE DBTABLE GLBLDBTB ; 
Status = 0 SQLSTATE = 00000 

After the New Copy, we started getting the DB347011 errors since another SEGMENT in the DBNAM01 DBNAME had the same AREAS included in it.

If the GENERATE does not catch this situation, how do I catch the DB347011 Error prior to putting this change into effect?

 

Answer:

 

No, the generate of the DBTABLE does not catch this situation.
One thing you can do after modifying a DMCL and or DBTABLE is run the IDMSLOOK utility with the DMCL parameter. 

As an example, I added SEGMENT APPLDICT to a DBNAME that already had a dictionary segment and, the LOOK report indicates a warning when a DBNAME includes SEGMENTS with conflicting area names.

DBNAME is ASFDICT match on subschema is OPTIONAL 
** Warning ** DBNAME includes SEGMENTS with conflicting AREA names in the DMCL 
Include SEGMENT ---> APPLDICT 0 BIN 
Include SEGMENT ---> ASFDICT 0 BIN 
Include SEGMENT ---> SYSMSG 0 BIN

Environment

Release: IDADSO00100-18.5-ADS-for CA-IDMS
Component: