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 Refresh prior to 'component list' functions is required, to ensure synchronization.
Customer reports that when a component is deleted from a package through the ZMF ISPF interface the deletion is not necessarily picked up in ZDD unless a 'refresh' is issued. If a checkout is attempted on the ZDD side without the refresh, for the component just deleted, "All selected components are already checked out to package." is issued.
CMS-XML Delete component function fails on three character application packages
If a user attempts to delete a package component from a package associated with a three character application name the request will fail with a ‘Delete Components’ – ‘ No components eligible for this operation.’ ... Customer has confirmed that this behaviour existed in the ZDD client and it has been recreated using our latest versions, too.
CMS-XML Search function not honouring defined Editor.
Using the search functionality within ZDD on a component and trying to edit the component the editor doesn’t honour the specified editor in the ZDD properties. The editor always defaults to the ChangeMan DS editor.
CMS-XML ZMF4ECL: Package create function fails on D sites
Attempts to create a package on a D site using the WD4ZMF interface do not allow the user the opportunity to specify any package installation sites.
CMS-XML "Exception running background job ZMF/Eclipse search..." is issued, attempting to search a staging library that has been deleted by housekeeping aging processing.
"Exception running background job ZMF/Eclipse search..." is issued, attempting to search a staging library that has been deleted by housekeeping aging processing.
CMS-XML When attempting to compare staging to baseline -1 version, customer is getting member not found.
To correct this issue, upgrade to a modern supported release of ZMF. This issue was reported when running against a ZMF server. The issue is not present in more modern supported ZMF releases.
CMS-XML Baseline library member names containing national characters are not being translated correctly
Component/member names in baseline libraries that contain 'national' characters (i.e. #, @ and $ in US terms) are not being translated in the expected manner for non-US environments. They can be browsed but attempts to execute functions against them are liable to fail with ‘member not found’-type errors. The same member names are displayed and processed correctly in other ZMF4ECL folders (e.g. Data Sets, package library types, etc.).
CMS-XML ZMF4ECL: Multiple users still unable to connect to ZMF Server (SER8210E) despite running fix for OCTCR46A38001
Notes: - Reporting customer is not using SSL connections and all settings are appropriate for this. - The same users can connect successfully from the same client machines to the same ZMF Server using ZDD.
CMS-XML BSOD using ZDD with APSWARE VISUALjob transfer function
The customer is using ZDD GA Build 522. The problem did not exist with ZDD 7.1.3.
CMS-XML ZMF4ECL: Problems creating new package components
A customer has reported the following issues when attempting to create new package components in the ChangeMan Explorer view running ZMF4ECL 8.2 Patch 3 Hotfix Build 512 (issue persists in ZMF4ECL 8.2 Patch 4 GA Build 539): a) when creating a new package component of a library type that contains a relatively large number of baseline components (e.g. c.60,000) the request hangs for a significant time and eventually fails with the following error in the customer's environment:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs