XCM: Large Amounts of XYGATECM Audit
Large amounts of XYGATECM (XCM) audit does not necessarily indicate a problem with XCM, but is symptomatic of activity elsewhere on the NonStop system that is being audited by XCM.
An XCM report should provide clues on system activity contributing to the excessive audit.
1. RUN $<vol>.XYGATECM.XCM INSTALL ($<vol> is the disk volume where XCM is installed
2. XCM_REPORT
3. Option B, to set the reporting date/time range
4. If an XCM audit file other than the current one is desired, it can be selected using Option A, Audit File, otherwise the current audit file will be the default.
5. Option 5, Sort Order to change the sorting order. The default is USER
6. Z or ZP to run the report
The Result Count Summary totals on the last page of the report will show record counts for the following:
- Failed Actions
- Successful Actions
- Ignored Actions
- Duplicate Records
- Total number of records processed
Depending on the sort option selected, the detail records in the report will show the requestor (program), the action (e.g. LOGON, RUN, STOP, etc.), time and date and the user id performing the given action. While the XCM audit does not show specifically what may be occurring on a NonStop system to generate the audit, the data can be useful in directing the user to an application or activity that is the cause of the excessive XCM audit.
The frequency of the audit file rollovers may indicate that they are too small and need to be re-sized. This is done by changing the default extent sizes in the CMCONF file configured for the audit file specified with the AUDIT keyword. Please see Chapter 11, Auditing in the XYGATE Supported $CMON Process (XCM) manual for more information on XCM auditing.
If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.