IT24940: PROTECT STGPOOL TO REMOTE SERVER UPDATES LASTPROTECTLOCAL_DATE INSTEAD OF LASTPROTECT_DATE.

8.1.6.000-IBM-SPSRV-AIX
8.1.6.000-IBM-SPSRV-Linuxppc64le
8.1.6.000-IBM-SPSRV-Linuxs390x
8.1.6.000-IBM-SPSRV-Linuxx86_64
8.1.6.000-IBM-SPSRV-WindowsX64
8.1.6.000-IBM-SPOC-AIX
8.1.6.000-IBM-SPOC-LinuxPPC64le
8.1.6.000-IBM-SPOC-Linuxs390x
8.1.6.000-IBM-SPOC-Linuxx86_64
8.1.6.000-IBM-SPOC-WindowsX64
8.1.6.000-IBM-SPCMS-Linuxx86_64
8.1.6.000-IBM-SPCMS-WindowsI32
8.1.6.000-IBM-SPCMS-WindowsX64
8.1.6.100-IBM-SPSRV-Linuxppc64le
8.1.6.100-IBM-SPSRV-AIX
8.1.6.100-IBM-SPSRV-Linuxs390x
8.1.6.100-IBM-SPSRV-Linuxx86_64
8.1.6.100-IBM-SPSRV-WindowsX64
IBM Spectrum Protect Server V8.1 Fix Pack 6 (V8.1.6) Downloads
IBM Spectrum Protect Server V8.1.6.X interim fix downloads

APAR status

• Closed as program error.

Error description

• The PROTECT STGPOOL command to a remote server completes
  successfully but incorrectly updates the LASTPROTECTLOCAL_DATE
  field rather than the LASTPROTECT_DATE. The date is properly
  updated with the current date/time but the wrong field is
  updated.
  
  The select command from the stgpools table shows the
  LASTPROTECTLOCAL_DATE is updated rather than LASTPROTECT_DATE.
  For example :
  
  select stgpool_name, LASTPROTECT_DATE, LASTPROTECTLOCAL_DATE
   from stgpools where stg_type='DIRECTORY'
  
           STGPOOL_NAME: DIRECTORY_POOL_NAME
       LASTPROTECT_DATE:
  LASTPROTECTLOCAL_DATE: 2018-04-23 16:11:15.000000
  
  Similarly, the QUERY STG F=D command shows the
  "Date of Last Protection to Local Pool" field is updated
  rather than the "Date of Last Protection to Remote Pool".
  For example :
  
                       Storage Pool Name: DIRECTORY_POOL_NAME
                       Storage Pool Type: Primary
                       Device Class Name:
                            Storage Type: DIRECTORY
                 Protection Storage Pool: REMOTE_DIR_POOL_NAME
           Protect Local Storage Pool(s):
                Reclamation Volume Limit:
  Date of Last Protection to Remote Pool:
   Date of Last Protection to Local Pool: 04/23/2018 16:11:15
  
  Customer/L2 Diagnostics :
  The wrong field is updated when the source server has a
  SERVER_ID value in the Server_Connect_Info table which matches
  the SERVERID value of the target server in the
  Replicating_Servers table.
  
  Logon with the instance userid and run the following commands :
  
  1) db2 connect to tsmdb1
  2) db2 set schema tsmdb1
  3) db2 "select server_name from Server_connect_Info a,
      Replicating_Servers b where a.server_name='SOURCE_SERVER'
       and b.servername='TARGER_SERVER' a.server_id=b.serverid"
  
  Replace SOURCE_SERVER and TARGET_SERVER with the appropriate
  server names involved with the PROTECT STGPOOL command.
  If any value is returned, you are affected by this issue.
  
  Initial Impact: Low
  Additional Keywords: SP TSM
  
  Versions Affected:
  IBM Spectrum Protect server V7.1 and V8.1 and above, on all
  platforms.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Spectrum Protect server users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available.                           *
  * This problem is currently projected to be fixed in level     *
  * 8.1.6.                                                       *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms for reported release:  AIX, Linux, and
  Windows.
  Platforms fixed:  AIX, 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