1.0 General description

==================
This fix pack includes the superseded fixes listed in section 2.4. It updates the IBM Tivoli Monitoring framework components to v6.3.0 Fix Pack 07 Service Pack 6, including the IBM SDK Java® Technology Edition Java Runtime Environment (JRE) and the IBM GSKit Security Interface.

2.0 Problems fixed

===============

  2.1 APARs
  -------------

    APAR: DT363530
  Abstract: LFA agent prints "Not found" messages in the agent logs.
  Additional information: Log File agent logs is flooded with "Not found" messages, filling up the log space and resulting in high disk space usage.
  A recent change made to fix an APAR of the Log File Agent caused flooding of "Not found" messages in one of the log file of LFA agent due to an unwanted print statement.
 
  2.2 Defects
  --------------
    None

  2.3 Enhancements  
  ---------------------
  None

  2.4 Superseded fixes
  -------------------------

  2.5 APARs and defects included from superseded fixes
  ---------------------------------------------------------------
  
    6.3.0.7-TIV-ITM_LFA-IF0003
  -------------------------------------
    APAR: IJ47476
    Abstract: Log File Agent crashes during repetitive replacement of .conf and .fmt files.     
    Additional information:  When TransportList is used in the .conf file, replacing the .conf and .fmt files multiple times causes the agent to crash.
    
    Defect: 219278
    Abstract: Log File Agent crashes when ETX control character encountered.
    Additional information:  Log File Agent crashes when agent encounters ETX control character in log line.
    Stack Trace:
    Segmentation fault in List::add(const void*) at 0x10000c5e4 ($t74)
    0x10000c5e4 (List::add(const void*)+0x30) 9064000c            stw   r3,0xc(r4)
    (dbx) where
    List::add(const void*)(0x0, 0x113475bd0) at 0x10000c5e4
    LogMonitorQueryClass::expandForLFA(const char*,Metric*,char*,int*,bool,char*,HashMap*)(0x11130e1d0, 0x113473f10, 0x11013c110, 0x113473b70, 0x11157deb8, 0x100000000000001, 0x1134724b0, 0x113469a70) at 0x100154e0c
    LogMonitorQueryClass::setInstanceData(char*(*)[2],int,char*,char*)(0x11130e1d0, 0x113477b70, 0x200000002, 0x113473810, 0x113473b70) at 0x100156b34
    LogMonitorQueryClass.dataCallbackFunc(const char*,const char*,const char*,const char*,char*(*)[2],int)(0x11346cd50, 0x11346d870, 0x113473810, 0x113473b70, 0x113477b70, 0x200000002) at 0x1001574dc
    KUMP_PerformDataCallback(0x110056760, 0x11346cd50, 0x11346d870, 0x113473810, 0x113473b70, 0x113477b70, 0x200000002) at 0x900000018dfaa58
    KUMP_DequeueDCHWork(0x11157e510) at 0x900000018dfa318
    KUMP_DCHclientRoutine(0x111565c10) at 0x900000018dfd0a0
      
  -------------------------------------

    6.3.0.7-TIV-ITM_LFA-IF0002
  -------------------------------------
  APAR: IJ45819
  Abstract: Memory leak in LFA 6.3.0 FP7
  Additional information:  Log File Agent when upgraded from 6.3.0 Fix Pack 03 to 6.3.0 Fix Pack 07 high memory consumption was observed under heavy load.
    High memory leak is observed only when DISCARD event is used in the FMT file.
      
  -------------------------------------
      6.3.0.7-TIV-ITM_LFA-IF0001
  -------------------------------------
  APAR: IJ39278
  Abstract: LOG FILE AGENT STOPS FORWARDING EVENTS TO EIF RECEIVER WITH LARGE EVENT.
  Additional information: The problem occurs when the Log File Agent is configured to send EIF events, the .conf file contains the BufferEvents and EventMaxSize keywords and an event larger than the EventMaxSize is processed. The event is written to the .cache file, but there is an issue when EIF reads the event from the .cache file to forward to the EIF receiver.
    At this point no new events are being sent to the EIF receiver and the .cache file gets filled with events.

    Install Actions: If the .cache file continues to grow due to the above  issue, after the fix is installed, then you need to stop the agent, remove the .cache file, and then restart the agent. This will result in a new .cache file being created which allows messages to be forwarded again.

  Defect: 219237
  Abstract: Log File agent crashes when CTIRA_HOSTNAME is not set and LABEL used.
  Additional information:  If the .fmt uses the keyword LABEL, for example hostname  LABEL it will try to use the value for CTIRA_HOSTNAME.  If that is not set the agent will crash.
      
See 6.3.0-TIV-ITM_LFA-FP0007.README for a list of APARs and fixes included from
  superseded fixes.

     

3.0 Architecture and prerequisites

==========================
This fix is supported on all operating systems listed in the Tivoli Log File Agent User's Guide, version 6.3.0.

The following link is for the Tivoli operating system and application support matrix. Refer to this matrix for the latest certification information.
Refer to the IBM Software Product Compatibility Reports (SPCR) for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html
                                          
  3.1 Prerequisites for this fix
  --------------------------------

  The installer included in this fix includes APAR IJ37912, which checks if the system is running multiple components and if so it must be at ITM 6.30 FP7 Service Pack 6 (or later) and if not, then the installer stops and displays a message (or writes to the log in the case of remote deploy) indicating that:
    SP06 or later framework must be installed to continue.

  When installing the fix on a system running only the Log File Agent, the installation can continue and the shared components will be upgraded to the ITM 6.30 FP7 SP6 level.

In summary:
   - If you install this fix on system where only the Log File Agent has been previously installed, the installation can continue.
   - If you install this fix on a system where along with Log File Agent other agents or server components are also installed, then the framework must first be upgraded to ITM 6.30 FP7 SP6 (or later) before this Log File Agent Fix Pack 08 can be installed.   
   - If you install this fix by using remote deploy, the remote system must be at ITM 6.30 FP7 SP6 (or later).

 

5.0 Installation instructions

=====================

This fix can only be installed over an existing installation.  Use the following steps to install this fix.

  5.1 Before installing the fix 
  -------------------------------
  - The prerequisites listed in section 3.1 entitled 'Prerequisites for this fix' must be installed before you install this fix. 
    
  - For the purpose of this README, the symbol <CANDLEHOME> is the IBM Tivoli Monitoring installation directory. The default value for <CANDLEHOME> is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM' on Windows systems.

  - Before installing this fix on UNIX systems, set the environment variable <CANDLEHOME> to the IBM Tivoli Monitoring installation directory.
        
    For example: 
    > CANDLEHOME=/opt/IBM/ITM
    > export CANDLEHOME  
  
  - As there is no uninstall utility for this fix, make sure to back up your environment before installing this fix.

  5.2 Local agent update
  -----------------------
  For installation instructions, see the Log File Agent User's Guide v6.3.0: 
  http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/logfile/logfileagent_user.htm?lang=en
  
  Note: 

5.3 Remote agent update
  ----------------------------
1. Transfer the archive file 6.3.0-TIV-ITM_LFA-FP0008.tar.gz to a temporary directory on the IBM Tivoli Enterprise Monitoring Server system. For the purpose of this README, the symbol <TEMP> represents the fully qualified path to this directory.

Note: On Windows systems, this path includes the drive letter.

2. Expand the archive file by using the "tar" command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that contains fixes for all of the supported platforms.

3. To add the agent fix bundles into the remote deploy depot, use the "tacmd addBundles" command found in $CANDLEHOME/bin on UNIX systems or in %CANDLE_HOME%\bin on Windows systems. For more information on the "tacmd addBundles" command, see the IBM Tivoli Monitoring Administrator's Guide.

     Note:

     

       On UNIX systems, 
       If the fix was expanded to <TEMP>/KLO_DVD-202404240032-41151:
      > $CANDLEHOME/bin/tacmd addBundles -t LO -i <TEMP>/KLO_DVD-202404240032-41151/unix
     
     On Windows systems, 
     If the fix was expanded to <TEMP>\KLO_DVD-202404240032-41151:
     > %CANDLE_HOME%\bin\tacmd addBundles -t LO -i <TEMP>\KLO_DVD-202404240032-41151\WINDOWS\Deploy

     
       where:
         -i is the directory that contains the deployment bundles to be added to the depot. 

4. To log in to the Tivoli Enterprise Monitoring server and deploy the fix to the appropriate nodes where the agent is running, use the following "tacmd" commands.  For more information on the "tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli Monitoring Administrator's Guide.

     On UNIX systems: 
     > $CANDLEHOME/bin/tacmd login -s <server>
                                   -u <itmuser> 
                                   -p <password>
                                   
     > $CANDLEHOME/bin/tacmd listSystems
          
     The output shows the Managed System Name for the OS agent on the remote system to be updated. Use this value as the target in the "tacmd updateAgent" command.
     
     > $CANDLEHOME/bin/tacmd updateAgent -t lo 
                                         -n <Managed system name>
                                         -v 06300800

     On Windows systems:
     > %CANDLE_HOME%\bin\tacmd login -s <server>
                                    -u <itmuser> 
                                    -p <password>
                                    
     > %CANDLE_HOME%\bin\tacmd listSystems
          
     The output shows the Managed System Name for the OS agent on the remote system to be updated. Use this value as the target in the "tacmd updateAgent" command.
     
     > %CANDLE_HOME%\bin\tacmd updateAgent -t LO 
                                        -n <Managed system name>    
                                        -v 06300800
                              
     Note:
     - The component (-t) in the "tacmd updateAgent" command is specified as two characters (LO), not three characters (KLO).
     - The node (-n) in the "tacmd updateAgent" command is the managed system name of the operating system (OS) agent to be updated.
      - The target node in the "tacmd updateAgent" command is always an OS agent.

  5.4 Agent support update
  ------------------------------

There are no agent support updates for the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal Desktop included in this fix. No additional installation steps are required.
  

6.0 Additional installation information

=============================

 6.1 Updates to shared components
  ----------------------------------------
 Note: This fix pack includes updates to the following shared components that might be installed into the IBM Tivoli Monitoring installation directory (for example, CANDLEHOME), if a later version does not already exist. These shared components are at the same levels that are shipped as a part of 6.30 FP7 Service Pack 6.

       - IBM Tivoli Monitoring framework (ax/gl) component to version 6.30.07.13 

       - IBM GSKit Security Interface to version 08.00.55.17

       - IBM Tivoli Monitoring installer version to 6.30.07.12

       - IBM Tivoli Monitoring user interface version to 6.30.07.12

       - IBM SDK Java Technology Edition Java Runtime Environment (JRE) for the JRE installed in the CANDLEHOME directory:

          

         - 1.8.0 SR6 FP15 for CANDLEHOME on AIX, Linux, Solaris amd64, and Windows.

         - 1.8.0 SR6 FP10 for CANDLEHOME on HP-UX ia64

         - 1.7.0 SR10 FP70 for CANDLEHOME on HP-UX PA-Risc

         - 1.7.0 SR10 FP70 for CANDLEHOME on Solaris Sparc 

         - 1.7.0 SR10 FP70 for AIX 6.1 oslevel -r less than TL7 (6100-07) and 

         - AIX 7.1 oslevel -r less than TL3 (7100-03) and for Linux RHEL < 6.0 and SLES < 11.1

 
 6.2 Installation instructions for agent baroc file
  -----------------------------------------------------
  There are no updates to the baroc files included in this fix or any of the superseded fixes.  No additional installation steps are required.
 

 6.3 Verifying the update
  ----------------------------
  1. To verify that the agent was updated correctly, use the "tacmd" command to view the agent's current version after the agent is restarted.
     You are required to log in to a Tivoli Enterprise Monitoring Server prior to viewing the agent version.  
                 
     For example:
     On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring installation directory, the default location is '/opt/IBM/ITM'.   
    
     > $CANDLEHOME/bin/tacmd login -s <server>
                                 -u <itmuser> 
                                 -p <password>

     On Windows systems, where %CANDLE_HOME% is the IBM Tivoli Monitoring installation directory, the default location is 'C:\IBM\ITM'.   

     > %CANDLE_HOME%\bin\tacmd login -s <server>
                                   -u <itmuser> 
                                   -p <password>
                                     
     > %CANDLE_HOME%\bin\tacmd listSystems -t LO 

     Note: The component (-t) in the "tacmd listSystems" command is specified as two characters (LO), not three characters (KLO).

     When the agent update is successful, the agent version is displayed as 06.30.08.00.
    
     After the agent is restarted, you can also use the GUI to verify that the agent was successfully updated.
    
     For the agent on Windows systems, the version number is displayed as 06.30.08.00.                                         

  2. To verify that all the agent components were updated correctly, use the "cinfo" command on Linux or UNIX systems or the "kincinfo" command on Windows systems. The sample output below shows the minimum versions of IBM Tivoli Monitoring framework component, IBM SDK Java Technology Edition Java Runtime Environment (JRE), and the version of the Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring Server, and Tivoli Enterprise Portal Desktop systems after this fix pack has been successfully applied.
     
     Note: The displayed date of the build might not be accurate. This is a known problem.      
                            
     On UNIX or Linux systems (except PowerPC little-endian):
     ---------------------------------------------------------
     To validate that all components have been installed, run the following command:

     ./cinfo -i    
     
     For example:
     > $CANDLEHOME/bin/cinfo -i

 
     On Windows systems:
     ---------------------
     To validate that all components have been installed, run the following command:

     kincinfo -i
    
     For example:
     > %CANDLE_HOME%\InstallITM\kincinfo -i   
    C:\Users\Administrator>kincinfo -i

********* Tuesday, May 21, 2024 11:29:59 PM **********
User       : Administrator         Group     : NA
Host Name  : COMMON2K221           Installer : Ver: 063007130
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
 
IN        Install INS/Windows Install Component
          WINNT Version: 06.30.07.15 Build: 202112071309
 
IN        TEMA(32-bit) INS/ITM 6.x Agent Install Component
          WINNT Version: 06.30.07.15 Build: 202112071309
 
IN        TEMA(64-bit) INS/ITM 6.x Agent Install Component Extensions
          WINNT Version: 06.30.07.13 Build: 202103261420
 
AC        KAC(64-bit) CMA/32/64 Bit Agent Compatibility Package
          WIX64 Version: 06.30.07.13 Build: 202103261420
 
GL        KGL(64-bit) CMA/Tivoli Enterprise Monitoring Agent Framework
          WIX64 Version: 06.30.07.15 Build: d1071a
 
GL        KGL(32-bit) CMA/Tivoli Enterprise Monitoring Agent Framework
          WINNT Version: 06.30.07.15 Build: d1071a
 
GS        KGS(64-bit) GSK/IBM GSKit Security Interface
          WIX64 Version: 08.00.55.17 Build: d1067a
 
GS        KGS(32-bit) GSK/IBM GSKit Security Interface
          WINNT Version: 08.00.55.17 Build: d1067a
 
JM        KJM(64-bit) JVM/Embedded JVM
          WIX64 Version: 08.06.15.00 Build: 202010091045
 
JM        KJM(32-bit) JVM/Embedded JVM
          WINNT Version: 07.10.35.00 Build: 201901031153
 
LO        KLO(64-bit) CMA/Tivoli Log File Agent
          WIX64 Version: 06.30.08.00 Build: 202404240032
 
NT        KNT(64-bit) CMA/Monitoring Agent for Windows OS
          WIX64 Version: 06.30.07.06 Build: 10571
 
UE        KUE(32-bit) CMA/Tivoli Enterprise Services User Interface Extensions
          WINNT Version: 06.30.07.00 Build: d6350a
 
UI        KUI(32-bit) CLI/Tivoli Enterprise Services User Interface
          WINNT Version: 06.30.07.13 Build: 202103261420
          
  3. To verify that the agent that you are running contains the updates from the fix, see the following lines in the agent log:                   
        <hostname>_lo_<instance>_kloagent_<timestamp>.log located in
     $CANDLEHOME/logs on UNIX systems and
     %CANDLE_HOME%\tmaitm6\logs on Windows systems:

     <timestamp>      Component: ira
     <timestamp>      Driver: agent-fac:202403290352/5260679.3
     <timestamp>      Timestamp: Mar 29 2024 03:52:32

7.0 Known problems and workarounds

=========================
None

8.0 Additional product information

======================
None

 

9.0 Copyright and trademark information

======================================= 
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.

10.0 Notices

============
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.