Previous Topic: Mixed Page Groups and Maximum Records Per PageNext Topic: Defining and Generating the Database Name Table


Sharing Database Name Tables

One Database Name Table Per Environment

In most cases only one database name table is needed for each of your runtime environments. This means that all DMCLs defined in a system dictionary normally specify the same database name table in their DBTABLE clause. The database name table used at runtime is the one identified in the DMCL being used.

Missing Segments

Since multiple DMCLs are associated with the same database name table, it is possible (in fact likely) that a segment included in a database name is not included in the DMCL being used. This is a normal condition and will result in an error only if an application attempts to access data from the missing segment.