If you have database areas with conflicting names, you must define separate database names for each set of conflicting areas. This means that if two segments have an identically named area, they cannot be included within the same database name. Areas that must be shared across databases (for example, areas containing corporate-wide insurance information) should be placed in their own segment so that they can be included in multiple database names without causing conflicts.
If a DMCL includes a segment with the same name as a database in the associated database name table, then that database name must include the segment of the same name. For example, if a DMCL contains a segment named EMPDB and its associated database name table contains a database name called EMPDB, then the segment EMPDB must be included in the database named EMPDB. This ensures that applications accessing EMPDB will always access the same data.
Both of the above conditions are checked by the runtime system. If a name conflict is detected, the database name is flagged in error and no application will be able to access it. To detect conflicts before placing a new DMCL or database name table into production, use the DMCL option of the IDMSLOOK utility.
To eliminate warning messages for database names created only for administrative convenience, you can designate them for utility use only.
|
Copyright © 2014 CA.
All rights reserved.
|
|