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 Cannot commit any changes when using the compare function.
Cannot commit any changes when using the compare function.
CMS-XML ZDD Library types defined for Panvalet and Librarian are not saved across reboot
ZDD Library types defined for Panvalet and Librarian are not saved across reboot
CMS-XML “Lock Component” check box setting is no longer being saved between checkouts.
“Lock Component” check box setting is no longer being saved between checkouts.
CMS-XML Default Job Cards cannot be changed and then saved.
Default Job Cards cannot be changed and then saved .
CMS-XML Members starting with § cannot be changed and saved using ZDD.
c) X'7B' (hash) However; when you want to save a member which starts with one of these special characters after editing it ZDD issues one of the following messages: "Serena Network - missing or invalid file name"
CMS-XML Edited ZDD jobnames not being saved for subsequent job submission
When submitting a ZMF build job within ZDD whilst changing the jobname to a non-default name (i.e., a name which is not of the form USERID + 1 character) then the new format jobname is not retained for subsequent job submissions. It automatically reverts to the default model jobname for the next request.
CMS-XML Smart editor changes not being saved to staging datasets
When components are changed in a ZMF4ECL 8.2 smart editor session the changes are not always being saved to the staging dataset. To date this has only be reported and recreated in international configurations (e.g. French environment, LCLCCSID=1147). Hence this may be a factor in the problem.
CMS-XML ZMF4ECL: Changes not saved when made in smart editor browse session
If the user selects 'Yes' and makes changes to the component these are reflected in the transient edit dataset allocated by the ZMF Server started task when the component is saved or the edit session closed. However, the changes are not copied to the staging dataset. No warning or error messages are issued to the user in this situation.
CMS-XML ZMF4ECL not freeing notification ports.
In certain circumstances, ZMF4ECL is not closing/ freeing the notification port used for receiving notifications. This may lead to the port numbers not being reused. This may cause firewall problems for some customers.
CMS-XML 0C4 SERVDSNO+9B38 uploading/saving component to ZMF package using ZDD
0C4 SERVDSNO+9B38 uploading/ saving component to ZMF package using ZDD
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs