Resynchronization management

To limit the number of the required regenerations, you can exclude non-functional design modifications from the calculation of the desynchronization between the design and the generated code and force the resynchronization. You select these modifications from the resynchronization wizard in the Generation Manager view. In this wizard, you select the Rational Team Concert™ work items whose change sets contain non-functional design modifications. You limit the scope of the resynchronization request by selecting the streams where these change sets were delivered.

For example, you add a Data Element before a filler at the end of the -CE Lines of a Segment and you decrease the size of the filler consequently. If only one Program uses this Data Element, you need to regenerate this Program only and not all the Programs that use the Segment. You can then exclude this modification from the calculation of the desynchronization. In this way, all the generated files that use this Segment will not be marked as to be generated again because they are desynchronized.

In the Generation Manager view, you specify the resynchronization requests by clicking Open synchronization dialog in the toolbar. The resynchronization wizard opens then.

Resynchronization wizard

The resynchronization wizard opens with a table that displays the resynchronization requests already specified. The list of the deactivation requests is shared between all the user of the repository on the server. When you open this list, all the requests are loaded from the server. When you validate a new request, it is saved on the server.

You can create requests or modify the list of the existing requests.

The table contains the following columns:
  • The Error/warning column displays an error or a warning if a change set that was delivered to the stream has been modified since the resynchronization request. Each error or warning is followed by an explanation. A warning is generated, for example, if the work item contains new change sets or if a change set was copied from another stream to the stream that is selected in the request. You can then integrate this evolution by clicking Update/Quick fix.
  • The Work item column displays the ID and summary of the work item that was used to deliver the non-functional design modification. This modification will not be taken into account in the calculation of the desynchronization between the generated COBOL code and the design. If a COBOL code is desynchronized only because of this modification, it will not be marked as to be generated again.
  • The Stream column displays the name of the stream where the change set was delivered.
In the resynchronization wizard, you can do the following actions on the resynchronization requests:
  • Create a request by clicking Add. The New resynchronization item wizard opens.
  • Delete a request. To do so, select a request line and click Delete.
  • Integrate the evolution of a Rational Team Concert work item since the initial creation of the request. To do so, select a request line that contains an error or a warning and click Update/Quick fix. You make the error or the warning disappear by integrating this evolution.

New resynchronization item

When you create a resynchronization request by clicking Add in the resynchronization wizard, the New resynchronization item wizard opens. You must select the Rational Team Concert work item whose change sets contain a non-functional design modification. You must also select the stream where the change sets were delivered. Click the browse buttons to open the selection wizards where you can select the work item and the stream. These wizards are the Rational Team Concert wizards.

Note: Several change sets that apply to the same design can be integrated into the same work item only if there is no gap in the sequence of change sets. To solve the problem, you must move the faulty change sets to new work items.

After the selection, you can click Next to display the next pages that provide information on the content of the work item change sets in the stream. These information pages can be used for additional controls. You can use them to see whether a change set is empty or whether it contains only one COBOL file. You can also use them to see whether a change set was delivered to the correct stream.

If you do not want to see the information pages, you can click Finish to validate the resynchronization request.

List of the modified designs (from the change sets) included in the stream

This page displays, for information only, the content of the change sets of the work item after they were delivered to the stream. It shows the modified design files only.

It does not show the generated files (COBOL files for example) and the files that were added or deleted.

Click Next to display the next information page. You can click Finish to create the resynchronization request without seeing the other page.

List of potentially impacted generated files (list built from the current local workspace)

This page displays, for information only, the generation super references of the design files that are listed on the previous page.

If these super references are already synchronized, they are not impacted by the resynchronization request.

If these super references are desynchronized, the following cases are possible:
  • If the desynchronization is due to the modified designs from the previous page, the generation super references are resynchronized.
  • If the desynchronization is due to modified designs from the previous page and to other design modifications, the following two cases are possible:
    • If all the change sets are included in resynchronization requests, all the generation super references are resynchronized.
    • If some change set are not included in resynchronization requests, the generation super references are not resynchronized.

Click Finish to create the resynchronization request.

In the Generation Manager view, click Resfresh to start computing the desynchronizations that incorporate the resynchronization requests.

Then, when you open a generated file that was resynchronized, a message informs that the new generation can produce a COBOL code different from the current COBOL file.


Feedback