System options affect the overall behavior of CICS® Configuration Manager, and hence affect every user. Each system option is either active or inactive; by default, all system options are inactive. Table 1 describes the system options and their effects.
Compare these system options, whose values are the same for all users, with the ISPF dialog user options, which can be different for each user. For details, see Setting user options.
System option (CCVXSYSO parameter) 1 |
Effect | |
---|---|---|
Inactive (default) | Active | |
Approval checking for change packages (PackageApprovals) |
No change packages require approval before migration. CICS Configuration Manager does not check whether change packages have been fully approved before migrating them. | Change packages may require approval. For details, see Change package approval. |
Automatic change package numbering (PackageAutoNumber) |
Users can specify their own alphanumeric change package identifiers. | New change packages are automatically assigned
the next available 8-digit identifier (00000001, 00000002, etc.). Users cannot specify their own change package identifiers. |
Security checking for server API commands 2 (SecurityActive) |
The CICS Configuration Manager server does not
check whether users are authorized to perform server API commands. This includes API commands for approving or disapproving change packages. If security checking is inactive, then any user can represent any approval role to approve or disapprove any change package. When you attempt to activate security checking for server API commands, the CICS Configuration Manager server checks whether you have the authority to update the system options. The server performs this check even if security checking is currently inactive. |
Each time the CICS Configuration Manager server receives an API command from a client (such as the ISPF dialog interface), the server checks whether the user is authorized to perform that API command. |
Security checking for resource definition keys 2 (ObjectSecurityActive) |
The CICS Configuration Manager server does not check whether users are authorized to manipulate resource definitions based on the resource definition key values (group, type, and name). | For some API commands, each time the command attempts to manipulate a resource definition, the server checks whether the user who requested the command is authorized to manipulate a resource definition with those key values. |
Transformation processing for resource migrations (TransformRulesActive) |
Transformation rule sets are ignored. When migrating a change package, CICS Configuration Manager copies candidate resource definitions directly from the source to the target CICS configurations. | When migrating a change package, CICS Configuration Manager uses the transformation rule sets identified by the migration scheme to transform candidate resource definitions. |
Automatic remove of deleted groups from CSD
lists (AutoRemoveDeletedGroups) |
If CICS Configuration Manager detects that a CSD-based group is deleted or emptied (as a result of delete or rename processing), then CICS Configuration Manager performs no action, except to display information messages about the affected lists. | If CICS Configuration Manager detects that a CSD-based group is deleted or emptied (as a result of delete or rename processing), then CICS Configuration Manager automatically removes any references to the group from lists. CICS Configuration Manager displays information messages about the list adjustments. |
Exit point processing in the CICS Configuration Manager server (ExitPoints) |
User exit programs are ignored. | CICS Configuration Manager invokes user exit programs that are marked as active. For details, see Invoking user exit programs. |
For details, see Restricting access to API commands and resource definitions.