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 File DOWNLOAD option from Serena Explorer context menu does not allow path to be specified by over typing.
File DOWNLOAD option from Serena Explorer context menu does not allow path to be specified by over typing.
CMS-XML Installing ZMF4ECL in batch or via script
"C:\Program Files\IBM\SDP\eclipsec.exe" -application org.eclipse.equinox.p2.director -noSplash -repository file:"C:\Users\snevin2\Documents\ZMF4ECL 8.2.0 .424\ZMF4ECL Update Site 424" -installIUs ChangeMan_ZMF_Eclipse_Plugin.
CMS-XML ChangeMan ZMF 8.2 Patch 1 and ChangeMan ZMF Client Pack Patch 1 are now available
ChangeMan ZMF 8.2 Patch 1 and ChangeMan ZMF Client Pack Patch 1 were released on March 28, 2019. You can download them here .
CMS-XML CMN ZMF Web Services Sample Code
These are available for download by any customer entitled to ZMF. The challenge here is that these web services cannot be used asis. They must be implemented within a programming language to manage session state.
CMS-XML ChangeMan ZMF 8.2 Patch 2 and ChangeMan ZMF Client Pack Patch 2 are now available
ChangeMan ZMF 8.2 Patch 2 and ChangeMan ZMF Client Pack Patch 2 were released on September 27th, 2019. This release includes support for IBM z/OS 2.4 and new ZMF REST Service APIs. You can download them here .
CMS-XML BrowseComponent web service fails and crashes tomcat accessing specific component
A customer has their own homegrown eclipse integration tool built using ZMF web services. When downloading a specific component that contains a significant amount of non-display, hexadecimal characters using the BrowseComponent web service they are encountering the following type of error:
CMS-XML ZMF4ECL: Problem accessing contents of package and baseline components
Affected users appear to be unable to access any components and ZMF Server traces suggest that the download request is never being sent to the server. The RDz .log file shows the following types of error:
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 Users unable to access ZMF components – corrupt-looking data presented
e. close the open/corrupt window, wait until the ZMF started task is restarted and retry. However, the problem persists. Traces show a 'SER4184E DATASET DOWNLOAD request is not allowed' message which would appear to be related.
CMS-XML Users unable to access ZMF components - corrupted data displayed
However, after several days the problem apparently ‘disappears’ in response to no particular action. In both of the occurrences we have traced we do see a ‘SER4184E DATASET DOWNLOAD request is not allowed’ message which would appear to be related. Whether or not this is the cause or a symptom of the problem is unclear.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs