Migrating the first member of a group to Db2 13 at function level 100

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

Before you begin

When migrating a data sharing group to Db2 13, complete the migration steps for the first member to Db2 13 at function level 100 before starting any other members on Db2 13. For more information, see Migrating an existing data sharing group to Db2 13.
If your Db2 environment contains PBR RPN table spaces, APAR PH61633 is an important PE fix that you must apply on all data sharing members before migrating to or activating function levels in Db2 13.
Attention: If your Db2 environment contains PBR RPN table spaces, do not migrate any data sharing members to function level V13R1M100, or activate function level V13R1M500 or higher, until you apply the PTF for PH61633 on all data sharing members and complete all ++HOLD actions. For more information, see the 21 June 2024 Red Alert.

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: Inactive members that never started in Db2 12 with the fallback SPE (APAR PH37108) applied cannot start after the first data sharing member is migrated to Db2 13 at function level 100.

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 tasks of the procedure that is described in Migrating a Db2 for z/OS subsystem to Db2 13 at function level 100.

What to do next

The Db2 data sharing group can run with the migrated Db2 13 member in coexistence with any remaining Db2 12 members until you finish migrating them. For more information, see Release coexistence in Db2 data sharing.
When you are ready to migrate the other data sharing members to Db2 13, complete the tasks that are described in Migrating subsequent members of a group to Db2 13 for each member.
The data sharing group must remain at function level 100 until you finish migrating all members.