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 ZMF4ECL notifications not reaching users on 8.1.1.01 instance
ChangeMan ZMF Client Pack Client Pack 8.1.2 ChangeMan ZMF Client Pack ZMF4ECL 8.1.2
CMS-XML ZMF4ECL: Focus problem deleting entries from ZMF Notifications view
ChangeMan ZMF 8.1.3 ChangeMan ZMF Client Pack Client Pack 8.1.3
CMS-XML Clicking on the date header on the ZMF Notifications TAB does not work correctly
ChangeMan ZMF Client Pack 7.1.2 Hotfix
CMS-XML Security failures should be reported back to ZMF4ECL users
When using ZMF 4ECL, if a security problem (e.g. a S913 abend and/or a ICH408I message) is encountered accessing a dataset for any reason then the user is not notified of the failure. The folder simply fails to expand without any explanation of the problem. The cause of the problem will usually be reported on the mainframe side of the integration.
CMS-XML Unexplained disconnection from Server task for ZMF4ECL users
out and disconnected from the Server task in a much shorter period. For one example, a user's ZMF 4ECL Notification view shows that they submitted a promotion job at 11:55 which
CMS-XML Defects resolved in ChangeMan ZMF for Eclipse (ZMF4ECL) 8.2 Patch 5
OCTCR46A55005 Issue with Monitor Jobs for Completion not being seen under Notification tab. OCTCR46A56004
CMS-XML ZMF4ECL: Dataset allocation failures
If trace options are enabled, the user does not receive this pop up but a message stating the following can be seen in the .log file and both the Notifications and Error Log views:
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 New Features in ChangeMan ZMF for Eclipse 8.2 Patch 1
Option To Allow Freeze To Issue Notification When JCL Build Complete A new option has been added
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs