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 Issue integrating with SSM when MLS is turned ON in SSM.
Issue integrating with SSM when MLS is turned ON in SSM.
CMS-XML Bad date causes "create package" to start over from the beginning.
Bad date causes "create package" to start over from the beginning.
CMS-XML Logon for new Servers popping up whenever a wrong ID is first entered at Windows startup.
Logon for new Servers popping up whenever a wrong ID is first entered at Windows startup .
CMS-XML ZDD truncating submitted JCL at first ‘JOB’ encountered, even in comments
ZDD truncating submitted JCL at first ‘JOB’ encountered, even in comments
CMS-XML ZMF4ECL 8.1.3 issue with 'Variable Name' not being displayed as coded in ZDDOPTS BUILD component
<field name="UserOption801" readonly="N" label=" First 5 chars " required="N" validation="ALPNANUM" default="/> Points of note: - The assumption is that this applies to all of the extended user option fields (i.e. UserOption101- UserOption7205).
CMS-XML SubmitJcl function works only once.
In ZDD 6.1.1 when you issue the "SubmitJcl" function for a JCL member in a ZMF package it only submits the first instance and subsequent submits do not get submitted. Also there is no notification back so say the JCL has been submitted. To recreate the issue you need to carry out the following steps:
CMS-XML Access denied message when reusing files.
Customer submits a job that transfers a dataset from mainframe to the client. The first time it always works fine, further trials sometimes work, sometimes leads to the problem “access denied”, as the system thinks that the dataset is still in use. They also see the problem when working with ZMF datasets.
CMS-XML Failure of DEF174972: SubmitJcl function works only once.
This is still an issue and what happens now is the reverse. The first SubmitJcl does not work the first time, then all subsequent ones do get submitted. This happens from submitting JCL from a Package and also JCL from your personal dataset.
CMS-XML Language and procedure dialog error processing new SRC component
A dialog error exists staging a new SRC component after it is first checked into a package. After selecting the component language, and then selecting the appropriate build procedure, the language is inadvertently reset to the first on the list and must be re-changed to the correct value.
CMS-XML Updating complex package properties removes all participating package information
When any package property is updated on the first window for a complex package and ‘Finish’ selected from here, the ‘Participating Packages Update’/’Complex/Participating Package Reset’ function is executed and all participating packages linked to the complex are removed. Problem occurs on both builds tested (185 and 207).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs