PI85657: DB2 12 FOR Z/OS NEW FUNCTION APAR TO SPLIT DSNTIJUZ INTO 4 JOBS DSNTIJUZ, DSNTIJUA, DSNTIJUM AND DSNTIJUL

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• DSNTIJUZ is splitted into 4 jobs:
  - DSNTIJUZ: Define the DB2 subsystem (DSNZPxxx) parameters
  - DSNTIJUA: Define the DB2 application defaults
  - DSNTIJUM: Define DB2 offline message generator
  - DSNTIJUL: Update DDF related information in the BSDS
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All DB2 12 for z/OS users of job DSNTIJUZ                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Placement of multiple tasks in job                           *
  * DSNTIJUZ is convenient for DB2                               *
  * installation and migration but not                           *
  * for service and updates.                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  Installation job DSNTIJUZ performs multiple tasks:
  - creates the DB2 subsystem parameter (DSNZPxxx) module
  - creates the DB2 appplication defaults (DSNHDECP) module
  - creates the DB2 offline message CCSID (DSNHMCID) module
  - updates DDF settings in the BSDS
  
  This grouping works well for DB2 installation and migration
  but not afterwards, particularly for maintenance of the
  DSNZPxxx and DSNHDECP modules.  Customers either need to
  use JCL overrides to execute only specific job steps of
  DSNTIJUZ or split DSNTIJUZ into several single-purpose
  jobs.  This is particularly the case in DB2 12 because
  function level activation can entail changing the
  default application compatibility (DSN6SPRM.APPLCOMPAT)
  parameter in DSNZPxxx and the default precompiler SQL
  level (DSNHDECP.SQLLEVEL) parameter in DSNHDECP.
  

Problem conclusion

Temporary fix

Comments

• Changes to DSNTIJUZ:
  --------------------
  In response, this APAR splits DSNTIJUZ into four jobs as
  follows.
  - DSNTIJUZ: Creates the DB2 subsystem (DSNZPxxx) module
              (only)
  - DSNTIJUA: Creates the DB2 application defaults (DSNHDECP)
              module
  - DSNTIJUM: Creates the DB2 offline message CCSID
              (DSNHMCID) module
  - DSNTIJUL: Updates DDF related information in the BSDS
  
  Procedural changes:
  -------------------
  When performing a DB2 installation, migration, update, or
  function level activation, continue to run DSNTIJUZ at the
  usual point documented in the DB2 Installation Guide.  Then
  run any additional jobs - DSNTIJUA, DSNTIJUM, or DSNTIJUL -
  that were customized by the CLIST for the process (see
  below).  Which jobs to run and when is also noted in updates
  to the DB2 Installation Guide.
  
  If you have already installed or migrated to DB2 12 for z/OS,
  see the ++HOLD ACTIONs for this APAR for guidance on how to
  adapt your existing DSNTIJUZ job.
  
  Changes to the DB2 installation CLIST:
  --------------------------------------
  The DB2 installation CLIST is modified to customize these
  jobs as follows:
  - Installation of a DB2 subsystem or the first member of
    a data sharing group, including enabling data sharing on
    an existing DB2 subsystem:
    -> DSNTIJUZ, DSNTIJUA, DSNTIJUM, and DSNTIJUL
  - Installation of the second or subsequent member of a data
    sharing group:
    -> DSNTIJUZ and DSNTIJUL
  - Migration of a DB2 subsystem or the first member of
    a data sharing group:
    -> DSNTIJUZ, DSNTIJUA, and DSNTIJUM
  - Migration of the second or subsequent member of a data
    sharing group:
    -> DSNTIJUZ
  - Activation of a function level:
    -> DSNTIJUZ and DSNTIJUA
  - Updating a DB2 subsystem or data sharing member:
    -> DSNTIJUZ and DSNTIJUA.  DSNTIJUL is also customized
       if one or more DDF-related parameters is modified.
  Note: Currently, data sharing enablement, function level
        activation and update mode are not supported by the
        DB2 z/OSMF processes.
  
  z/OSMF panel changes:
  ---------------------
  The panels described here are displayed when you run the
  CLIST and enter YES in the USE Z/OSMF WORKFLOW field on
  the main panel, DSNTIPA1.  Which panels are displayed
  depends on whether you run the CLIST in INSTALL or MIGRATE
  mode and whether you specify non-data sharing, the first
  member of a data sharing group, or a subsequent data
  sharing member.
  
  In the following DB2 CLIST panels:
    o DSNTIPMI (Steps for installing a subsystem or the
                first member of a data sharing group)
    o DSNTIPMA (Steps for adding a data sharing member)
    o DSNTIPME (Steps for enabling data sharing)
      -> Note: Currently, data sharing enablement is not
               supported by the DB2 z/OSMF processes.
    o DSNTIPMS (Steps for migrating a subsystem or the
                first member of a data sharing group)
    o DSNTIPMD (Steps for migrating a second or subsequent
                member of a data sharing group)
  the step "Define DB2 initialization parameters (DSNTIJUZ)"
  is split into one of more of these steps depending on the
  CLIST panel, as inidicated in Table A below:
    o Define the DB2 subsystem parameter module (DSNTIJUZ)
    o Define the DB2 application defaults module (DSNTIJUA)
    o Define the DB2 offline message CCSIDs module (DSNTIJUM)
    o Update DDF related information in the BSDS (DSNTIJUL)
  
  To accommodate the additional steps described above, the
  following CLIST panels are split:
    o DSNTPMI is divided into two panels:
      o DSNTIPMI now specifies the installation steps to
        be performed prior to starting DB2 12.
      o DSNTIPMJ (Steps for installing a subsystem or the first
        member of a data sharing group - panel 2) is a new
        panel that specifies the continuation of steps for
        DB2 installation, beginning with startup (DSNTIJSA) and
        beyond, that were previously on DSNTIPMI.
        The CLIST displays DSNTIPMJ immediately after DSNTIPMI.
    o DSNTPMS is divided into two panels:
      o DSNTIPMS now specifies the migration steps to be
        performed prior to starting DB2 12.
      o DSNTIPMT (Steps for migrating a subsystem or the first
        member of a data sharing group - panel 2) is a new
        panel that specifies the continuation of steps for
        DB2 migration, beginning with startup (DSNTIJSA) and
        beyond, that were previously on DSNTIPMS. The following
        step is moved to DSNTIPMT from panel DSNTIPMN:
        o Convert EXPLAIN tables to the current format
          (DSNTIJXA)
        The CLIST displays DSNTIPMT immediately after DSNTIPMS.
  
  Finally, in DSNTIPMN (Steps for activating new function), the
  step "Convert EXPLAIN tables to the current format
  (DSNTIJXA)" is moved from DSNTIPMN to panel DSNTIPMT.
  
  z/OSMF workflow changes:
  ------------------------
  The workflows described here are generated when you run the
  CLIST and enter YES in the USE Z/OSMF WORKFLOW field on the
  main panel, DSNTIPA1.  Which workflows are generated depends
  on whether you run the CLIST in INSTALL or MIGRATE mode and
  whether you specify non-data sharing, the first member of a
  data sharing group, or a subsequent data sharing member.
  
  In the following z/OSMF workflow definition files:
    o DSNTIWIN (Installing a subsystem or the first DSG member)
    o DSNTIWIA (Adding a data sharing group member)
    o DSNTIWIE (Enabling data sharing)
      -> Note: Currently, data sharing enablement is not
               supported by the DB2 z/OSMF processes.
    o DSNTIWMS (Migrating a subsystem or the first DSG member)
    o DSNTIWMD (Migrating a second or subsequent DSG member)
  the step "Define DB2 initialization parameters(DSNTIJUZ)" is
  split into one of more of these steps depending on the type
  of workflow, as inidicated in Table A below:
    o Define the DB2 subsystem parameter module(DSNTIJUZ)
    o Define the DB2 application defaults module(DSNTIJUA)
    o Define the DB2 offline message CCSIDs module(DSNTIJUM)
    o Update DDF related information in the BSDS(DSNTIJUL)
  
  Table A. Correspondence of jobs/steps and panels/workflows
  -------------------------------------------------------------
  |         |                    CLIST Panel                  |
  |         |          zOSMF Workflow Definition File         |
  -------------------------------------------------------------
  |         |DSNTIPMI |DSNTIPMA |DSNTIPME |DSNTIPMS |DSNTIPMD |
  |  Step   |DSNTIWIN |DSNTIWIA |DSNTIWIE |DSNTIWMS |DSNTIWMD |
  -------------------------------------------------------------
  |DSNTIJUZ |    Y    |    Y    |    Y    |    Y    |    Y    |
  |DSNTIJUA |    Y    |         |    Y    |    Y    |         |
  |DSNTIJUM |    Y    |         |    Y    |    Y    |         |
  |DSNTIJUL |    Y    |    Y    |    Y    |         |         |
  -------------------------------------------------------------
  
  SMP/E GENASM considerations:
  ----------------------------
  The last job step of the current DSNTIJUZ, DSNTIMQ, is
  optional and disabled by default.  If enabled, it processes
  SMP/E JCLIN that defines GENASM entries on the DB2 subsystem
  parameter (DSN6xxxx), DSNHDECM, and DSNHMCIM macros.  Then,
  when service is applied to one of these macros, its GENASM
  entry triggers SMP/E to initiate reassembly of the DSNZPxxx,
  DSNHDECP, or DSNHMCID module.  This automation, although
  convenient, should not be deployed without specific
  knowledge of GENASM behavior and management because
  subsequent changes to DSNTIJUZ can affect SMP/E processing
  for DB2.
  
  As described above, this APAR splits DSNTIJUZ into four jobs.
  Three of these jobs, DSNTIJUZ, DSNTIJUA, and DSNTIJUM, each
  have a disabled DSNTIMQ job step as follows:
  - DSNTIJUZ: Defines GENASM entries on the DB2 subsystem
              parameter (DSN6xxxx) macros
  - DSNTIJUA: Defines GENASM entries on the DSNHDECM
              macro
  - DSNTIJUM: Defines GENASM entries on the DSNHMCIM
              macro
  
  If you have already defined GENASM entries on one or more of
  these macros, see the ++HOLD ACTIONs for this APAR for
  guidance on how to adapt them for this change.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI51760

Modules/Macros

• DSNTIJUZ DSNTIWIN DSNTIPMS DSNTIPMT DSNTIWMD DSNTINMF DSNTIWIA
  DSNTIPME DSNTIJUM DSNTIPMD DSNTIWIE DSNTIPMA DSNTIJUL DSNTIJUA
  DSNTIPMN DSNTIWMS DSNTINST DSNTIPMJ DSNTIPMI
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI51760

     UP17/11/28 P F711

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.