IC99145: REPLICATION "END TIME" STATISTIC INCORRECTLY UPDATED BY A CONCURRENT REPLICATION PROCESS

APAR status

• Closed as program error.

Error description

• The command QUERY REPLICATION may report an incorrect "End Time"
  for an already ended replication process if the following
  conditions are met :
   - Two or more replication processes are started at the exact
     same time, i.e. in the same second.
   - One replication process ends before the other.
  
  A QUERY REPLICATION done when the first process has finished,
  shows the correct "End Time" value for this process.
  Later when the other process(es) finishes, the "End Time" value
  for all the processes that have the same "Start Time" are
  updated using the last process "End Time" value.
  
  
  Tivoli Storage Manager Versions Affected:  All platforms  6.3
  
  Customer/L2 Diagnostics :
  
   - Two processes are started  from a script in the same second:
  
   2014-01-22 11:00:22  ANR0984I Process 1914 for Replicate
    Node started in the FOREGROUND at 11:00:22. (SESSION:
    926929, PROCESS: 1914)
   2014-01-22 11:00:22      ANR0984I Process 1915 for Replicate
    Node started in the FOREGROUND at 11:00:22. (SESSION:
    926930, PROCESS: 1915)
  
    - One process ends at 11:10:14
  
   2014-01-22 11:10:14      ANR0986I Process 1914 for Replicate
    Node running in the FOREGROUND processed 2,593,354 items
    for a total of 13,131,799,040 bytes with a completion
    state of SUCCESS at 11:10:14. (SESSION: 926929, PROCESS: 1914)
  
    - A "Q REPLICATION"  done here shows the correct "End Time"  :
  
  Node  Filespace FSID Start Time  End Time    Status Process
  Name  Name                                          Number
  
  ----  ---------- --- ----------  ----------  ------ -------
  NODEX /test      1   01/22/2014  01/22/2014  Ended   1,914
                       11:00:22    11:10:14
  
    - The second process ends at 11:50:02 :
  
   2014-01-22 11:50:02      ANR0986I Process 1915 for Replicate
    Node running in the FOREGROUND processed 5,363,417 items
    for a total of 477,803,835,392 bytes with a completion state
    of SUCCESS at 11:50:02. (SESSION: 926930, PROCESS: 1915)
  
   - A "Q REPLICATION" shows now that the  "End Time" for the
  previous process has been updated incorrectly to the "End Time"
  of the second process:
  
  
  Node  Filespace FSID Start Time  End Time    Status Process
  Name  Name                                          Number
  
  ----  ---------- --- ----------  ----------  ------ -------
  NODEX /test      1   01/22/2014  01/22/2014  Ended   1,914
                       11:00:22    11:50:02
  NODEY /testy     3   01/22/2014  01/22/2014  Ended   1,915
                       11:00:22    11:50:02
  
  Initial Impact: Low
  
  Additional Keywords:
  TSM REPL endtime statistics zz63
  

Local fix

• - Do not use a script to start concurrent replication processes
  to avoid having them started with exact the same "Start Time"
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users that perform Node    *
  * Replication.                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 7.1.1.0. 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

• R63A PSY

     UP

• R63W PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R71A PSY

     UP

• R71W PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP