Abend code 5007 DB347030 non unique page groups binding subschema

Products

• IDMS
• IDMS - Database

Issue/Introduction

An IDMS task abends with code 5007. Error messages:

PREVIOUS TASK ABENDED WITH ABEND CODE 5007
DB347030 non unique page groups binding <name> subschema
DC027007 TASK:<name> PROG:<name> ABENDED WITH CODE 5007

How to determine which segment is causing the issue and how to resolve this.

Environment

Release: 19.0

Cause

The DB347030 and 5007 errors occur when a subschema uses a DBNAME that maps to multiple physical segments that do not contain the same page group or number of records per page (dbkey radix).

To find what segment is causing the problem display the DBTABLE by running IDMSLOOK with:
DMCL ALL 

In the report look for message 'non unique PAGE GROUP' in a segment included in a DBNAME like this:

DBNAME is <dbname>     match on subschema is OPTIONAL

            Include SEGMENT ---> <segment name> non unique PAGE GROUP

Resolution

To resolve the problem, the DBNAME definition in the DBTABLE must be modified to specify MIXED PAGE GROUP BINDS ALLOWED. Then generate, punch and link the DBTABLE.
Use the following syntax in IDMSBCF:

CONNECT TO SYSTEM; 
ALTER DBNAME <dbtable.name>.<dbname>
            MIXED PAGE GROUP BINDS ALLOWED;
GENERATE DBTABLE <dbtable.name>;
PUNCH DBTABLE LOAD MODULE <dbtable.name>;

There are 2 conditions where mixed page groups are not allowed:

• For segments containing dictionary areas, all segments in a dictionary must be in the same page group.
  
  
• For segments containing cross area chained sets, the owner and member records must be in the same page group and have the same number of records per page.

Additional Information

See documentation section Planning a Database Name Table, DBTABLE Statements and DBNAME Statements.