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

• Related Articles

• 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: 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: The OSS lib added to version 3.60 of XCM can't be used to intercept USER_AUTHENTICATE_ call

  XCM v3.60 does not support restricting LOGONs from the OSS process, so XUA should be used.

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

• XOS: OSSGROUP does not appear to be providing correct privileges for OSS/POSIX directory or file

  This is not an XOS issue. This is a known issue where the HPE name server does not consult XOS for some OSS operations. HPE must resolve this before XOS OSS rules can work consistently for all POSIX operations. The workaround is to ensure that the ...