IT32494: TAPE OPTIMIZED RECALL USING DSMRECALL DOES NOT LOG RECALLED FILES

APAR status

• Closed as program error.

Error description

• When a tape optimized recall is performed, using dsmrecall in
  conjunction with the HSMLOGEVENTFLAGS FILE configuration option,
   the files recalled by dsmrecall are not logged into the
  HSMLOGNAME file, instead only the following is logged:
  
  02/18/2020 07:26:39 File list recall begin list node: NODENAME
  pid: 28446 file: filelist
  02/18/2020 07:29:51 File list recall end list node: NODENAME
  pid: 28446 file: filelist result: 0
  
  
  IBM Spectrum Protect Versions Affected:
  IBM Spectrum Protect Space Management 8.1.x on Unix platforms
  
  
  Initial Impact:
  Low
  
  
  Additional Keywords:
  Spectrum Protect; Space Management; HSM; HSMLOGEVENTFLAGS;
  dsmrecall
  

Local fix

• To retrieve the information about the staged files in real time,
   launch the dsmrecall process with -detail option and monitor
  the STDOUT output.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect for Space Management client versions    *
  * 7.1 and 8.1 on Linux and AIX platforms.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * see ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed in level 8.1.11. Note that this is subject to    *
  * change at the discretion of IBM.                             *
  ****************************************************************
  *
  

Problem conclusion

• HSM log file will include FILE events in case of running tape
  optimized recall.
  

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

• recall
  

Fix information

• Fixed component name

  TSM SPACE MGMT

• Fixed component ID

  5698HSMCL

Applicable component levels