Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
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 S32E-11C abend in ZMF Server started task when multiple HSM recall requests are processed simultaneously
179 TIME =07.16.42 SEQ
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 V7.1.3 Request to update the P-site PMAST archive process
V7.1.3 Request to update the P-site PMAST archive process
CMS-XML ERO: Invalid 'No Packages Found'/CMR9508I error processing area demotion request
ERO: Invalid 'No Packages Found'/CMR9508I error processing area demotion request
CMS-XML ERO - Scratch/rename requests are not processed when packages are attached to a release
A package with scratch and rename requests is attached to a release. When the release is baselined, the scratch and rename requests are not processed.
CMS-XML "CMN2561I - Component requested is in use by another user" results with SEQ libtype processed by CMNEX037
Beginning in zmf 8.2.0B, customer reported the following error when staging an SEQ libtype, using a custom process. This libtype is processed by CMNEX037 during edit, which calls a custom REXX program to perform service cmponent/service/checkin. CMN2561I - Component requested is in use by another user.
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