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 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 Batch checkout issue if the baseline version is not changed after a -1 checkout of a non-src component.
Batch checkout issue if the baseline version is not changed after a -1 checkout of a non-src component.
CMS-XML 8.2 P1 version of ZMF4ECL no longer allows compare of components tied to source.
8.2 P1 version of ZMF4ECL no longer allows compare of components tied to source.
CMS-XML VERSION statement is missing from DB2 compiles, when settings are set on in Global DB2 Admin.
VERSION statement is missing from DB2 compiles, when settings are set on in Global DB2 Admin.
CMS-XML SAXParseException when password has expired
Customer is running an old version of the ZMF4ECL plugin. When logging into ZMF via ZMF4ECL (using Rdz), with an expired password, the user receives error 'SAXParseException with Premature End of File' message. The message does not provide sufficient information for the user to understand the problem.
CMS-XML ChangeMan ZMF and Supported Releases
The maintenance status of ChangeMan ZMF (and associated products) can be found on the Support Site. Click here to navigate to the page containing "Changeman ZMF products -- versions and maintenance status". The page provides details on the various releases of ChangeMan ZMF, such as, the date it was first announced, the current maintenance release, the date on which current maintenance was announced, and the "End of Development" date.
CMS-XML Proxy stub code is missing in ZDD 6.1.0
With previous versions of ZDD, ZDD was shipped with a file named ZosShell_p.c which as part of the COM folder. This file contained the proxy stub code. However, with ZDD 6.1.0 this is not part of the base code and has been missed in the delivered code.
CMS-XML Missing ZDDOPTS BUILD member validation list options
We have set up a ZDDOPTS BUILD member as follows: <?xml version ="1.0"?> <options name="BUILD" strict="Y">
CMS-XML Unable to see generated LOD and LST when a BUILD is submitted.
Using the ZDD 6.1.1 GA client version , the LST and LOD components are not viewable following the build of a source member. If you connect to a ZMF 5.6.2 subsystem and select a package with a checked out source member in it, the BUILD operation completes successfully and activates the source. However, the associated LST and LOD members are not seen in their corresponding folders when viewed through ZDD.
CMS-XML Unable to see generated LOD and LST when a BUILD is submitted.
Using ZDD 6.1.1 GA client version , if you connect to a ZMF 5.6.2 subsystem and select a package with a checked out source member in it, when you issue a BUILD for the source member although the BUILD completes and activates the source, the associated LST and LOD members are not seen in there corresponding folders when viewed through ZDD. ZMF 5.6.x side.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs