IT28810: MOVE CONTAINER WITH DEFRAG=YES COMPLETES WITH FAILURE WITHOUT LOGGING A MESSAGE IN THE ACTIVITY LOG.

8.1.9.000-IBM-SPSRV-WindowsX64
8.1.9.000-IBM-SPSRV-Linuxx86_64
8.1.9.000-IBM-SPOC-WindowsX64
8.1.9.000-IBM-SPCMS-WindowsX64
8.1.9.000-IBM-SPSRV-Linuxs390x
8.1.9.000-IBM-SPCMS-WindowsI32
8.1.9.000-IBM-SPOC-Linuxx86_64
8.1.9.000-IBM-SPCMS-Linuxx86_64
8.1.9.000-IBM-SPSRV-Linuxppc64le
8.1.9.000-IBM-SPOC-Linuxs390x
8.1.9.000-IBM-SPOC-LinuxPPC64le
8.1.9.000-IBM-SPSRV-AIX
8.1.9.000-IBM-SPOC-AIX
IBM Spectrum Protect Server V8.1 Fix Pack 8 (V8.1.9) Downloads

APAR status

• Closed as program error.

Error description

• A MOVE CONTAINER command is run with the DEFRAG=YES parameter.
  The command ends in failure and there is no message logged
  in the server activity log. For example :
  
  ANR2017I Administrator ADMIN issued command:
  MOVE CONTAINER <container-name> defrag=yes wait=no
   (SESSION: xxx)
  ANR0984I Process nnn for Move Container started in the
  BACKGROUND at <timestamp>. (SESSION: xxx, PROCESS: nnn)
  ANR0985I Process nnn for Move Container running in the
  BACKGROUND completed with completion state FAILURE at
  <timestamp>. (SESSION: xxx, PROCESS: nnn)
  ANR1893E Process nnn for Move Container completed with a
  completion state of FAILURE. (SESSION: xxx, PROCESS: nnn)
  
  The same issue can also occur when the MOVE CONTAINER
  is launched by the automatic container defrag.
  
  Customer/L2 Diagnostics :
  Examine the server instance dsmffdc.log for error.
  In this case the following error is logged :
  
  [timestamp][ FFDC_GENERAL_SERVER_ERROR ]: (sddefrag.c:3851)
   Marking process FAILED due to No Data Copied, code 4
  
  A server trace (SD) of the MOVE CONTAINER command shows all
  extents are skipped. For example :
  
  <timestamp> [nnn][sddefrag.c][3007][SdMoveContainer]:
   Skipping chunk nnn due to lastRef <timestamp> and reuse
   padding time <timestamp>
  <timestamp> [nnn][sddefrag.c][3187][SdMoveContainer]:
   Chunk nnn didn't get moved due to I/O error or reusedelay
   padding.
  
  In this case, the container cannot be moved with DEFRAG=YES
  because the container extents are eligible for deletion.
  
  A proper message should be logged in the server activity log
  to provide additional information on the failure.
  
  Initial Impact: Low
  
  Additional Keywords:
  defrag TS002044914
  
  Versions Affected:
  IBM Spectrum Protect server 8.1.4 and above on all platforms.
  

Local fix

• Run the MOVE CONTAINER command with DEFRAG=NO to avoid the
  failure.
  

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 levels 8.1.9. 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.
  
  New Message
  ANR3808E: A process for moving container Container Name was
  started, but no data was moved.
  
  Explanation: The process for moving the specified container is
  reported as a failure because no eligible data was detected, and
  no data was moved.
  
  SystemAction: System operation continues, but the specified
  process failed.
  
  UserResponse: When you run the MOVE CONTAINER command, ensure
  that the DEFRAG=NO setting is specified. For example, if the
  name of the container is BOSTON23, issue the following command:
  MOVE CONTAINER BOSTON23 DEFRAG=NO
  

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