CA Hyper-Buf implements several levels of control at which you can specify constraints. These levels (from least specific to most specific) are as follows:
Within each of the above levels, you can impose constraints on CA Hyper-Buf. Constraints include the maximum allowable amount of virtual storage that can be used at OPEN time for buffers, the minimum amount of virtual storage that you want left available in the region below 16M after the OPEN completes, the maximum number of data and index buffers that CA Hyper-Buf can select for an OPEN, and so forth, all of which is explained later in Chapter 3, "Constraint Control Statements."
Most of the constraints are available at each of the above levels. Any constraints that are restricted in any way are documented with the restrictions explicitly mentioned. This means that you can adjust the constraints for specific clusters, jobs, and programs if you wish, or you can set only the system level constraints that apply to all OPENs.
The system level constraints are used as the default for any OPEN constraints that are not specified at any of the other levels. If you do not supply a system default for any constraint, CA Hyper-Buf creates a default for you.
|
Copyright © 2011 CA.
All rights reserved.
|
|