PM71045: NEW SET COMMAND SUBTASK-DATASET-EXTENSIONS

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• This enhancement allows dataset extents to be processed in any
  available subtask. Previously, all extents were always processed
  after the initial (A001) dataset and in the same subtask. If
  there are a significant number of extents to be processed by the
  target job, this might be an option to consider to improve the
  total elapsed time of the target job. If DB2 START commands
  starts are enabled for target objects, they will be done when
  the last extent of an object has been processed, regardless of
  the subtask used. The number of subtasks must be greater than
  one for this to be a useful feature.
  .
  There are several restrictions when using this enhancement...
  #1. no log apply
  #2. no data masking
  #3. no runtime repository
  #4. no DB2 STOP commands in the target job (via the PARMLIB
      parm, AUTO_STOP_TARGET_SPACE)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Cloning Tool.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: This enhancement allows dataset         *
  *                      extents to be processed in any          *
  *                      available subtask. Previously, all      *
  *                      extents were always processed           *
  *                      after the initial (A001) dataset and    *
  *                      in the same subtask. If there are a     *
  *                      significant number of extents to be     *
  *                      processed by the target job, this       *
  *                      might be an option to consider to       *
  *                      improve the total elapsed time of the   *
  *                      target job. If DB2 START commands       *
  *                      starts are enabled for target objects,  *
  *                      they will be done when the last extent  *
  *                      of an object has been processed,        *
  *                      regardless of the subtask used. The     *
  *                      number of subtasks must be greater      *
  *                      than one for this to be a useful        *
  *                      feature.                                *
  *                      There are several restrictions when     *
  *                      using this enhancement...               *
  *                      1. no log apply                         *
  *                      2. no data masking                      *
  *                      3. no runtime repository                *
  *                      4. no DB2 STOP commands in the target   *
  *                       job                                    *
  *                      (via the PARMLIB parm,                  *
  *                      AUTO_STOP_TARGET_SPACE)                 *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

Temporary fix

Comments

• APPLY the PTF.
  

APAR Information

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

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

  UK81404

Modules/Macros

•    CKZ00500 CKZ00501 CKZ00536 CKZ00537 CKZ00545
  CKZ00546 CKZ00760
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R220 PSY UK81404

     UP12/09/01 P F208

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.