When testng UD6/CMtool Driver with PVCS Version Manager the following problems were observed, that we were unable to find reference to in the associated manuals.
Event Triggers only support the use of a single command line macro, once per trigger (ie: cannot use the same command line macro several times in the one trigger). This is worked around using a shell script (unix) or batch file (windows).
A file cannot be checked in if it is open, even if it is only open for read-only access. Since UD6/CMtool driver contains considerable caching mechanisms to improve performance, PVCS often gives an error, if a file is being checked in shortly after it was worked on, or where the developers PC has remained inactive for some time since (but still logged into the IDF). This problem is addressed by using the USYS$UD6_PARAMS setting cleanmmf hard auto. NOTE: this setting may reduce the performance of UD6 since it circumvents much of the UD6 performance caching.
If you double click on an XML file PVCS Version manager offers to check it out to the temp directory, and may open up IE5 to display the file. Unfortunately since it copies the file to the TEMP directory to display it, IE5 cannot find the references to the stylesheet so it fails to display it.
To resolve this issue, select the XSL file (e.g.: components.xsl), then the ud6logo.gif file, then the file that you wish to view. This copies the stylesheet to the temp directory as well.
How to use the driver with PVCS Version Manager (cont.)