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 Change History and Deleted Items Reports Fail When Set as Scheduled Reports
Change History and Deleted Items Reports Fail When Set as Scheduled Reports
CMS-XML CMNBAT12 component history aging not accounting for deleted applications
CMNBAT12 component history aging not accounting for deleted applications
CMS-XML 'DE' command in LIMBO does not remove component history records for deleted package
'DE' command in LIMBO does not remove component history records for deleted package
CMS-XML SDA: Error "This version cannot be deleted because it is in use by the following" when deleting component version history
Component versions cannot be deleted , if ANY of these constraints are true:
CMS-XML CMNBAT10 processing deleting ‘last’ component history record when it should be retained
Customer is on v7.1.3 and reporting CMNBAT10 process is deleting the last component history record, when it should not be. When they run CMPONENT HISTORY LISTBASE it shows the component history record for the package which it is assumed will be the ‘last’ component history record to be retained, but in the CMNBAT10 CMNRPORT they see an entry suggesting the last history record for component will be deleted (AGING IN TERMS OF DAYS HAS BEEN MET).
CMS-XML Housekeeping job is deleting component history when aging is set to '0'.
If you run Housekeeping with the Application Component aging set to '0', . COMPONENT HISTORY ===> 0
CMS-XML Ability to delete and/or update history information using CMNBAHST
Example 1. Delete initial history for ABC10000.SRC: CMP=ABC10000,LIB=SRC,FUN= DELETE Example 2. Replace initial history for ABC10000.SRC:
CMS-XML Dim 12.2.2 - Refactoring History lost if the workset is deleted
If a project or stream is deleted , refactoring history is lost. Although this will no longer be an issue in 14.1 due to change sets, it is still needs to be addressed in a 12.2.x maintenance release.
CMS-XML Default application assigned to IA components (deleted application history)
During the conversion of impact analysis data from the 5.6 to 6.1 formats default applications are assigned to components to cater for shared baseline library processing. This default application is only supposed to be temporary except for the situation where no component history at all is found for any given component. It should be resolved by either the conversion process itself or when CMNIA000 is executed for the first time post upgrade.
CMS-XML Errors in Application Repository after running Purge History to remove deleted process app versions. e.g. Error: Failed creating domain adapter for null. AssetVersion: 165266
In certain cases running a Purge History in Application Repository can lead to NULL pointer exceptions.
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