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 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
Please do not perform any operations that will update the repository (Put, AddFiles, etc.) while this variable is in effect unless you are certain the repository is File Server-based. ... as the user who installed Version Manager (a.k.a. the setuid user) or as a system administrator .
CMS-XML Change the Text Color of Inactive Items
The example below demonstrates how to change the color of inactive items to red. ... 4. From SBM System Administrator , select ... 5. Stop and start your Web server and clear your browser cache for the change to take effect .
CMS-XML After making an archive update, user gets: Serena PVCS Version Manager could not read the information stored in the archive ""
As a result the actual archive was not changed, so there is no permanent damage, but the archive change the user tried to make has been lost.
CMS-XML Mashup Script may cause unexpected results when using UpdateWithLock() in a Shell.Item context
If you are using Mashup Scripts where you have a Shell.Item, invoking the Ext.UpdateWithLock() function may cause unexpected results to the current item. For example, if you are using Mashp Script to write to a field on the current item in a Pre- or Post-Transition context, in one case, trying to UpdateWithLock causes the PROJECTID field to be set to zero (" 0 "). That makes the item unaccessable by anybody.
CMS-XML KM-Dim9: File Get hangs on the Results dialog; Add Item Results dialog flashes but fails.
When trying to Get File through Web Client, the results dialog hangs. When trying to Add Item through Web Client, the Results dialog flashes and disappears, but item is not added.
CMS-XML PBrowse/PVIEW of VSAM data set results in PDS961E VSAM POINT error at RBA=00000000; Feedback=D708009C
PDS182I Tracks: ALLOCATED USED FREE EXTENTS CATALOGED PDS182I 585 585 0 1 SRSM34 PDS195I INDEXED NONSPANNED NOIMBED NOREPLICAT SHROPTNS(2,3)
CMS-XML KM-Build6: Evaluation of Builder results in directory listing of files being displayed when trying to connect to Builder
The license must be pasted into the License Manager GUI and the license.ini file, located in the installation directory tomcat\webapps\openmake.ear\openmake.war\license, must be modified to point to the license server.
CMS-XML Dim10: VM2DIM: Warning:8005:Shared Archive is shared by the following items to be migrated: -or- Warning:8005:TestPdb
), each shared instance of an item is treated as a separate entity, and a separate Dimensions item will exist for each instance. For example, if a single Version Manager file is shared across three PDB locations being migrated, the resulting Dimensions repository will contain three separate items with the file contents .
CMS-XML Dim10: VM2DIM: Warning:8006:Shared Archive appears to be owned by an external PDB. Migrated from PDB items(s): -or- Warning:8006:MigPdb
), each shared instance of an item is treated as a separate entity, and a separate Dimensions item will exist for each instance. For example, if a single Version Manager file is shared across three PDB locations being migrated, the resulting Dimensions repository will contain three separate items with the file contents .
CMS-XML KM-Dim7: The Effects of Change Management Rules on Items and Change Documents
1) The individuals with the proper roles can extract, edit, update, etc. the Item without PCMS forcing a change document as long as the Item is not in the APPROVAL state. 2) Once the Item is actioned to the APPROVAL state, any attempt to extract, edit, or update the Item will cause PCMS to require a change document be generated and related as 'affected' to the item.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs