PH11514: ADD PRE-MIGRATION REPORT TO DSNTIJPC/DSNTIJPM TO IDENTIFY ACTIVELOG DATA SETS WITH SIZE GREATER THAN 4GB (HI-A-RBA)

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• This apar adds a pre-migration report to DSNTIJPC/DSNTIJPM to
  report active log data sets with size greater than 4GB.  During
  migration to Db2 12,  if  the size of an active log data set in
  Db2 11 is greater than 4 GB (HI-A-RBA),  Db2 12 will abnormally
  terminate during startup with message DSNJ158I.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 11 for z/OS users who are                            *
  * migrating to Db2 12 for z/OS                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Add a new report (REPORT24) to                               *
  * Db2 12 pre-migration checkout jobs:                          *
  * o DSNTIJPM (Db2 12)                                          *
  * o DSNTIJPC (Db2 11)                                          *
  * to list active log data sets that                            *
  * have a size of greater than 4 GB.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * APPLY PTF                                                    *
  ****************************************************************
  Db2 12 supports active log data sets that have sizes of up to
  768 GB each but only when the activated function level is
  V12R1M500 or higher.  However, when the activated function level
  is V12R1M100, the maximum size of any active log data set must
  be 4 GB or less and otherwise Db2 12 terminates during startup
  with this message:
  DSNJ158I ACTIVE LOG DATA SET DSN=dsname IS GREATER THAN 4
  GB IN SIZE
  
  Because Db2 11 can tolerate active log data sets that have
  sizes of more than 4 GB, by ignoring the excess space, it is
  possible that an active log data set that works in Db2 11 will
  not work following migration to Db2 12 during the initial
  function level of V12R1M100.
  
  By adding a new report (REPORT24) to the Db2 12 pre-migration
  checkout jobs which will list all active log data sets that
  have a size of greater than 4 GB, users are warned about this
  limitation, and Db2 abnormal termination during startup can
  be prevented.
  

Problem conclusion

Temporary fix

Comments

• A new report (REPORT 24) is added to the following Db2 12
  pre-migration checkout jobs to list active log data sets
  that have a size of greater than 4 GB.
    o DSNTIJPM (Db2 12)
    o DSNTIJPC (Db2 11)
  
  REPORT 24 is based on information gathered from the DSNJU004
  (Print Log Map) and LISTCAT outputs. In order for jobs
  DSNTIJPC and DSNTIJPM to have access to the DSNJU004 output,
  this APAR makes the following additional changes to DSNTIJPC
  and DSNTIJPM:
  o  Adds the prefix.SDSNEXIT library to the JOBLIB DD
     concatenation.
  o  Modifies the prolog to include guidance on how to
     customize the new job step DSNTJU04.
  o  Adds a new job step (DSNTJU04) before step DSNTGEN.
     This step executes DSNJU004 to get the active log data
     set names (copy 1 and copy 2) and their respective group
     and member names from the BSDS of each member in the data
     sharing group, or from the BSDS of a non-data sharing
     Db2 system. The output from DSNJU004 is passed to the
     REXX program DSNTPMQ which generates the pre-migration
     reports.
  o  Adds a new DD statement JU004PRT to job step DSNTPMQ,
     the step which invokes the REXX program DSNTPMQ.
     The JU004PRT DD allocates the DSNJU004 output which
     was generated earlier in step DSNTJU04.
  
  The size of each active log data set is retrieved from the
  corresponding LISTCAT output.
  ×**** PE20/04/17 FIX IN ERROR. SEE APAR PH12364  FOR DESCRIPTION
  

APAR Information

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

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

  UI63887 UI63888

Modules/Macros

• DSNTIJPM DSNTIJPC
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI63888

     UP19/07/11 P F907

• RC10 PSY UI63887

     UP19/07/11 P F907

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.