This subcommand shows information about the specified process rules. Any user may use this command.
ccm pr|process_rule|ut|update_temp|update_template|rt|recon_temp| reconfigure_template -s|-sh|-show (i|info|information) -f|-format format [-nf|-noformat] ([-ch|-column_header] | [-nch|-nocolumn_header]) [-sep|-separator separator] process_rule_spec... ccm pr|process_rule|ut|update_temp|update_template|rt|recon_temp| reconfigure_template -s|-sh|-show (i|info|information) process_rule_spec...
The process_rule command displays and sets process rules. Note that the process_rule command was referred to as the update_template and reconfigure_template commands in prior releases.
A process rule specifies how a baseline is chosen for a project grouping's update properties and for a project's update properties. Process rules support these selection modes:
The latest baseline matching the process rule's baseline release-purpose pair list is chosen as the baseline for the project grouping. For a project, the corresponding project in that baseline is used as the baseline project.
The baseline specified for the process rule is used for the project grouping. For a project, the corresponding project in that baseline is used as the baseline project.
A process rule does not specify a baseline. You must select a baseline for the project grouping's update properties manually. For a project, the corresponding project in that baseline is used as the baseline project.
A baseline project is chosen by getting the latest baseline projects that match the release or baseline release, and that match any specified version matching criteria on the project version.
A process rule specifies how a project is updated when an update operation is performed on the project. The combination of a project purpose and release value determines which process rule can be used in the project. Multiple process rules can be created for a release/purpose pair. You can set up rules, and then select rules to apply to a given release and purpose, and switch among the set of process rules during the course of a release. You can also reuse process rules for future releases, rather than continually modifying the process rule for each purpose.
Process rules are automatically created whenever one of the following occurs.
General process rules are shipped with the product for both standard and distributed processes. A non-DCM-initialized database contains the standard process, and a DCM-initialized database contains both the standard and the distributed processes. The process rules have the same behavior in each, with these exceptions:
The standard process is used to provide process rules in the CLI when a purpose is specified.
You can specify which process rules to use when you create a new release. For more information, see the release command.