This subcommand queries for objects matching a query expression or criteria, and then for each, finds which projects, project groupings, process rules, folders, or baselines use them. You can modify the query expression in either or both of these ways:
Each query-related option generates a query clause. For example, the -name name option generates a query clause in the form (name='name').
When the same query option is repeated, the query clauses are combined with an or. For example, -name file1 -name file2 generates a query clause (name='file1' or name='file2').
Query clauses from different options or from the query expression are combined with an and. For example, -name file1 -owner joe generates a query clause (name='file1') and (owner='joe').
ccm finduse [-q|-query query_expression] [(-n|-name name)...] [(-o|-owner owner)...] [(-st|-state state)...] [(-t|-type type)...] [(-v|-version version)...] [(-i|-instance instance)...] [(-release release_spec)...] [-working_proj|-working_projs|-working_project|-working_projects] [-shared_proj|-shared_projs|-shared_project|-shared_projects] [-prep_proj|-prep_projs|-prep_project|-prep_projects] [-released_proj|-released_projs|-released_project|-released_projects] [-all_proj|-all_projs|-all_project|-all_projects] [-personal_fold|-personal_folds|-personal_folder|-personal_folders] [-shared_fold|-shared_folds|-shared_folder|-shared_folders] [-prep_fold|-prep_folds|-prep_folder|-prep_folders] [-non_write_fold|-non_write_folds|-non_write_folder| -non_write_folders] [-all_fold|-all_folds|-all_folder|-all_folders] [-all_baseline|-all_baselines] [-wpg|-working_project_grouping|-working_project_groupings] [-mpg|-my_project_grouping|-my_project_groupings] [-ppg|-prep_project_grouping|-prep_project_groupings] [-spg|-shared_project_grouping|-shared_project_groupings] [-apg|-all_project_grouping|-all_project_groupings] [-all_process_rule|-all_process_rules]
The finduse command searches the database for uses of a specified object and returns a list of where the specified object is used.
Each finduse command supports options that define a scope for the returned objects. These scope-related options define what type of searches to perform. You can perform these kinds of searches:
The results include the projects that match the scope and use of the specified object. Each result is shown in a sc_r_h_file_specs_cso.html#__wp763404.
The results include the project groupings that match the scope and use the specified object. Each result is shown as a Project grouping specification.
The results include the process rules that match the scope and use the specified object. Each result is shown as a Process rule specification.
The results include the folder templates that match the scope and use the specified object. Each result is shown as a Folder template specification.
The results include the folders that match the scope and use the specified object. Each result is shown as a Project specification.
The results include the CRs that match the scope and use the specified object. Each result is shown as a Change request specification.
The results include the baselines that use the specified object. Each baseline is shown as a Baseline specification.
The default scope used depends on the type of object you use with the finduse command.
If you do not specify a scope option, the default is all baselines.
If you do not specify a scope option, the default is all projects.
If you do not specify a scope option, the default is all projects.
If you do not specify a project or project grouping scope option, all projects are always included in the scope.
If you do not specify a scope, the default is all process rules.
If you do not specify a project grouping scope option, then all project groupings are included in the scope.
The scopes available specify the scope of the search and include.
Specifies to show all uses in change requests.
Specifies to show all uses in prep (build management) folders.
Specifies to show all uses in folder templates.
Specifies to show all uses in prep (build management) projects.
Specifies that all uses in development projects should be shown.
Specifies to show all uses in process rules of a baseline, folder, or folder template object with a type of that is specified or found by using a query.
Specifies to show all uses in project groupings for any state or owner).
Specifies to show all uses in project groupings owned by you.
Specifies to show all uses in prep (build management) project groupings.