Step 1.9 – Propagate Members to Environment Libs.

INCONTROL BASE libraries are shipped with members containing symbolic variables that must be resolved according to local values that are determined during installation. During the installation of INCONTROL products, members related to the products are copied from IOA libraries to the appropriate product libraries and the variables are resolved. (This process of copying elements from a BASE library to a working product library, and resolving the symbolic variables is termed propagation.)

If product members that require propagation are replaced in the BASE libraries by this ad hoc cycle, they need to be propagated to the working product libraries, for the changes to take effect. Propagation is not performed automatically - to avoid overwriting the product members (in the working libraries) that may have local modifications.

In the event that you made local modifications to the members in your working library, back up the members and, after the propagation step has been completed, reapply the modifications to the new versions of the members (based on the backups).

1. Select Minor Step 9, Propagate Members to Environment Libs.

   If there are no members requiring propagation in the ad hoc cycle, the step is marked COMPLETE and a message to this effect is displayed. Continue with Step 1.10 – Copy Elements into Site Libraries.

2. Enter L in the S column in the row with the Propagate selected elements description, to display a list of elements that were introduced by this ad hoc cycle and require propagation.

   A panel opens with a table listing the elements and propagation data. Statuses are displayed for the elements according to the following propagation considerations:

   • Elements that can be propagated without further analysis. There is no chance of overwriting local modifications, since they did not exist previously in the working library. These elements have a 'New' status and are pre-selected with an S (this selection cannot be removed).
   • Elements that must be propagated. There is a chance of overwriting local modifications, since they previously existed in the working library. These elements have a 'MustReplace' status and are pre-selected with an S (this selection cannot be removed). Make sure to back up the appropriate members as described above.
   • Elements that require further analysis before they are propagated. There may be a chance of overwriting local modifications, since they did exist previously in the working library. These elements have a 'Replacement' status.

   For assistance in deciding which elements to propagate or more to obtain more information about any element on the list, use the following line commands for each element:

   B - to view the new version of the element

   V - to read the PTF description

   Note: The V option is not active after the PTFs for the upgrade have been ACCEPTed.

   For the elements that are being propagated, check if there are local modifications that were made previously and must be reapplied. Back up the appropriate elements to preserve the modifications for reference.

3. Select the elements from the list that you decide to propagate, by entering S in the O column next to the elements. Press PF3 (END) to close the panel.
4. Submit the job.

   If you enter L after the job has completed, elements that have been propagated have a Propagated! status.

5. When the job has completed, examine the status. If the job did not complete successfully, use B to browse the log for more details.
6. After propagation, apply the local modifications as they existed previously using local site procedures. Use the backups that you created in step 2 as references.
7. Press PF3 (END) to return to the Minor Steps Selection panel.