PM72853: SUBSYSTEM CLONING FROM A DB2 SLB STOPS WHEN 00D10906 AND DSNR020I WTOR ARE ISSUED BY THE TARGET DB2.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Subsystem cloning from a DB2 SLB stops when 00D10906 and
  DSNR020I WTOR are issued by the target DB2.
  Part of cloning a data sharing group from a DB2 SLB is to
  truncate theactive logs of all the target members to the data
  complete LRSN of the SLB. This is to get all the target members
  to be at the same point in time.
  During group restart by the primary target member the pending
  truncation of the active logs of the other members causes a
  00D10906 and a DSNR020I WTOR to be issued. The DB2START command
  times out waiting for the target DB2 subsystem to complete its
  startup and will by default give a return code of 8 indicating
  an error thus stopping the cloning.
   An option will be added to the DB2START command to complete
  when a DSNR020I WTOR is issued by the DB2 subsystem.
  The subsystem cloning stored procedure will be updated to
  generate the necessary jobs to handle the 00D10906 and DSNR020I
  WTOR when cloning a data sharing group from a DB2 SLB.
  Also corrected:
  Possible DSNJ098E CRCR ENDLRSN OF rrr IS HIGHER THAN ANY KNOWN
  message when cloning a data sharing group from a DB2 SLB.
  If a member of the data sharing group is less used it is
  possible for its active log to not contain log records that are
  after the BACKUP SYSTEM data complete LRSN.
  The condtional restart record to truncate the active log to the
  data complete LRSN should not be created if the LRSN does not
  exist in the active log.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Cloning Tool.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Subsystem cloning from a DB2 SLB stops  *
  *                      when 00D10906 and DSNR020I WTOR are     *
  *                      issued by the target DB2. Part of       *
  *                      cloning a data sharing group from a DB2 *
  *                      SLB is to truncate the active logs of   *
  *                      all the target members to the data      *
  *                      complete LRSN of the SLB. This is to    *
  *                      get all the target members to be at the *
  *                      same point in time. During group        *
  *                      restart by the primary target member    *
  *                      the pending truncation of the active    *
  *                      logs of the other members causes a      *
  *                      00D10906 and a DSNR020I WTOR to be      *
  *                      issued. The DB2START command times out  *
  *                      waiting for the target DB2 subsystem    *
  *                      to complete its startup and will by     *
  *                      default give a return code of 8         *
  *                      indicating an error thus stopping the   *
  *                      cloning.                                *
  *                      An option will be added to the DB2START *
  *                      command to complete when a DSNR020I     *
  *                      WTOR is issued by the DB2 subsystem.    *
  *                      The subsystem cloning stored procedure  *
  *                      will be updated to generate the         *
  *                      necessary jobs to handle the 00D10906   *
  *                      and DSNR020I WTOR when cloning a data   *
  *                      sharing group from a DB2 SLB. Also      *
  *                      corrected: Possible DSNJ098E CRCR       *
  *                      ENDLRSN OF rrr IS HIGHER THAN ANY       *
  *                      KNOWN message when cloning a data       *
  *                      sharing group from a DB2 SLB. If a      *
  *                      member of the data sharing group is     *
  *                      less used it is possible for its        *
  *                      active log to not contain log records   *
  *                      that are after the BACKUP SYSTEM data   *
  *                      complete LRSN. The condtional restart   *
  *                      record to truncate the active log to    *
  *                      the data complete LRSN should not be    *
  *                      created if the LRSN does not exist in   *
  *                      the active log.                         *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

Temporary fix

Comments

APAR Information

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

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

  UK82001

Modules/Macros

•    CKZ00021 CKZ00201 CKZ00246 CKZ00255 CKZ00271
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R310 PSY UK82001

     UP12/10/03 P F210

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.