This appendix provides information about the CA CSM system registry environment profiles and the environment variables that they contain.
A set of environment profiles is defined for each non-staging system defined within the CA CSM system registry. Environment profiles logically group related environment variables and represent the execution environment of a given target system.
The variable data contained in the CA CSM system registry is shared by all products managed by CA CSM. The environment variables are available for use by the set of products enabled for configuration by CA CSM. A product configuration only uses the environment variables that are relevant to that product.
Not all environment profile variables contain values. Where allowed, the Software Configuration Service (SCS) uses a single space to indicate no value. Not all variables accept a blank as a valid value. When editing a variable value, delete any blank space and place the cursor at the beginning of the data entry field. Only those environment variables that product configurations reference must contain a value.
The description that is associated with the variable indicates whether a single blank space is allowed. Variables containing the string (blank) are used to show fields containing a single blank value.
In some cases, the environment variable data provides execution preferences that product configurations use to establish the default values specific to a given target system. In other cases, the variables represent the data describing an explicit aspect of the target system. For example, the z/OS version, the CAICCI system name that is associated with the system, or attributes specific to a CICS region.
The environment variables defined for use within a product configuration appear in the Define System Preferences step of the Configuration wizard. The value associated with the environment variables that you have previously specified in the system registry is prepopulated with their respective values.
Note: The composition of the environment profiles within the system registry may change as product configurations are performed when environment variables that those configurations require are not previously defined in the system registry. That is, when you build a product configuration, it is possible for the structure and variables defined in the system registry to be dynamically updated. Therefore, the content of the profiles described in the following sections may not match the system registry at your site.
This section contains the following topics:
|
Copyright © 2014 CA.
All rights reserved.
|
|