IT28530: STUB RESTORE USING NQR IN BA CLIENT JAVA UI ENDS WITH ANS2610S (COMMUNICATION ERROR)

APAR status

• Closed as program error.

Error description

• When using the B/A client Java GUI (dsmj) to restore the full
  file system or full directories via no-query restore (NQR) and
  these file system or directories include stubs (an HSM migrated
  file), the message 'ANS2610S TCP/IP communications failure
  between the client and the server machine.' is displayed and the
  dsmagent stops.
  The dsmj.log contains the message ANS2610S.
  The dsmerror.log on Linux contains message 'ANS0361I DIAG: 1st
  Restore Consumer thread, fatal error, signal 6', while on AIX it
  contains 'ANS0361I DIAG: cuEndTxnEnhanced: Out of sequence verb:
  verb: 9'
  
  Product affected:
  IBM Spectrum Protect Backup-Archive client v7.1 and 8.1 on Linux
  and AIX platforms
  
  Impact: Medium
  

Local fix

• Two workarounds exist:
  1 - disable NQR by using option "DISABLENQR YES"
  or
  2 - restore individual files instead of full directories.
  Both will switch from NQR to classic restore.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Backup-Archive client version 7.1 and   *
  * 8.1 on Linux and AIX platforms                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * see Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * This issue is projected to be fixed in the IBM Spectrum      *
  * Protect Backup-Archive client version 8.1.8                  *
  * on Linux and AIX platforms supporting IBM Spectrum Protect   *
  * for Space Management.                                        *
  * Note 1: This is subject to change at the discretion of IBM.  *
  ****************************************************************
  The dsmagent crash occured after the first migrated file was
  restored. All subsequent operations will fail until the dsmj UI
  is restarted.
  

Problem conclusion

• The client has been changed to handle the situation correctly.
  

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:

Modules/Macros

• DSMJ     DSMAGENT
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R81L PSY

     UP

• R81A PSY

     UP