Migrating the first member of a group to Db2 13

You must first complete the migration of one member of the data sharing group to Db2 13 before starting any other members at Db2 13. You may choose any member as the first member to migrate to the new release.

About this task

The DB2I CLISTs are edited when the first member of a data sharing group migrates to Db2 13. The sample jobs are edited when the first member migrates to Db2 13.

Jobs tailored by they CLIST

Jobs that are marked with an asterisk (*) are modified only when you migrate the first member of a data sharing group.

DSNTIJCX*
DSNTIJEX*
DSNTIJIC*
DSNTIJFT
DSNTIJFV
DSNTIJGF
DSNTIJIN*
DSNTIJMV
DSNTIJPD*
DSNTIJPM
DSNTIJSG*
DSNTIJVC*
DSNTIJTC*
DSNTIJTM
DSNTIJUZ
DSNTIJRT*
DSNTIJRV*
DSNTIJRW*

Procedure

Important: Follow these directions carefully. The first member of the data sharing group uses DSNTIDXA as its input member name. If you use SAP, specify DSNTIDXB, the SAP-specific CLIST input member, instead of DSNTIDXA. A subsequent member must use a previous member's output member name as its input member name.

To migrate the first member of a data sharing group to Db2 13:

Make a plan to migrate the data sharing group in as short a time period as possible. Migrating an existing data sharing group requires careful planning.
Apply maintenance through the Db2 13 fallback SPE to all active members.

Important: Apply the for fallback SPE (APAR PH37108) and stop and restart Db2 12 for every subsystem or data sharing member that you plan to migrate to Db2 13. For data sharing, every member must be started in Db2 12 after the fallback SPE is applied. Inactive members that never started with the fallback SPE applied in Db2 12 cannot start in Db2 13 or Db2 12 after migration to Db2 13 and activation of function level 500 on any other member. See Required maintenance for Db2 13 installation or migration.

In case fallback becomes necessary, keep the subsystem parameter load module that is used by Db2 12.
Generate tailored JCL jobs for migrating to Db2 13. You can use the DSNTIJBC batch job or the Db2 installation CLIST.
Tip: You can avoid working through the Db2 installation CLIST panels in interactive mode by running a batch job with valid input files to generate the required JCL jobs and input files with a background process. See Generating tailored Db2 migration or function level activation jobs in the background.
To generate the required JCL jobs and input files with a background process, complete the following steps:
1. Customize the DSNTIDOM parameter override file by following the instructions in the file.
2. Customize the DSNTIJBC job. For example, if prefix.SDSNSAMP(DSNTIDOM) is the customized parameter override file, you can specify the following values in the IPSTART command in DSNTIJBC.
```
  ISPSTART CMD(%DSNTINSB + 
    OVERPARM(prefix.SDSNSAMP(DSNTIDOM)) + 
    ) BREDIMAX(1)
```
3. Submit the customized DSNTIJBC job.
To generate the required JCL jobs and input files with the Db2 installation CLIST in interactive mode, complete the following steps. For more information, see Generating tailored installation, migration, or function level activation jobs by running the Db2 installation CLIST in interactive mode.
Genterate tailored migration jobs for your first Db2 data sharing member. You can use the DSNTIJBC batch job or the Db2 installation CLIST.
Tip: You can avoid working through the Db2 installation CLIST panels in interactive mode by running a batch job with valid input files to generate the required JCL jobs and input files with a background process. See Generating tailored Db2 migration or function level activation jobs in the background.
To generate the required JCL jobs and input files with a background process, complete the following steps:
1. Customize the DSNTIDOM parameter override file by following the instructions in the file.
2. Customize the DSNTIJBC job. For example, if prefix.SDSNSAMP(DSNTIDOM) is the customized parameter override file, you can specify the following values in the IPSTART command in DSNTIJBC.
```
  ISPSTART CMD(%DSNTINSB + 
    OVERPARM(prefix.SDSNSAMP(DSNTIDOM)) + 
    ) BREDIMAX(1)
```
3. Submit the customized DSNTIJBC job.
To generate the required JCL jobs and input files with the Db2 installation CLIST in interactive mode, complete the following steps. For more information, see Generating tailored installation, migration, or function level activation jobs by running the Db2 installation CLIST in interactive mode.
1. Specify the following settings on panel DSNTIPA1:
```
INSTALL TYPE ===> MIGRATE
DATA SHARING ===> YES
.
DATA SET(MEMBER)NAME ===> this member's previous release output member
.
INPUT MEMBER NAME  ===> DSNTIDXA or DSNTIDXB
OUTPUT MEMBER NAME ===> this member's output PDS member
```
2. On panel DSNTIP0B, specify option 1 to indicate that this is the first member of the group to migrate.
```
| DSNTIP0B                            |
|                                     |
|  FIRST MEMBER OF GROUP TO MIGRATE?  |
|                                     |
|  Select one.                        |
|          1 1. Yes                   |
|            2. No                    |
```
3. Proceed through the remaining Db2 installation CLIST panels, specify or accept values for your Db2 environment, and wait for the Db2 installation CLIST to tailor the jobs for the migration process. The output data set contains the tailored jobs for the migration process. For more information, see The Db2 installation CLIST panel session.
Complete all of the steps to migrate to Db2 13.