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 Configuring the Execution History Cleanup sweep for hung cleanup requests
Configuring the Execution History Cleanup sweep for hung cleanup requests
CMS-XML SDA: Error "This version cannot be deleted because it is in use by the following" when deleting component version history
If you decide that you want or need to deploy versions, even though they were previously deployed, you can use the " Execution History Cleanup " feature. This is documented in the User's Guide. In SDA 6.1.4, the Execution History Cleanup feature was in Chapter 15 .
PDF Serena Deployment Automation User's Guide
Execution History Cleanup Audit .................................................................. 181
CMS-XML SDA 6.1.2 UI microhelp for create resource is incorrect
On SDA 6.1.2, the create resource button micro helps incorrectly states "run execution history clean up when you hover over it"
HTML SBM Version Diff
Differences Between Versions ... -compact mode clean up categories and ... + history = chart. ... ... if (! history .length) + history .length = ... // clear history + history = chart. ... ... + lastinfo = history .pop( ... ... access the last history + history = chart. ... + history .push( ... ... current state to history ... then pop the history state that we + history .pop( ... + history = chart. ... + history .push( ... ... current state to history ... then pop the history state that we + history .pop( ...
HTML SBM Version Diff
Differences Between Versions ... For now, clean up problems with ... ... for state change history // is ... // clean up left options ... ... ) // cleanup in case we ... ... { // cleanup in case we ... ... -STATE CHANGE HISTORY */ function ... ... -CHANGE ACTION HISTORY */ function ... // clean up left options ... ... when doing the clean up. // cleanup (if any ... ... / This will clean up those divs ... ... a full report execution ... a full report execution ... //reset history collection of added ... ... {// clean from repeats ... {// clean from repeats
CMS-XML New Features in ChangeMan ZMF 8.2
... followed with an execution of CMNSRCPP which ... libraries to be cleaned up after the ... ... Component and Query History Panels ... to the Component History (CMNCMPH1 ... ... on the Component History Panel Has Been ... ... on the Component History (CMNCMPH1 ... The Component Cleanup ... needs to be cleaned (that is ... ... types that have clean -up requirements ... ... variable CLNCNT ( clean count) in ... to check the value of &CLNCNT before generating clean -up JCL. ... Release Component History Report This report contains a list of releases, release areas, and release component history information.
HTML ZMF_61101_Readme.htm?H5GBtAnCGZlpFVssX_w5CzgUniSyjaM-r1t_lO5l-So4vSiPhZ3l55Kulxy_bMaCPtk7HCuw-nXpAHZT6l75uDphk_22zRgnHggnn86wfUFDCxcwBEXn5wJfthyc0nylS0hqfK_te9hvJ6kOvemxZLAWPN92i5XyrPAHGWrgyAqD8W64
... the loss of historical component relationship data ... ... message running CMNRPKSN cleanup utility DEF155004 ... ... DEF155277 Component history "by application ... ... DEF159790 Component history options 'lost ... ... D/A history only DEF167835 ... (deleted application history ) DEF167869 ... successful installation and execution of the DA ... ... AGING: COMPONENT HISTORY field on the ... Aging: Component History should be less ... Component history records for a ... ... Aging - Component History should be equal ... ... the AGING COMPONENT HISTORY field on the ... Aging: Component History should be less ... Component history records for a ...
PDF ChangeMan ZMF ERO Getting Started Guide
... 283 Displaying Promotion History . . . ... ... the area, execution of the check ... ... the area, execution of the check ... If no package status is selected, automatic cleanup is effectively disabled. ... If the approval rule for an area is set to require check-in approval, and there are no check- in approvers defined for the area, execution of the check-in approval notification function sets the check-in approval flag to Y. ... HISTORY TABLE Displays the return code from the history table update. ... HISTORY TABLE Displays the return code from the history table update.
PDF ChangeMan ZMF 7.1.2 ERO Getting Started Guide
... Removing Unneeded Component History . . . ... ... the area, execution of the check ... ... the area, execution of the check ... If no package status is selected, automatic cleanup is effectively disabled. ... If the approval rule for an area is set to require check-in approval, and there are no check- in approvers defined for the area, execution of the check-in approval notification function sets the check-in approval flag to Y. ... HISTORY TABLE Displays the return code from the history table update. ... HISTORY TABLE Displays the return code from the history table update.
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