IBM Information Server

IBM Information Server patch installation instructions

Instructions for installing patches for IBM® Information Server 8.0.1. Version 3.

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 successful installation of patches. Access the latest version of the instructions at http://www.ibm.com/support/docview.wss?uid=swg27011896.

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

Contents

© 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.

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

About patches and patch installation

Patches for IBM Information Server 8.0.1 are distributed separately from the Update Installer components that are required to install the patches.

Patch components
The patch distribution consists of two files. The following table lists the patch component files:
Table 1. Patch component file names and descriptions
Patch component Description
README.txt Contains important information specific to the patch. Read the information in the README.txt file before you install a patch.
*.ispkg The contents of the patch package.
Update Installer components
To install a patch you use the operating system-specific launcher to start the installation and an associated .jar file that is compatible with all operating systems. The following table lists the Update Installer components.
Table 2. Update Installer component file names and descriptions
Update Installer component File name Description
Update Installer Launcher Updater.exe or Updater Operating system-specific launcher application for Microsoft® Windows® or UNIX® and Linux®
Update Installer updater.jar .jar file for all operating systems
Patch 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.

Restrictions

Before you install a patch, read these restrictions and ensure that your computer and user privileges meet the following requirements.

Install the patch on all layers that the patch applies to: domain first, then server, and then client layer
Some patches apply to more than one layer. In distributed installations of IBM Information Server, you must install these patches on all computers that have layers installed that the patch applies to. When you install patches on multiple computers, install the patch on the domain layer first, then the server layer, and then the client layer. See the README.txt file included with the patch to determine which layers the patch applies to.
Patch uninstallation is not possible for all patches
Only certain patches can be uninstalled. Contact IBM customer support for assistance with uninstalling patches.
UNIX systems umask setting
On UNIX systems, set the umask value to 022.
UNIX root user
On UNIX operating systems, patches must be installed by the root user.
Windows administrator privileges on server and domain layers
For server and domain layers on Windows operating systems:
  • Patches must be installed by a user with administrator privileges.
  • Use the same user name you used to install IBM Information Server to ensure you have the correct privileges.
Windows Vista administrator privileges on the client layer
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.

Preparing your system for installation on domain and server layers

Shut down IBM Information Server
Shut down IBM Information Server, including WebSphere Application Server, before you perform a complete backup.
Back up content
Before you install a patch, create a complete backup of all IBM Information Server content, including the metadata repository database and WebSphere® Information Analyzer Information Analyzer analysis database (if installed).
Delete temporary reporting workspace directory
Operating systems: All
Delete the temporary reporting workspace directory:
  • Windows: %TEMP%\WDISuite directory. On Windows Server 2003 systems, TEMP is typically c:\Windows\Temp.
  • Linux and UNIX: /tmp/WDISuite directory
Note: If this directory is not deleted, patch installation might appear to succeed when installation is not successful.
Start IBM Information Server
Start IBM Information Server after backing up the content.
Increase Inactive Session Timeout value for Global Session Properties
Increasing the value of the Inactive Sessions Timeout is recommended before you install patches on slower systems. Increase the value of the Inactive Sessions Timeout to 14400 seconds (120 minutes) to ensure a successful installation. 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 14400 for the Inactive Session Timeout field.
  6. Click Save and Close.
Note: You can reset the Inactive Sessions Timeout value to your original value after you install a patch.
Ensure that the server and domain are running
To ensure that the server and domain are 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 Information Server Administrator user name and password (this is not the WebSphere Application Server user name).
Ensure that the following products and services are running properly
The database for IBM Information Server and other products and services must be running for the patch installation to succeed.
  • Metadata repository database and database server
  • WebSphere Information Analyzer database and database server (if installed)
  • WebSphere Application Server
  • Logging Agent
  • Application Services Backbone (ASB) Agent
  • WebSphere DataStage® engine
Ensure that IBM Information Server 8.0.1 is not in use
Do not perform any actions on IBM Information Server components during patch installation. The server and domain layers of IBM Information Server must be fully dedicated to the installation process. Do not run any other applications or attempt to access any IBM Information Server services during the installation.
During patch installation, the WebSphere Application Server and IBM Information Server may be shut down and restarted one or more times. Do not interfere with the automatic shutting down and restarting of WebSphere Application Server and IBM Information Server .
Note: After the patch installation is complete, you might have to restart the computer. See the README.txt file included with the patch to determine whether a restart is necessary.
Set IDTHTOIN to 600 seconds when using DB2® for z/OS® for the metadata repository
The value of the currently active DB2 DSNZPARM parameter IDTHTOIN (in the DSN6FAC macro) must be set to 600 seconds during installation on the domain layer. After installation is complete this parameter can be restored to its original value. This is a system-wide parameter and requires a database administrator to set it.
Note: IBM WebSphere Information Services Director deployment requires that the IDTHTOIN parameter be set to a value longer than the time required to deploy an application. If you do not plan to have your database administrator change this value for each application deployment you must leave the DSNZPARM parameter set to a value which allows application deployment to succeed.

Preparing your system for installation on the client layer

Shut down clients
Ensure that no IBM Information Server 8.0.1 client applications are running on the computer.

Installing a patch

The Update Installer Launcher (Updater.exe on Windows or Updater on UNIX and Linux) and the Update Installer (updater.jar) must be in the same directory to install a patch.

The paths shown in the following commands assumes that the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location.

The patch package file name patch_e000000_type_os.ispkg in the following commands is a sample patch package file name. Use the correct name of the patch you are installing.

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

The patch installer supports two installation modes on all operating systems: installation wizard mode and console mode. Command line parameters can be used in both installation modes.

Command line parameters

The following command line parameters are available for patch installation. If you do not specify values for an optional parameter, the installer prompts you to enter the values during the patch installation. You must always provide the –i parameter and value.

-i
IBM Information Server installation root directory, required
-p
The file name of the patch installation package, optional
-user
IBM Information Server administrator user name, optional
-password
IBM Information Server administrator password, required when the -user parameter is provided
-wasadmin
WebSphere Application Server administrator (server ID) user name, optional, applies only when installing a patch on computers with the domain layer installed
-waspassword
WebSphere Application Server administrator (server ID) password, required when the -wasadmin parameter is provided
-console
Install without opening the installation wizard, optional
-force
Force reinstallation of a patch. Required when a fix pack is reinstalled after installing a new product component in an existing IBM Information Server installation. See the fix pack release notes for further details.
-verbose
Include detailed information in the console output, optional
-version
Display the version number of the Update Installer, ignores all other parameters except the -i parameter, which is required. The only action taken is the display of the version number.
Note: The administrator user name and password are not required when installing the patch on computers where only the client layer is installed.

Using console mode installation on UNIX and Linux operating systems

Follow these steps to install a patch on UNIX or Linux operating systems:
  1. Log in as root.
  2. If your installation includes WebSphere DataStage, source the dsenv file. In the command prompt window, type the following command:
    . /opt/IBM/InformationServer/Server/DSEngine/dsenv
  3. In the command prompt window, type the following command to install a patch:
    ./Updater -i /opt/IBM/InformationServer -console
    Alternatively, you can specify all of the command line parameters and values to avoid interactive installation prompts. Type the following command to install a patch:
    ./Updater -i /opt/IBM/InformationServer –p patch_e000000_type_os.ispkg -user admin -password manager –console

Using wizard installation on UNIX and Linux operating systems

Wizard installation of patches on UNIX and Linux operating systems requires that your X11 client is 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 an application that uses X11.
Note: The installation wizard prompts you to enter the required values before you install the patch.
  1. Log in as root.
  2. Set the DISPLAY environment variable. For example,
    export DISPLAY=myhost.mydomain.com:0.0
  3. Start the X11 client application to test the DISPLAY environment. In the command prompt window, type:
    xterm
    On Solaris operating systems, type:
    /usr/openwin/bin/xterm 
    A new window opens to confirm that the X11 DISPLAY variable is configured properly. You cannot use the wizard to install patches in wizard mode without the correct DISPLAY environment variable.
  4. If your installation includes WebSphere DataStage, source the dsenv file. In the command prompt window, type:
    . /opt/IBM/InformationServer/Server/DSEngine/dsenv
  5. Type the following command to start the installation:
    ./Updater -i /opt/IBM/InformationServer
  6. 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 on Windows operating systems:
  1. Log in with administrator rights.
  2. In the command prompt window, type the following installation command to install a patch:
    Updater -i C:\IBM\InformationServer -console
    Alternatively, you can specify all of the command line parameters and values to avoid interactive installation prompts. Type the following command to install a patch:
    Updater -i C:\IBM\InformationServer -p patch_e000000_type_os.ispkg -user admin -password manager -console
    Note: The administrator user name and password are not required when installing the patch on computers where only the client layer is installed.

Using wizard installation 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, type the installation command to start the installation:
    Updater -i C:\IBM\InformationServer
  3. Follow the instructions in the installation wizard to install the patch.

Verifying installation

After you install the patch, verify the installation. The paths shown assume that the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location.

  • Ensure that all IBM Information Server client applications start and run properly.
  • 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
    • UNIX and Linux: /opt/IBM/InformationServer/Version.xml
    In the Version.xml file the entry for the last patch installed will be at the end of the history section and will be similar to the following:
    ...
    <History>
    ...
        <Sequence description="Description of the patch" id="1" installLocation="" 
    lastUpdateDate="Thu Feb 14 13:13:52 EST 2008" patch="patch_e000000" 
    rollback="/opt/IBM/InformationServer/Updates/patch_e000000" 
    status="Success" version=""/>
    </History>
    ...
  • Review the ISinstalltimestamp.txt log file (where timestamp is the timestamp in YYYY.MM.dd.hh.mm.ss format) to ensure that FATAL and SEVERE errors are not present. Locate the ISinstalltimestamp.txt file:
    • Windows: C:\IBM\InformationServer\logs\ISinstalltimestamp.txt
    • UNIX and Linux: /opt/IBM/InformationServer/logs/ISinstalltimestamp.txt
    See IBM Information Server Version 8.0.1 known patch installation problems for errors that can be safely ignored. For all other errors, contact IBM customer support.

Post-installation backup

Perform a complete backup of the IBM Information Server installation. See "Back up content" in the Preparing your system for installation on domain and server layers section for details.

IBM Information Server Version 8.0.1 known patch installation problems

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

Patch installation fails with "InstallShield VPD database may be corrupted" error message
Operating system: All

If the vpd.script file has been manually edited, it might have been corrupted. It is also possible that the vpd.script file was not saved correctly if the IBM Information Server installation was terminated before it was completed.

Workaround

Contact IBM customer support.

Patch installation fails with "Port number: is not properly formatted" error message
Operating system: All

When a response file was used with earlier versions of the IBM Information Server Suite Installer, several values were not correctly recorded in the vpd.script file. Incorrect values in the vpd.script file cause the patch installation to fail.

Workaround

Ensure that the necessary values are present in the vpd.script file.
  1. Locate the vpd.script file for your system.
    The following table lists the directory by operating system to locate the vpd.script file on your system.
    Table 3. Directory of vpd.script file by operating system.
    Operating system Directory
    Windows C:\Program Files\Common Files\InstallShield\Universal\IBM\InformationServer\Gen2\_vpddb
    AIX® /usr/lib/objrepos/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb
    Solaris /InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb

    Red Hat Linux

    SUSE Linux

    SUSE Linux for IBM zSeries®

    HP-UX 11i v2 on Intel® Itanium®

    HP-UX 11i v2 on PA-RISC

    /root/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb
  2. Search for LPV_APP_SERVER to locate the entry that is similar to:
    INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES(99,'LPV_APP_SERVER','websphere',NULL,'false')

  3. Edit the vpd.script file and verify that the values are correct. Add the following two entries to the end of the file if they do not exist:
    INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES(99,'LPV_ASB_HOST','hostname.domain.com',NULL,'false')
    INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES(99,'LPV_ASB_PORT','9080',NULL,'false')
  4. Change 99 to the value shown in step 2.
  5. Change 9080 to the correct port for your installation.
  6. Save the vpd.script file.
  7. Restart the installation.
Update Installer Launcher cannot find Java™ in the IBM Information Server installation directory
Operating system: All
On machines on which only the domain layer is installed the Update Installer Launcher might not be able to locate a Java JRE and fails with the following message:
  • Windows:
    Could not find a valid IBM Java virtual machine in any of the following places:
    c:\IBM\InformationServer\ASBNode\apps\jre\bin\java.exe
    c:\IBM\InformationServer\_jvm\jre\bin\java.exe
  • Linux, UNIX:
    Could not find a valid IBM Java virtual machine in any of the following places:
    /opt/IBM/InformationServer/ASBNode/apps/jre/bin/java.exe
    /opt/IBM/InformationServer/_jvm/jre/bin/java.exe
This occurs when IBM Information Server was installed with a version of Java available in the environment.

Workaround

Copy the Java JRE used by the IBM WebSphere Application Server to the root directory of the IBM Information Server installation. The paths shown in the following commands assume that the product is installed in the default location. Your path will vary if you installed IBM Information Server or WebSphere Application Server in a different location.
  • Windows:
    • Copy the contents of C:\IBM\WebSphere\AppServer\_jvm to C:\IBM\InformationServer\_jvm
  • Linux, UNIX:
    • Run the following command:
      cp -rf /opt/IBM/WebSphere/AppServer/java/jre /opt/IBM/InformationServer/_jvm
ASBAgent fails on engine when LD_PRELOAD is set
Operating system: HP-UX 11i v2 on Intel Itanium
Patch and fix pack installation on operating systems other than HP-UX 11i v2 on Intel Itanium requires the following command:
source installation_dir/Server/DSEngine/dsenv

The LD_PRELOAD environment variable that is established causes the ASBAgent to fail.

Workaround

The path shown in this command assumes that the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location. Use the following command to unset the LD_PRELOAD environment variable:
cd /opt/IBM/InformationServer/Server/DSEngine
. dsenv
unset LD_PRELOAD
Patch installation fails if the port for the IBM Information Server domain has been changed in WebSphere Application Server
Operating systems: All
If the port for the IBM Information Server domain computer was modified in 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

Confirm that the value in the vpd.script file reflects the actual port being used for IBM Information Server before installing the patch.
  1. Confirm the port number by using a Web browser to access the IBM Information Server Web console. For example, the IBM Information Server port number in the following URL is 9080: http://domain:9080/index.jsp.
  2. Locate the vpd.script file for your system.
    The following table lists the directory by operating system to locate the vpd.script file on your system.
    Table 4. Directory of vpd.script file by operating system.
    Operating system Directory
    Windows C:\Program Files\Common Files\InstallShield\Universal\IBM\InformationServer\Gen2\_vpddb
    AIX /usr/lib/objrepos/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb
    Solaris /InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb

    Red Hat Linux

    SUSE Linux

    SUSE Linux for IBM zSeries

    HP-UX 11i v2 on Intel Itanium

    HP-UX 11i v2 on PA-RISC

    /root/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb
  3. Edit the /root/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb/vpd.script file to ensure the port is correct.
    Search for LPV_ASB_PORT to locate the port configuration entry that is similar to:
    INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES(211,'LPV_ASB_PORT','9080',NULL,'false')
  4. If the port is incorrect, change the value to the port being used.
  5. Save the vpd.script file.
  6. Restart the installation.
Patch installation fails when the installation is unable to stop the ASBAgent service
Operating systems: Windows
During patch installation, the WebSphere Application Server and the IBM Information Server are automatically shut down and restarted. The patch installation fails when the ASBAgent service is not stopped in one of the following scenarios:
  • The installer fails to stop the ASBAgent service using a net stop command. When this occurs the following entry is found in the installation log file:
    WARNING: java.lang.Exception: Information Server cannot be shut down in a timely manner, please reboot windows and 
    complete the rest of the installation.
  • The installer 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
  • UNIX and Linux: /opt/IBM/InformationServer/logs/ISinstalltimestamp.txt

Workaround

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

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

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

Workaround

Set the maximum heap size property to 1280 MB before installing the patch.
Follow these steps 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 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 your original value after you install the patch.
Invalid Version.xml file causes the patch installation to fail
Operating systems: 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, delete this file before you install the patch. Copy the original Version.xml file to retain a record of what patches were previously installed before you delete it.
Patch installation might fail if you do not have local administrator privileges
Operating systems: 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.
Workaround
Log on as a user that is a member of the local administrators group and reinstall the patch.
Patch installation fails when NLS is enabled and locale is Spanish
Operating system: Solaris
Patch cannot be installed on Solaris systems when NLS is enabled and the locale is es_ES (or any other Spanish locales designated with es_). Installation fails with the error message:
A license file was not created.
Workaround
Install the patch after changing the system to use an English language locale, such as en_GB or en_US.
Successful patch installation has a SEVERE error in the installation log
Operating systems: All
IBM Information Server installations that include WebSphere DataStage 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. You can safely ignore the error message.
Successful patch installation has a warning message in the log
Operating system: SUSE Linux Enterprise Server 10 on Intel x86
Successful patch installations might include the following warning message in the patch installation log:
Error: cat: /scratch/Ascential/DataStage/DSEngine/.asbnode: No such file or directory
This warning message appears in the following scenario:
  • DataStage engine with NLS disabled is upgraded from WebSphere DataStage 7.5.3 to WebSphere DataStage 8.0.1
  • Configuration includes a remote DB2 repository
  • ITAG with NLS enabled is installed on SUSE Linux Enterprise Server 10 on Intel x86 with the following DataStage Server values:
    • ITAG value not equal to the default ADE
    • Port number not equal to the default 31538
  • The selected product components to install are:
    • DataStage and QualityStage™
    • Information Analyzer
    • Business Glossary
Workaround
The patch installed successfully. You can safely ignore the error message.

IBM Information Server Version 8.0.1 known problems and workarounds

For information about the known problems and workaround for the operation of IBM Information Server, go to http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/topic/com.ibm.swg.im.iis.productization.iisinfsv.rnotes.kpw.doc/topics/knownprob.html.

Accessing information about IBM

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

You can find the latest information about IBM 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 Information Server in the United States or Canada, call 1-866-INFO-NOW (1-866-463-6669).

To find worldwide support contact information for IBM Information Server, see the eService Support Center Directory at https://www.ibm.com/software/data/support/iis/eservice/.

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, the IBM logo, and ibm.com® 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:

Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

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

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

Microsoft, Windows, Windows NT® 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.