3 – Adjust Connector for RACF parameters

Perform the customization steps described below on the target system.

Note
As an alternative to steps 3A and 3B below, you can use utility CTSAADPT to rename the Managed System on the target system. For more information, see Renaming a Managed System.

3A – RSSPARM Parameters

Edit member RSSPARM member in the Connector PARM library.

The RSSPARM member contains the Managed System parameters for the installed Managed System.

Each line is in the format:

<Managed System-name> <parameter_name> <parameter_value>

where <Managed System-name> is either ALL_RSS or the Managed System name specified during installation.

If the Managed System name defined in SailPoint for the target system is different from the one specified in the member RSSPARM, you must update member RSSPARM to reflect that difference.

To perform the required update in member RSSPARM, change the <Managed System-name> value on all lines that specify the source system Managed System name to the new Managed System name that is correct for the target system.

In addition, the Managed System name qualifier in the value specified for parameter RSS_WORK_DIR must be modified.

Note
The Managed System name specified in the RSSPARM parameters file must match the name defined in SailPoint for the target system. If the names do not match, SailPoint will not be able to connect to Connector for RACF.

3B – RSSAPI Parameters

Edit member RSSAPI member in Connector PARM library.

RSSAPI member contains the script activation definitions for the Managed System.

Each line is in the format:

RSS_type RSS_name additional_parameters

where:

  • RSS_type – hyphen (-)

  • RSS_name – Managed System name specified during installation.
    Default: MVSRACF

The complete syntax of this member is described under Structure of the RSSAPI Member.

If the Managed System name defined in SailPoint for the target system is different from the one specified in member RSSAPI, you must update member RSSAPI to reflect that difference.

To perform the required update in member RSSAPI, change the RSS_name parameter on all the lines containing the source system Managed System name to the new Managed System name that is correct for the target system.

3C – Adjust Procedures

If the Managed System name was changed, modify the RSS= parameter in each of the following procedures:

  • CTSAADPT

  • CTSADFR

  • CTSAOFI

  • CTSOFLI

  • CTSAOFS

  • CTSAONI

  • CTSC100

3D – Allocate Connector for RACF Work Datasets

The datasets listed below are created during Connector for RACF installation. These datasets should not be copied from the source system to the target system. Instead, they should be allocated and formatted directly on the target system.

Originally, allocation of these datasets was performed by job FORMCTS, which is run in installation step Step 8 – Format Connector for RACF Datasets.

You may run job FORMCTS in the Connector INSTALL Library to allocate the datasets on the target system.

<o_prefix>.<o_version>.CARECNN

<o_prefix>.<o_version>.CAREGRP

<o_prefix>.<o_version>.CAREUSR

<o_prefix>.<o_version>.DIAGLVL

<o_prefix>.<o_version>.QUEUE

<o_prefix>.<o_version>.RCFDELRQ

<o_prefix>.<o_version>.RSSKWDS

<o_prefix>.<o_version>.RSSOFLI

<o_prefix>.<o_version>.ENCRINT

<o_prefix>.<o_version>.ENCREXT

3E – Encryption Datasets

The following datasets are used during the operation of Connector for RACF and must be copied from the source system to the target system:

<o_prefix>.<o_version>.ENCREXT

<o_prefix>.<o_version>.ENCRINT

These datasets are allocated in step 3D – Allocate Connector for RACF work datasets and must be overwritten in this step.