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 5.3.4 README contains incorrect SERCOMC version
5.3.4 README contains incorrect SERCOMC version
CMS-XML Invalid SER8207E message after upgrade from 7.1.3.03 to 8.1.2 caused by incorrect version of SERLCSEC
Invalid SER8207E message after upgrade from 7.1.3.03 to 8.1.2 caused by incorrect version of SERLCSEC
CMS-XML Wrong version of component in production library after double package backout
Wrong version of component in production library after double package backout
CMS-XML Attempts to edit -n versions of components result in invalid CMN2556A errors
Attempts to edit -n versions of components result in invalid CMN2556A errors
CMS-XML SMS Id in Msg SER_820 contains unprintable characters and incorrect OS/390 version
SMS Id in Msg SER_820 contains unprintable characters and incorrect OS/390 version
CMS-XML Changes to prior release content version regression processing (ERR0417! errors) in ChangeMan ZMF 7.1.2
Changes to prior release content version regression processing (ERR0417! errors ) in ChangeMan ZMF 7.1.2
CMS-XML Staging versions panel CMNSIDV1 lists component versions in wrong sequence
Staging versions panel CMNSIDV1 lists component versions in wrong sequence
CMS-XML CMNVNSRD reports wrong number of delta versions and DSS.SERVICE.EXPAND fails when no deltas exist
CMNVNSRD reports wrong number of delta versions and DSS.SERVICE.EXPAND fails when no deltas exist
CMS-XML Inconsistent version regression reporting between ERO and package audit (ERR0417! and SYNCH10!)
In a simple, non-ERO package, if you checkout the -x version of a component (e.g. -1), change it and audit the package then we do NOT report a SYNCH10! error . This is by design and makes sense because the baseline component has not been changed since the checkout was executed.
CMS-XML Various versions of an "Invalid character (Unicode 0x0)" error message when trying to approve a linked package from TT.
The error has to do with a particular setup in ChangeMan ZMF. If there are no notifications in the approver levels and hierarchical approval is on, the error occurs. The approval is actually completed, even though there is an error message, and further approvals have no issues. If notifications are added, the error goes away.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs