Installing on z/OS

Use this procedure if you are installing with IBM® DB2® for z/OS®.

Before you begin

Make sure that you meet these prerequisites:

You added the InfoSphere® MDM offering to IBM Installation Manager.
You completed the preparation tasks for creating the database and application server.
You completed the Preparing an existing WebSphere Application Server messaging bus for InfoSphere MDM installation on z/OS.
The IBM WebSphere Application Server (deployment manager and node) and database are started.

Note: In DB2 for z/OS, the MDM database tables are distributed across thirteen databases to help ensure better performance and to balance the bufferpool workload by feature. For example, all tables for production are inside the PROD database, all tables for EventManager are inside the EMGR database, and so on. This partitioning strategy is used in DB2 for z/OS for all out-of-the box DDLs. You can redistribute the tables according your organization's internal policies.

Tip: Maintain a good bufferpool distribution to avoid congestion, deadlocks, and timeouts.

About this task

The installation process on DB2 for z/OS requires two distinct sessions. In the first session, you extract and run the JCLs that are used to manually install the physical MDM database.

After the physical database load is complete, the second installation session installs the virtual part of the MDM database, the operational server, and any other features you select.

The installation uses a three character prefix (db_prefix). This prefix must match the last three characters of the schema name or database user ID (assuming the schema and user ID are the same). <db_prefix>ZMDS is the virtual MDM database.

Procedure

Ensure that the user ID that you are using to run the installation has the correct privileges.
1. Ensure that the user has rights to the MDM database.
2. Grant BINDADD privileges on the database to the user.
```
GRANT BINDADD TO db_user
```
3. Grant CREATETAB privileges on the database to the user.
```
GRANT CREATE ON COLLECTION * TO db_user
```
  Note: The db_user user name is used in the InfoSphere MDM JCL and DDL scripts as the schema name to create all MDM tables. The user account is granted USE OF TABLESPACE and CREATETAB privileges for all MDM databases in the DDL scripts.

For the first session, extract and run the physical MDM JCLs. Extract the Installation Startup Kit to extract the InfoSphere MDM DB2 for z/OS assets to the STARTUPKIT_INSTALL_HOME directory.

Navigate to the directory where you have saved the downloaded InfoSphere MDM packages.
Open disk1.zip and extract the subfolder StartUpToolkit to a directory of your choice. We will refer to this directory location as STARTUPKIT_INSTALL_HOME.
Go to STARTUPKIT_INSTALL_HOME.
Copy the MDM Operational Server z/OS assets from the STARTUPKIT_INSTALL_HOME/CoreData/Full/DB2/ZOS/pds and STARTUPKIT_INSTALL_HOME/Full/DB2/ZOS/pds directories to the z/OS system.

For the second session, install the MDM Operational Server and other features:

Start IBM Installation Manager and click Install on the home panel.
On the Install Packages panel, select the edition and click Next.
Continue through the prompts to accept the license agreement, select an installation location, and select a language.
Attention: If you have IBM Rational® Application Developer installed, make sure that you do not install InfoSphere MDM into the same package group. On the Install Packages panel, select Create a new package group.
Select the MDM Operational Server, MDM Database, and any other features you want to install.
Enter the configuration information:
- On the database configuration panel, select DB2 for z/OS and provide the database details.
- For IBM WebSphere Application Server configuration, make sure that you enter the information that you used during application server preparation. Use the mdmadmin user and password. Click Verify MDM Instance on Server before you exist the panel.
- On the Messaging Server panel, select IBM WebSphere Default Messaging or MQ Messaging Provider. For information about manually installing SIB tables on WebSphere Application Server, see the Creating data store tables topic in the WebSphere Application Server online documentation.
Review the installation summary information to ensure that the details are accurate, then click Verify Installation Requirements to run the prerequisite checks.
The checks will help to ensure that your environment and configuration is sufficient to successfully complete the installation.
Take corrective action to address any warnings or errors in the prerequisite checks, then click Install.
On the final IBM Installation Manager panel, click View Log Files if you want to open the log file viewer.
Click Finish and close IBM Installation Manager.
From a command line, navigate to MDM_INSTALL_HOME/mds/scripts and run the following command to open the installation configuration tool:
- On Microsoft Windows operating systems:
```
madconfig Configure_MasterDataManagement
```
- On Linux or UNIX based operating systems:
```
./madconfig.sh Configure_MasterDataManagement
```
Provide the details of your deployment as prompted by the installation configuration tool.
The configuration tool will complete the configuration of your installation.

What to do next

A success message on the final installer panel indicates that the verification tests were automatically run as part of the installation process. You can also view the log files to verify a successful installation. If the installation is not successful, view the log files and use the information in the troubleshooting topics to assist you.