(C) Copyright International Business Machines Corporation 2009. All
rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent,
       Version 6.2.1

Component ID: 5724C040U

Fix: Interim Fix 0010 (6.2.1.0-TIV-ITM_UNIX-IF0010)

Date: 30 November 2009

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices


1.0 General description
=======================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.4.


2.0 Problems fixed
==================
The following problems are addressed by this fix.

  2.1 APARs
  ---------
  APAR:   IZ65644
  Abstract: UNIX OS AGENT UNABLE TO COLLECT METRICS ON AGILE DISKS
          ON HP-UX 11.31
  Additional Information: Agile disks are not shown by the UNIX OS
          Agent on HP-UX 11.31.  The UNIX OS Agent only lists the
          disks that follow the Legacy DSF naming convention.  Disks
          using the Persistent DSF naming convention that were
          introduced in HP-UX 11.31 are not displayed.  The
          environment variable MAX_NUMBER_OF_DISKS_HPUX allows the
          user to specify the maximum number of disks to monitor on
          the machine.  The environment variable EXCLUDE_LEGACY_DISKS
          set to true (EXCLUDE_LEGACY_DISKS=TRUE) can be used to
          exclude disks that follow the Legacy naming convention.

  2.2 Defects
  -----------
  None.

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

  2.4 Superseded fixes
  --------------------
  6.2.1.0-TIV-ITM_UNIX-IF0009
  6.2.1.0-TIV-ITM_UNIX-IF0008
  6.2.1.0-TIV-ITM_UNIX-IF0007
  6.2.1.0-TIV-ITM_UNIX-IF0006
  6.2.1.0-TIV-ITM_UNIX-IF0005
  6.2.1.0-TIV-ITM_UNIX-IF0004
  6.2.1.0-TIV-ITM_UNIX-LA0003
  6.2.1.0-TIV-ITM_UNIX-IF0002
  6.2.1.0-TIV-ITM_UNIX-IF0001

  2.5 APARS and defects included from superseded fixes
  ----------------------------------------------------

    6.2.1.0-TIV-ITM_UNIX-IF0009
    ---------------------------
    APAR: IZ65193
    Abstract: WRONG VALUE FOR THE "TOTAL VIRTUAL MEMORY" ATTRIBUTE OF THE
            SYSTEM ATTRIBUTE GROUP ON AIX
    Additional Information: On AIX the IBM Tivoli Monitoring Agent for UNIX OS
            reports wrong values for "Total Virtual Memory" attribute of the
            System attribute group.

    APAR: IZ64688
    Abstract: FILE CONTENT CHANGE ATTRIBUTE DOES NOT WORK AFTER THE FIRST CHANGE
    Additional Information: The "File Change" is not changing after the first
            change is triggered hence any situation monitoring that attribute
            will not work properly.

    APAR: IZ63849
    Abstract: KUXAGENT ON AIX SHOWS HIGH CPU WHEN IOSTAT DOES NOT WORK AS
            EXPECTED
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS kuxagent
            process shows high cpu when the command /bin/iostat does not work as
            expected, i.e., when iostat returns an error message or iostat is not
            present on the machine. The UNIX OS Agent should handle this
            particular case by simply stopping to collect metrics for the "Disk
            Performance" attribute group and logging it.

    APAR: IZ63160
    Abstract: THE ITM 6.2.1 TEP DOESN'T ALLOW USER TO CREATE SITUATIONS FOR
            CPU UTILIZATION WITH VALUES GREATER THAN 100
    Additional Information: It is not possible to create a situation with a value
            "Process Cpu Utilization" (UNIXPS.CPU) greater than 100. If you try
            to do it, TEP highlights the value in red as it considers it invalid.

    APAR: IZ62782
    Abstract: HUGE PROCESS ELAPSED TIME ON SOLARIS SYSTEMS WITH ITM UX UNIX OS
            AGENT
    Additional Information: On Solaris, the IBM Tivoli Monitoring Agent for UNIX
            OS returns a huge value for the attribute ElapsedTime of the Proccess
            attribute group for zombie processes. This value is equal to the
            system time of the Solaris OS, with values of 14000+ days.

    APAR: IZ62784
    Abstract: STRANGE VALUES FOR PROCESSES TIME ATTRIBUTES ON SOLARIS
    Additional Information: On Solaris, the IBM Tivoli Monitoring Agent for UNIX
            OS returns strange timestamp values for some process attributes.
            Soma example of values returned for CPU time are the following:
               000d00:00:-0 or 1.09063E+15
            This may also be reported as negative or invalid values for times for
            process attributes in Tivoli Data Warehouse (TDW).

    6.2.1.0-TIV-ITM_UNIX-IF0008
    ---------------------------
    APAR: IZ56215
    Abstract: AGENT FILES DO NOT CONTAIN RUNSON TAGS
    Additional Information: The file kux_tmsdla.xml of the IBM Tivoli Monitoring
            agent for UNIX OS does not contain the runsOn tags. This causes
            problems with consistent mapping of appname/computer name when the
            idml book generated by tmsdla is consumed into IBM Tivoli Business
            Service Manager (TBSM) or IBM Tivoli Application Dependency
            Discovery Manager. This APAR is coupled to APAR IZ45340 that is
            tracking the needed changes on the tmsdla utility.

    APAR: IZ59021
    Abstract: KUXAGENT HANGS AT STARTUP ON SOLARIS WITH TWO KUXAGENT PROCESSES
    Additional Information: The IBM Tivoli Monitoring agent for UNIX OS process
            (kuxagent) hangs at startup in a vfork while spawning the
            stat_daemon process for a known issue of the Solaris vfork.
            Two kuxagent processes in hang are a symptom of this problem.

    APAR: IZ60264
    Abstract: INCORRECT VALUES FOR SWAP SPACE METRICS ON AIX
    Additional Information: The value of the metrics "Available Swap Space",
            "Total Swap Space", "Percent Swap Space Used", "Percent Swap Space
            Available", and "Swap Space Free" do not match with AIX operating
            system commands such as "lsps -s".

    Defect: 112690
    Abstract: Description in ux sit not ok if its superseded

    Defect:   114561
    Abstract: Wrong memory allocation for the username and groupname strings

    6.2.1.0-TIV-ITM_UNIX-IF0007
    ---------------------------
    APAR: IZ50683
    Abstract: WRONG REAL TOTAL MEMORY
    Additional Information: On AIX, the IBM Tivoli Monitoring Agent for UNIX OS
            collects the total real memory installed on the machine only at
            the start-up, but the total real memory can change without a server
            restart.

    APAR: IZ50834
    Abstract: ITM IDML BOOK CONTAINS INVALID MAPPING - UNIX OS AGENT
    Additional Information: In a private IP network, when running tmsdla you may
            get messages like:
                 "No default template found".
            The resulting idml book is therefore invalid, and when loading the
            book into IBM Tivoli Application Dependency Discovery Manager
            (TADDM) using loadidml, you will get the following errors:
                2008-11-11 06:50:32,326   main   ERROR bulk.CdbRandomAccess
                - Invalid relationship entry located in file:
                <cdm:installedOn source="xxxxx" target="yyyyy"/>
                2008-11-11 06:50:32,326   main   ERROR bulk.CdbRandomAccess
                - The source or target in a relationship defintion were
                not found in the file.
            where xxxxx is the source address, and yyyyy is the target address.

    APAR: IZ51663
    Abstract: PROCESS MISSING SITUATION MIS-FIRING WITH GREAT PROCESS ACTIVITY
    Additional Information: A process missing situation could mis-fire on AIX
            if many processes start in a short timeframe (less than 2 seconds).

    APAR: IZ52165
    Abstract: KUX_VMSTAT PROCESS HANGS RESULTING IN REPEATED CPU AND VIRTUAL
            MEMORY METRICS ON AIX
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS helper
            process kux_vmstat process hangs. As a consequence, the CPU and
            virtual memory metrics will always be the same from the moment of
            the hang onward. The process hangs because a system call abnormally
            takes more that 30s to complete and this results in errors in the
            computation of the sleep time.

    APAR: IZ53750
    Abstract: UNABLE TO COLLECT THE "GROUP NAME" ATTRIBUTE (RESULT TOO LARGE)
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS is not
            able to collect the "Group Name" attribute due to a small buffer
            used with getgrgid_r(). The logs will report the following error:
            "Result too large".

    Defect: 86707
    Abstract: Agent files do not contain runsOn tag(s) so relationships are not
            mapped.
    Additional Information: The agent file knt_tmsdla.xml does not contain the
            runsOn tags. This causes problems with consistent mapping of
            appname/computer name when the idml book generated by tmsdla is
            consumed into TBSM or TADDM.

    Defect: 105837
    Abstract: port of 96339: Agent xml files, e.g. knt_tdmdla, in wrong directory
    Additional Information:Installation of TEPS lays down the agent files
            (knt_tmsdla.xml) under the wrong directory path. This causes the
            tmsdla to only use the tmsdla_default.xml which results in a IDML
            book with very little information about the agent.

    6.2.1.0-TIV-ITM_UNIX-IF0006
    ---------------------------
    APAR: IZ52973
    Abstract: KUXAGENT ON SOLARIS UNEXPECTEDLY EXITS WHEN THE PROCESS ARGUMENT
             STRING IS VERY LONG.
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS on
            Solaris may crash if a process argument is longer than 20000
            characters.

    6.2.1.0-TIV-ITM_UNIX-IF0005
    ---------------------------
    APAR: IZ50401
    Abstract: MEMORY LEAK IN KUXAGENT WHEN RETRIEVING PROCESS DATA ON AIX
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS kuxagent
            process leaks when handling requests for the UNIXPS attribute
            group on certain AIX levels. The problem has been ascertained on
            AIX TL4 and AIX TL5. The fix uses a cache for the resolution of
            UID/GID in usernames/groupnames. The environment variable
            UID_USERNAME_REFRESH_TIME that can be specified in the
            configuration file ux.ini allows the user to set the refresh time
            in minutes for the cache. If the environment variable is not
            specified, the agent uses the default refresh time of 60 minutes.
            Please also note that specifying UID_USERNAME_REFRESH_TIME=0
            results in the cache not being used at all.

    APAR: IZ51116
    Abstract: HIGH CPU UTILIZATION IN THE PROCESS WORKSPACE ON SOLARIS
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS kuxagent
            process spikes in CPU when handling requests for the UNIXPS
            attribute group on Solaris 5.8 machines, when interacting with a
            third-party authentication software. The fix uses a cache for the
            resolution of UID/GID in usernames/groupnames. The environment
            variable UID_USERNAME_REFRESH_TIME that can be specified in the
            configuration file ux.ini allows the user to set the refresh time
            in minutes for the cache. If the environment variable is not
            specified, the agent uses the default refresh time of 60 minutes.
            Please also note that specifying UID_USERNAME_REFRESH_TIME=0
            results in the cache not being used at all.

    APAR: IZ50471
    Abstract: KUXAGENT CRASHES ON SOLARIS IN CONVERT_TO_TIMESTAMP
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS kuxagent
            process crashes on Solaris in the convert_to_timestamp function,
            with the a stack trace that can be similar to the following:

    /opt/IBM/ITM/sol296/ux/bin/kuxagent:stacktrace_handler+0x58
    /lib/sparcv9/libc.so.1:0xd418c
    /lib/sparcv9/libc.so.1:0xc7d28
    /lib/sparcv9/libc.so.1:0xc7f20
    /opt/IBM/ITM/sol296/ux/bin/kuxagent:__1cUconvert_to_timestamp(...)
    /opt/IBM/ITM/sol296/ux/bin/kuxagent:__1cRsave_process_data6FpnIps_table(...)
    /opt/IBM/ITM/sol296/ux/bin/kuxagent:__1cSget_entire_process6FpnIps_tabl(...)
    /opt/IBM/ITM/sol296/ux/bin/kuxagent:__1cMget_ps_table6FpnIps_table__i_(...)
    /opt/IBM/ITM/sol296/ux/bin/kuxagent:__1cSomunx_unixps_agentKTake(...)

    Defect: 87462
    Abstract: Sit for the missing file does not trigger as expected

    6.2.1.0-TIV-ITM_UNIX-IF0004
    ---------------------------
    APAR: IZ45137
    Abstract: SOME VALUES COMBINED IN PROCESS COMMAND ATTRIBUTE.
    Additional Information: On the Tivoli Enterprise Portal, the process
              "Command" Attribute may display some garbage in the "Command"
              attribute for the processes of the Monitoring agent for UNIX
              OS.  Specifically, if you open the Tivoli Enterprise Portal,
              right-click on "Process", then select "Workspace", and click
              on "All Processes", the "Command (unicode)" column may display
              the process command together with some additional garbage (i.e.
              the command of a different process).

    APAR: IZ45383
    Abstract: ITM UNIX OS AGENT DOESN'T EXIT GRACEFULLY WHEN TACMD COMMAND
            IS USED TO INSTALL A PATCH
    Additional Information: When using tacmd update agent to upgrade the
            Monitoring agent for UNIX OS, the installation of the patch fails
            with the following message:
               "the agent was not installed because there is not enough disk
               space on the server or you do not have permission to install
               the agent."
            However, both the disk space and the permissions are correct.

    APAR: IZ49452
    Abstract: STAT_DAEMON HIGH CPU IF PHYSICAL DISK NAMES ARE LONG ON AIX
    Additional Information: On AIX, the IBM Tivoli Monitoring Agent for UNIX OS
            helper process stat_daemon process shows a high CPU usage if
            physical disk names are long.

    APAR: IZ49507
    Abstract: KUXAGENT CRASH ON SOLARIS WHEN UNABLE TO COLLECT DISK DATA FOR
            MOUNT POINT
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS kuxagent
            will crash on Solaris when it is unable to collect disk data for
            mount point. The last function of the stack trace is
            _string_to_decimal.

    Defect: 96254
    Abstract: Unable to collect aggregate cpu statistics on old AIX 5.3 MLs

    6.2.1.0-TIV-ITM_UNIX-LA0003
    ---------------------------
    APAR: IZ40154
    Abstract: ITM UNIX OS AGENT 06.20.01.00 LOCAL LOGFILE GROWS BY 2MB/HOUR OR
            MORE, LEADING TO AGENT FAILURE.
    Additional Information:  The size of the log file of the IBM Tivoli
            Monitoring Agent for UNIX OS will increase (more or less by
            2MB/hour) so to lead to the agent's failure on AIX, because it is
            not possible to disable the logging for the UNIX Printer queues.

    6.2.1.0-TIV-ITM_UNIX-IF0002
    ---------------------------
    APAR: IZ38759
    Abstract: STAT_DAEMON CONSUMING HIGH CPU AFTER SOME DISKS ARE PUT OFFLINE
    Additional Information: In systems where disks go offline and online
            frequently, such as data mover machines, the IBM Tivoli Monitoring
            Agent for UNIX OS helper process stat_daemon may hang, after some
            disks operations are performed.

    APAR: IZ40188
    Abstract: THE UNIX OS AGENT TERMINATED SOON AFTER START UP.
    Additional Information: When LC_ALL=Ja_JP is set in the environment
            variable, the IBM Tivoli Monitoring Agent for UNIX OS terminates
            soon after the agent is started up.

    APAR: IZ42543
    Abstract: Aggregate CPU statistics on a shared-CPU AIX LPAR do not match
            with mpstat, vmstat and lparstat.
    Additional Information: On a shared-CPU AIX LPAR, the aggregate CPU
            statistics "User CPU (Percent)", "System CPU (Percent)", "Idle CPU
            (Percent)" and "Wait I/O (Percent)" that belong to the "System"
            attribute group do not match with the corresponding metrics of the
            AIX commands mpstat, vmstat and lparstat. In particular, the IBM
            Tivoli Monitoring Agent for UNIX OS aggregates the CPU statistics by
            averaging over the number of logical CPUs, whereas the mpstat,
            vmstat and lparstat take into account further partition data such
            as the entitled CPU capacity.

    APAR: IZ46984
    Abstract: ITM UNIX OS AGENT'S ON FAST SOLARIS BOXES HANGS AT START-UP
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS hangs
            at start-up after a quick stop and start on powerful Solaris
            systems.

    6.2.1.0-TIV-ITM_UNIX-IF0001
    ---------------------------
    APAR: IZ33792
    Abstract: UNIXNET IS USING DIFFERENT AGGREGATION TYPES
    Additional Information: Network attributes "Frames_Received" and
            "Frames_Transmitted" have been defined with different aggregation
            rules (Gauge and Count respectively). This implies that the
            Summarization and Pruning agent will perform a different
            aggregation on the two attributes. In addition to that, also the
            following attributes have the wrong aggregations available:
            Input_Errors, Output_Errors, Collisions. They were considered as
            COUNT (TOT, HI, LOW, LAT), and should be on the contrary considered
            as GAUGE (MIN, MAX, SUM, AVG).

    APAR: IZ37604
    Abstract: ITM 6.2 UNIX AGENT CRASHES WHEN PROCESS NAMES ARE LONGER THAN
            2000 CHARACTERS
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS on
            Solaris may crash if the process name or some arguments are longer
            than 2000 characters.

    APAR: IZ39999
    Abstract: UNIX AGENT UNABLE TO DETERMINE THE CORRECT NUMBER OF SPUS ON
            HP-UX NPARS
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS is
            currently unable to determine the correct number of SPUs on HP-UX
            nPARs. The APAR will address the following: determine the correct
            number of SPUs allocated to the current nPar, to be distinguished
            between Active, Disabled, Failed and In Transition.

    APAR: IZ41918
    Abstract: PROCESS MISSING SITUATION ERRONEOUSLY FIRES ON AIX FOR PROCESSES
            WITH HIGH PID NUMBERS
    Additional Information: Process missing situation fires erroneously on AIX
            for processes with high PID numbers, i.e., the situation triggers
            for a missing process but the process is actually up and running as
            witnessed by a ps -ef. The situation is obviously expected not to
            fire false alerts, but it does.

    APAR: IZ42141
    Abstract: ITM UNIX OS AGENT'S KUX_VMSTAT PROCESS HANGS AT STARTUP ON AIX
    Additional Information: The IBM Tivoli Monitoring Agent for UNIX OS helper
            process kux_vmstat hangs at startup on AIX 5.2 when reading CPUs
            metrics.


3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: UNIX OS Agent User's Guide, version 6.2.1.

The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.

 http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

  3.1 Prerequisites for this fix
  ------------------------------
  - IBM Tivoli Monitoring, Version 6.2.1


4.0 Image directory contents
============================
This fix image contains the following files:

- 6.2.1.0-TIV-ITM_UNIX-IF0010.README  - This README file
- 6.2.1.0-TIV-ITM_UNIX-IF0010.tar     - Fix archive .tar format
- 6.2.1.0-TIV-ITM_UNIX-IF0010.zip     - Fix archive .zip format

NOTE: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX environment; use the .zip file if
you are working in a Microsoft Windows(R) environment.

The fix archive file contains the following :

- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_tems_teps_tepd_if0010.tar - UNIX Agent support files for tems/teps
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_tems_teps_tepd_if0010.zip - Windows TEPS Support files.
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_aix523_tema_if0010.tar    - UNIX Agent binaries for AIX 32-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_aix526_tema_if0010.tar    - UNIX Agent binaries for AIX 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_hp11_tema_if0010.tar      - UNIX Agent binaries for HP-UX 32-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_hp116_tema_if0010.tar     - UNIX Agent binaries for HP-UX 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_hpi116_tema_if0010.tar    - UNIX Agent binaries for HP-UX Itanium.
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_sol283_tema_if0010.tar    - UNIX Agent binaries for Solaris 8 32-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_sol286_tema_if0010.tar    - UNIX Agent binaries for Solaris 8 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_sol293_tema_if0010.tar    - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_sol296_tema_if0010.tar    - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kux_sol606_tema_if0010.tar    - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxaix523.dsc                 - Descriptor file for AIX 32-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxaix526.dsc                 - Descriptor file for AIX 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxsol283.dsc                 - Descriptor file for Solaris 8 32-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxsol286.dsc                 - Descriptor file for Solaris 8 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxsol293.dsc                 - Descriptor file for Solaris 9/10 32-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxsol296.dsc                 - Descriptor file for Solaris 9/10 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxsol606.dsc                 - Descriptor file for Solaris 10 Opteron 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxhp11.dsc                   - Descriptor file for HP-UX 32-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxhp116.dsc                  - Descriptor file for HP-UX 64-bit
- 6.2.1.0-TIV-ITM_UNIX-IF0010/kuxhpi116.dsc                 - Descriptor file for HP-UX Itanium

Each tar or cab file has updates to the IBM Tivoli Enterprise Monitoring
Server component for a specific platform. The platform that each file
applies to is included in its name.

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 under section 3.1 entitled 'Prerequisites
    for this fix' must be installed before this fix can be installed.

  - 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

  5.2 Local agent update
  ----------------------
  1. Transfer the appropriate archive file
     (e.g. 6.2.1.0-TIV-ITM_UNIX-IF0010.tar) to a temporary directory
     on the system that contains the agent code to be updated.
     For the purpose of this README, the symbol <TEMP> represents
     the fully qualified path to this directory.

  2. Expand the archive file using the tar command. This creates a directory
     structure that contains fixes for all of the supported platforms.

  3. Use the itmpatch command to install the fix for that agent platform.
     For more information on the itmpatch command, see section 6.1

     For example:
     On a UNIX system, if the fix was expanded to
     <TEMP>/6.2.1.0-TIV-ITM_UNIX-IF0010, the install command would be:

     > itmpatch -h <CANDLEHOME>
                -i <TEMP>/6.2.1.0-TIV-ITM_UNIX-IF0010/kux_xxxxxx_tema_if0010.tar

       where:
          - xxxxxx corresponds to the value in the first column returned
             by the ./cinfo -i command.

       In the following example, the file would be kux_aix523_tema_if0010.tar
       > ./cinfo -i
       ux      Monitoring Agent for Unix OS
                   aix523  Version: 06.21.00.00


  5.3 Remote agent update
  ------------------------
  1. Transfer the appropriate archive file
     (e.g. 6.2.1.0-TIV-ITM_UNIX-IF0010.tar or .zip) 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, this includes
     the drive letter.

  2. Expand the archive file using the tar command on UNIX systems or
     an unzip utility on Windows systems. This 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.

     For example:
     On UNIX systems,
     if the fix was expanded to <TEMP>/6.2.1.0-TIV-ITM_UNIX-IF0010
     > $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.1.0-TIV-ITM_UNIX-IF0010

     On a Windows system,
     if the fix was expanded to <TEMP>/6.2.1.0-TIV-ITM_UNIX-IF0010
     > %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.1.0-TIV-ITM_UNIX-IF0010

     where:
         -n indicates that prerequisite bundles are not automatically
            added. The -n parameter must be used because the fix
            directory does not contain any prerequisites that the fix
            might require.  Please see Section 3.1 for the prerequisites
            for this fix.
         -i is the directory that contains the deployment bundles to be
            added to the depot.

  4. To login 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 updateAgent commands, see the IBM Tivoli Monitoring
     Administrator's Guide.

     For example:
     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 of the
     tacmd updateAgent command.

     > $CANDLEHOME/bin/tacmd updateAgent -t ux
                                         -n <Managed System Name>
                                         -v 062100010

     On a Windows system:
     > %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 of the
     tacmd updateAgent command.

     > %CANDLEHOME%/bin/tacmd updateAgent -t ux
                                          -n <Managed System Name>
                                          -v 062100010

     Note:
         - The component (-t) for the updateAgent command is specified as
           two characters (ux), not three characters (kux).
         - The node (-n) for the updateAgent command is the managed system
           name of the operating system (OS) agent to be updated. The
           target node for an updateAgent command is always an OS agent.

  5.4 Agent support update
  ------------------------
  Use the following steps to update the Tivoli Enterprise Monitoring
  Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal
  Desktop.

  1. Transfer the appropriate archive file (on UNIX systems
     6.2.1.0-TIV-ITM_UNIX-IF0010.tar and on Windows systems
     6.2.1.0-TIV-ITM_UNIX-IF0010.zip) to the IBM Tivoli Enterprise Monitoring
     Servers, IBM Tivoli Enterprise Portal Servers and Tivoli Enterprise
     Portal Desktop.

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

  3. Expand the archive file (e.g
     6.2.1.0-TIV-ITM_UNIX-IF0010\kux_tems_teps_tepd_if0010.tar on UNIX
     systems or 6.2.1.0-TIV-ITM_UNIX-IF0010\kux_tems_teps_tepd_if0010.zip
     on Windows systems) that contains the updates for Tivoli Enterprise
     Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli
     Enterprise Portal Desktop using the tar command on UNIX
     systems or an unzip utility on Windows systems. This creates a
     directory structure that includes a subdirectory called CD-ROM,
     with the necessary updates.

  4. Start the Application Support Installer GUI to install the fix.
     The GUI can be started by using one of the following commands
     from within the CD-ROM directory where setup.jar is located.

     On UNIX systems:
          > $CANDLEHOME/JRE/<platform>/bin/java -jar setup.jar

     On a Windows system:
          > <"C:\Program Files\IBM\Java142">\jre\bin\java -jar setup.jar

          where <"C:\Program Files\IBM\Java142"> is the default drive
          and location of IBM Java 1.4.2. The location of IBM Java 1.4.2
          on your system might vary.

     When prompted by the Application Support Installer for the
     installable media directory, select the CD-ROM directory, not the
     component directory. The installer can install updates for
     multiple components at the same time.

  5. The next panel presented by the Application Support Installer asks
     for the selection of which three Tivoli Monitoring components you
     would like to add application support to. For this fix the check
     boxes should be as follows:

             checked - Tivoli Enterprise Monitoring Server(TEMS)
             checked - Tivoli Enterprise Portal Server(TEPS)
             checked - Tivoli Enterprise Desktop Client(TEPD)

     Continue through the remaining GUI panels selecting the Unix OS Agent
     06.21.00.10 support to complete the installation.

  6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal
     Browser was running when the update was installed, it must be
     restarted.


6.0 Additional installation information
=======================================

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

  6.2 Additional information on using itmpatch command
  -----------------------------------------------------
  The itmpatch command has the following syntax.

  Usage: itmpatch -h <installation home> [OPTIONS]

  itmpatch -h <installation home>
           -i { <patch_file_directory> | <patch_file> }

  itmpatch -h <installation home>
           -t { <patch_file_directory> | <patch_file> }

  where:
  -h  Specifies the IBM Tivoli Monitoring installation directory
  -i  Specifies the path to the directory or patch file to be installed
  -t  Generates a report of the actions to be taken by the patch

  For example, on UNIX systems:
  <CANDLEHOME> points to the IBM Tivoli Monitoring installation directory
  <TEMP> points to the temporary directory where the fix is located.

  - To preview the fix installation, use the "-t" option:
    > <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

  - To install the fix, use the "-i" option:
    > <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

  where:
  <CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
  installation directory. On Windows, this must include the drive
  letter.
  <TEMP> represents the fully qualified directory specification, where
  the fix is located. On Windows, this must include the drive letter.

  6.2 Verifying the update
  -------------------------
  1. To verify 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 login 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>
     > $CANDLEHOME/bin/tacmd listSystems -t ux

     On a Windows system, 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 ux

     When the agent update is successful, the agent version should now
     be:
     06.21.00.10

     Note:
     - The component (-t) for the tacmd listSystems command is specified
       as two characters UX, not three characters KUX.

  2. To verify the agent support files were updated correctly, use the
     kincinfo command on Windows systems or the cinfo command on Linux
     or UNIX systems. The sample output below shows the versions of
     the Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring
     Server, or Tivoli Enterprise Portal Desktop systems after this
     fix has been successfully applied.

     Note:
     - The date of the build displayed might not be accurate. This is a
       known problem.


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

     ./cinfo -i

      This command offers you four options on the CINFO menu shown in
      the example that follows.  Choose the option that meets your needs.

      *********** Mon Apr 06 05:03:29 EST 2009 ******************
      User      : root         Group: system bin sys security cron audit lp
      Host name : candleaix3   Installer Lvl:06.21.00.00
      CandleHome: /data/rthan/fp1temsteps
      ***********************************************************

          -- CINFO Menu --
       1) Show products installed in this CandleHome
       2) Show which products are currently running
       3) Show configuration settings
       4) Show installed CD release versions
       X) Exit CINFO
      1

      *********** Mon Apr 06 05:03:29 EST 2009 ******************
      User      : root         Group: system bin sys security cron audit lp
      Host name : candleaix3   Installer Lvl:06.21.00.00
      CandleHome: /data/rthan/fp1temsteps
      ***********************************************************
      ...Product inventory
       .
       .
       .

      ux      Monitoring Agent for UNIX OS
               aix523  Version: 06.21.00.10
               tms     Version: 06.21.00.10
               tps     Version: 06.21.00.10

       .
       .
       .

    Sample output of the kincinfo command on a Windows System
    ---------------------------------------------------------
    To validate that all components have been installed, run the
    following command kincinfo -i and check UNIX OS Support Version.


7.0 Known problems and workarounds
==================================
None.


8.0 Additional product information
==================================
None.


9.0 Notices
===========
This information was developed for products and services offered in the United
States. IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for information
on the products and services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify
the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

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 states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

Trademarks and Service Marks
----------------------------
IBM, the IBM logo, and ibm.com(R) are trademarks or registered
trademarks of International Business Machines Corporation in the
United States, other countries, or both. If these and other IBM
trademarked terms are marked on their first occurrence in this
information with a trademark symbol (R or TM), these symbols
indicate U.S. registered or common law trademarks owned by IBM
at the time this information was published. Such trademarks may
also be registered or common law trademarks in other countries.
A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at
http://www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.

Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Other company, product, or service names may be trademarks or service
marks of others.
