IBM InfoSphere Information Server

InfoSphere Information Server patch installation instructions

Instructions for installing patches for InfoSphere™ Information Server 8.1. Document updated September 20, 2011.

Important: Latest version of patch installation instructions

Always refer to the latest version of the patch installation instructions. The instructions are periodically updated and contain critical information to ensure the successful installation of patches. Access the latest version of the instructions at http://www.ibm.com/support/docview.wss?uid=swg27012519.

Note: Before using this information and the product that it supports, read the general information under Notices and trademarks.

© Copyright International Business Machines Corporation 2008. All rights reserved. US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM® Corp.

Contents

This information is the most current about the product on the date of publication.

About this document

Instructions in this document use the default installation paths. Your path varies if you installed IBM Information Server in a different location.

Default installation paths
The following table lists the default IBM Information Server installation locations:
Table 1. Default installation locations
Operating system Directory
Windows® C:\IBM\InformationServer
Linux®, UNIX® /opt/IBM/InformationServer

Patch installation log files

Viewing the log files that are created during installation is useful when you are troubleshooting installation problems. During the installation and uninstallation process, the log file is simultaneously updated in the following directories:

Microsoft® Windows:
  • C:\IBM\InformationServer\logs
  • C:\IBM\InformationServer\Updates\PatchName
Linux, UNIX:
  • /opt/IBM/InformationServer/logs
  • /opt/IBM/InformationServer/Updates/PatchName

After a successful installation, the log file is named ISInstall.YYYY.MM.DD.HH.MM.SS.log where YYYY.MM.DD.HH.MM.SS is the date and time that the installation was started.

After an unsuccessful installation, the ISInstall.YYYY.MM.DD.HH.MM.SS.log file is included in the InformationServer/logs directory, and all logs that are used for troubleshooting are included in the InformationServer/isdump-operating_system-YYYY.MM.DD.HH.MM.SS.zip file.

About patches

Patches for IBM InfoSphere Information Server Version 8.1 consist of two files.
Table 2. Patch component file names and descriptions
Patch component Description
README.txt Contains important information specific to the patch.
*.ispkg Patch package installed with the Update Installer.

Use the latest version of the Update Installer

Update Installer
Patches are installed with the Update Installer that is part of the IBM InfoSphere Information Server installation. Updates to the Update Installer are made available separately.
Before you install a patch, follow these steps to ensure that you are using the latest version of the Update Installer:
  1. From the command line run the following command:
    • Windows: C:\IBM\InformationServer\Updates\bin\VersionInfo.bat
    • Linux, UNIX: /opt/IBM/InformationServer/Updates/bin/versionInfo.sh
    For example, the following Update Installer version information is displayed for Version 8.1.0.160:
    IBM Information Server Update Installer Version 8.1.0.160
  2. Ensure that the version number returned by the script is the same version as the latest Update Installer that is available at http://www.ibm.com/support/docview.wss?rs=14&uid=swg24020897.

On IBM AIX®, Microsoft Windows, and Red Hat Linux, the script might not exist. If the script does not exist, you do not have the latest version of the Update Installer. When you install a patch with Update Installer Version 8.1.0.160 or later, the script is created automatically for future use.

After you download the latest version of the Update Installer, install it by replacing the updater.jar file in the following directory:
  • Windows: C:\IBM\InformationServer\Updates\bin
  • Linux, UNIX: /opt/IBM/InformationServer/Updates/bin

Patches are installed with the Update Installer that is part of the IBM InfoSphere Information Server installation. Updated versions of the Update Installer are located at http://www.ibm.com/support/docview.wss?uid=swg27012519.

Requirements

Ensure that the following requirements are met before you install patches.

Install the patch on all tiers that the patch applies to: services first, then engine, and then client tier
Some patches apply to more than one tier. In distributed installations of IBM InfoSphere Information Server, you must install these patches on all computers that have tiers installed that the patch applies to. When you install a patch on multiple computers, install the patch on the services tier first, then on the engine tier, and then on the client tier. See the README.txt file included with the patch to determine which tiers the patch applies to.
UNIX systems umask setting
On UNIX systems, set the umask value to 022.
UNIX root user
On UNIX operating systems, you must log in as the root user to install a patch.
Windows administrator privileges on engine and services tiers
For engine and services tiers on Windows operating systems:
  • Patches must be installed by a user with administrator privileges.
  • Use the same user name that you used to install IBM InfoSphere Information Server to ensure that you have the correct privileges.
Windows Vista administrator privileges on the client tier
To install IBM Information Server patches, you must use a command window that has been elevated to have full administrative privileges. Follow these steps to open an elevated command window:
  1. Click the Start menu.
  2. Type cmd in the Start Search box.
  3. Press Ctrl+Shift+Enter.
  4. Click Continue to accept the prompt asking for your permission to continue.
Patch-specific installation instructions
Before you install a patch, see the README.txt file that is included with the patch for any installation instructions that are specific to the patch.

Preparing your system for patch installation or uninstallation on services and engine tiers

Shut down IBM InfoSphere Information Server
Shut down IBM InfoSphere Information Server, including IBM WebSphere® Application Server, before you perform a complete backup.
Back up content
Before you install a patch, create a complete backup of all IBM InfoSphere Information Server content, including the metadata repository database and Information Analyzer analysis database (if installed). Access detailed backup instructions at http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.found.admin.common.doc/topics/t_admin_backup_infsrv.html.
Start IBM InfoSphere Information Server
Start IBM InfoSphere Information Server after backing up the content.
Ensure that the following products and services are running properly
The database for IBM InfoSphere Information Server and the following products and services must be running for the patch installation to succeed:
  • Metadata repository database and database server
  • InfoSphere Information Analyzer database and database server (if installed)
  • IBM WebSphere Application Server
  • Logging agent
  • Application Services Backbone (ASB) Agent
  • engine (if installed)
Ensure that the services tier is running
To ensure that the services tier is running:
  1. In a browser window, enter http://host_server:9080 where host_server is the name or IP address of the domain server.
  2. Log in by using the IBM InfoSphere Information Server Administrator user name and password (this is not the IBM WebSphere Application Server user name).
Increase Inactive Session Timeout value for Global Session Properties
Increase the value of the Inactive Session Timeout field to 7200 seconds (120 minutes) to ensure a successful installation when you install patches on slower computers.
Follow these steps to change the value of the timeout to avoid being disconnected automatically during patch installations:
  1. Log in to the IBM Information Server Web console.
  2. Click the Administration tab.
  3. In the Navigation pane, select Session Management > Active Sessions.
  4. In the Active Sessions pane, click Global Session Properties.
  5. Specify 7200 for the Inactive Session Timeout field.
  6. Click Save and Close.
Note: Reset the Inactive Session Timeout value to the original value after you install a patch.
Ensure that IBM InfoSphere Information Server 8.1 is not in use
Do not perform any actions on IBM InfoSphere Information Server components during a patch installation. The engine and services tiers of IBM InfoSphere Information Server must be fully dedicated to the installation process. Do not run any other applications or attempt to access any IBM InfoSphere Information Server services during the installation.
Some patches require that the IBM WebSphere Application Server and IBM InfoSphere Information Server be shut down and restarted one or more times. Do not interfere with the automatic shutting down and restarting of IBM WebSphere Application Server and IBM InfoSphere Information Server.
Note: See the README.txt file that is included with the patch to determine if you must restart the computer after the patch is installed.

Preparing your system for patch installation or uninstallation on the client tier

Shut down clients
Ensure that the IBM InfoSphere Information Server client applications are not running:

Installing a patch

The patch name patch_JR000000_type_os.ispkg in the following commands is an example. Use the correct name of the patch that you are installing.

The user name and password shown in the following commands are examples. Use the same user name and password that you used to install IBM InfoSphere Information Server.

The Update Installer supports two installation modes on all operating systems: installation wizard mode and console mode. You can use command line parameters in both installation modes.

Command line parameters

The following command line parameters are available for the patch installation. If you do not specify values for an optional parameter, the Update Installer prompts you to enter the values during the patch installation.

Table 3. Patch installation command line parameters
Parameter Description
-p Optional. The file name of the patch installation package.
-user Optional. IBM InfoSphere Information Server administrator user name.
-password IBM InfoSphere Information Server administrator password, required when the -user parameter is provided.
-wasadmin Optional. IBM WebSphere Application Server administrator (server ID) user name. Applies only when installing a patch on computers with the services tier installed.
-waspassword IBM WebSphere Application Server administrator (server ID) password, required when the -wasadmin parameter is provided.
-console Optional. Install without opening the installation wizard.
-force Forces reinstallation of a patch. To ensure a consistent installation, reinstall all patches and fix packs that were initially installed after you originally installed this patch.
-verbose Optional. Include detailed information in the console output.
-version Display the version number of the Update Installer.
Note: The IBM InfoSphere Information Server administrator and WebSphere administrator user names and passwords are not required when you install the patch on computers where only the client tier is installed.

Using console mode installation on Linux and UNIX operating systems

Follow these steps to install a patch on Linux or UNIX operating systems:
  1. Log in as the root user.
  2. If your installation includes , source the dsenv file. In the command prompt window, type the following command:
    . /opt/IBM/InformationServer/Server/DSEngine/dsenv
  3. If you are installing a patch on IBM AIX:
    1. Unset LDR_CNTRL after sourcing dsenv to avoid adversely impacting the amount of available memory in IBM WebSphere Application Server. Type the following command:
      unset LDR_CNTRL
    2. On the services tier, use only the JRE for WebSphere Application Server. By default, the JRE is located in the /opt/IBM/WebSphere/AppServer/java directory. Type the following command:
      /opt/IBM/WebSphere/AppServer/java/bin/java -jar updater.jar other arguments
      Note: If your topology contains a computer dedicated to the engine tier, when installing on the engine tier, use the JRE from the InfoSphere Information Server Version 8.1 Fix Pack 1 package. Alternatively, you can make a copy of the JRE located in the opt/IBM/InformationServer/ASBNode/lib directory.
  4. Type the following command in the /opt/IBM/InformationServer/Updates/bin directory to install a patch:
    ./InstallUpdate.sh -console
    Alternatively, you can specify all the command line parameters and values to avoid interactive installation prompts. Type the following command to install a patch:
    ./InstallUpdate.sh –p patch_JR000000_type_os.ispkg -user admin -password AdminPassword -wasadmin wasadmin -waspassword WebSpherePassword –console

Using the installation wizard on Linux and UNIX operating systems

If you use the wizard to install patches on Linux or UNIX operating systems, the X11 client must be running. The following instructions ensure that your DISPLAY variable is set properly, and verifies that the X Window System application is running by starting xterm, which uses X11. You can also verify that the X11 client is running by starting xclock or another application that uses X11.
Note: The installation wizard prompts you to enter the required values before you install the patch.
  1. Log in as the root user.
  2. Set the DISPLAY environment variable. For example,
    export DISPLAY=myhost.mydomain.com:0.0
    Where myhost.mydomain is the full name of the computer that the patch is being installed on.
  3. Start the X11 client application to test the DISPLAY environment variable. In the command prompt window, type:
    xterm
    A message confirms that the X11 DISPLAY environment variable is configured properly. You cannot use the wizard to install patches without the correct DISPLAY environment variable.
  4. If your installation includes , source the dsenv file. In the command prompt window, type:
    . /opt/IBM/InformationServer/Server/DSEngine/dsenv
  5. If you are installing a patch on IBM AIX, unset LDR_CNTRL after sourcing dsenv to avoid adversely impacting the amount of available memory in IBM WebSphere Application Server. Type the following command:
    unset LDR_CNTRL
  6. Type the following command in the /opt/IBM/InformationServer/Updates/bin directory to start the installation:
    ./InstallUpdate.sh
  7. Follow the instructions in the installation wizard to install the patch.

Using console mode installation on Windows operating systems

Follow these steps to install a patch in console mode on Windows operating systems:
  1. Log in with administrator rights.
  2. In the command prompt window, type the following command in the C:\IBM\InformationServer\Updates\bin directory to install a patch:
    InstallUpdate -console
    Alternatively, you can specify all the command line parameters and values to avoid interactive installation prompts. Type the following command to install a patch:
    InstallUpdate -p patch_JR000000_type_os.ispkg -user admin -password AdminPassword
    -wasadmin wasadmin -waspassword WebSpherePassword -console
    Note: The IBM InfoSphere Information Server administrator and WebSphere administrator user names and passwords are not required when you install the patch on computers where only the client tier is installed.

Using the installation wizard on Windows operating systems

Note: The installation wizard prompts you to enter the required values before you install the patch.
  1. Log in with administrator rights.
  2. In the command prompt window, go to the C:\IBM\InformationServer\Updates\bin directory and type the following installation command to start the installation:
    InstallUpdate
  3. Follow the instructions in the installation wizard to install the patch.

Verifying installation

After you install the patch, verify the installation.

  • Ensure that all IBM InfoSphere Information Server client applications start and run correctly.
  • Verify that the Version.xml file includes Status="Success". When the entry shows Status="PartialSuccess" or there is no entry for the patch that you installed, the patch installation did not succeed. Locate the Version.xml file:
    • Windows: C:\IBM\InformationServer\Version.xml
    • Linux, UNIX: /opt/IBM/InformationServer/Version.xml
    In the Version.xml file, the status entry for the last patch installed is at the end of the history section as shown in the following example:
    ...
    <History>
    ...
        <Sequence description="Description of the patch" id="1" installLocation="" 
    lastUpdateDate="Thu Feb 14 13:13:52 EST 2008" patch="patch_JR000000" 
    rollback="/opt/IBM/InformationServer/Updates/patch_JR000000" 
    status="Success" version=""/>
    </History>
    ...
  • Review the ISInstall.YYYY.MM.DD.HH.MM.SS.log file to ensure that FATAL and SEVERE errors are not present. See IBM InfoSphere Information Server Version 8.1 known patch installation problems for information about errors that can be ignored. For all other errors, contact IBM customer support.

Post-installation backup

Perform a complete backup of the IBM InfoSphere Information Server installation. See http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.found.admin.common.doc/topics/t_admin_backup_infsrv.html for more information.

Uninstalling a patch

Not all patches can be uninstalled. The README.txt file included with each patch indicates whether the patch can be uninstalled. Only the last patch installed can be uninstalled. To uninstall a patch that is not the last installed patch, you must first uninstall the latest installed patch and then uninstall all later patches. Installing a patch that cannot be uninstalled prevents all previously installed patches from being uninstalled because patches must be uninstalled in reverse order of their installation. To determine which patches have been installed, locate the Version.xml file:

  • Windows: C:\IBM\InformationServer\Version.xml
  • Linux, UNIX: /opt/IBM/InformationServer/Version.xml

In the Version.xml file, the entry for the last patch installed is at the end of the history section and is similar to the following example:

...
<History>
...
    <Sequence description="Description of the patch" id="1" installLocation="" 
lastUpdateDate="Thu Feb 14 13:13:52 EST 2008" patch="patch_JR000000" 
rollback="/opt/IBM/InformationServer/Updates/patch_JR000000" 
status="Success" version=""/>
</History>
...

You must use the Update Installer in console mode when you uninstall patches.

Command line parameters
The following command line parameters are available for patch uninstallation:
Table 4. Patch uninstallation command line parameters
Parameter Description
-rollback The name of the latest installed patch.
-verbose Optional. Include detailed information in the console output.

Uninstalling on Linux and UNIX operating systems

Follow these steps to uninstall the latest patch installed on Linux or UNIX operating systems:

  1. Log in as the root user.
  2. If your installation includes , source the dsenv file. In the command prompt window, type the following command:
    . /opt/IBM/InformationServer/Server/DSEngine/dsenv
  3. If you are installing a patch on IBM AIX, unset LDR_CNTRL after sourcing dsenv to avoid adversely impacting the amount of available memory in IBM WebSphere Application Server. Type the following command:
    unset LDR_CNTRL
  4. Type the following command in the /opt/IBM/InformationServer/Updates/bin directory to uninstall the latest installed patch:
    ./InstallUpdate.sh -rollback patch_JR000000

Uninstalling on Windows operating systems

Follow these steps to uninstall the latest patch installed on a Windows operating system:

  1. Log in with administrator rights.
  2. In the command prompt window, type the following command in the C:\IBM\InformationServer\Updates\bin directory to uninstall the latest installed patch:
    InstallUpdate -rollback patch_JR000000

IBM InfoSphere Information Server Version 8.1 known patch installation problems

At the time of publication, the following problems are known for patch installations.

Shut down SAP and BW listeners before installing a patch
Operating systems: All

If IBM InfoSphere Information Server Pack for SAP BW or the IBM InfoSphere Information Server Pack for SAP R/3 is installed on your computer, before installing a patch, shut down SAP and BW listeners to avoid a possible installation failure.

Workaround

  1. Before running the Update Installer, shut down the SAP and BW listeners.
  2. Install the patch.
  3. Restart the listeners.

Command line options for the Update Installer are ignored
Operating systems: IBM AIX, Linux, Windows

Command line options that are passed to the Update Installer are ignored when you use the InstallUpdate.sh or InstallUpdate.bat script. This issue exists only on some installations.

Workaround

Modify the InstallUpdate script to pass through command line options to the Update Installer.

Windows: Edit the C:\IBM\InformationServer\Updates\bin\InstallUpdate.bat script and add %* to the end of the command line as shown in the following example:

"C:\IBM\InformationServer\ASBNode\apps\jre\bin\java.exe" -jar updater.jar
 -i "C:\IBM\InformationServer" %*

AIX, Linux: Edit the /opt/IBM/InformationServer/Updates/bin/InstallUpdate.sh script and add “$@” to the end of the command line as shown in the following example:

"/opt/IBM/InformationServer/ASBNode/apps/jre/bin/java" -jar updater.jar
 -i "/opt/IBM/InformationServer" "$@"
Patch installation fails if the port for the InfoSphere Information Server services has been changed in IBM WebSphere Application Server
Operating system: All

If the port for the InfoSphere Information Server services was modified in IBM WebSphere Application Server after the original installation, the patch installation fails with an authentication error. The following error message appears in the log file:

SEVERE:
com.ibm.is.install.update.installer.ConsoleUpdateDriver Failed to 
authenticate username/password, please ensure your application server 
is running, and ensure you have entered valid Information server 
administrator user name/password. Return message is: null

Workaround

Before installing the patch, confirm that the ASBPort value in the Version.xml file matches the actual port used for InfoSphere Information Server.

  1. Confirm the port number by using a Web browser to access the InfoSphere Information Server Web console. For example, the InfoSphere Information Server port number in the following URL is 9080:
    http://hostname:9080/index.jsp
  2. Verify that the Version.xml file also has the correct LPV_ASB_HOST and LPV_ASB_PORT values.
  3. Locate the following variables in the <Properties> section:
    <Property name="AsbHostName" value=localhost.localdomain/>
    <Property name="AsbPortNumber" value=9080/>
    localhost.localdomain is your system hostname. In the AsbPortNumber value, enter the application server port number that you use to connect to the InfoSphere Information Server Web console.
Patch installation fails when the installation is unable to stop the ASBAgent service
Operating system: Windows

During patch installation, the IBM WebSphere Application Server and the IBM InfoSphere Information Server are automatically shut down and restarted. The patch installation fails when the ASBAgent service fails to stop the ASBAgent process after a shutdown request times out. When this occurs, the following entry is found in the installation log file:

taskkill.exe -Unable to Locate Component Window appears with the message.
This application failed to start because 
framedyn.dll was not found. Re-installing the application may fix the
problem.
ISinstalltimestamp.txt log file locations:
  • Windows: C:\IBM\InformationServer\logs\ISinstalltimestamp.txt
  • Linux, UNIX: /opt/IBM/InformationServer/logs/ISinstalltimestamp.txt

Workaround

Restart your computer, and then restart the patch installation. If the issue is not resolved, contact IBM customer support. To resolve issues with the taskkill.exe process, contact Microsoft Corporation.

Patch installation fails on OutOfMemory exception in IBM WebSphere Application Server
Operating system: All

Patch installation might fail if the maximum heap size is not sufficient for that system, resulting in an OutOfMemory exception in IBM WebSphere Application Server. Some systems runningIBM WebSphere Application Server might require increasing the heap size to successfully install a patch. The default maximum heap size allocation of IBM WebSphere Application Server process is automatically set to 768 MB during IBM InfoSphere Information Server installation.

Workaround

Set the maximum heap size property to 1280 MB before installing the patch.

To change the maximum heap size allocated to the application server process:
  1. Log in to the WebSphere administrative console as the WebSphere administrator.
  2. In the topology tree, expand Servers and click Application Servers.
  3. Click the server1 link (where server1 is the name of the application server that you want to configure).
  4. Under Server Infrastructure, expand Java and Process Management.
  5. Click Process Definition.
  6. Under the Additional Properties section, click Java Virtual Machine.
  7. In the Maximum Heap Size field, type 1280.
  8. Click Apply or OK.
  9. Install the patch.
  10. Reset the value of Maximum Heap Size to the original value after you install the patch.
Invalid Version.xml file causes the patch installation to fail
Operating system: All
If the Version.xml file is edited manually, the patch installation might fail.
Workaround
If the Version.xml file is edited or becomes corrupt, rename this file and extract the original version from the most recent ISdump-os-timestamp.zip file. Retain the renamed version of the original Version.xml file as a record of what patches were previously installed before you recovered it.
Patch installation might fail if you do not have all default local administrator privileges
Operating system: Windows
The installation might fail because of authentication and other errors if you are a member of the domain administrators group, but you are not a member of the local administrators group, or if the account used does not have all default local administrator privileges.
Workaround
Ensure that the account that is used has all default local administrator privileges and reinstall the patch.
Successful patch installation has a SEVERE error in the installation log
Operating system: All
IBM InfoSphere Information Server installations that include might generate a SEVERE error message in the installation log file.
SEVERE: Exit Code: 0, Info: Stopping JobMonApp JobMonApp has been shut down.
DataStage Engine 8.0.1.0 instance "801" has been brought down., Error: DeadLock Daemon shutdown
Workaround
The patch installed successfully. Ignore the error message.

Accessing information about IBM

IBM has several methods for you to learn about products and services.

You can find the latest information about IBM InfoSphere Information Server on the Web at http://www.ibm.com/software/data/integration/info_server/. To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at http://www.ibm.com/planetwide.

Contacting IBM

You can contact IBM by telephone for customer support, software services, and general information.

Customer support

To contact IBM customer service for IBM InfoSphere Information Server in the United States or Canada, call 1-866-INFO-NOW (1-866-463-6669).

Software services

To learn about available service options, call one of the following numbers:
  • In the United States: 1-888-426-4343
  • In Canada: 1-800-465-9600

General information

To find general information in the United States, call 1-800-IBM-CALL (1-800-426-2255).

Go to http://www.ibm.com for a list of numbers outside of the United States.

Providing comments on the documentation

Please send any comments that you have about this information or other documentation.

Your feedback helps IBM to provide quality information. You can use any of the following methods to provide comments:
  • Send your comments using the online readers' comment form at http://www.ibm.com/software/data/rcf/.
  • Send your comments by e-mail to comments@us.ibm.com. Include the name of the product, the version number of the product, and the name and part number of the information (if applicable). If you are commenting on specific text, please include the location of the text (for example, a title, a table number, or a page number).

Notices and trademarks

Notices

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.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

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.

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.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

IBM and the IBM logo are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US 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 complete and current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.

The following terms are trademarks or registered trademarks of other companies:

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

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

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

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