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 Potential userid regression if incorrect password entered once
The issue can be circumvented by switching to the Serena perspective after the initial failure, and logging on to the ZMF instance with the correct password. However, some users may already have re-tried the checkin expecting to be re-prompted for their password. This will have resulted in four failed logon attempts which will often exceed the installation defined maximum.
CMS-XML Upgrading from ZDD 3.2.1 to 5.6.0 creates additional and corrupt server entries
Upgrading from ZDD 3.2.1 to 5.6.0 creates additional and corrupt server entries
CMS-XML ZMF4ECL: Notifications not sent to users after automatic reconnection to ZMF Server
ZMF4ECL contains automatic reconnection logic that is executed if a user has been disconnected from the ZMF Server task (e.g. if the user has exceeded the specified SDNOTIFY/TIMEOUT parameter value for this ZMF instance ). If a user invokes this reconnection logic all subsequent notifications that should be sent to users are not being sent. Variable &NTFYIPA is set to &Z in all further file tailoring requests meaning that relevant notification parms and/or job steps are not included in the JCL being executed.
CMS-XML ZDD binary file transmission fails using 8.2 Patch 2+ Server
A customer is in the process of upgrading their ZMF environment (base and client pack) from 8.1.4.01 to 8.2 Patch 3. They transmit zip files from their Windows environment to datasets on MVS using the ZDD upload dataset functionality. These datasets are subsequently expanded and unzipped in their USS/zFS environment for use there.
CMS-XML Logon dialog box will not allow the '#' to be entered in the 'User ID' field
When customer displays the Server Properties page, from the 'Connection' tab the 'Test' button is selected. When the Logon dialog box is displayed, customer tries to enter '#9VW' in the 'User ID' field. The Logon dialog box will not allow the '#' to be entered.
CMS-XML ChangeMan ZDD not Setting &DB2PCLL Correctly
// REGION=3M, // PARM=(' HOST (COBOL390)', // ''),
CMS-XML Unable to see generated LOD and LST when a BUILD is submitted.
In ZDD 3. Logon to the ZDD server . 4. Goto the ZMF 5.6.x subsystem.
CMS-XML Errors when attempting to depoly ZMFWSEAR to WebSphere HTTP server.
The application contains validation errors. Correct the errors in the Problems view before publishing the application on the server . If you want to allow applications containing errors to be published on the server, enable the Allow applications containing errors to be published on a server check box (Windows > Preferences >Servers > WebSphere).
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 ZDD package filter window incorrectly displays 'Requestor name' instead of 'Creator'
In ZDD, if a ZMF Server – Application – Package filter is defined for an instance running a release lower than ZMF 8.1.1, we correctly display one of the available filter criteria as being the package ‘Creator:’. Attempting to define the same filter when connected to a ZMF 8.1.1 or higher release incorrectly displays the filter criteria as ‘Requestor name:’ or the value used to override that field in ISPF option A.G.9.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs