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 ERO customers upgrading from ZMF V6.1.x to V8.1.* must run conversion job HSTALTR4
Early versions of the ZMF 8.1 Migration Guide incorrectly stated that ERO customers upgrading from ZMF V6.1.x need not run upgrade job HSTALTR4 to add additional fields to the ERO history table. This is incorrect and ERO customers upgrading from V6.1.x to V8.1.* must run HSTALTR4. Failure to do so will result in a RC=8 and the following type of error when attempting to bind the new version of CMNDB2RQ:
CMS-XML ZMF 6.1 fix for conversion program error
The fix for the conversion program (CMNFIXHR) is attached to this Solution. Customers upgrading to ZMF 6.1.0 or 6.1.1 are encouraged to download this fix and use it in place of the CMNFIXHR load module delivered with ZMF 6.1.0 and ZMF 6.1.1.
CMS-XML CMN ZMF 7.1.3: Recovery of short component master general description records
The problem documented under DEF243550 existed in the ZMF 7.1.3 Component Master Conversion Job (CMVCONV7) for customers converting from earlier version 7 releases. This problem resulted in incorrectly formatted component general description records being written to the new short component master file (CMNCMPNT).
CMS-XML Importance of changing HPSPLIB/SVPARM contents when testing ZMF-related jobs
HPS0038E HPSINIT 09:53:05 Master files require conversion . At least 840 is required. Current version: 830
CMS-XML Urgent maintenance required for all customers upgrading to ZMF 8.1.2.
Due to the potentially severe impact of these issues, Serena requires that customers apply the 8.1.2 hotfix attached to this solution. Preferably this would occur prior to running the ZMF 8.1.2 conversion jobs. However, they should be applied even if conversion has already occurred.
CMS-XML Urgent Notices for ChangeMan ZMF
Urgent notices for ChangeMan ZMF Essential maintenance required for all customers upgrading to ZMF 8.1.2. 1) Component master corruption following conversion to 8.1.2 from releases below 7.1.3. 2) Install job (CMN20) is not submitted upon completion of CMN21.
CMS-XML NCL library type is no longer sacred in ZMF 6.1.0 and later releases
If making this change after conversion to 6.1.0 customers are also required to rerun the impact analysis table build procedure (CMNIA000) and reload the contents to the impact analysis dataspace (LDSLOAD) to ensure that this information is processed in the correct manner.
CMS-XML ZMF 7.1.2 GA Hotfix
DEF215526 : ERO Batch checkin failing to checkin to the third release area. DEF215656 : S0C1 encountered while executing CMNIACV4 conversion (5.6.3 to 7.1.2). DEF215838 : Batch keyword service module CMNVSRVC has no reply data.
CMS-XML Migration path for ZMF release 5.5.x to 6.1.0
Review the "Migration Guide Version 5.5 to 5.6" and the ZMF 5.6.1 Readme to identify the upgrade steps required to convert your 5.5 task to a 5.6 " conversion ready" state. Steps listed below are exceptions to the steps identified in the "Migration Guide Version 5.5 to 5.6" and the ZMF 5.6.1 Readme.
CMS-XML Upgrade to ChangeMan ZMF 8.2 DB2 option requires job DB2ADMGT to be run
All customers upgrading a ChangeMan ZMF 8.1.1- instance with the DB2 Option enabled must run conversion job DB2ADMGT. The relevant documentation (e.g. 8.2 Readme and/or Migration Guide) will be updated and re-published in due course to include this requirement.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs