search cancel

after creating a Page group dictionary in IDMS CV, using IDMSNWKA subschema to access the new dictionary causes DB347030 error


Article ID: 14535


Updated On:




We created a new dictionary Segment (DDLDML and DDLDCLOD) in a non-zero PAGE GROUP.  Created a new DBNAME that includes the new Segment and SYSMSG and any use of Subschema IDMSNWKA, such as in the IDD compilers, causes DB347030 error.

DB347030 Vnn Tnnnn non unique page groups binding IDMSNWKA subschema  

Why do the different Page Groups for the new dictionary Segment and SYSMSG (PG 0) cause this error?


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


Dictionaries cannot utilize Mixed Page Groups.

Subschema IDMSNWKA, used by the IDD compilers contains three areas:  DDLDML, DDLDCLOD and DDLDCMSG.

The dictionary DBNAME you set must have all three areas in the same page group.

If you must define a new dictionary which cannot be defined in PAGE GROUP 0, you must do the following unorthodox definition method to allow IDMSNWKA access to the new dictionary which shares the SYSMSG.DDLDCMSG area.  


To share the ddldcmsg area under different page groups:


For this example we will say that your new dict Segment (areas DDLDML and DDLDCLOD) is defined in page group 10:


- Either create a new segment or include the DDLDCMSG Area in the same segment as your Page Group 10 DDLDML & DDLDCLOD areas.

- The page range for this DDLDCMSG MUST be the Same as the SYSMSG area.

- In the FILE definition the ASSIGN TO name for the file MUST be UNIQUE 

- Do NOT code a DSNAME for the file.

- When including the segment into the DMCL be certain to code an override for the DDLDCMSG Area ON STARTUP SET STATUS TO RETRIEVAL.

- Add a DD to startup using the Unique ASSIGN TO name from File def mentioned above but point to the SAME DSN as SYSMSG.DDLDCMSG


* If you created a separate segment for this area, include that segment in the DBNAME that describes the PG 10 dict.