XCM: The OSS lib added to version 3.60 of XCM can't be used to intercept USER_AUTHENTICATE_ call

• Related Articles

• 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: 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: How to manually remove the XCM library name from an XCM library-installed object program file

  If the XCMBIND file or XCM##### file containing the backout information used by the XCM_LIB_UNINSTALL macro is unavailable, the commands below can be used to manually remove the XCM library name from an XCM library-installed object program file. If ...

• XCM: CMON Process (P08) version 3.35 release notes.

  RELEASE WARNINGS! * If XYGATE Merged Audit is used to report on security events from the XCM audit trail, your XMA installations must be upgraded to Version 1.95 or higher in order to support XCM 3.35. Steps: 1. Make sure to upgrade to XMA 1.95 or ...

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