XCM: How to manually remove the XCM library name from an XCM library-installed object program file

• Related Articles

• XCM: XCM OSS library cannot be attached to an OSS Symbolic or a hard link file

  The XCM OSS library can only be attached if the target of the XCM OSS library is not a link. A possible workaround in a hard link; - Remove a hard link - Install the XCM OSS library - Reestablish a hard link

• XCM: XCM_REPORT macro not reporting on logon information known to be in the XCM audit trails

  1. The XCM libraries must be attached in order to report on this information. Attach the appropriate XCM libraries to the TACL object Syntax: XCM_LIB_INSTALL <object-file> <method> <library> Where: <method> 1 Attach as Runtime Library to specified ...

• 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 ...

• XCM: Supported $CMON Process (P08) version 3.36 Release Notes

  RELEASE WARNINGS! * Due to the current XCM design, when a program has a LIB attached, XCM might get two messages from the program. One that the program does natively and the other one from the attached library. XCM detects when a program sends the ...

• XMA: OSS path and file name from Safeguard audit not showing up in XMA database or on SIEM

  OSS commands, such as 'cat', generate an "open" operation for the OSS file on which they were executed. The Safeguard audit for "open" operations caused by 'cat' do not show the OSS path and file name in the ObjectName field of the Safeguard record. ...