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 VM: How to set up workfile location for a file using the PCLI command SetWorkLocation (SWL)
When a workfile location is set , the location is stored in the default workspace by default. To be able to store the location in a workspace other than the default, by using the -sp option (as described below)an alternative workspace must be defined.
CMS-XML PCLI Put - How to check in file from non default workfile location
If the files are located at C:\test\chess\server\server.bat and C:\test\chess\server\shutdown.txt , you would set your basepath option to / to indicate that the -a directory C:\test is at the project hierarchy level of /.
CMS-XML PCLI: How to create private workspaces and set default workfile locations from command line
If you want to store the location in workspace other than the user's default, you must specify which workspace by using the -sp option. The argument entity_path determines which file or project within the workspace the change should be made to. If not specified, the workfile location is assigned to the project database root.
CMS-XML PCLI: How to list files containing a specific promotion group.
Is it possible to use the PCLI LIST command to indicate which revisions are set to a specific Promotion Group? pcli list -pre:\pvcs -caRevision:Ready_for_Build -z
CMS-XML PCLI "set var=value" syntax incorrectly expands file if value starts with @
Consider the following PCLI script (SetEqualExpandsAt.pcli):
CMS-XML PCLI: how to get a revision with multiple version label
# Get the tip revision for all archives that have 2 specific labels set -vLabel1 "$1" # Label that needs to exist on the file set -vLabel2 "$2" # Second label that also needs to exist on the file
MS-WORD When the PCLI Move command is used to move a versioned file from one project to another
--------------------------------------------------------------------------------- d:\Pvcs> set PCLI PCLI_ID=CHRISRO
CMS-XML PCLI get command on UNIX client throws "could not read the information stored in the archive" error, but the desktop client GUI running on the same system has no problems getting this file
This problem may be caused by having a Version Manager installation running in setuid (& setgid) mode, with end-users not being a member of the setgid group the VM executables are running with. When setuid mode is enabled, all users are expected to be a member of this group, and use a umask setting that allows group reading (the second to last digit that is returned by the command "umask" should be 0 or 2).
CMS-XML VM: PCLI GET 'Warning: archivename>: Could not check out the file because it does not contain the specified revision.'
------------------------------------------------------------------------- set PVCS_MX=-Xmx512m pcli Get -pr'<project database>' -ad:\MyWork -u -z /
CMS-XML VM 8.2 - GUI: Application List File problem: "pvcs/gui/applist.cfg" / PCLI: [Error] System Interfaces File problem: "pvcs/cmd/pcli.cfg"
An example of a malformed variable: set PVCSTZ=480 0 11/1/0 2:0:0 0 3/2/0 2:0:0 -60 The corrected variable:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs