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 ZMF 5.5 to ZMF 5.6 Migration Guide 'Sample Conversion Day Script' update
In the ZMF 5.5 to 5.6 Migration Guide, page 51 describes all the steps to create the IA table and the new BUN table. It even tells you to run the Full IA job after the ZMF V5.6 task comes up (point #4). However, in the 'Sample Conversion Day Script' on pages 60 + 61 there is no mention of the IA and BUN table jobs or when to run the Full IA job to populate the tables.
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 Receiving "CMNIAM00 I/A Dataspace open failed" after converting from ZMF 6.1.1 to ZMF 7.1.3.
Please see the ZMF 6.1.2 or later Readme for further information.
CMS-XML Modules CMNGNRPT/CMNRPTDS obsolete in Change Man Mainframe 5.1.0
In Change Man Mainframe 4.1.6, assembler module CMNGNRPT and copylib member CMNRPTDS were used to add custom reports to the report selection list. In Change Man Mainframe 5.1.0, the functionality that these modules provided is now accomplished via Global and Local Administration panels, effectively making these modules obsolete. This has not been documented in Release Notes or Summary of Enhancements, etc. We believe it should be as customers converting from 4.1.6.
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 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 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.
CMS-XML FAQ - DB2 Option Changes in ZMF 8.1.1
8.1.1+ moves these admin definitions to the DB2 tables created by DB2OPTN, which are populated by DB2OPTNC on conversion day. Don’t forget about DB2OPTNR which is required for all DB2 subsystems which are targets for promote and/or install DB2 processing.
CMS-XML ZMF 8.1.1 - New DB2 Option Tables and Packages
DB2OPTNC Refer to delivered JCL DB2OPTNC for converting existing SQL admin definitions to the new tables.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs