|
Size: 554
Comment:
|
Size: 932
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| * In the current configuration PACS5 is the operational database and "pacs_fm_ilt_2" is the operational database | * In the current configuration PACS5 is the operational database and "pacs_fm_ilt_3" is the operational database |
| Line 3: | Line 3: |
| * Scripts may be amended/created using the built-in editor of the CUSGUI, or standard editting of the ASCII copy of the script, to be found in the directory /home/oper/toREG/Name_of_Script.cus * If the script was modified within the CUSGUI, you must ''Commit'' your changes. If you have amended/created a file in toREG/, you must issue ''cus -f -import Name_of_Script.cus'' |
- In the current configuration PACS5 is the operational database and "pacs_fm_ilt_3" is the operational database
To achieve versioning control, any change to CUS (amended or new script) will generate a new CUS model.
- Scripts may be amended/created using the built-in editor of the CUSGUI, or standard editting of the ASCII copy of the script, to be found in the directory /home/oper/toREG/Name_of_Script.cus
If the script was modified within the CUSGUI, you must Commit your changes. If you have amended/created a file in toREG/, you must issue cus -f -import Name_of_Script.cus
A dedicated procedure, invoked as ccm -updatecus, creates the new model, updates the local CVS, and conditions testcontrol to work with te new model.
Only the test conductor should perform the updatecus procedure (the procedure stops testcontrol, causing any running TOPE task to abort in error)