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 event logging done for both catalog and volser
event logging done for both catalog and volser
CMS-XML HFS Incorrect output for DETECT log after long file name event.
If you create a UNIX file which is greater than 44 characters which is HFS tracked in SSM when you make updates to this file and the updates are written to the DETECT LOG the update records get truncated and affect the next lines in the report for the VOLSER. See below example:
CMS-XML IDCAMS delete of tracked dataset not being reported as an Event.
Looking in the RTO, no events for the delete are logged . However, if you use IEBCOPY to generate the dataset back, you get SSM reporting that the IEBCOPY performed the delete which is wrong and misleading. See below:
CMS-XML Missing RELOCATE event for DFSMSdss (ADRDSSU).
This will run sucessfully and change the volume of the dataset. Looking at the DETECT LOG there is no reference of the RELOCATE. However if a CAPTURE is performed within SSM, then you get the following entry.
CMS-XML Change Tracking not recording event for PDSE data sets processed with IEBCOPY
IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE Detect log for following time: 2010/03/23 07:16:23 UBSTWS3C Del T096291 CMNDELRN STCMN01 LIB.CHGMAN.SERT.CCLIS
CMS-XML ChangeMan SSM ARCMDEXT Exit
What is the purpose of the ChangeMan SSM ARCMDEXT exit? The function of the ARCMDEXT exit is to call HPSIMIGR to log data set MIGRATE events such as HMIGRATE, HRECALL and HDELETE during Change Tracking. If SSM Change Tracking of MIGRATE events is not active, SSM will just return to the caller.
CMS-XML SSM823: Missed update to tracked library...
SSM V823 was running on 4 Plexes and whilst a GLOBAL capture was being performed updates for ADD and UPD where missed, but when GLOBAL processing came accross the dataset it logged the events as GLOBAL when it was really a real time event . Nothing unusual in the DETECT log.
CMS-XML Incorrect results for multiple LPAR updates to a PDSE in short time.
If you have a defined a new PDSE dataset to change tracking. Then subsequently create 4 members in this dataset. When editing 1 different member on each of 4 lpars around same time (<1 min) the results in event logging do not reflect the actual events per lpar.
CMS-XML Data reporting error within the RTO when a BACKUP has completed.
These are standard LOG message, so they have the timestamp of when the message was issued, which corresponds to when the events were processed. The SSM LOG is not meant to replace the Events Report, but to report on the activity of the started task. You have to run an Events Report or History Report to see when the events took place.
CMS-XML mail2exe failing with s0c4
BEGAN SCANNING RTCT NOTIFY LOG AT 10:23:32 2012/01/31 Event types which trigger notification:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs