Previous Topic: Use CA Service Desk SupportNext Topic: Use Same Local Parmlib for All Systems


Disable Unused CA Allocate Environments

Disable unused CA Allocate Environments to improve performance.

Business Value:

You can reduce CPU usage by eliminating the overhead associated with initializing an unused Environment. You improve the performance of CA Allocate.

Additional Considerations:

The CA Allocate Environment indicates what allocation action CA Allocate requires. Depending on the Environment, your Allocation Selection Routine (ASR) takes different actions. For example, the &NEWNAME variable is selected only in the RENAME Environment, because only the RENAME Environment creates a new name. Likewise, for a new space allocation, you select different variables and take different actions than the actions that you do for a scratch operation.

If you do not want to use an Environment, CA Allocate provides a sysparm for each Environment that allows you to disable logically the initialization of that Environment. Logically disabling the Environment initialization results in a run-time performance improvement because the overhead associated with the logical initialization of those Environments is not needed. The default value of each of the Environment sysparms is (Y), which causes each Environment to be initialized for applicable allocation requests. To disable logically the initialization of any particular Environment, specify a value of (N) in your sysparm override member before either an INSTALL or PARMREF operation.

More Information:

For more information, see the section Environments in the chapter "Concepts and Facilities" in the User Guide.