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 Library types missing from global and application administration after upgrade to 8.2 Patch 4
After upgrading a ZMF 8.2 Patch 3 system to 8.2 Patch 4 using the documented conversion job (CMVCONVF) a large number of administration library type records are missing. For example, global admin shows 263 library types pre-upgrade but only 211 post-upgrade (option a.g.2). Similarly, my DEMO application shows 184 library types on 8.2 Patch 3 but only 138 on 8.2 Patch 4 (option a.a.2).
CMS-XML NCL library type is no longer sacred in ZMF 6.1.0 and later releases
Customers using the NCL library type to house subroutine-type components in CMN ZMF 6.1.0 must now ensure that these are defined as like-N libraries in the appropriate global , application and release administration panels or code CMNEX034 to define the NCL library type as like-NCL.
PDF Serena Application Release Manager Installation and Configuration Giude
1 AttheChangeMan ZMF Primary Option Menu, enter A.G.2intheOptionline to request Administration Options, select Global Administration Options, and select option 2 Library. The first of the Global Library Types panels displays.
CMS-XML What’s New in ChangeMan ZMF 8.2 Patch 4
Global administrators must specify a different library type on the Global Library Types Part 2 of 2 (CMNCGLT1) panel for the component activity file that is associated with a specified source component library type
CMS-XML ZMF 8.1.1 - Essential maintenance required to resolve baseline ripple problem
As documented in DEF284711 (Components not being 'rippled' by CMN30 and CMN55), a problem exists in the distributed ChangeMan ZMF 8.1.1 release that can result in components of some library types not being ‘rippled’ at baseline (CMN30) or backout (CMN55) time in the expected manner. In turn, this could compromise the integrity of the components residing in baseline libraries, especially where package backouts have occurred or where users need to work on –X versions of components.
CMS-XML The VFYILOD STEP gets a return code 8 when a RELINK fails or is submitted a 2nd time.
When using the RELINK function, the member / component has to be deleted from the package, before the relink can be rerun. VFYILOD issues an RC=08 for the listing library type for 'failed' relink requests and completed relinks get an RC=08 flagged on the target load library type .
CMS-XML New Features in ChangeMan ZMF for Eclipse 8.2 Patch 1
and used again next time selected. Relink is Available for Reserved Library Type Name of LCT Client Pack now supports relinks being generated
CMS-XML ZMF 6.1.2 Impact Analysis Problems
This problem may occur when the same baseline dataset is shared either between multiple applications or between multiple library types within a single application.
CMS-XML New Features in ChangeMan ZMF for Eclipse 8.1.4
if your installation has disabled the feature. You Can Update Component User Options for Like-Other Library Types You have been able to display user options in earlier ChangeMan
CMS-XML Autoresolve of load-to-load and object-to-load audit errors
2. Post-6.1.2.02, we continue processing and call CMNEX022 to assess whether or not there is a like-SRC linkedit control card library type associated with the target composite library type in the CSC$TBL table. See the CMNEX022 notes below on how this relationship is established. This processing is only relevant for configurations where linkedit control cards are stored as like-SRC and staged in their own right to build composite executables.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs