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 Double clicking on a non-PDS/PDSE item in Data Set tree no longer opens file.
"java.lang.NullPointerException" is issued when double clicking a non-PDS/PDSE item in Data Set tree. Right click and open with seem to work correctly.
CMS-XML "Retain Checkout Details in Eclipse" checkbox should not be active for 'checkin' of a new component.
When a new component is checked into a package, the "Retain Checkout Details in Eclipse" is active and if checked, will create a new checkout record. The "Retain Checkout Details in Eclipse" box should only be active at checkin, when the component has been checked out first. Right clicking the component in the ZMF Checkouts tab and selecting 'checkin' from the menu will simply reactivate the component, rather than check it in again from the personal dataset, as expected.
CMS-XML Users unable to access ZMF components - corrupted data displayed
This is fundamentally the same issue as that covered in DEF255354. See that CR for details .
CMS-XML Site Information Page is not not marked READ ONLY, and fields can be updated on an ALL Site.
Site Information Page is not not marked READ ONLY, and fields can be updated on an ALL Site.
CMS-XML Check-in of a new like-OTH component fails with "No component data available for LIKE-OTH build request."
Check-in of a new like-OTH component fails with " No component data available for LIKE-OTH build request."
CMS-XML Users unable to access ZMF components – corrupt-looking data presented
The problem is that when the affected user attempts to access a component (package or baseline in browse or edit) ZMF4ECL returns corrupt looking data . We have taken all the usual steps to try and resolve the issue:
CMS-XML ZMF4ECL: 8.1.3 Users unable to access ZMF components – corrupt-looking data presented
The problem is that when the user attempts to access a component (package or baseline in browse or edit) ZMF4ECL returns corrupt looking data . Again, traces show a ‘SER4184E DATASET DOWNLOAD request is not allowed’ message which suggests that an invalid user token is being generated for the affected user's sessions on the problem machine.
CMS-XML HLLX variable workChangeRequest is not handled in ZMF4ECL
When creating a package via ZMF4ECL, the workChangeRequest variable is not populated at exit points PCRE0001 and PCRE0101. This variable is populated in the ISPF and ZDD interfaces and the correct Work Change Request value is used at package creation, even from ZMF4ECL. However, the variable cannot be preset or validated in the ZMF4ECL interface via the appropriate HLLX.
CMS-XML Data available at the BULD0004and BULD0104 HLLX exit points, is inconsistent depending on where call originated.
Data passed to HLLX exit points for BUILD, is not consistent when called from different clients.
CMS-XML Missing Language (pre)selection for RDz Integration Details.
When you perform a Checkout to Personal Library from either Baseline or Package. You get the Select ”RDZ Integration Details” view. However in neither case the Language is preselected which should be taken from the Component History.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs