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 ZMF4ECL: Users must have a minimum of READ access to baseline and delta libraries
Similarly attempts to checkout or compare components from baseline , or baseline -1, result in the following type of error message when the user has less than READ access to the physical baseline or delta datasets: CMN1088A – {your.baseline.library
CMS-XML ZMF4ECL: Problems creating new package components
A customer has reported the following issues when attempting to create new package components in the ChangeMan Explorer view running ZMF4ECL 8.2 Patch 3 Hotfix Build 512 (issue persists in ZMF4ECL 8.2 Patch 4 GA Build 539): a) when creating a new package component of a library type that contains a relatively large number of baseline components (e.g. c.60,000) the request hangs for a significant time and eventually fails with the following error in the customer's environment:
CMS-XML ZMF4ECL: Problems sharing and synchronizing projects with ZMF packages
i ) Baseline changes are not identified If a component is being actively developed in an IDz
CMS-XML Hotfix solution for problem where CMN ZMF 7.1 restored master files cause U0023 abends and data corruption
subsystems with master files that have been restored from prior backups. Users may also encounter related User 23 (U0023) abends in this situation. The problem is limited to sites that have defined and are using HFS staging, promotion and/or baseline libraries.
CMS-XML Maintenance of ChangeMan ZMF Impact Analysis Table
Alternatively customers can run the IMPACT & LDSLOAD jobs on the same schedule. This has the added advantage that it will both re-organize the IA dataspace and also ensure that any small changes to baseline library definitions that have been made but forgotten about will also be picked up and reflected in the IA table contents. This is something that we often see here and usually presents itself in the form of unexpected or missing SYNCH errors in audit jobs.
CMS-XML KM-Dim9: Replicator: Error: Failed to run utility to import baseline.
Serena Changeman Replicator encountered an error while attempting to input the baseline details on the subordinate.
CMS-XML Release Package gives error "RequestTimeout: The orchestration request was submitted but the server timed out waiting for the response"
When editing a Release Package and attaching a Dimensions Baseline or a ZMF Package, the system make give error: Error occurred during web service invocation: SOAP Fault Code: env:Server
CMS-XML SYNCH10 incorrectly reported when components are staged from development.
Fixed in ZMF 5.5.3 and 5.6.0. Note: SYNCH10 is also incorrectly reported when components, which exist in baseline , are staged via BATCH STAGE. See Solution D5346 , also fixed in ZMF 5.5.3 and 5.6.0.
CMS-XML S906-08 abend on module SERRECAL running IMPACT job (CMNIA000)
They have over 52,000 baseline libraries defined in the problem ZMF instance, none of which are actually HSM migrated, and it appears that we are reLOADing SERRECAL for the majority/all of these libraries without an intermittent DELETE.
CMS-XML ZMF Server task S378-24 abend running RLSMAREA.DETAIL.TEST for specific release area
SER0953E Task abnormally terminated: Comp =S378 Function=MASTER/ENDREQ NSI=010AB158 ...
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Comparing files (demonstration)
This Dimensions CM demonstration shows you how to compare two item revisions in the repository, and compare an item revision in the repository with a file in a work area
Dimensions CM: Overview (demonstration)
This animation describes what you need to know about Dimensions CM to help you get started with your developement tasks.

Additional Assistance

  • Submit a Case Online
  • FAQs