IT26739: WINDOWS CLIENT BACKUP VERSION 7.1.8.2 CAUSES HIGH MEMORY UTILIZATION

APAR status

• Closed as program error.

Error description

• Error Description:
  
  Performing a backup using the client version
  7.1.8.2 on a Windows platform will see high memory utilization.
  
  The memory will be consumed by the dsmagent.exe process when
  using the Java GUI or the dsmc.exe process when using the
  command line.
  
  Customer/L2 Diagnostics (If Applicable)
  
  Obtaining a client service trace will show many thousands of
  calls to the WMIUtil() function :
  
  03-07-2018 09:50:11.111 [004684] [6964] :
  ..\..\common\winnt\wmiutil.cpp(1532): ENTER =====> WMIUtil()
  03-07-2018 09:50:11.111 [004684] [6964] :
  ..\..\common\winnt\wmiutil.cpp(1659): ENTER =====>
  WMIUtil::InitializeWMI():
  03-07-2018 09:50:11.111 [004684] [6964] :
  ..\..\common\winnt\wmiutil.cpp(1659): EXIT  <=====
  WMIUtil::InitializeWMI():, rc = 0
  
  This is a side issue from fixing IT23234 and already has been
  fixed internally in all versions apart from 7.1.8.2
  
  |MDVREGR 7.1.8.2-5898ISMCL|
  
  Spectrum Protect Versions Affected:
  IBM Spectrum Protect client 7.1.8.2 on Windows only.
  
  Initial Impact: Low|Medium|High
  Medium
  
  Additional Keywords:
  TSM, IT23234, mem, TS000845363,
  

Local fix

• Local Fix:
  Use any other version of the client.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Backup-archive client version 7.1.8.2 running on all         *
  * Microsoft Windows platforms                                  *
  ****************************************************************
  * 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
  information is subject to change at the discretion of IBM?
  

Problem conclusion

• ISP client running the VSS operation may seems as 'hang' before
  fix.  Now the long termination operations are changed. No 'hang'
  occur any more.
  

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 CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels