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 Attempting to checkout multiple components from the package view, causes error messages to be issued and checkout fails.
Attempting to checkout multiple components from the package view, causes error messages to be issued and checkout fails .
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 ZMF4ECL Team checkout of hfs component fails
When working within the Java perspective, any attempt to checkout a hfs component fails with the following error: Exception in ZmfServer: ; nested exception is:java.io.IOException: java.io.IOException: java.io.IOException: Non nillable element 'componentType' is null. Checkout of 'standard' MVS component types works fine.
CMS-XML ZMF4ECL: Checkout to personal lib fails for renamed component
If a new SRC component has been staged into a package using the ISPF ‘stage from development’ (1.6.1/S1) option, renamed in the process, and not subsequently built, an attempt to check it out to a personal development library in ZMF4ECL will fail. This is because the dialog references the original member name, not the renamed SRC component. The following type of message will be returned if the user attempts to continue the checkout request:
CMS-XML ZMF4ECL checkout processing fails with NullPointerException
We can recreate the failure here. For example, if I specify work request ID WORK00000001 in the checkout filter I can reproduce the problem. However, customer’s workspace is not filtering checkout on work request ID so there are obviously other potential causes.
CMS-XML ZMF4ECL: Dataset allocation failures
"' Checkout ' has encountered a problem. No response from ChangeMan ZMF for New Dataset request."
CMS-XML New Component name validation failure
Observed an error in the new component process for HFS names. Name is validated using data set member name validation, rather than HFS naming validation..
CMS-XML Checkin from external dataset fails for three character application names
Attempts to check -in a component from the Data Sets folder to a package with a three character name fail . The package name in the check-in window is truncated to three characters (i.e. no number) and when check-in is attempted it fails with the following error message:
CMS-XML Invalid dataset ENQueue failures editing components in personal development libs
Problems encountered during checkout and subsequent edit of a component in a personal development library results in one or more of the following symptoms: 1. An invalid SER4155E in the eclipse or RDz client Data Set ENQ failure: SER4155E Serial lock could not be obtained
CMS-XML Browse/Edit failing due to Component Security Error
Failures were observed viewing components. Component Security error was being encountered. Problem was resolved by making sure user signs on with an upper case userid.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs