IT05156: SIMULTANEOUS WRITE FAILS, NO SERVER ERRORS, BUT "ANS1315W THE SERVER FOUND AN ERROR WHILE WRITING THE DATA" ON CLIENT.

7.1.3.000-TIV-TSMSRV-WIN
7.1.3.000-TIV-TSMSRV-SolarisSPARC
7.1.3.000-TIV-TSMSRV-Linuxx86_64
7.1.3.000-TIV-TSMSRV-Linuxs390x
7.1.3.000-TIV-TSMSRV-Linuxppc64
7.1.3.000-TIV-TSMSRV-HP-UX
7.1.3.000-TIV-TSMSRV-AIX
IBM Tivoli Storage Manager (TSM) server V7.1.1.x interim fix downloads

APAR status

• Closed as program error.

Error description

• Starting at Server 7.1, backups objects larger than
  MAXFRAGMENTSIZE, which by default is 10 GB, are split  to avoid
  pinning the logs.  If such a file is backed up to a storage
  pool hierarchy with simultaneous writes enabled
  (COPYSTGPOOLS=copypoolname) , and the DESTINATION does not have
  enough space and overflows to the NEXSTGPOOL, the backup will
  fail, but will not report any errors in the server activity log.
  
  There are 3 criteria for the problem to occur:
  - object must be larger than MAXFRAGMENTSIZE (10GB by default)
  - backup sent to pool hierarchy: destination -> next
  - the destination pool does not have enough space or MAXSIZE
     exceeded
  
  TDP Clients are more likely to see this as it's more common
  that they backup really large objects.
  
  The client error log will show:
  ANS0278S The transaction will be aborted.
  ANS1315W Unexpected retry request. The server found an error
  while writing the data.
  
  L2 Advanced diagnostic:
  A server trace with BF AF DF SS AS DS SW will show
  [ssswtr.c][1413][ssSWStore]:Source has ended STORE transfer.
  [bfswcrt.c][2762][StoreBitfile]:Translated ssSWStore
     returned 3266.
  [bfswcrt.c][2771][StoreBitfile]:Received
     GRC_SIZE_LIMIT_REACHED after 10485966832 bytes
  [bfutil.c][14213][BfSetSWOpMode]:Setting SW move type
     to 4 for pool DISKPOOL.
  [bfutil.c][14213][BfSetSWOpMode]:Setting SW move type
     to 4 for pool COPYPOOL.
  
  The GRC_SIZE_LIMIT_REACHED return code is an indication that
  the 10GB limit was reached.
  
  Versions Affected: Server 7.1
  Initial Impact:  medium
  Additional Keywords: zz71 SW TDP TSM
  

Local fix

• There are 3 different workarounds:
  
  1 - Send the backups to a storage pool that does not have a
  next pool.
  
  2 - Increase the 10GB limit by using the server option
  "MAXFRAGMENTSIZE" in dsmerv.opt.
  
  For example, to set it at 200 GB:
  MAXFRAGMENTSIZE   200000
  
   It can have a maximum value of 999,999 MB (or approx 1 TB).
  
  3 - It's also possible to update the affected node(s) to have
  SPLITLARGEObjects=No, the default is yes:
    update node NODENAME SPLITLARGEObjects=NO
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users of the simultaneous  *
  * write function.                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This                      *
  * problem is currently projected to be fixed                   *
  * in levels 7.1.1.200 and 7.1.3. 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 and Windows.
  

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:

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP