File controls upon server deliveries and promotion between streams
If you are an administrator, you can use the Rational Team Concert™ control features to ensure that the files that are uploaded to the server do not cause errors. You can then select controls, which correspond to preconditions.
About this task
- File controls upon server deliveries. These preconditions are client preconditions because they
apply to the uploads from the user workspace.
- RPP - Prevent Data Element creation.
This precondition controls that no Data Element is created out of the selected scope of components.
- RPP - Prevent Data Element override, RPP - Prevent Meta Entity
override, and RPP - Prevent design artifact override.
These preconditions control that the Data Elements, Meta Entities, or all the design artifacts (except the Data Structures) that are about to be delivered, and that have been created, do not override artifacts in the same projects hierarchy. You can select components where overrides remain possible.
These controls do not apply to the overridden and modified artifacts. They are not active upon the Pacbase migration and do not apply to the migrated instances that were overridden in Pacbase.
- RPP - Prevent unresolved design references.
This precondition controls that all the references of the design files that are about to be delivered or promoted are resolved.
The references are not resolved in the following cases:- Local modifications are partially delivered or promoted. References are not resolved, for example, if a new Data Element is called in a new Segment but if only the Segment is delivered or promoted.
- An instance that is used by other instances is deleted. References are not resolved, for example, if a Data Element that is called in a Segment is deleted but if only this deletion is delivered or promoted.
Note: This precondition is a first way to control that the references between design files are resolved. However, to detect the unresolved references in the delivered change sets automatically and globally, it is advised to create nightly builds on the Rational Team Concert server. You can then use all the tools to go back in the changes history and to correct the origin of an error. - RPP - Prevent multiple design files update.
This precondition controls that each of the change sets that are about to be delivered contains only one design instance.
- RPP - Prevent multiple generated files update.
This precondition controls that each of the change sets that are about to be delivered contains only one generated file.
- RPP - Prevent generated file inconsistency. This precondition controls that the generated files that are about to be delivered are consistent. It completes the following integrity checks:
- The generated files and their corresponding pdp files must be delivered simultaneously. For example, a cbl file must be delivered with its corresponding cblpdp file.
- The generated files must be synchronized with the design files that were involved in their local generation.
- The generated files cannot be modified if the pattern forbids it. For the Pacbase pattern, only the cbl files of Programs, Screens, or Servers can be modified to insert specific code. The other generated files (.bms, .cpy, or .ddl for example) are in read-only mode.
Note: This precondition is based on the content of the Pending changes view. So, if design files that are involved in a generation were loaded into the workspace with Load required artifacts and if they have not been shared, they are not recognized by the precondition. - RPP - Prohibit generated files delivery if design files
contributors are missing. This precondition controls that all the design files involved in the generation of a file to be delivered or promoted have already been delivered (or promoted) or are delivered (or promoted) at the same time as the generated file.Note: This precondition is based on the content of the Pending changes view. So, if design files that are involved in a generation were loaded into the workspace with Load required artifacts and if they have not been shared, they are not recognized by the precondition.
- RPP - Prohibit generated files delivery if incoming changes contain design files
contributors. This precondition controls that the incoming change sets do not contain files that might impact the generated files to be delivered.Note: This precondition is based on the content of the Pending changes view. So, if design files that are involved in a generation were loaded into the workspace with Load required artifacts and if they have not been shared, they are not recognized by the precondition.
- RPP - Prohibit project diagram update.
This precondition controls that the structure of the project diagram in the design build path was not modified. The project diagram can be viewed or updated, depending on the access rights, by right-clicking an opened location in the Design Explorer view and by selecting Properties.
- RPP - Team deliver quality control advisor client.
This precondition controls that the COBOL and design files that are about to be delivered do not contain serious Rational® Programming Patterns quality control errors.
Quality control is implemented with Rational Software Analyzer. To know how to use it, see Quality Control Rules.
- RPP - The generated file and the design file used to produce it, must be delivered in
the same change set.
This precondition controls that each of the change sets that are about to be delivered contains both the generated file and the design file that was used to produce it, if this design file was modified.
All these controls apply to the contents of the change sets that are about to be delivered, and to the indexed content of the server. This content might be desynchronized with the actual content of the server. Before you deliver your modifications, you must then synchronize the indexed content of the server with its actual content. You must also deliver all the related changes simultaneously, or, if not, you must ensure that the server content is indexed again before you deliver your remaining changes. So, for example, if you deliver the deletion of a Data Element call in a Segment, the server content must be indexed so that the deletion of the Data Element can be authorized later.
The server content can be indexed in different ways:- A scan is automatically triggered after each design file delivery if you select the follow-up
action RPP - Trigger a scan for delivered design files if necessary in the
same tab as the selection of the preconditions. This follow-up action is operational with Rational Team Concert version 6.0.2 and
later.A scan is triggered after the following deliveries:
- Delivery of a design instance creation. The new instance then appears in the results of the server requests.
- Delivery of a design instance deletion. The deleted instance then disappears from the results of the server requests.
- Delivery of the subreferences of a design instance. Such is the case when a Data Element call is added or deleted in the Lignes -CE of a Segment.
- A scan can be started manually. To do so, open the Work Items perspective and the Team Artifacts view. Expand the project area that contains the change sets to be delivered and expand Enterprise Extensions. Right-click Source code data and select Update source code data.
- RPP - Prevent Data Element creation.
- File controls upon work items promotion. These preconditions are server preconditions because
they apply when a stream is updated by another stream. For explanations about promotion between
streams, see the Rational Team Concert help. These preconditions are operational with Rational Team Concert version 6.0.2 and later.
- RPP - Prevent unresolved design references.
This precondition controls that all the references of the design files that are about to be delivered or promoted are resolved.
The references are not resolved in the following cases:- Local modifications are partially delivered or promoted. References are not resolved, for example, if a new Data Element is called in a new Segment but if only the Segment is delivered or promoted.
- An instance that is used by other instances is deleted. References are not resolved, for example, if a Data Element that is called in a Segment is deleted but if only this deletion is delivered or promoted.
Note: This precondition is a first way to control that the references between design files are resolved. However, to detect the unresolved references in the delivered change sets automatically and globally, it is advised to create nightly builds on the Rational Team Concert server. You can then use all the tools to go back in the changes history and to correct the origin of an error. - RPP - Prohibit generated files delivery if design files
contributors are missing. This precondition controls that all the design files involved in the generation of a file to be delivered or promoted have already been delivered (or promoted) or are delivered (or promoted) at the same time as the generated file.Note: This precondition is based on the content of the Pending changes view. So, if design files that are involved in a generation were loaded into the workspace with Load required artifacts and if they have not been shared, they are not recognized by the precondition.
- RPP - Prevent unresolved design references.
Procedure
Results
If you checked the User may override box, the developers will be able to right-click the error in the Team Advisor view and ignore it. They will then be able to deliver their updates or promote the files.
If you did not check the User may override box, the developers must correct the error before they can deliver or promote.
To correct an error upon a server delivery, the solution for a synchronization error is to generate the COBOL code again. To correct a quality control error, a solution can be to restore the generated code from the Generated Structure Code view.
To correct an error upon a stream promotion, the solution is to promote the work items that contain the design files that are missing for the references or the design files that contribute to a generated file.