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 SSM832: Incorrect (truncated) TOTALs within MRT Report
be released shortly, and made available in a solution . Resolution Update – 07/15/2009:
CMS-XML SSM830: SHOW=MLS Report missing TSO or SAF mode descriptions
The solution is, when in SAF mode in 8.3, to go into the ISPF option A.5.4 and overtype the MLS definitions that are marked TSO but which really have a SAF profile. When the entries are updated, they will be converted to SAF mode.
CMS-XML SSM832 16D Abend accessing the SSM ISPF facility - avoidance solution.
SSM832 16D Abend accessing the SSM ISPF facility - avoidance solution .
CMS-XML ChangeMan SSM compatibility with z/OS 1.10
For specific solutions documenting z/OS 1.10 reported issues, perform a search of our knowledge base. Any new features in the operating system will be scheduled for exploitation in later versions.
CMS-XML SSM832 Beta Patch Package Number: SSM83201
This Solution was
CMS-XML When upgrading SSM from releases prior to V8.3.0, it is important to review the SSM V8.2.x README Documents
This solution contains all the SSM V8.2.x README documents, for review, when upgrading from an SSM release prior to SSM V8.3.x..
CMS-XML RTO hangs when the HPS0051E is issued.
1) The HPS0051E message is insufficiently documented. Surely some "Explanation" and/or " Solution " is possible to include within the Messages PDF when the database is either not found -- misspelled -- and/or otherwise unavailable -- in use.
CMS-XML HPS0607E I/0 read failure
Install hotfix available in solution S140902
CMS-XML SSM832: Unable to delete existing MRT history for member DELETE MEMBER=$UNCEXIT
Resolution from Research and Development: This fix will be part of a cumulative patch package for SSM V8.3.2, scheduled to be released shortly, and made available in a solution . Resolution Update – 07/15/2009:
CMS-XML SSMMAIL getting connect failed RC= 61 reason= ECONNREFUSED Connection refused
Solution : A TCPSMPD Daemon (server) was down on the LPARS where the task was failing. To test, change SMTPSERVER= parm in MAIL4NFY value to an IP address were it works.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs