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: Getting 16D Abend, and message ISPC506E: Error File SSMHFSK not found or was empty.
However it is the suggestion which is entirely self contained within the product software (i.e. our ability to influence/control/manage implementation). And, the addition of another library allocation and subsequent deployment related to the SSM product implementation is a trivial additional bullet point item task within any future product rollout plans. I should like to pursue this approach concurrent with the other implementation design changes already bundled for implementation within the anticipated rollout of SSM v832.
CMS-XML Product Lifecycle and Platform Matrix
The Supported Platform Matrix outlines the product releases with their supported client-side and server-side information , including supported operating systems, browser, third party plugins, product integrations, character sets, and upgrade paths . To navigate to this page:
CMS-XML SSM830: When SSM STC is activated CA-Endevor product getting S913 abends.
PRODUCT: ChangeMan SSM, 8.3.0 DETAILS :
CMS-XML SSL 3.0 Vulnerability - Poodle - Serena Mainframe Products
For a detailed write-up of the POODLE vulnerability, refer to
CMS-XML XML License Installation Quick Start for Mainframe Products
If you downloaded the .XML library to a permanent PDS you can point JCL to this PDS. If the .XML download library is temporary, you can to copy the NAMES member from the temporary library to the newly created license file - there is no need to create a separate, permanent .XML
CMS-XML SSM823: Need information regarding implementing MLS w/ACF2
CMS-XML SSM823: Event information needs to be consistent
PRODUCT : ChangeMan SSM, 8.3.0 DETAILS:
CMS-XML HPS0100I HPSTRANS Dynamic allocation SVC99 error field = x'0218' info = x'0000
CMS-XML SSM v832 DELTA restore of a specific module results in a non executable module
A customer has discovered that the DELTA tracking recovery of modules is not always successful. In a test case scenario detailed below, the recovery of a DELTA=Y defined dataset's module - SERCOPY from the Comparex product libraries results in a non executable module. If this happens with one it is potentially possible that it could happen with any other vendor's module's and may occur when a module is recovered when trying to recover from a critical problem.
CMS-XML Questions on XML licensing and CSA
1) If a product using XML licensing encounters invalid license information , does it immediately fail or does it continue and try the alternatives? For
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Delivering changes from a work area to a stream (demonstration)
This demonstration shows you how to deliver changes from a work area to a stream in Dimensions CM, restrict the deliver to specific folders in the work area, and relate a new item to the correct design part.
Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes
Dimensions CM: Resolving conflicts (demonstration)
This demonstration shows you how to resolve conflicts between your work area files and the item tip revisions in a stream in Dimensions CM

Additional Assistance

  • Submit a Case Online
  • FAQs