Installation customization process

Installation customization process allows you to provide setup and configuration information to create a customized installation environment for a source server, a target server, or both.

This process involves a set of steps that you perform after completing the mainframe SMP/E installation. You provide setup and configuration information that is used to generate all sample JCL and configuration members in the USERHLQ.USERSAMP data set that requires edit. You then run installation customization jobs that are generated based on the parameters that you specify to create a customized installation environment.

The installation customization process is based on the role of the Classic data server. The possible roles for a Classic data server for Data Replication for IMS are the source server or the target server. You can customize an installation environment for a source server, a target server, or both a source and a target server. You specify the role of a Classic data server with the SERVERROLE parameter for the installation customization utilities. This parameter controls the installation components that you customize. You create installation data sets (USERHLQ.USERSAMP and USERHLQ.USERCONF) that contain the required components for the type of installation that you choose, and you customize only the parameters that are needed for that environment.

You can set up one or more Classic data servers on the same LPAR. When you complete the installation customization process, an operational environment is established that you can build upon as needed. The environment includes a functional Classic data server and all the required services for the specified role. All services are pre-configured during the customization process.

When setting up an active/standby or active/active environment, you can capture or replicate changes bi-directionally. Separate source and target servers (that runs on each LPAR) must be created. In these environments, perform the installation or customization process twice, specifying the role of the source and then target. These independent environments and cannot share any resources between the source and target servers (for instance, configuration dataset, diagnostic or event log streams, or TCP/IP ports). Each server must have its own set of USERSAMP and USERCONF datasets.

Overview of installation customization procedure

The installation customization process consists of these steps:
  1. The user samples allocation utility creates a working set of the SCACSAMP and SCACCONF data sets that contain all customized JCL and configuration members. This working set is referred to as the USERHLQ.USERSAMP and USERHLQ.USERCONF data sets.
  2. You gather site-specific configuration information that is needed to customize the environment and enter that information in the customization parameters file.
  3. The installation customization utility generates customized JCL and configuration members and stores them in the USERHLQ.USERSAMP and USERHLQ.USERCONF data sets that were created in the first step.
  4. You allocate and initialize the following components by using generated customization jobs:
    • z/OS® log streams
    • Configuration files
    • Data sets to store your subscriptions and replication mappings
  5. You use the generated JCL and configuration members to start the runtime environment.

Installation customization components

The following table lists the components and sample JCL members that you use during the installation customization process.
Table 1. Summary of installation customization components distributed in the SCACSAMP data set.
Component name Description
User samples allocation utility Allocates the USERHLQ.USERSAMP and USERHLQ.USERCONF data sets. Populates the USERHLQ.USERSAMP data set with a copy of the customization parameters file (CECCUSPI) and the installation customization utility JCL (CECCUSI2). The SCACSAMP(CECCUSI1) JCL runs this utility.

SCACSAMP(CECCUSI1) is the JCL that runs the user samples allocation utility. CECCUSI1 is the only member in the distributed SCACSAMP data set that you edit. The JCL comments provide editing instructions.
Installation customization utility Reads the customization parameters file USERHLQ.USERSAMP(CECCUSPI) and generates the necessary JCL and configuration members in the USERHLQ.USERSAMP and USERHLQ.USERCONF partitioned data sets. The USERHLQ.USERSAMP(CECCUSI2) JCL runs this utility.

USERHLQ.USERSAMP(CECCUSI2) is the generated JCL that submits the installation customization utility and generates all necessary JCL and configuration members.

Customization parameters file Contains the installation and customization information that you specify in the form of parameter and value pairs to complete an installation and establish an initial functioning environment. This file is located in USERHLQ.USERSAMP(CECCUSPI).
The following components are specific to the server role for source or target server.
USERHLQ.USERSAMP(CECISSLS) Generated JCL that runs the Administrative Data Utility (IXCMIAPU) to define the z/OS event log stream and a log stream for the diagnostic log for the source server.
USERHLQ.USERSAMP(CECITSLS) Generated JCL that runs the Administrative Data Utility (IXCMIAPU) to define the z/OS event log stream and a log stream for the diagnostic log for the target server.
USERHLQ.USERSAMP(CECISCFG) Generated JCL that allocates and initializes the configuration files for the source server.
USERHLQ.USERSAMP(CECITCFG) Generated JCL that allocates and initializes the configuration files for the target server.
USERHLQ.USERSAMP(CECISSUB) Generated JCL that allocates and initializes the VSAM data sets for the source server that store metadata for subscriptions and replication mappings.
USERHLQ.USERSAMP(CECITSUB) Generated JCL that allocates and initializes the VSAM data sets for the target server that store metadata for subscriptions and replication mappings.
USERHLQ.USERSAMP(CECIMSSC) Generated JCL to start the source server.
USERHLQ.USERSAMP(CECIMSTG) Generated JCL to start the target server.