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 Job List information incorrect and duplicate column names.
Job List information incorrect and duplicate column names .
CMS-XML ZDD package filter window incorrectly displays 'Requestor name' instead of '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. The package creator field is separate to the requestor name and will almost always contain a different value. ZDD correctly continues to use the package creator field when processing the filter.
CMS-XML Several valid ZDDOPTS COMMAND member fields generating ‘!MESSAGE Name field invalid.’ messages
A number of valid ZDDOPTS COMMAND fields, several of which are included in the sample member supplied with ZDD, generate invalid error messages at ZMF Server logon time in ZMF4ECL. For example:
CMS-XML ZMF4ECL: SAXParseException error displayed in relation to failed user logon attempt
ICH408I USER(USER001 ) GROUP(ZMFSUP ) NAME (SUPPORT USER ) 823 LOGON/JOB INITIATION - PASS PHRASE IS NOT VALID ICH408I USER(USER001 ) GROUP(ZMFSUP ) NAME(SUPPORT USER ) 808
CMS-XML Errors when attempting to depoly ZMFWSEAR to WebSphere HTTP server.
src-resolve: Cannot resolve the name 'typeYesNo' to a(n) 'type definition' component.
CMS-XML WITH Z/OS 1.4, JES2 EXIT22 PARMLIST IS INCORRECT
Reported Release ......... 707 Fixed Release ............ Component Name 5752 JES2 Special Notice Current Target Date ..03/09/30 Flags
CMS-XML Smart Editor setup fails with "Target Resource not found" message.
Smart Editor setup may fail with a "Target Resource Not Found" or a "Source Resource Not Found" message in some international environments. The error is due to the data set names not being translated properly before calling a RDZ Copy API.
CMS-XML New Features in ChangeMan ZDD 8.2
The network name has been changed ... This network name is the name that appears on the ChangeMan ... New Test Package Integrity wizard tests a package for component integrity errors . ... A “New name ” field has been added ... Like ISPF, you can only specify a new name when checking in a single component. The “New name ” field is disabled (grayed
CMS-XML ZMF4ECL: Browse listing function assuming LST library type
When selecting the ‘Browse Listing’ option for a source component in ZMF4ECL it appears to be assuming the listing will reside in a library type named LST. This will not be the case for many customers and will produce the following type of error message when the function is selected: ... <libtype name ="SRC" show="Y" listing="LSX" />
CMS-XML ZMF4ECL ZDDOPTS BUILD member issues
<options name ="BUILD" strict="Y"> ... <field name ="UserOption06" label="Load module type:" readonly="N" required="N" uppercase="Y" ... However, the customer feels that the displayed messages (e.g. ‘ZDDOPTS Profile: Name = UNNAMED Internal ID = 10 ... ’) could be misinterpreted by users as error messages.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs