Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML VSQL command generates INSERT statements with “Archive Description” and “Revision Update Note” fields truncated when using -DV"VARCHAR2(....)"
VSQL command generates INSERT statements with “Archive Description” and “Revision Update Note” fields truncated when using -DV"VARCHAR2(....)"
HTML Merant PVCS Version Manager Release Notes
Embedded Disallow Directives Appended to Every Configuration File [1020757] When users made changes to the configuration files, disallow statements were appended to the configuration file. The customer would need to remove the disallow statements that were appended to the configuration file, but when a change was made, the disallow statements were appended again. This has been fixed.
CMS-XML Problem: VM6.5: Reference directories created with incorrect path
If specifying a Project database of M:\PVCS\PDB, and working in a project called Proj1, if the VCSDIR statement and REFERENCEDIR in the cfg file are as follows: VCSDIR = "M:\PVCS\PDB\archives/* " REFERENCEDIR = "X:\Ref/*"
CMS-XML VM6.5: 63419: How to do an SQL Export through the GUI.
In the Version Manager 6.0 GUI, there is a routine to generate SQL statements that will export archive information to a file that can then be imported into a database.
CMS-XML Error: - Vlog: Unable to Open Library "vmufvc.a"'
User received this error when executing the VLOG command. The path to the VM executable directory containing vmufvc.a was in his path statement and he confirmed it by running the 'which' statement . Both the directory & library had permissions set to 777.
CMS-XML Error: Error 2. The specified archive does not exist
The above error can happen if the user is running Tracker 6.0.20 with a Version Manager 6.5 project. If the user has a VCSDIR statement ending in /* and attempts to check out a file or browse to find a revision number on the check out screen this error happens. To resolve this remove the /* from the VCSDIR statement.
CMS-XML VM: Unable to start java applet. Cannot find
2. The Netscape executable directory is set in the users PATH statement for the current shell. 3. The MOZILLA_HOME environment variable is set to <Netscape_Home> directory for the current shell.
CMS-XML PVCS VM SCC IDEs: Tracing SCC-API layer calls using SccSpy.dll
This article contains an attachment that captures communication between the PVCS Version Manager (VM) IDE client and an SCC-Compliant IDE by tracing the calls on the SCC-API levels. Caution Statements Micro Focus is providing this information "as is". Micro Focus does not provide any warranty of the attachments or information provided, whether express or implied.
CMS-XML How To: Command Line Basics
Note: Unless you are reading a config file with a VcsDir statement , you will need to specify the full path to the archive, including archive name.
CMS-XML Error: PB --- PVCS : PVCS INTERFACE ERROR : PVCS QUERY CONFIGURATION. UNSPECIFIED INTERNAL PROCESSING ERROR
The Powerbuilder-PVCS interface requires that you have the Version Manager executable directory in your path statement . When you try to connect Powerbuilder to VM, the interface reads the main Version Manager dll e.g VMWFVC.DLL for any embedded information such as the master configuration file, access database etc.
Pages [Next]

Welcome kb sso

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs