Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Release Activity and Environment views hang when filter by Owner
Release Control 6.1
CMS-XML CMN15 installation jobs hanging when package created on old release
We have recreated a customer-reported issue where CMN15 jobs for packages created in older versions of ZMF hang when they are installed under ZMF 8.1.1.01. The customer’s packages were originally created under ZMF 7.1.3.03. Our recreation scenario was using packages created on earlier versions of ZMF. On occasion loops in the started task can also be encountered in relation to this problem.
CMS-XML Release install jobs hanging and eventually failing
In our recreation they eventually fail after c. 2 hours with a RC=6 and a “CHANGE MAN CONNECTION LOST, LOGGING TO DELAY FILE” error. We are running our task with an SDNOTIFY=M120 parm which probably explains the timing of these RC=6 failures . These jobs need careful manual intervention to cancel and restart.
CMS-XML ZMF Promote Release (promoteRelease) Service Component Overlay Failures
Release Manager 3.5
CMS-XML Delete frozen releases from CLI not possible if release name has trailing space
Delete frozen releases from CLI not possible if release name has trailing space
CMS-XML Maintain On Frozen Release To Pending Prod Area Does Not Ask For Approvals
Maintain On Frozen Release To Pending Prod Area Does Not Ask For Approvals
CMS-XML CLI - Frozen release name gets truncated after 50 characters
CLI - Frozen release name gets truncated after 50 characters
CMS-XML Frozen Release Maintain does not allow new project names with spaces (P18)
Frozen Release Maintain does not allow new project names with spaces (P18)
CMS-XML Builds - Relative path for Make Procedure in frozen release gets truncated to 50 characters
Builds - Relative path for Make Procedure in frozen release gets truncated to 50 characters
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.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs