IT04939: INSTALLATIONS ON ZOS WILL PRINT SERVLET MESSAGES TO THE CONSOLE RATHER THAN A FILE

Tivoli Storage Productivity Center Refresh Pack 5
Refresh Pack 5.2.5 (March 2015) for Tivoli Storage Productivity Center
Fix Pack 5.2.5.1 (April 2015) for Tivoli Storage Productivity Center
Refresh Pack 5.2.6 (June 2015) for Tivoli Storage Productivity Center
Refresh Pack 5.2.7 (August 2015) for Tivoli Storage Productivity Center
IBM Spectrum Control V5.2.8 (December 2015)
IBM Spectrum Control V5.2.9 (February 2016)
IBM Spectrum Control V5.2.10 (May 2016)
IBM Spectrum Control V5.2.10.1 (July 2016)
IBM Spectrum Control V5.2.11 (August 2016)
IBM Spectrum Control V5.2.12 (November 2016)
IBM Spectrum Control V5.2.13 (March 2017)
IBM Spectrum Control V5.2.14 (May 2017)
IBM Spectrum Control V5.2.15 (August 2017)
IBM Spectrum Control V5.2.15.2 (November 2017)
IBM Spectrum Control V5.2.16 (March 2018)
IBM Spectrum Control V5.2.17 (May 2018)
Fix Pack 5.2.7.1 (February 2016) for Tivoli Storage Productivity Center

APAR status

• Closed as fixed if next.

Error description

• On install the logging.properties file should be correctly
  placed into the properties file of the replicationServer if it
  is not placed there, overwriting the default the large amounts
  of messages will be printed to system out and shown in the
  console.
  

Local fix

• 1) Backup the existing logging properties file:
  /opt/Tivoli/RM/wlp/usr/servers/replicationServer/properties/logg
  ing.properties
  2) Copy the file from the install location
  /usr/lpp/Tivoli/RM/config/logging.properties to the above
  location
  3) Restart IWNSRV
  

Problem summary

• | fix pack | 5.2.5-TIV-TPC-FP0000 - target 1Q 2015 |
  
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future fix packs do not represent a formal
  commitment by IBM. The dates are subject to change without
  notice.
  
  The logging.properies file may not get copied to the production
  directory properly and edited as required for target system.
  This is especially prevelant in customers who skip a maintence
  PTF level (e.g. move from 5.2.0 to 5.2.3)...  By
  default if the installation already has a properties folder in
  the target production HFS the properties files will NOT be
  copied over or updated. This can cause an issue in installations
  of PTF's 5.2.x if the default logging.properties has already
  been copied. Manual edit / copy will be necessary.
  

Problem conclusion

Temporary fix

• 1) Edit the existing :
  /opt/Tivoli/RM/wlp/usr/servers/replicationServer/properties/logg
  ing.properties
  
  2) Replace the contents of this file with the following:
  #
  # Defines the log file for the CSM Servlet code
  #
  ServletLogger = com.ibm.storage.csm.gui.log.FileLogger
  ServletLogger.file = logs/CSM/csmGuiTrace.log
  ServletLogger.file.maxFiles = 10
  ServletLogger.file.maxFileSize = 10240
  ServletLogger.level = ALL
  
  #
  # Defines the log file for the Servlet Output Stream to the
  client.
  #
  XMLOutputLogger = com.ibm.storage.csm.gui.log.FileLogger
  XMLOutputLogger.file = logs/CSM/csmGuiXMLTrace.log
  XMLOutputLogger.file.maxfiles = 10
  XMLOutputLogger.file.maxFileSize = 10240
  XMLOutputLogger.level = ALL
  
  CacheLogger = com.ibm.storage.csm.gui.log.FileLogger
  CacheLogger.file = logs/CSM/csmGuiCache.log
  CacheLogger.file.maxFiles = 10
  CacheLogger.file.maxFileSize = 10240
  CacheLogger.file.level = ALL
  
  * note the xxxxx.file paths here are set up relative to the JVM
  working directory. If logs are not output as expected or this
  does not fix the issue please substitute the fully qualified
  path e.g.
  <-path_prefix>//opt/Tivoli/RM/wlp/usr/servers/replicationServer/
  logs/CSM/csmGuiTrace.log
  
  3) Stop and re-start IWNSRV
  

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

Applicable component levels