Setting the location of the tenant definitions

Set the location of the tenant definitions.

Before you begin

Setting the location of the tenant definitions requires the use of override embed members. For more information about using override embed members, see the following topics:

Using Configuration Manager: Using override embed members
Using PARMGEN: Override embed members, Customizing the override embed members

About this task

The customer, group, and user definitions for the tenant can exist in either PDS members or an external security system, such as RACF. It is recommended that you test your tenant definitions using PDS members and then, when satisfied, transfer the definitions to an external security system.

You control the location of the tenant definitions to use with the following override embed parameters:

MULTI_TENANCY_DEFS

Specifies the location of the tenant definitions to use. Valid values are as follows:

PDS: (Default) Definitions are in PDS members located in the data set specified in the DD statement named in the MULTI_TENANCY_DDNAME parameter.
SAF: Definitions are made using the System Authorization Facility (SAF) interface for use with an external security system, such as RACF.

MULTI_TENANCY_DDNAME

Specifies the DD name of the data set containing the tenant definitions when defined in PDS members. The default value is RKOBPROF, which uses the UKOBDATF data set.

These parameters are defined in override embed member KOB$PENV. Following a standard override embed procedure places the parameters into member RKANPARU(KOBENV) for Configuration Manager or WCONFIG(KOBENV) for PARMGEN.

Use the following steps to set the location of the tenant definitions to use.

Procedure

Using Configuration Manager:
1. Locate your embeds data set. If you do not have an embeds data set, you must enable override embed members for your runtime environment by running a CREATE action with KFJ_USE_EMBEDS set to Y. For more information, see Enable override embed members for an existing RTE.
2. In the override embed member KOB$PENV in the embeds data set, specify the location of the tenant definitions as follows:
  - To use tenant definitions in PDS members, include the following statement:
```
MULTI_TENANCY_DEFS=PDS
```
    You can also use a DD name other than the default value of RKOBPROF by including the following statement:
```
MULTI_TENANCY_DDNAME=<ddname>
```
  - To use tenant definitions in an external security system, such as RACF, include the following statement:
```
MULTI_TENANCY_DEFS=SAF
```
3. Run the GENERATE action.
Using PARMGEN:
1. Update the override embed member KOB$PENV, as follows:
  1. From the Workflow - Primary Option Menu, select option 2, Customize PARMGEN configuration profiles.
    The Customize PARMGEN Configuration Profile Members (KCIP@PG6) panel is displayed.
  2. Select WCONFIG.
  3. Select and edit the KOB$PENV member.
  4. Specify the location of the tenant definitions, as follows:
    To use tenant definitions in PDS members, include the following statement:
    MULTI_TENANCY_DEFS=PDS
    You can also use a DD name other than the default value of RKOBPROF for the location of the PDS members by including the following statement:
    MULTI_TENANCY_DDNAME=<ddname>
    To use tenant definitions in an external security system, such as RACF, include the following statement:
    MULTI_TENANCY_DEFS=SAF
  5. Save the changes and return to the Workflow - Primary Options Menu panel.
2. Regenerate the runtime members and jobs, as follows:
  1. Select Create the RTE members and jobs.
    The $PARSE/$PARSESV: Create the RTE Members and Jobs (KCIP@PR1) panel is displayed.
  2. Select option 1 to submit the $PARSE job (or the $PARSESV job, if variables are enabled).
  3. Return to the Workflow - Primary Options Menu panel.
3. Copy the runtime members from the work libraries to the production libraries, as follows:
  1. Select Submit batch jobs to complete PARMGEN setup from the menu.
    The Submit Batch Jobs To Complete PARMGEN Setup (KCIP@SUB) panel is displayed.
  2. Optional: Select option 11 and submit the KCIJPCPR job to back up the production libraries.
  3. Select option 12 and submit the KCIJPW2R job (or the KCIJPW1R job) to copy the work libraries to the production libraries.