Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
CMS-XML SSMMAIL getting connect failed RC= 61 reason= ECONNREFUSED Connection refused
SSMMAIL getting connect failed RC= 61 reason= ECONNREFUSED Connection refused
CMS-XML SSL 3.0 Vulnerability - Poodle - Serena Mainframe Products
A new security vulnerability called POODLE (Padding Oracle On Downgraded Legacy Encryption) is currently in the news. This is the result of a flaw in the SSL 3.0 protocol and the specific attack affects web communications.
CMS-XML Are Serena products affected by the OpenSSL Heartbleed Bug?
In response to the security flaw found in OpenSSL, known as the Heartbleed Bug (CVE-2014-0160), Serena has analyzed our software to determine if any are vulnerable to this bug. The nature of the bug is such that secure connections to a server are vulnerable to potential bleeding of somewhat random server memory into a response to a client. See for full details.
CMS-XML SSM830 In an z/OS 1.8 environment, an S0F4-24 Abend occurs due to a PDSE pgm object being left open, when system attempts to close the PDSE
In a z/OS 1.8 environment: On exit from ZMF, ISPF or SERXMLBC, job either gets an S0F4-24 abend, or an "IEC214I 614-14,IGG0201Y,..." message is seen. This is due to a connection to a PDSE program object being left open when the system attempts to close the PDSE.
CMS-XML SSM830: Using RACF groups, in place of TSO UserID's, for Change Tracking Access
(c) Grant RACF READ authority for one or more existing RACF User Groups and/or TSO Id's, to the appropriate Resource profile(s). 4. Establish a connection between any given SSM Change Tracking Group and the Resource Profile that will be used to control User access to it, in one of two ways:

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs