In most cases, each application dictionary will require a separate database name definition. The only time a database name definition is not required for a dictionary is if all areas other than the system message area are in one segment.
Note: For more information about defining dictionaries, see Chapter 25, “Dictionaries and Runtime Environments".
If areas are shared between dictionaries, place those areas in separate segments and include the segment in all appropriate database names. For example, if two or more dictionaries share the same DDLDCLOD area, then place the load area in its own segment and define a database name for each dictionary including in each the segment that contains the shared load area.
If your dictionaries have different page groups (or maximum records per page), they cannot share areas. This also applies to the system message area, which can be included only in dictionaries with the same page group.
Note: All of the AREAS in a dictionary subschema (for example, IDMSNWKA, IDMSNWKG, and so on) must be in the same PAGE GROUP. A BIND for such a subschema containing AREAS that map to different PAGE GROUPS is not supported and will result in the task being abended with error messages DB347030 and DC208001 and abend code 5007.
|
Copyright © 2014 CA.
All rights reserved.
|
|