PM83053: PARALLEL BACKUP STG PROCESSES FOR THE SAME DISK STORAGE POOL DO NOT COPY ALL DATA

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When running more than one BACKUP STG process in parallel for
  the same source disk storage pool (e.g. for creating copies in
  different libraries or data centers), not all data will be
  copied to all target storage pools due to internal locks on
  objects. The final statistics of the BACKUP STG processes
  indicate successfully completed operation including all data
  copied but verifying the data stored in the primary disk storage
  pool and the copy storage pools using the Q OCC command will
  illustrate not all data was copied to each copy storage pool.
  
  Example:
  - Primary disk storage pool 1 has objects A, B and C
  - Two BACKUP STG processes are startet in parallel copying data
  to pools 2 and 3
  - Objects A and C are locked by BACKUP STG copying to pool 2
  - Object B is locked by BACKUP STG copying to pool 3
  - BACKUP STG copying to pool 3 will silently skip A and C
  - BACKUP STG copying to pool 2 will silently skip B
  
  This exclusive lock behavior was introduced due to changes made
  for APAR IC61439.
  
  A subsequent run of the BACKUP STG process will copy the missing
  objects.
  
  Platforms and versions affected:
  Tivoli Storage Manager 5.5.4 and above, 6.1.3 and above, 6.2 and
  6.3
  
  Initial Impact:
  Medium
  
  Additional Keywords:
  tsm movement data copy pool dr disk simultaneous storage pool
  xlock shared lock zztsm63 zz62 zztsm62 zz61 zztsm61
  

Local fix

• Run BACKUP STG processes for the same disk storage pool one at a
  time.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 5.5.7, 6.1.6, 6.2.5 and 6.3.2.     *
  *                 Note that this is subject to change at the   *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Solaris, Linux, z/OS and
  Windows.
  

Temporary fix

Comments

APAR Information

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

  IC81195

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

Fix information

• Fixed component name

  TSM FOR OS/390

• Fixed component ID

  5698ISMVS

Applicable component levels

• R550 PSY UK91785

     UP13/02/21 P F302

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.