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 KM-Dim9: Is there a way to include empty workset directories in a baseline, release or get (recursive)?
KM-Dim9: Is there a way to include empty workset directories in a baseline , release or get (recursive)?
CMS-XML AUDIT and components not in baseline
Audit is a directory driven process. This means audit finds the name of the staging and baseline libraries from the package master and then searches the directory of each library examining each member that is found against the package master ICPY, ISAL, ILOD, ISIC, history records, and impact analysis tables, as opposed to going the other way by examining all the package master ISIC, ISAL, ILOD, ICPY, history records and impact
CMS-XML Baseline Analyzer Rpt: Non-Standard Directory
When looking at the Baseline Analyzer report, what does the following mean? " Components with non-standard directory "
CMS-XML Audit for "same-named" source components sharing the same baseline dataset
***** R000120 Created 2012/08/13 at 14:24:34 by ACHERNA * 2/12/30 Package Status: DEV * cription of member from library directory entry * R:SR2 CHER:SR3 * **************************
CMS-XML Dimensions returns error when user tries to revise a baseline with a directory item.
A baseline exists that contains a directory item.
CMS-XML Dim: How to baseline s single folder structure
b) Relate all of the items to a design part that only those items are on then you can take a baseline of only that design part. Then only those items will be included in the baseline. However the down side is once the items are related to the request and in the baseline you can not change the design part they are related to.
CMS-XML Folder offset is broken when doing Get (recursive) on sub-project baseline
User then does a recursive Get on the baseline sub-project. The baseline contents are fetched to work area, but folder offset is not included in the path to work area
CMS-XML Dim: Upgrade to CM 14.1.0.4 - Baselines and projects in schema fails to upgrade because of path conflicts between directories and directory items
DBA3200088E Path conflict: Directory UID 5528454 conflicts with item 'TESTMAN:LIB-5279050.A-DAT' at 'etc/Utilities/TESTMM0001MYFILE/Lib/'. DBA3200873E "TESTBASELINE:BASELINE_2.0.2" contains path conflicts. Examples of Project failures
CMS-XML KM-Dim6: SP2: Items are not being created in the correct directory location for a revised baseline
Attached to this article are patches for NT and Solaris. Should you require the patch for a different platform please contact the answerline and quote defect number 1021610. The defect needs to be applied to all PVCS Dimensions server installations including DFS nodes.
CMS-XML SDA: Metadata is included when importing from a Baseline into code station
5. Version appears as the baseline spec Click on baseline name ./dm directory appears along with associated files
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Overview (demonstration)
This animation describes what you need to know about Dimensions CM to help you get started with your developement tasks.

Additional Assistance

  • Submit a Case Online
  • FAQs