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 ZDD: Unable to stage a like-load component into a package
It is currently not possible to stage an executable module directly into a package using ZDD, e.g. a vendor load module. No like-load/like-lod
CMS-XML ZMF4ECL: Inconsistency in edit and build after package revert
ZMF4ECL: Inconsistency in edit and build after package revert
CMS-XML Checkout issue with Client Pack version 8.2.0.422 Web Services version 820 build 298
Checkout issue with Client Pack version 8.2.0.422 Web Services version 820 build 298
CMS-XML When EDIT COMPONENT is checked, the staging dataset is edited, when using checkout from package. Target of the checkout (personal dataset) should be what is edited.
When a component is checked out from a package to a personal dataset, if the EDIT COMPONENT box is checked, the staging dataset is opened for edit and the changes made are not saved to the personal dataset. In this scenario, the personal dataset should be opened for edit, since it is the 'target' of the checkout request.
CMS-XML Compile and link parms not parsed when ZDDOPTS is enabled.
When ZDDOPTS is enabled and you have source component in a package with Compile and Link parms. When you issue the BUILD on ZDD these PARMS are not parsed back to ZDD.
CMS-XML "Approve" is grayed out after an unplanned/TEMP package is in TCC status. POST approvals cannot be done.
The "Approve" link is grayed out after an unplanned/TEMP package is backed out to TCC status. POST approvals cannot be done. POST TCC status approvals should be allowed for unplanned packages.
CMS-XML Blue screen issued in ZDD when trying to view packages.
All the happens is that ZDD blue screens. The customer is running ZDD 3.1.1 build 142 and CMN ZMF 5.3.2 (SERNET 5.4.5)
CMS-XML ZDD package filter window incorrectly displays 'Requestor name' instead of 'Creator'
In ZDD, if a ZMF Server – Application – Package filter is defined for an instance running a release lower than ZMF 8.1.1, we correctly display one of the available filter criteria as being the package ‘Creator:’. Attempting to define the same filter when connected to a ZMF 8.1.1 or higher release incorrectly displays the filter criteria as ‘Requestor name:’ or the value used to override that field in ISPF option A.G.9.
CMS-XML ZMF4ECL: Attempts to checkout from another package fail with CMN8490I
In ZMF 8.1.2 new functionality was added to the ISPF interface to allow users to fully checkout components directly from one package to another. This functionality was extended to ZMF4ECL in the 8.1.3 release of the client software. However, attempts to use this functionality from ZMF4ECL 8.1.3 when connected to a ZMF Server task running at 8.1.1.01 or lower will fail with the following error:
CMS-XML ZDD: Inconsistencies in ISPF and Client Pack invocation of HLLX BULD* routines
Opening separate CRs in both ZDD and ZMF4ECL to have these issues assessed/resolved. Will link both CRs once complete.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs