DBNAMEs and subschema mapping receiving DB347003 1474

Document ID:  TEC1866207
Last Modified Date:  06/08/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA IDMS

Releases

  • CA IDMS:Release:18.0
  • CA IDMS:Release:18.5
  • CA IDMS:Release:19.0

Components

  • CA IDMS/DB:IDMS
Question:

I have this situation

 

DBNAME *DEFAULT MATCH ON SUBSCHEMA IS OPTIONAL

SUBSCHEMA ABC????? MAPS TO ABC????? USING DBNAME AB1

 

and

 

DBNAME AB1 MATCH ON SUBSCHEMA IS OPTIONAL

SEGMENT RECAB101 180 BIND count

SUBSCHEMA ABC????? MAPS TO ABC????1

 

If I do a BIND RU, with the subschema ABC01014 and I don't specify a dbname, I expect the search to match the default statement, find it and matches to dbname AB1.

 

With AB1 entries I expect the subschema name to be change for ABC01011.

 

But no, the subschema name remains ABC01014 and we get 1474

DB347003 V1850 T736 ABC01014 subschema not found

 

I changed the default statement for

DBNAME *DEFAULT MATCH ON SUBSCHEMA IS OPTIONAL

SUBSCHEMA ABC????? MAPS TO ABC????1 USING DBNAME AB1

and the problem is corrected.

 

 

So, do I understood when the matches operate with the default DBNAME, the MAPS statement in the DBNAME is not in effect? 

Answer:

It is working correctly. IDMS only does the subschema matches at the first level that it finds. With no DBNAME specified that is the default specified on the DBTABLE level. If a DBNAME is specified on the BIND RUNUNIT then we'd expect to find the translation from that DBNAME to be applied.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >