Differences between revisions 1 and 2
Revision 1 as of 2006-09-26 09:43:44
Size: 410
Editor: dcesarsky
Comment:
Revision 2 as of 2006-12-11 14:48:19
Size: 330
Editor: dcesarsky
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
To invoke CUS procedures from TOPE, you have to logon to the dedicated acount '''cususer''' in PACS1.
This account (ask Ekki or Diego or Thomas for the password) will define for you:

 a. the HCSS_PROPS pointing to the Versant database '''sftcode'''

 a. the DISPLAY environment variable to allow the testcontrol-server to provide a comunication link between TOPE and the CUS engine

(To be continued)
Only CUS procedures stored in the Operational Database (''pacs_fm_ilt_2@pacs5'') can be scheduled by the TOPE application (SCOS2000 framework) running in ''pacsscos''. The communication between TOPE and CUS is done via the application '''testcontrol-server'''. Setting up the link TOPE -- CUS is (should be!) automatically done,

Only CUS procedures stored in the Operational Database (pacs_fm_ilt_2@pacs5) can be scheduled by the TOPE application (SCOS2000 framework) running in pacsscos. The communication between TOPE and CUS is done via the application testcontrol-server. Setting up the link TOPE -- CUS is (should be!) automatically done,

Herschel: PACS/FM_ILT/SetupCUS (last edited 2009-07-15 14:32:36 by localhost)