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 ChangeMan ZMF REST Services 8.2 Patch 2 Hotfix 1
ChangeMan ZMF REST Services 8.2 Patch 2 Hotfix 1
CMS-XML hotfixes for CMN scheduler problems hotfixes for CMN scheduler problems
CMS-XML ChangeMan ZMF, excessive GRS memory usage and related issues
In ZMF 8.1.2 (and some hotfix ) environments, ChangeMan ZMF altered the way in which it handled ‘third party notification’ messages. These are messages that are sent by the ZMF Server started task to ‘third parties’ who have not instigated the action that resulted in the message being issued. For example, checkout conflict notification messages caused by a concurrent checkout requested by a different user.
CMS-XML z/OS 2.5 Compatibility with ChangeMan ZMF, ChangeMan ZMF Client Pack, ChangeMan SSM, Comparex, StarTool FDM and StarTool IOO
ChangeMan ZMF 8.2 Patch 5 plus the hotfix for OCTCR46A157001 (see resolution for details)
CMS-XML Urgent maintenance required for all customers upgrading to ZMF 8.1.3.
They cover problems in user variable translation and transition to the associated function and may result in, for example, component history records losing their user option data. Due to the potentially severe impact of these issues, Serena requires that customers apply the 8.1.3 hotfix attached to this solution. The fixes can be applied at any time to resolve the issues.
CMS-XML Housekeeping job uses a large amount of CPU and runs for excessive amount of time
This will be addressed in CMN ZMF and the hotfixes released alongside the 7.1.2 GA version, if they have been downloaded on or after April 17th 2012. In earlier versions, customers may wish to disable the aging of component history records by setting the ‘AGING - COMPONENT HISTORY’ parameter to a value of ‘0’ in application admin.
CMS-XML ZMF4ECL Compatibility with IDz 14.1.x
support has been added to ZMF4ECL 8.1.4 Hotfix build 386 and higher. Customers interested in IDz 14.1.x
PDF 11019232b20c6401660b6b50730079ed#CM 14.4 Parallel Dev - Araxis.pdf
The following diagram describes a typical two-line development model where a second line of development is initiated to create a patch or hotfix . Subsequently the patch/hotfix code is merged back into the mainline development stream.
CMS-XML Which version of SERXPTIK should I use?
The one exception mentioned above is for customers upgrading from the original ZMF 8.1 GA version of the product. They will experience problems when using later versions of SERXPTIK. Such customers will need to apply the ZMF patch level, or the 8.1 GA-compatible hotfix for the issue covered by DEF264963, before using later versions of SERXPTIK.
CMS-XML Invalid SER8207E message after upgrade from to 8.1.2 caused by incorrect version of SERLCSEC
Also, a linkdates report compared favourably with a working system here although it showed the expected differences in user exits, applied hotfixes , etc.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs