Implementing Security for CA Roscoe › Install the CA Roscoe Interface

Install the CA Roscoe Interface

Important! Before installing the CA Roscoe interface, check the CA Roscoe Security Administration Guide to determine your security needs based on what types of security CA Roscoe offers in addition to the security provided by CA Top Secret.

CA Roscoe CA Top Secret support modules interface with, or replace, CA Roscoe user or security exits. Module TSSRXBEX must be link‑edited with CA Roscoe programs LIBSERVE, ROSCOPY, ROSDATA, and LIBUTIL.

Note: For CA Roscoe r6.0 and above, you should not install CA Top Secret‑supplied ACFEXIT and OUTEXIT modules. You should instead allow security to be handled through the (SAF) jesspool calls for the OUTEXIT. CA Top Secret protects these functions and provides a higher level of granularity of control.

• Certain exits are required in certain situations. The exits and when they are required are listed below.
• Sites that have defined LCF rules for protecting CA Roscoe commands and monitors must install the CMDEXIT. This exit is also required if sites wish to implement the CA Top Secret automatic terminal lock facility instead of the terminal locking facility provided by CA Roscoe.
• Sites that wish to receive the CA Top Secret security messages for data set access, rather than CA Roscoe messages, must implement DSAEXIT.

The JCL for the installation of the CA Top Secret/CA Roscoe interface resides in File 17 (TSSROSCO) of the distribution tape. There are two members:

INSTALL1

Copies exits and TSSSIM modules to the CA Roscoe loadlib and links TSSRXBEX with CA‑Roscoe, ROSCOPY, ROSDATA, LIBSERVE, and LIBUTIL.

INSTALL2

Installs CMDEXIT, SUBEXIT, or ACFEXIT if user‑written code is combined with CA Top Secret‑supplied code.