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 HPS0702W Msg. generated during Fingerprinting when DSCB1 does not match the dataset information provided.
HPS0702W Msg. generated during Fingerprinting when DSCB1 does not match the dataset information provided.
CMS-XML SSM823: GLOBAL processing looping when no data sets defined to change tracking
ChangeMan SSM, 8.2.3 DETAILS : According to the screenshot below, Global Capture is "looping" (or at least continuously outputting "in progress" status update messages) where no objects are (yet) defined to the database.
CMS-XML SSM823: GLOBAL processing looping when no data sets defined to change tracking
ChangeMan SSM, 8.2.3 DETAILS : GLOBAL processing seems to be looping when there are not data sets (objects) defined to change tracking.
CMS-XML Unable to REPRO MASTER datasets whilst SSM 834 RTO is running on SYSPLEX.
Customer is performing housekeeping and they suffer the following messages IEC161I 006-027 opening the OBJECT MASTER with PGM=IDCAMS to REPRO the OBJECT Master whilst the STC are up and running. A more detailed explanation is printed out in the SYSPRINT of REPRO command: REPRO INFILE(INDD) -
CMS-XML RACF and Conversion of SSM V8.2.3 to V8.3.2. Additional Detail
SSM V8.2.3 system uses tsoid's. Customers can continue to use the same authorities with the 8.3.2 (converted) system. They can also keep their SITEADMINS spec in HPSPARMS if they wish - no changes needed. The system will continue to function much as it did in V8.2.3.
CMS-XML Event Type Line Command is not reset upon HPSUHEV1.
It has been identified that there is a ISF panel processing problem, after use/function completion, and even after the function is exited (even all the way back to the main/primary SSM ISPF options menu), the user's previous (Event Type) "S"election is retained/saved upon subsequent displays of HPSUHEV1. See below details :
CMS-XML SSM832: Unable to delete existing MRT history for member DELETE MEMBER=$UNCEXIT
We have *not* tested this against *any* other special characters, but request and rely upon Serena to already be considering such possible additional conditions. From the detail provided: 1) definition records for the $-named component exist.
CMS-XML NEWMEM\NEWNAME cannot be abbreviated in the RECOVER command.
Taking the information from (page 96 of the latest v833 version of) the Change Tracking PDF, which states: Command Structure The general format for the batch commands in ChangeMan SSM is as follows:
CMS-XML Wrong message HPS1307E issued for HFS Group with no INCLOBJ parm.
When running HPSTRACK to get the EVENTS information for a HFS Group when you specify the command with no INCLOBJ= parm the message issued is not representative of that the parm INCLOBJ is missing. See below recreation and example:
CMS-XML Basket IMPORT APPLY does not write all IEBCOPY messages to SYSPRINT data set
During an APPLY, ALL the IEBCOPY information is not written to the SYSPRINT DD temporary data set. However, the complete IEBCOPY informations shows up in the SYSOUT if it is sent to SYSOUT.
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