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 compare of PDS members results in CSV026I HPSTRANS NO ACCESSED followed by CSV028I ABEND306-34 JOBNAME=M1GNW00 STEPNAME=
NAME=UNKNOWN DATA AT PSW 013A9758 - 8400181E 0 A 0 D18FB 180C181D AR/GR 0: 00000000/00001F00 1: 00000000/84306000
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 HPSTRANS duplicates results using the LIST=BASE parm.
//HPSIN DD * SETPRINT= DETAIL =YES BASE=GENERIC=(DSN=AAAAAA.SSM832.LOAD)
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 Detect and Sync Option S.A.2 generated JCL results in HPS0100W HPSTRANS 15:04:34 * Failure * Dynamic allocation of: /
===> Scroll ===> CSR ***************************** Top of Data ****************************** //DDELANOF JOB (X170,374),'CHANGEMAN SSM',NOTIFY=DDELANO,
CMS-XML HPSTRANS with missing DD statement results in RC=20
//*HPSIN DD * ******************************** BOTTOM OF DATA ******************************** SDSF OUTPUT DISPLAY T250963O J0386969 DSID 114 LINE 0 COLUMNS 02- 81
CMS-XML SSM822: MRX data display/processing problem on HPSMRMXU
Placing an "I" next to the "@*" member results in expected processing. HPSMRMXU Update Member Reference GLOBAL Exclusion List Row 1 of 32 Command ====> SCROLL===> CSR
CMS-XML SSM v832: Events look like they are being lost
HPS0108W OBJVIEW 18:07:44 1 events were lost from following history record. As a result of the messages above which give us no value the following diagnostic data is being seen: 811,064 bytes dumped at x'2032EFC8'
CMS-XML SSM823: Additional MRT (Member Reference Tracking) documentation notes
Performing the swaps on all LPARS will insure the latest information will be written to the AUX3 database. The only impact of not issuing the MRTSWAP command is that, the MRT data will not be as current as possible. You do need to worry about corruption from not running the swap at the same time on all LPAR's.
CMS-XML SSM830: HPS0104E message when attempting to define a Delta Tracked Object
0COMPLETION CODE SYSTEM = 0C4 REASON CODE = 00000010 PSW AT ENTRY TO ABEND 078D0000 87A3AF50 ILC 02 INTC 0079 0 PSW ADDRESS 01040746 AT TIME OF ERROR DOES NOT POINT TO AN ACTIVE MODULE
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

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

Additional Assistance

  • Submit a Case Online
  • FAQs