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  
Pages [Next]
CMS-XML SSM823: Problems with not receiving E-mail notifications
Note: We have found that some mail servers require brackets around the email address "<>". This is noted with a message similar to below:
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 SSMMAIL getting connect failed RC= 61 reason= ECONNREFUSED Connection refused
SSMMAIL notification fails sending sending to an SMTP server . The SSMMAIL task is getting the following error message as seen below:
CMS-XML Mainframe Websphere abend with SSM active
Websphere applicate server has been abending since starting the SSMSTAR STC on the two LPAR's on which ssm is running. ChangeMan SSM was stopped which allowed WEBSPHERE to run successfully. Does SSM have problems running with Mainframe Websphere?
CMS-XML SSM830: Minor panel change HPSHTF59 DRM -> SSM
ChangeMan SSM, 8.3.0 DETAILS: Change help panel example to use SSM instead of DRM as a node name.
CMS-XML S0C4 encountered in global capture after start of the STC
05.06.33 S0373859 Initialization of ChangeMan SSM RTO in progress. 05.06.35 S0373859 SER0810I SerNet server " initialized and ready for communications 05.06.35 S0373859 SER0824I Attempting to load PAN#1 to determine if feature present; Please ignore any associated CSV003I message.
CMS-XML SSM notifications and the use of translation tables.
> CALL 0 46 ChangeMan SSM RTCT Member Event Notification > CALL 0 19 HOST : AAAA.ZZZ.BB > CALL 32 EPIPE Broken pipe
CMS-XML Web Browser complains the SSL certificate has expired, even though the expiration date is in the future.
The certificate shown by the browsers is that of the server itself, but it validated the entire certificate chain. If the server certificate is valid, check the rest of the chain to ensure the root certificate, and any intermediate one(s), have not expired either.
CMS-XML SSM831 Message HPS0103E when running the $ADMSET installation job.
This is an indication of the following: 'B6' error code (OPEN) - RLS specified in the HPSPARMS member, but SMSVSAM server is not available. Development provided this helpful link information to assist with questions regarding VSAM return codes.
MS-EXCEL SSM_8.3.2_Supported_Platform_Matrix.xls
The "Hdwr" worksheet describes which processor versions are supported on which operating systems for each release. The " Server OS" worksheet describes the Server operating systems are supported on a per release basis The "Client OS" worksheet describes the Client operating systems are supported on a per release basis
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs