IBM Tivoli Monitoring: Unix(R) OS Agent 6.3.0.5-TIV-ITM_UNIX-IF0005

Download Description

Copyright International Business Machines Corporation 2016.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent,
Version 6.3.0 Fix Pack 5

Component ID: 5724C040U

Interim Fix 0005 (6.3.0.5-TIV-ITM_UNIX-IF0005)

Date: July 29, 2016
Updated: April 19, 2017

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 Copyright and trademark information
10.0 Notices
11.0 Change History


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: IV79797
Abstract: False alerts from situations monitoring process command lines on AIX.
Additional Information: The Monitoring Agent for UNIX OS can randomly fail to
determine the arguments associated to the command line of a running
process. In such a case it may assign to a process the command line of
another process, because of missing memory initialization in the error
code branch. Situations based on the Process.Process_Command attribute
can then trigger/not trigger improperly.

APAR: IV81845
Abstract: Monitoring Agent for UNIX OS becomes unresponsive on AIX
Additional Information: Monitoring Agent for UNIX OS becomes unresponsive on
AIX due to an incomplete response of the AIX api perfstat_netinterface

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

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

2.4 Superseded fixes
--------------------
6.3.0.5-TIV-ITM_UNIX-IF0004
6.3.0.5-TIV-ITM_UNIX-IF0003
6.3.0.5-TIV-ITM_UNIX-IF0002
6.3.0.5-TIV-ITM_UNIX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.3.0.5-TIV-ITM_UNIX-IF0004
---------------------------
APAR: IV80830
Abstract: The Monitoring Agent for UNIX OS may corrupt memory while monitoring disks
Additional Information: A condition has been identified where the buffer containing data for a filesystem
can be overridden by those for another filesystem. This memory corruption is caused by a timing condition
between two agent internal threads and it may occur when one or more filesystems do not respond within the
2 seconds default timeout for the statvfs64 system call.

6.3.0.5-TIV-ITM_UNIX-IF0003
---------------------------
APAR: IV79257
Abstract: Failure collecting historical data for the "Disk" attribute group after upgrade to 6.30 FP5
Additional Information: After the upgrade to 6.30 FP5 the Summarization and Pruning Agent starts failing to add new rows to the hourly, daily, weekly, monthly, quarterly and yearly summarized tables for the "Disk" attribute group in a DB2 Data Warehouse. This is because of new columns added to these tables' definitions that make their size cross the DB2 legacy 4Kb limit.

See Section "8.0 Additional product information" for additional steps required for
this APAR.

6.3.0.5-TIV-ITM_UNIX-IF0002
---------------------------
APAR: IV77559
Abstract: Events from situations on custom scripts do not close automatically.
Additional Information: The data gathered executing the custom scripts in 6.30 FP5 are reported using the
KXX_Custom_Scripts_Runtime attribute groups. These groups implement 'pure event' tables. Because of this,
situations cannot receive 'clearing' events and need to be manually closed. New KXX_Custom_Scripts_Rtm_Smp
sampled tables are added by this APAR. They report the same customs scripts' output data as those reported
by the existing pure event tables.

APAR: IV75908
Abstract: Missing summarized historical data for the "Unix Memory" attribute group after upgrade to 6.30 FP5
Additional Information: After the upgrade to 6.30 FP5 the Summarization and Pruning Agent starts failing to add new rows to the hourly, daily, weekly, monthly, quarterly and yearly summarized tables for the "Unix Memory" attribute group in a DB2 Data Warehouse. This is because of new columns added to these tables' definitions that make their size cross the DB2 legacy 4Kb limit.

See Section "8.0 Additional product information" for additional steps required for
this APAR.

APAR: IV74707
Abstract: Monitoring Agent for UNIX OS becomes unresponsive on AIX servers with very large volume groups.
Additional Information: he Monitoring Agent for UNIX OS may take several seconds, or minutes, to respond to
queries on the Disk Performance attribute group when running on AIX servers configured with hundreds, or
thousands, of physical volumes. This can lead various infrastructure timeouts to expire and the agent may
look like hanging.

APAR: IV75662
Abstract: The attribute UNIXDISK.Mount_Point_U is not defined as primary key.
Additional Information: The attribute Mount_Point_U of the group UNIXDISK is not defined as primary key. This
prevents its use with performance analyzer as it needs 2 primary keys.

6.3.0.5-TIV-ITM_UNIX-IF0001
---------------------------
APAR: IV70848
Abstract: The Monitoring Agent for UNIX OS does not provide an option to stop unneeded data collections
Additional Information: The Monitoring Agent for UNIX OS is sometimes only installed to support remote
deploy of other agents, or to perform take actions or other infrastructural tasks. No operating system
resources actually need to be monitored, but still the agent consumes a lot of CPU and memory because
it anyway starts its subdaemons for gathering statistical metrics (stat_daemon, ifstat, kux_vmstat,
kuxdstat, nfs_stat, mount_stat and aixdp_daemon). In order for this APAR to be properly implemented in
your environment, a new environment variable has been added. See the "Install Actions" section of the
APAR conclusion for more details.

APAR: IV71746
Abstract: The nfs_stat daemon exits also if there are available, although partial, information to collect
in Solaris systems.
Additional Information: The nfs_stat daemon of the Monitoring Agent for UNIX OS terminates when the NFS
data are not available although the RPC data are available in Solaris systems.

APAR: IV69631
Abstract: User Name field not updated when agent restarted with different userid.
Additional Information: When Watchdog is monitoring a non-OS agent and that agent is restarted with a
different userid, the Watchdog workspace Agents' Runtime Status does not update the User Name for the
process. This works correctly on Windows.

APAR: IV69716
Abstract: AIX shared memory not released by the Monitoring Agent for UNIX OS.
Additional Information: Two segments in the AIX shared memory are not released by the Monitoring Agent
for UNIX OS when it stops. These segments are allocated during initialization of the SPMI interface by
the child process aixdp_daemon and not released at shutdown time. However they are reused when the agent
starts up again.

APAR: IV74060
Abstract: Monitoring Agent for UNIX OS is not able to monitor more than 4096 disks on AIX platform.
Additional Information: Monitoring Agent for UNIX OS is not able to monitor more than 4096 disks on the
AIX platform.

Defect: 215239
Abstract: Script execution duplicate rows for the standard output

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.3.0, Fix Pack 5.

Please refer to the IBM Software Product Compatability 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
------------------------------
- IBM Tivoli Monitoring, Version 6.3.0 Fix Pack 5.


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

- 6.3.0.5-TIV-ITM_UNIX-IF0005.README - This README file
- 6.3.0.5-TIV-ITM_UNIX-IF0005.tar - Fix archive .tar format
- 6.3.0.5-TIV-ITM_UNIX-IF0005.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(R) environment; use the .zip file if
you are working in a Microsoft Windows(R) environment.

The fix archive file contains the following :
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_tems_teps_tepd_if0005.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_tems_teps_tepd_if0005.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_aix523_tema_if0005.tar - UNIX Agent binaries for AIX 32-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_aix526_tema_if0005.tar - UNIX Agent binaries for AIX 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_hp11_tema_if0005.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_hp116_tema_if0005.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_hpi116_tema_if0005.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_sol283_tema_if0005.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_sol286_tema_if0005.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_sol293_tema_if0005.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_sol296_tema_if0005.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kux_sol606_tema_if0005.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.3.0.5-TIV-ITM_UNIX-IF0005/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

- Since there is no uninstall utility for this fix, we suggest you
perform a backup of your environment before installing this fix.


5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(e.g. 6.3.0.5-TIV-ITM_UNIX-IF0005.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 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. Use the itmpatch command to install the fix for that agent platform.
For more information on the itmpatch command, see section 6.2

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

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.3.0.5-TIV-ITM_UNIX-IF0005/kux_xxxxxx_tema_if0005.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_if0005.tar
> ./cinfo -i
ux Monitoring Agent for Unix OS
aix523 Version: 06.30.05.00


5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file
(e.g. 6.3.0.5-TIV-ITM_UNIX-IF0005.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 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 Command Reference Guide.

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

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

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 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 updateAgent commands, see the IBM Tivoli Command Reference 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 063005005

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 063005005

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

5.4 Agent support update
------------------------
This fix (6.3.0.5-TIV-ITM_UNIX-IF0005) includes changes to the agent
support files which need to be installed. If you have already
installed these updates, there are no additional installation
steps. Otherwise, use one of the two following alternative methods
to update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise
Portal Server, and Tivoli Enterprise Portal Desktop.

A. Installing with the Application Support Installer (ASI)

1. Transfer the appropriate archive file (6.3.0.5-TIV-ITM_UNIX-IF0005.tar
or .zip) to the IBM Tivoli Enterprise Monitoring Servers,
Tivoli Enterprise Portal Servers, and Tivoli Enterprise Portal
Desktops.

2. Expand the archive file 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. Expand the archive file (kux_tems_teps_tepd_if0005.tar or .zip)
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 extract
utility on Windows systems. This step 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:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

where <JAVAHOME> is the fully-qualified path (do not include
bin directory in JAVAHOME path) to the directory where Java(R)
is installed. The location of Java 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 Tivoli Monitoring components you want
to add application support to. For this fix, check or clear the
check boxes as follows:

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

Continue through the remaining GUI panels selecting the product
06.30.05.05 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.

7. Note that the version reported by cinfo command for the TEP Browser
(TEPB/tpw) App Support component will not be updated by the itmasi tool.

B. Exploiting the Self Describing Agent (SDA)

1. In order to exploit this method SDA needs to be enabled on the agent,
on the R-TEMS and on the HUB-TEMS. SDA is enabled by default on all
components, but the HUB-TEMS. In order to enable it on the HUB-TEMS, if
not already enabled, set KMS_SDA=Y in its environment and restart it.
This is the only possible server restart required by this method, as
opposed to the multiple restarts of each server required during the
ASI install.

2. Double check SDA status is ON through command

> tacmd listsdastatus

Hub/RTEMS State Status
<HUB_name> ON 0
<RTEMS_name> ON 0


3. Enable SDA for this Interim Fix through command

> tacmd addsdainstalloptions -t ux -v 06300505

KUICO2054I: No configuration options were found for the specified
type(s). The following options will be created:

PRODUCT VERSION
UX 06300505

Are you sure you want to update the selected options? Type Y for yes.
Type N for no.
Y

KUIAIO150I: The selected SDA configuration options records were
successfully updated.

4. Double check required SDA install options are in place

> tacmd listsdainstalloptions

KUILIO200W: No default SDA installation settings exist.

PRODUCT VERSION
UX 06300505

5. You need at least one agent upgraded to this Interim Fix level running
in this HUB environment. In a few moments from its startup all the needed
support files will be propagated from the agent to the servers.

6. Double check the seeding of the support files has successfully completed
(STATE=IC Installation Complete)

> tacmd listappinstallrecs

HUB/RTEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS
<HUB_name> UX 06300505 5655 TMS 06300505 Y IC 0
<RTEMS_name> UX 06300505 5655 TMS 06300505 Y IC 0

7. Note that the version reported by cinfo command for the TEP Desktop
(TEPD/tpd) App Support component will not be updated by the SDA method.


6.0 Additional installation information
=======================================
For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>.

6.1 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.2 Additional information on using itmpatch command
-----------------------------------------------------
The "itmpatch" command has the following syntax:

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

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

itmpatch -h <installation home>
-i { <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.3 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.30.05.05

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


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

./cinfo -i

*********** Mon Feb 11 03:01:21 EST 2010 ******************
User : root Group: system bin sys security cron audit lp
Host name : candleaix3 Installer Lvl:06.30.05.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.

ux Monitoring Agent for UNIX OS
aix523 Version: 06.30.05.05

.
.
.
2. To verify the agent support files were updated correctly run the cinfo
command on a Unix/Linux server, or the kincinfo command on Windows server,
and check UNIX OS Support version.

Sample output of the kincinfo command on a Windows System
---------------------------------------------------------

kincinfo -t ux
********** Friday, February 28, 2014 7:02:03 PM **********
User : Administrator Group : NA
Host Name : WIN2K3SP2-32BIT Installer : Ver: 06300000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory


PC APPLICATION SUPPORT DESC PLAT APP VER BUILD INSTALL DATE

UX TEMS App Support/Monitoring Agent for UNIX OS WICMS 06.30.05.05 201410140000 20141014 1101
UX TEPS App Support/Monitoring Agent for UNIX OS WICNS 06.30.05.05 201410140000 20141014 1101
UX TEPB App Support/Monitoring Agent for UNIX OS WIXEB 06.30.05.05 30241 20130624 1101
UX TEPD App Support/Monitoring Agent for UNIX OS WIXEW 06.30.05.05 201410140000 20141014 1101

7.0 Known problems and workarounds
==================================
It can happen that installation of this Interim Fix can fail while
adding the agent supports for TEMS and TEPS, when using Java 1.7,
giving an error as below:

"The wizard cannot continue because of the following error: could not
load wizard specified in /wizard.inf (104)
Trace log location: C:\Users\ADMINI~1\AppData\Local\Temp\2"

When this issue occurs, please choose another version for Java (JRE)
installed on the machine for running the setup.jar file.
Java version 1.5 or 1.6 are suggested

8.0 Additional product information
==================================
APARs IV79257 and IV75908 provide a set SQL files that
need to be copied to the Warehouse server and run to update
tables for DB2.

For IV79257, the kux_63migr_Memory_*.sql files are copied to
the portal server when the application support is installed via the
Application Support Installer (ASI).

If the application support is installed via the Self Describing
Agent (SDA), the files need to be obtained from the technote
attachment:
http://www.ibm.com/support/docview.wss?uid=swg21964406

For IV75908, the kux_63migr_Disk_*.sql files are copied to the
portal server when the application support is installed via either
the Application Support Installer (ASI) or Self Describing Agent
(SDA).

Files for APAR IV79257 (kux_63migr_Disk_*.sql) and APAR IV75908
(kux_63migr_Memory_*.sql) need to be copied from either the portal
server (if they exist) or the technote to the Warehouse server.
The files then need to be run using the steps documented in the
"Procedure" section for the "System" summarized tables in the Appendix
A "Upgrading your warehouse for primary key and tablespace changes"
of the UNIX OS Agent Reference Guide.


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.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.

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

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.

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.

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.

11.0 Change History
===================
July 29, 2016 - Original publish date.
April 19, 2017 - Added details in Section 8 for APARs IV79257 and IV75908.