Installing
Db2 involves running the installation jobs,
connecting the facilities that allow TSO, batch, IMS, and CICS® to access Db2 resources, and preparing Db2 for use. After you complete the installation
steps, function level 500 or higher is activated and
available for use.
Before you begin
Before you begin installing Db2:
- Review the information about Db2 security with your system security
administrator, and plan and implement your Db2 security environment. See in particular Defining RACF user IDs for Db2-started tasks and Permitting RACF access, which can help you
plan your security environment even if you use an alternative security product. After initial
installation of Db2, subsequent
installation tasks and jobs require specific authorization in order to connect to Db2.
- If you plan to have data sharing enabled (Enable option on panel DSNTIPP1), you should save all
your jobs from the original installation or migration in a different data set than the enabling
jobs. If you save them in prefix.NEW.SDSNSAMP, the jobs might be
overwritten.
- Use Information/Access or the ServiceLink facility of IBMLink to check the most current information about Db2 and other products. If you do not have access to
IBMLink, contact IBM Support. For keyword specifications used
for Preventive Service Planning (PSP), see the Db2 Program Directory.
You must not use secondary authorization IDs to perform any of the following installation
steps.
Procedure
- Estimate storage needs for your Db2 12 environment. For more information, see Storage requirements for Db2 for z/OS.
- If you are using distributed data, install TCP⁄IP, VTAM, or both. For more information, see Connecting distributed database systems .
- If you plan to use data sharing, set up a Parallel Sysplex®. For more information, see Parallel Sysplex requirements for Db2 data sharing.
- Use SMP/E to load the Db2 12 libraries. For more information, see Making the Db2 product code available.
Remember: If you copy
Db2 library data sets from one system another, such as for installing a related test or production subsystem, ensure that you copy all of the
Db2 library data sets to the same location. For example, if you copy the SDNSLOAD data set from one system to another but omit the DBRMLIB data set, the resulting mismatch can cause job DSNTIJRT to fail with SQLCODE -812.
If you plan to use the callable SQL interface of Db2, see Configuring Db2 ODBC and running sample applications for the additional installation jobs that you need to run. If you plan to use Db2 for z/OS Java™ Edition, you must run more installation jobs. For more information, see Installing the IBM® Data Server Driver for JDBC and SQLJ.
-
Provide an SMS
environment for managing Db2 catalog and
directory data sets.
The SMS environment must include a data class for allocating the
data sets in extended format and using extended addressability. You are not required to convert
existing
Db2 catalog and directory data
sets to the SMS environment before migrating to
Db2 12. These data sets will be converted the next
time the related table space is reorganized. For information on using sample job DSNTIJSS to define
an SMS environment for data sets that are associated with the
Db2 catalog and directory, see
Installation step 1: Define the SMS environment for Db2 catalog and directory data sets: DSNTIJSS.
- Generate tailored JCL jobs for installing Db2 12. For more information, see Generating tailored Db2 12 installation, migration, or function level activation jobs.
- Edit and run the jobs that install your Db2
Db2 12 subsystem by completing the following
tasks:
- Installation step 1: Define the SMS environment for Db2 catalog and directory data sets: DSNTIJSS
- Installation step 2: Define Db2 to IRLM and MVS: DSNTIJMV
- Installation step 3: Define Db2 address space startup procedures, language procedures, and the Java WLM environment: DSNTIJMA, DSNTIJMW, DSNTIJMP, DSNTIJMJ
- Installation step 4: Define the ICF catalog and alias: DSNTIJCA (optional)
- Installation step 5: Define system data sets: DSNTIJIN
- Installation step 6: Define Db2 initialization parameters: DSNTIJUZ, DSNTIJUA, DSNTIJUM, and DSNTIJUL
- Installation step 7: Initialize system data sets: DSNTIJID, DSNTIJIE, and DSNTIJIF
- Installation step 8: Define user authorization exit routines: DSNTIJEX (optional)
- Installation step 9: Record Db2 data to SMF (optional)
- Installation step 10: Establish subsystem security (optional)
- Installation step 11: Connect Db2 to TSO
- Installation step 12: Connect Db2 to IMS (optional)
- Installation step 13: Connect CICS to Db2 (optional)
- Installation step 14: Define Db2 to z/OS
- Installation step 15: Start the Db2 subsystem
- Installation step 16: Tailor the Db2 catalog: DSNTIJTC
- Installation step 17: Activate Db2 12 function levels: DSNTIJAF (optional)
- Installation step 18: Create default storage group, define temporary work files, and bind Db2 REXX Language Support: DSNTIJTM
- Installation step 19: Define and bind Db2 objects: DSNTIJSG
- Installation step 20: Populate the user-maintained databases (optional)
- Installation step 21: Configure Db2 for running stored procedures and user-defined functions
- Installation step 22: Set up Db2-supplied routines
- Installation step 23: Back up the Db2 directory and catalog: DSNTIJIC
- Installation step 24: Set up the administrative task scheduler
- Installation step 25: Verify successful installation of Db2 12
- Enable more capabilities in your Db2 environment. For more information, see Configuring additional capabilities for Db2 for z/OS.
What to do next
You might want to activate new capabilities that are introduced by higher
Db2 12 function levels. For more information about continuous delivery and function levels in
Db2 12, see the following topics: