Avoid DB347011 runtime error at GENERATE time

Products

• IDMS

Issue/Introduction

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

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, DB347011 errors started appearing since another SEGMENT in the DBNAM01 DBNAME had the same AREAS included in it.

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

Environment

Release: All supported releases.

Resolution

No. The generate of the DBTABLE does not catch this situation.

One way to catch this is to run IDMLOOK on the DMCL after the GENERATE. IDMSLOOK will catch it. 

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