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 Extended component user option fields not presented to users on 7.1 ZMF Servers
Users connected to ZMF 7.1 servers from a ZDD 8.1.1 (build 500) client are not presented with the extended component user variables (UserOption101-UserOption7205/CUSR0101-CUSR7205) at component build time. Similar tests running against an 8.1 ZMF Server do show the user options.
CMS-XML Checkin of like-OTHER does not 'remember' server selection from 1st screen.
When a new like-OTHER component is checked in to a package, from a personal dataset, the first screen presented requests a Server selection. The selected server is not subsequently used / populated on the next checkin screen, but is the only on available for selection in the pull-down.
CMS-XML ZMF4ECL: Problem accessing contents of package and baseline components
A customer is running various RDz 9.1.1+ client builds with ZMF4ECL build 267 against a Websphere application server with build 194 of the ZMF Web Services and a ZMF 6.1.1.02 Server . A growing number of users are reporting problems accessing package and baseline components for browsing/editing, as appropriate.
CMS-XML Server selection button is greyed out when checking in from z/OS perspective.
Issue checking in new component from personal library in RDz z/OS perspective. The dialog is asking for server but button inactive (greyed out).
CMS-XML Issues checking in components to more than one package
- Now attempt to check it into another package. Server button is active but only contains the current server so cannot be changed. Server, Application and Library Type are displayed, apparently pre-filled from the checkout information, but cannot be selected or changed to a different package.
CMS-XML Users unable to access ZMF components - corrupted data displayed
We have tried the following to clear the issue: a. close and attempt to reopen the affected component window. b. close the open/corrupt file window in RDz, explicitly disconnect from the ZMF server in RDz (right-click on the Server folder and select the ‘Disconnect...’ option), then reconnect and retry. c. close the open/corrupt window, shutdown the RDz client (including the –clean startup parm), restart the RDz client and retry.
CMS-XML ZMF4ECL: Unable to edit some components containing hexadecimal characters in text editor
Problem can be recreated using ZMF4ECL 8.2 Patch 5 Build 568 running against a ZMF 8.2 Patch 5 Server task.
CMS-XML Unexplained disconnection from Server task for ZMF4ECL users
=nnnnnnnn ) at 12:45, 49 minutes later. If a component edit session is open and the user
CMS-XML ZDD only scratches source component
After further investigation, we could only recreate this issue when connected to ZMF 6.1.* Servers . When connected to ZMF 7.1.*
CMS-XML Users unable to access ZMF components – corrupt-looking data presented
a. close and attempt to reopen the affected component window. b. close the open/corrupt file window in RDz, explicitly disconnect from the ZMF server in RDz, then reconnect and retry. c. close the open/corrupt window, shutdown the RDz client (including the -clean startup parm), restart the RDz client and retry.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs