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 Inaccurate message HPS1484I being issued during DEFINEDS of uncataloged test file
Inaccurate message HPS1484I being issued during DEFINEDS of uncataloged test file
CMS-XML Disaster Recovery Keys for Mainframe Products
In the event of a real Disaster Recovery scenario or a planned Disaster Recovery test , you will need to request license keys to run your Micro Focus mainframe products on the Disaster Recovery CPU.
CMS-XML HPS0104E : HPSMAINT Get Failure on SM Program return code = 0104
Testing ZMF v8.1.0 and when running HPSMAINT it failswith the following: HPS0104E HPSINTEG
CMS-XML ChangeMan SSM compatibility with z/OS 1.10
At this time, we do not anticipate any issues with SSM V8.3.2 and z/OS 1.10; however, we will thoroughly test the current releases of SSM once z/OS 1.10 is installed at Serena. If any issues are identified, they will be announced and resolved immediately.
CMS-XML SSM RTO incorrectly identifies LPA modules as not being in LPA.
This is intermittent issue. Sometimes after an IPL when the LPA modules are loaded into LPA, one of the modules will get an address which does not match the SSM test for being in LPA.
CMS-XML SSM v832: Global Capture Stopped via unexplained SHUTDOWN.
While performing some Change Tracking testing , I observed something inexplicable within one of our SSM v832 STCs.
CMS-XML HPS1322E HPSTRACK does not support Length=44 objects.
Testing HPSMAINT, we have noticed an object name "collision" with VOLSER within the output for objects (DSNs) with length = 44. See below example:
CMS-XML HPSMAINT not honoring combination of parameters
$MAINT processing is either not properly honoring a combination of processing parameter specifications. The intended test was as follows: 1) Given the existing, historical database ("full" of a wide variety of versions from up to 800 days),
TEXT DEF244314.hf1.installinstr.txt
Following are installation instructions: 1) Save the attachment to disk 2) File transwer it to MVS as a binary file. The receiving file should be RECFM=FB,LRECL=80,BLKSIZE=multipleof80 3) Issue TSO RECEIVE INDS(yourtransferredfile) against the transferred file on MVS 4) RECEIVE will ask you for further parameters, if you just hit enter (null reply) it will allocate a dataset As with any hotfix, please install in a TEST SSM environment before placing it in the SSM prod instance.
CMS-XML SSM conflicts with ENDEVOR third party software resultin in U1314 abend
SSM 8.3.4 is running with RTO option activated. When testing Endevor R15 processes, the batch processes abend with U1314 error code when SSM is active.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs