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 SSM V832: Problem when executing 64-bit JAVA code when the RTO is running.
CEE3204S The system detected a protection exception (System Completion Code=0C4). From entry point JzosVM::spawnChild(const char*,const char**,int*,int*,int*) at compile unit offset +000000001C502A80 at entry offset +0000000000000240 at address 000000001C502A80.
CMS-XML SUPERUSER.FILESYS security messages in ChangeMan SSM started task
The following information from ChangeMan ZMF can be followed if your site wishes to eliminate the SUPERUSER.FILESYS messages, however this is not necessary for SSM since SSM does not use this function of SERNET. ---- from zmf Java -HFS guide ---------- Set ZMF User-ID Security for USS File Systems
CMS-XML SSM v832: HPS0100I: Dynamic Allocation error on DM/OM when running $INTEG
HPS0022I HPSINIT 17:10:55 Parmlib in effect: SYS5.????.PARMLIB(HPSPARMS) Security Userid : SSMSITE Exec parm = "TRACE"
With ACF2 security implemented, experiencing an S047 Abend in module HPSMAINT and HPSINTEG even though the SSM LOAD library is APF authorized.
CMS-XML OpenSSL Heartbleed Bug and impact on Serena products
A security flaw has been discovered in the popular OpenSSL cryptographic software library that is used by up to two thirds of the internet. There is no evidence that Serena or your data has been compromised in any way. More information about the security advisory is available at
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 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 HPSMAINT not calculating the AGING parameter correctly.
HPS0022I HPSINIT 01:26:49 Parmlib in effect: STRQA.SSM833T7.PARMLIB(HPSPARMS) Security Userid : SITADMN1 Execute parm = "AGING=5000"
CMS-XML SSM830: Note regarding conversion of SSM V8.2.3 Master Files to V8.3.0
it is important to the customer, to preserve any stored History of changes to these OBJECTS, and the customer is planning to use SAF security to control access to Change Tracking Administration in V8.3.0, then these OBJECTS must be defined to SAF-controlled Departments and Groups (with the CTCLASS and CTSITEADMIN parameters in effect in HPSPARMS), before bringing up the V8.3.0 system under the old TSO security method (SITEADMINS parameter in effect) and deleting them.
CMS-XML Minor spelling/spacing error in HPS0013E (Syntax Error 69).
HPS0022I HPSINIT 14:16:19 Parmlib in effect: SEXTON.DR83.PARMLIB(HPSPARMS) Security Userid : SSMSITE Execute parm = "PURGE=2000/01/01_24:00"
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs