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 Install date and time change causing other package options to become unavailable
f. Everything looks fine in ISPF and the package can be progressed in that interface . Just not in ZMF4ECL.
CMS-XML Disabling non-ZMF functions from client pack interfaces
Disabling non-ZMF functions from client pack interfaces
CMS-XML The relink option is not displayed in the ZDD interface for library types defined as like-N.
The relink option is not displayed in the ZDD interface for library types defined as like-N.
CMS-XML ZMF4ECL: Call to BULD00XD inconsistent with other interfaces
ZMF4ECL: Call to BULD00XD inconsistent with other interfaces
CMS-XML The relink option is greyed out in the ZMF4ECL interface for library types defined as like-N.
The relink option is greyed out in the ZMF4ECL interface for library types defined as like-N.
CMS-XML ZMF4ECL: Problems sharing and synchronizing projects with ZMF packages
A customer testing the capabilities of sharing IDz development projects (specifically IBM Data Studio projects) with ZMF using the ZMF4ECL interface has reported several issues in both use and execution of functions in this integration. a) Concurrent development issues
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 ZMF4ECL: Incorrect sites being displayed at package create time
When creating a package for a DP site in the ZMF4ECL interface we need to mirror the behaviour of the ISPF interface . That is, display only the sites that have production datasets defined plus the local host site. Creating a package with invalid sites can result in errors that are difficult to resolve later in the life cycle (e.g. at package freeze, package install or package baseline time).
CMS-XML ZDD 7.1: Problem when staging new files into packages.
A problem which is related to ZDD interfacing with "PRO/JCL Workstation" on the PC. When users are just saving components back into the package after a change, e.g. just a normal "save", then it works as expected. However there are problems with "save as":
CMS-XML ZMF4ECL 7.1.1 - ZDDOPTS LIBTYPE does not work
Coding the ZDDOPTS LIBTYPE member to suppress libtypes from being displayed in the plug-in interface , does not work. All libtypes are still displayed in the various dialogs.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs