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

You must first complete the migration of one member of the data sharing group to Db2 12 before starting any other members in Db2 12. 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 12. The sample jobs are edited when the first member migrates to Db2 12.

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.

  • DSNTIJCB
  • 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 12:

  1. 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.
  2. Apply maintenance through the Db2 12 fallback SPE to all active members.
    Important: Inactive members that never started in Db2 11 with the fallback SPE (APAR PI33871) applied cannot start after the first data sharing member is migrated to Db2 12 at function level 100.

    In case fallback becomes necessary, keep the subsystem parameter load module that is used by Db2 11.

  3. Generate tailored JCL jobs for migrating to Db2 12. You can use the Db2 installation CLIST. 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.
  5. Start of change Complete all of the tasks of the procedure that is described in Migrating a Db2 for z/OS subsystem to Db2 12 at function level 100. End of change

What to do next

  • The Db2 data sharing group can run with the migrated Db2 12 member in coexistence with any remaining Db2 11 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 12, complete the tasks that are described in Migrating subsequent members of a group to Db2 12 for each member.
  • The data sharing group must remain at function level 100 until you finish migrating all members.