To facilitate certain processing operations, you can instruct the database to store entity occurrences in a specific portion of an area (non-SQL defined databases only).
By restricting entity occurrences to a specific set of pages, you can minimize overflow conditions.
Displace a clustered entity from its owner
You can displace a clustered entity from its owner. The DISPLACEMENT clause of the non-SQL schema ADD RECORD statement allows you to store clustered entities away from their owner entity in a database area. By specifying the number of pages to displace the clustered entities, you can separate different entity types within a cluster.
Specify a subarea in which to store an entity
You can specify a subarea within an area in which a particular entity is to be stored. To separate CALC entities from other entities in an area, CA IDMS/DB allows you to assign all occurrences of a particular entity type to a range of pages.
For further information, see the WITHIN AREA clauses of the non-SQL schema ADD RECORD statement in CA IDMS Database Administration Guide.
Specify a subarea in which to store an index
When specifying index placement, you can specify a subarea within an area in which the owner of a system-owned index is to be stored. If you decide to place an index in an area with other database entities, you might want to assign the owner to a specific range of pages in the area.
For further information, see the WITHIN AREA clauses of the non-SQL schema ADD SET statement in CA IDMS Database Administration Guide.
As you plan the use of storage resources, you need to keep in mind these options for minimizing overflow conditions in the database.
|
Copyright © 2014 CA.
All rights reserved.
|
|