IT00815: DSMC MULTI-SESSION NO-QUERY RESTORE PROCESS IS COMPLETED, BUT ANS1074W MESSAGE IS RETURNED.

IBM Tivoli Storage Manager (TSM) Client 7.1.1 Downloads and READMEs
IBM Tivoli Storage Manager (TSM) client 6.3.2.x interim fix downloads - EOL

APAR status

• Closed as program error.

Error description

• dsmc restore command seems to finish successfully since the
  number of objects restored matches the number of objects
  inspected.
  But "ANS1074W The operation was stopped by the  user." message
  is generated at the bottom of restore log and dsmerror.log,
  although user never terminates the restore. And restore
  completes with return code 8. So user cannot judge if the
  restore was certainly completed or not.
  
  In detail, the symptom happens by the following scenario
  internally:
  1. Customer run multi-session no-query restore.
  2. One of the sessions with the server is terminated due to
  network problem while others continue working.
  3. It leads to terminating all other sessions internally because
  it is no-query restore and the TSM client is not aware of the
  restore point.
     An internal termination of living sessions is accomplished
  via "user abort" technique.
  4. Then the restore operation is restarted.
  5. The restarted restore finished successfully but the final
  return code was not reset correctly and remained to be set to
  "user abort".
  
  As a result, the restore ended with ANS1074W even though it was
  successfully done.
  
  This problem can be seen from client error log and service trace
  like below.
  
  excerpt from dsmerror.log
  ANS1809W A session with the TSM server has been disconnected. An
  attempt will be made to reestablish the connection
  .....
  ANS1074W The operation was stopped by the  user.
  
  
  excerpt from client service trace
  [009244] [11548] : ..\..\common\com\commtcp.cpp(1638): TcpOpen:
  Trying to connect to server at:
  [009244] [11548] : ..\..\common\com\commtcp.cpp(1639):
  Domain Name: 10.5.6.54
  [009244] [11548] : ..\..\common\com\commtcp.cpp(1641):
  Port #: 1500
  [009244] [11548] : ..\..\common\com\commtcp.cpp(1666): TcpOpen:
  using blocking sockets
  [009244] [11548] : ..\..\common\winnt\pscomtcp.cpp(1193):
  Attempt connection results, rc = 0.
  .......
  [009244] [11548] : ..\..\common\ba\DccTaskStatus.cpp(1451):
  Total number of objects inspected :      36,038
  [009244] [11548] : ..\..\common\ba\DccTaskStatus.cpp(1455):
  Total number of objects restored   :      36,038
  ...
  [009244] [11548] : ..\..\common\ba\DccTaskStatus.cpp(1479):
  Total number of objects failed        :            0
  [009244] [11548] : ..\..\common\ba\DccTaskStatus.cpp(1483):
  Total number of bytes transferred   :       548.45 GB
  ...
  [009244] [11548] : ..\..\common\ba\DccTaskStatus.cpp(1489): Data
  transfer time                      :     5,686.78 sec
  [009244] [11548] : ..\..\common\ba\DccTaskStatus.cpp(1490):
  Network data transfer rate        :   101,128.44 KB/sec
  [009244] [11548] : ..\..\common\ba\DccTaskStatus.cpp(1491):
  Aggregate data transfer rate         :    48,310.61 KB/sec
  .....
  [009244] [11548] : ..\..\common\ba\DccRCMap.cpp( 418): Enter
  DccRCMap::ccMap: rc = 101
  [009244] [11548] : amsglog.cpp         ( 460): nlLogPrintf: msg
  number = 1074
  [009244] [11548] : amsglog.cpp         ( 519): adding newline
  character to buffer
  [009244] [11548] : ..\..\common\cu\cuopt.cpp( 541): return from
  nlLogPrintf:
  
  Total number of objects restored matches total number of objects
  inspected as expected, but rc = 101 and msg number = 1074
  remain.
  
  
  Tivoli Storage Manager Versions affected:
  Tivoli Storage Manager 5.5 and higher client
  
  Additional Keywords:
  multi session no query restore ANS1074W
  
  Initial Impact:
  Mid
  

Local fix

• run restore with single session
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Backup-archive client versions 5.1.0 and higher on all       *
  * supported platforms                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This                      *
  * problem is currently projected to be fixed                   *
  * in levels 6.3.2.3 (UNIX), 6.3.2.4 (Win), 6.4.2, and 7.1.1.   *
  * Note that this is subject to change at                       *
  * the discretion of IBM.                                       *
  ****************************************************************
  

Problem conclusion

• The problem has been fixed so that an internal return code is
  reset upon restart restore.
  

Temporary fix

• 6.3.2.3 for UNIX and Linux clients; 6.3.2.4 for Windows clients
  

Comments

APAR Information

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

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

Modules/Macros

• DSMC
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R64A PSY

     UP

• R64H PSY

     UP

• R64L PSY

     UP

• R64M PSY

     UP

• R64S PSY

     UP

• R64W PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP