The CA XCOM Data Transport CICS interface assigns a default security value of 01 to all CA XCOM Data Transport transactions. It is the CICS System Administrator's responsibility to assign the correct value to the CA XCOM Data Transport CICS interface transactions. Two transactions are defined in the sample definitions: XCOM and XCON.
Both transactions have exactly the same functionality. They differ based on the way that CA XCOM Data Transport was installed and the XCOMCNFG member was configured. If the CA XCOM Data Transport server was defined in the XCOMCNFG member as OPERSEC=NONE or OPERSEC=USER, then both transactions are identical.
When the CA XCOM Data Transport server is defined as OPERSEC=OPER, then the transactions can act differently, depending on the CICS configuration. The CA XCOM Data Transport CICS interface lets one transaction ID be defined as equivalent to the TSO OPER authorization mechanism, because CICS has nothing equivalent to it. The CA XCOM Data Transport CICS interface defines such a transaction ID using the OPER‑TRAN parameter of the XCOMDFLT configuration program.
For more information about CA XCOM Data Transport server OPERSEC security validation, see CA XCOM Data Transport CICS Operator Security in this chapter.
If one transaction is defined to CICS as having OPER capability (via the OPER‑TRAN parameter) and the other transaction does not have this capability as a default, then you can change the CICS security parameters to restrict access to the transaction that has OPER capability. The general user population can then access the standard CA XCOM Data Transport transaction.
| Copyright © 2012 CA. All rights reserved. |
|