Find Answers

Filter Search Results
All Products:

Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Notification server taking a long time to process a cycle
Development Manager 1.1Development Manager 1.2Release Control 3.2Release Control 3.3Release Manager 2.0 Requirements Manager 1.0SBM 10.1Service Manager 3.0
CMS-XML Started task looping processing release checkin requests
A customer has recently encountered several loops in their started task. Monitoring suggests that they are being encountered in the release checkin function, both package-to-area and area-to-area. A sample Strobe report taken during one occurrence shows the release component locking routine (CMN$RCLK) to be the most intensively executed procedure at the time of failure.
CMS-XML CMN050 report takes excessive time to flush after CPU timeout.
If cust runs same job in CLASS=5 (unlimited CPU time) job runs to completion in approximately 13+ minutes wall clock and 6+ minutes CPU time. So cust knows that running the job in CLASS=3 (1 minute CPU time ) is insufficient CPU time to process the amount of data being requested .
CMS-XML S0C7 SERDATES+222 in started task delay file processing component history aging request
896 SYSTEM COMPLETION CODE=0C7 REASON CODE=00000000 896 TIME =04.33.58 SEQ=03988 CPU=0000 ASID=0185 896 PSW AT TIME OF ERROR 078D2000 957296EA ILC 6 INTC 07
CMS-XML S0C4-10 in unknown module apparently processing CMPONENT.HISTORY.LISTBASE request
563 SYSTEM COMPLETION CODE=0C4 REASON CODE=00000010 563 TIME =09.30.23 SEQ=22796 CPU=0000 ASID=0639 563 PSW AT TIME OF ERROR 078D1000 F1F94040 ILC 2 INTC 10
CMS-XML Inconsistent timing of CMNEX019 call in batch checkout processing
As can be seen above, CMNEX019 is always called for its post execution processing after the staging library member and associated entities (e.g. component description) have been updated EXCEPT when a batch checkout is executed. For batch checkout the post execution call is executed before the library and associated updates are complete. The sequence of events for batch checkout processing needs to be made consistent with the other three options regardless of whether the requests are issued online, in batch or via XML/other interfaces.
CMS-XML Dim12: Timestamp in history of an Attachment of a Request is showing the incorrect time.
You will want to determine what the TZ variable is currently set to on your AIX Server using the export $TZ command. Change the above to suit your environment. 5. After modifying, a stop/restart of all Services will be needed. Make sure that there are no rogue processes before restarting.
CMS-XML Proposed Requirements cannot be handled through the “Approve / Reject” process in Requirements View
A new requirement is created using the “Propose New” dialog on the Actions menu of the Requirements view. At some point in time , a user wants to process the proposed requirement and selects the “Approve / Reject” dialog on the Actions menu of the Requirements view. The dialog opens only long enough to state that “No Change Requests exist for this object.”
CMS-XML Change propagation takes too long if there are many fields with the same name in Composer
This can then become a problem when forms are generated, especially when there are many forms - each control name for the form must be generated to be unique on the forms and this process requires all field data to be loaded, potentially many times and this can cause loading, validation and other phases of the modification process to take a long time . The actual check-in, check-out and deploy times are unaffacted, but the processes can be lengthened to hours rather than minutes.
CMS-XML Error occurred while processing the search request using ascii symbols.
Error occurred while processing the search request using ascii symbols.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs