IBM WebSphere Development Studio Client, Version 7.0.0.1 Readme

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

Contents

1.0 About this release
2.0 Installation information
   2.1 Hardware requirements
   2.2 Software requirements
   2.3 Other requirements
   2.4 Installation instructions
      2.4.1 Installing WebSphere Development Studio Client, Version 7.0.0.1 as an update
      2.4.2 Downloading the fix pack for local installations
   2.5 Uninstalling the fix pack
3.0 Fixes contained in this release
4.0 Known limitations, problems, and workarounds
   4.1 Data tooling documentation contains a reference to unsupported functionality
   4.2 Internal server error "SAXException: Premature end of file" occurs when invoking an Axis Web service on WebSphere Application Server
   4.3 J2C "Same Input and Output" Sample link does not work on the Linux operating system
   4.4 Converting static Web project with Web site navigation enabled to a dynamic Web project fails with an exception
   4.5 Publishing an EJB with multiple source directories fails with an error
   4.6 The rollback feature is not supported in Installation Manager, Version 1.0.0.2
5.0 IBM WebSphere Software Support
6.0 Notices and trademarks

1.0 About this release

This fix pack contains fixes to the version 7.0 release of IBM^® WebSphere^® Development Studio Client for iSeries.

You can install this fix pack either as an update to IBM WebSphere Development Studio Client for iSeries, when version 7.0 is already installed on your computer, or it can be installed at the same time that you install IBM WebSphere Development Studio Client for iSeries, Version 7.0.

To view the latest version of this readme file, visit: http://download.boulder.ibm.com/ibmdl/pub/software/awdtools/wdsc/v7/7001/documents/readme/readme.html

In addition, see the release notes for version 7.0 of this product to learn about its new features and any limitations or problems known at the time of its release. The release notes for version 7.0 are available at: http://download.boulder.ibm.com/ibmdl/pub/software/awdtools/wdsc/v7/70/documents/readme/readme.html

2.0 Installation information

This section describes the installation requirements and specific installation instructions for this fix pack.

For information about installing WebSphere Development Studio Client for iSeries, Version 7.0, including installation prerequisites, see the Installation Guide online at http://download.boulder.ibm.com/ibmdl/pub/software/awdtools/wdsc/v7/70/documents/install_instruction/install.html.

2.1 Hardware requirements

There are no additional processor or memory requirements for installing this fix pack; however, there might be additional disk space requirements depending on whether you are installing the fix pack at the same time that you install WebSphere Development Studio Client, Version 7.0 or if you are installing the fix pack as an update:

• If you are installing the fix pack at the same time that you install WebSphere Development Studio Client, Version 7.0, then the disk space requirements are essentially the same as for Version 7.0.
• If you are installing the fix pack as an update, however, you might need up to an additional 335 MB of disk space. Your actual disk space requirements depend on the feature that you selected when you installed version 7.0 of the product.

(Optional) If you choose to download the update as a compressed file for local installation, you require approximately 335 MB to store and extract the compressed file.

2.2 Software requirements

This section describes the additional software requirements for installing WebSphere Development Studio Client for iSeries, Version 7.0.0.1; to see the requirements for installing WebSphere Development Studio Client 7.0, see the Installation Guide.

Before you can install this fix pack, you must install IBM Installation Manager, Version 1.0.0.2. In Installation Manager, if you have not disabled the default setting to search the linked repositories during installation and update, IBM Installation Manager, Version 1.0.0.2 is automatically installed on your computer when you attempt to update or install packages using an earlier version of Installation Manager.

For additional information about Installation Manager, Version 1.0.0.2, refer to http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/im/1002/docs/readme/readme.html

2.3 Other requirements

Internet access is usually required because, by default, the update is located and installed by Installation Manager directly from the IBM update repository for WebSphere Development Studio Client, Version 7.0.

Important: When WebSphere Development Studio Client is installed, the location of its update repository is automatically embedded in Installation Manager. For Installation Manager to search the default update repository, the preference Search the linked repositories during installation and updates on the Repositories preference page must be selected. This preference is selected by default.

To install the fix pack from a different repository location (for example, if the fix pack is available on a shared drive or HTTP or HTTPS server) you must add the repository location in Installation Manager. To add a repository location:

1. Start Installation Manager
2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
3. On the Repositories page, click Add Repository.
4. In the Add repository window, enter the URL of the repository location or browse to it and enter a file path, and then click OK.
5. Click OK to close the Preference page.

2.4 Installation instructions

The following are the two common ways to install this update:

• If IBM WebSphere Development Studio Client for iSeries, Version 7.0 is already installed on your system, then you can install this update by using the Update Packages wizard in IBM Installation Manager. For general instructions on installing an update, refer to the section "Updating WebSphere Development Studio Client" in the Installation Guide. For detailed instructions, see Installing WebSphere Development Studio Client, Version 7.0.0.1 as an update.
• If you are installing IBM WebSphere Development Studio Client, Version 7.0 for the first time or if you are installing an additional instance of it, then you can install this update at the same time that you install IBM WebSphere Development Studio Client, Version 7.0 by clicking Check for updates on the Install page of the Installing Packages wizard in IBM Installation Manager. For general instructions on installing an update, refer to the section "Installing IBM WebSphere Development Studio Client using the IBM Installation Manager graphical interface" in the Installation Guide.

By default, the update is installed directly from the IBM update repository; however, it is also available for download. For details, see the specific installation instructions noted below for WebSphere Development Studio Client, Version 7.0.0.1.

2.4.1 Installing WebSphere Development Studio Client, Version 7.0.0.1 as an update

Install the fix pack with the same user account that installed the product.

Restrictions:

• WebSphere Development Studio Client, Version 7.0 must be installed.
• The product cannot be open when you install this fix pack. Also, ensure that all browsers and other applications opened by WebSphere Development Studio Client are closed.
• On Windows^® operating systems, you must use an account with Administrator privileges.

To find and install WebSphere Development Studio Client, Version 7.0.0.1 as an update:

1. Start IBM Installation Manager.
2. On the Start page of Installation Manager, click the Update Packages button.
3. If a new version of Installation Manager is found, you are prompted to confirm that you want to install it before you can continue. Click OK to proceed. Installation Manager automatically installs the new version, stops, restarts, and resumes.
4. In the Update packages wizard, select the Installed Location for WebSphere Development Studio Client and click Next. Installation Manager searches for updates in the WebSphere Development Studio Client repository on the Web, as well as any repository locations that you entered. A progress indicator shows the search is taking place.
5. By default, recommended updates are displayed and selected on the Update Packages page. Ensure that you select Version 7.0.0.1 for WebSphere Development Studio Client, then click Next.
6. On the Licenses page, read the license agreements for the update. On the left side of the License page; click each item to display the license agreement text.
   1. If you agree to the terms for all of the license agreements, click I accept the terms of the license agreements
   2. Click Next to continue.
   3. On the Summary page, review the information displayed, and then click Update. A progress indicator shows the percentage of the installation completed.
7. When the update process completes, a message that confirms the success of the process is displayed near the top of the page. Click View log file to open the log file for the current session in a new window. You must close the Installation Log window to continue.

You can download a compressed file containing the WebSphere Development Studio Client, Version 7001 fix pack; the files that you extract from the compressed file form a repository for the fix pack. You can install the fix pack from the repository on your own computer, or you can copy the repository to a shared drive or a HTTP or HTTPS server.

To download and install the fix pack, complete the following steps:

1. Download the fix pack.
2. Extract the compressed file in an appropriate directory. For example, extract the file to C:\temp.
3. Add the fix pack's repository location in IBM Installation Manager:
   1. Start IBM Installation Manager.
   2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
   3. On the Repositories page, click Add Repository.
   4. On the Add repository window, browse to and enter the file path to the rad\updates directory. For example, enter C:\temp\wdsc\updates and then click OK.
   5. Click OK to close the Preference page.
4. Install the fix pack as described previously in this document.

   Note:
   During the process of updating from a local repository, Installation Manager might prompt you for the location of the repository for WebSphere Development Studio Client, Version 7.0. If you installed the product from CDs or other media, they must be available when you use the update feature.

2.5 Uninstalling the fix pack

Although mentioned in the documentation, the rollback feature in the Uninstall Packages wizard is not enabled in Installation Manager, Version 1.0.0.2. As such, if you installed WebSphere Development Studio Client, Version 7.0, and then updated to version 7.0.0.1, it is not possible for you to revert to version 7.0 by using the Uninstall Packages wizard.

To revert to WebSphere Development Studio Client, Version 7.0, you must uninstall the entire package. A single uninstallation procedure removes the version 7.0 package and the upgraded version 7.0.0.1 package. After uninstalling, you can reinstall the version 7.0 package.

Before you uninstall WebSphere Development Studio Client, Version 7.0.0.1, perform the following steps:

1. Log in with a user account that has the same privileges as the account that was used to install the packages to be uninstalled.
2. Close WebSphere Development Studio Client, Version 7.0.0.1 and any other applications that you installed with Installation Manager.
3. If any applications opened by WebSphere Development Studio Client are still open, such as a browser or WebSphere Application Server, then close them.

To uninstall WebSphere Development Studio Client, Version 7.0.0.1:

1. Start IBM Installation Manager.
2. On the Start page, click Uninstall Packages.
3. Follow the instructions in the wizard.

For additional instructions on uninstalling WebSphere Development Studio Client, see the Installation Guide or see the Installation Manager online help.

3.0 Fixes contained in this release

The following APARs are fixed in this release:

For all WebSphere Development Studio Client APARs refer to: http://www-1.ibm.com/support/search.wss?rs=3239&lang=en&loc=en_US&r=10&cs=utf-8&rankfile=0&cc=&spc=&stc=&apar=include&q1=5722WDS03+OR+5722WDS04+OR+5722WDS05+OR+5722WDS05+OR+5722WDS06+OR+5722WDS07+OR+5722WDS08+OR+5722WDS09&q2=7.0.0.1&Go.x=0&Go.y=0&sort=desc&tc=SSZND2&dc=DB550+D100&dtm

• (PK12110) The tutorial on creating a Web service from an enterprise bean does not locate the enterprise bean's implementation class correctly.
• (PK28902) Problem in Web service tutorial on temperature conversion.
• (PK20134) Incorrect documentation on setting the context root of a Web project.
• (PK37099/PK37167) In UML modeling, when migrating a v6.x model to v7.0, notes are lost in sequence diagrams.
• (PK33881) In UML modeling, the functionality of hiding execution occurrences is needed in sequence diagrams.
• (PK10647) In UML modeling, lifelines cannot be resized vertically in sequence diagrams.
• (PK12787) In UML modeling, operation signatures are not properly displayed with the show operation signature preference selected.

The following known limitations or problems that were listed in the version 7.0 release notes have been fixed in this release:

• Web and Java Tools:
  • The Program Call wizard, Web Services wizard, or Web Interaction wizard fail to import files if the name starts with the file extension, for example, pcml1.pcml
  • When creating a Web service from an iSeries program with structure array parameters, exceptions may occur at runtime under the following conditions:
    • The value for the structure arrays "count" refers to another program parameter (for example, a variable length count)
    • That parameters data type is defined as integer.
  • When creating a Bottom up iSeries Program Web Service from an RPG or COBOL source file, the default value of the Program object field may not be desirable.
• WebFacing:
  • Conversion failed for DDS with database reference fields which have a mix of specified and unspecified database records.
  • Running HATS/WebFacing enabled applications caused iSeries thread build-ups.
  • Cursor did not progress properly to subfile fields with EDTMSK keyword.
  • Could not include help panels outside of the current panel group.
  • Syntax errors were incorrectly reported while editing DDS.
  • Positioning the cursor to a field using the Hyperlink Web Setting cleared its previous contents.
  • DDS object mapping was wrong after deleting one of multiple members with the same name.
• In IBM Installation Manger, if a floating license server configuration is being recorded using the -record filename option a Null Pointer Exception will occur and the recording files will not be correctly written.
• In Software Development Platform core, some User Interfaces are displayed in the platform locale language even if only English is selected in installation by IBM Installation Manager.
• In Software Development Platform core, if you search the online documentation in the Help window (Help > Help Contents) and click one of the results, the content frame displays an XML source file rather than something readable.
• In IBM Packaging Utility, update offerings can only be copied into a target repository that contains the base offering. 
• In JET authoring, JET projects cannot be created in locations other than the default location.
• In J2EE extensions, a validation error occurs for a compound primary key that is generated from IBM xdoclet annotations.
• In J2EE extensions, IBM xdoclet annotations do not always update the JNDI name correctly.
• In J2EE extensions, an invalid value for destination type occurs when using IBM xdoclet annotations
• In WebSphere server tools, the Remove button on the Manage Shared WebSphere Servers dialog box does not work correctly.
• In WebSphere server tools, the New Server wizard might not retrieve the correct port information.
• In WebSphere server tools, the Profile Management tool does not work under a 64 bit processor.
• In WebSphere server tools, publishing large applications is slower than in the previous version.
• In WebSphere server tools, a TargetInvocationException error might occur when using the Table and Data Source Creator wizard
• In WebSphere testing and publishing tools, EJB jar changes are not picked up after running EJB through Universal Test Client (UTC).
• In User Assistance, Welcome pages may show errors or unexpected behavior.

For an updated list of fixes in this release, refer to the updated version of this readme file at: http://download.boulder.ibm.com/ibmdl/pub/software/awdtools/wdsc/v7/7001/documents/readme/readme.html.

4.0 Known limitations, problems, and workarounds

Updates, limitations, and known problems about WebSphere Development Studio Client for iSeries, Version 7.0, are documented in the form of technotes on the IBM Support Web site http://www.ibm.com/software/awdtools/wdt400/support.

As limitations and problems are discovered and resolved, the IBM Software Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems that you experience. The Technotes link in the Self Help section of the WebSphere Development Studio Client for iSeries Web site launches a customized query of the live Support knowledge base. To narrow your search, specify V7 as the search term. To create your own query, go to the Advanced search page on the IBM Software Support Web site.

4.1 Data tooling documentation contains a reference to unsupported functionality

The "Developing data access applications" section of the information center incorrectly contains a reference to functionality supporting the deployment of JAR files for Java^™ stored procedures, in the topic called "Routine and JAR file deployment." 
JAR file deployment is not supported, and the reference should be ignored. The rest of the information in this topic is accurate.

4.2 Internal server error "SAXException: Premature end of file" occurs when invoking an Axis Web service on WebSphere Application Server

When invoking an Axis Web service created using the Web Services Wizard on a WebSphere Application Server server, you might get a "(500) Internal Server Error" with the following message in the server console:

org.apache.axis.InternalException: org.apache.axis.ConfigurationException: org.xml.sax.SAXException: Fatal Error: URI=null Line=-1: Premature end of file.

This error occurs because the server-config.wsdd file in the Web project's WebContent/WEB-INF directory is empty.

Workaround: Choose a non-default location as the Web project's Java output directory before creating an Axis Web service on a WebSphere Application Server. 
To change the Java output directory:

1. In the Project Explorer view, right-click the Web project and select Properties.
2. In the left-hand pane of the Properties window, click Java Build Path.
3. Click the Source tab.
4. On the Source folders on build path page, Select Allow output folders for source folders check box, and then change the Default output folder entry to something other than WebProject/WebContent/WEB-INF/classes, whereWebProject is the name of the Web Project.   For example, change the output folder to WebProject/output/classes.
   

4.3 J2C "Same Input and Output" Sample link does not work on the Linux operating system

An error occurs when you run the application on the Linux operating system only. When you open Help > Samples Gallery > Technology Samples > J2C Java Bean Technology Samples > Same Input and Output sample, and you click on the Import the sample (for WAS 6.0) link, you will get an error. The import wizard does not open, and a Null Pointer Exception message appears in the console:

Exception in GalleryWizardAction: java.lang.NullPointerException
wizard = com.ibm.etools.project.interchange.generic.CustomProjectInterchangeImportWizard
java.lang.NullPointerException
        at com.ibm.etools.project.interchange.generic.CustomProjectInterchangeIm portWizard$1.getAllProjectMap(Unknown Source)
        at com.ibm.etools.project.interchange.generic.CustomProjectInterchangeIm portWizard$1.doAddPages(Unknown Source)
        at com.ibm.etools.emf.workbench.ui.wizard.datamodel.WTPWizard.addPages(U nknown Source)
        at org.eclipse.jface.wizard.WizardDialog.createContents(Unknown Source)
        at org.eclipse.jface.window.Window.create(Unknown Source)
        at org.eclipse.jface.dialogs.Dialog.create(Unknown Source)
        at com.ibm.samplegallery.GalleryWizardAction$RunnableWizardDelegate.run( Unknown Source)
        at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
        at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Sourc e)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
        at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Sou rce)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runAppli cation(Unknown Source)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Un known Source)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)
        at org.eclipse.core.launcher.Main.basicRun(Unknown Source)
        at org.eclipse.core.launcher.Main.run(Unknown Source)
        at org.eclipse.core.launcher.Main.main(Unknown Source)

Workaround:  Select the Import the sample (for WAS 6.1) link, and it will work on either WebSphere Application Server 6.0 or 6.1.

4.4 Converting static Web project with Web site navigation enabled to a dynamic Web project fails with an exception

When you attempt to convert a static Web project that has the Web site navigation enabled to a dynamic Web project (by selecting the project in the Project Explorer view, and then selecting Convert to a Dynamic Web Project from the Project menu), the conversion fails with exception "Cannot remove nature org.eclipse.wst.common.modulecore.ModuleCoreNature because it is a prerequisite of nature com.ibm.etools.siteedit.WebSiteNature."

Cause: The internal process of converting a static Web project (with Web site navigation) to a dynamic Web project requires removal of a project nature (ModuleCoreNature) that has a dependant nature (WebSiteNature).

Workaround: To convert the project successfully, first edit the .project file of your static Web project using the following steps:

1. Click Window  > Open Perspective > Other > Resource. The Resource perspective opens.
2. In the Navigator view expand the project folder and open the project's .project file. The XML editor opens by default.
3. In the Design view, expand the projectDescription node and then expand the natures node.
4. Select the nature com.ibm.etools.siteedit.WebSiteNature, then right-click and select Remove. The com.ibm.etools.siteedit.WebSiteNature is deleted from the natures node.
5. Save the .project file.

You can now successfully convert the project to a dynamic Web project.

 

4.5 Publishing an EJB with multiple source directories fails with an error

If you attempt to publish an EJB project containing more than one source folder (for example, an annotation project that has an alternative source folder), publishing fails with errors.
You might see errors similar to the following example in the Console view:

 [1/11/07 15:28:36:906 PST] 00000027 SystemErr     R
*** ERROR ***: Thu Jan 11 15:28:36 PST 2007    org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0023E Unable to open module file "AuctionV60EJB.jar" in EAR file "C:\v7001workspaces\7001Week2\AuctionV60EAR"
    Stack trace of nested exception:
    org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0006E Archive is not a valid EJB JAR File because the deployment descriptor can not be found (case sensitive): META-INF/ejb-jar.xml

Workaround:  Edit the looseconfig.xmi file (a generated file) using the following steps:

1. On your computer, navigate to your workspace directory open in an editor the file /.metadata/.plugins/com.ibm.etools.wrd.websphere/looseconfigurations/EAR project name/looseconfig.xmi, where EAR project name is the name of your EAR project.
2. Change the two path attributes binariesPath and resourcesPath so to reference "ejbModule" instead of  "gen/src" for the EJB jar file.
3. Save your changes.

If the server is still running, restart the server for the changes to take effect.
You should now be able to successfully publish the EJB.

 

4.6 The rollback feature is not enabled in Installation Manager, Version 1.0.0.2

The rollback feature in the Uninstall Packages wizard and the rollback command for silent installation is not enabled in Installation Manager, Version 1.0.0.2. As such, you cannot revert to a previously installed version of a package.

For example, if you installed WebSphere Development Studio Client, Version 7.0, and then updated to version 7.0.0.1, it is not possible for you to revert to version 7.0 by using the wizard or the command.

Workaround: To revert to an earlier version of a package, you must uninstall the entire package. A single uninstallation procedure removes the version 7.0 package and the upgraded version 7.0.0.1 package. After uninstalling, you need to reinstall the version 7.0 package.

 

5.0 IBM WebSphere Software Support

IBM WebSphere Software Support provides you with technical assistance.

For contact information and guidelines or reference materials that you will need when you require support, read the IBM Software Support Handbook.

For FAQs, lists of known problems and fixes, and other support information, visit the IBM WebSphere Software Support Web site.

For WebSphere software product news, events, and other information, visit the IBM WebSphere Software Web site.

Before you contact IBM WebSphere Software Support, gather the background information that you will need to describe your problem. When describing a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

• What software versions were you running when the problem occurred?
• Do you have logs, traces, or messages that are related to the problem?
• Can you reproduce the problem? If so, what steps do you take to reproduce it?
• Is there a workaround for the problem? If so, be prepared to describe the workaround.

Posting questions on a newsgroup

To post your questions on the newsgroups, use the following resources.

News server:

• news://news.software.ibm.com/ibm.software.websphere.studio400

Suggested newsgroup:

• ibm.software.websphere.studio400

Other suggested forum:

• http://lists.midrange.com/cgi-bin/listinfo/wdsci-l

6.0 Notices and trademarks

© Copyright IBM Corporation 2007. All Rights Reserved.


This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation 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 documentation. The furnishing of this documentation does not give 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, 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 OR CONDITIONS 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.

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:

Intellectual Property Dept. for Rational Software
IBM Corporation
3600 Steeles Avenue East
Markham, Ontario
Canada L3R 9Z7

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 documentation 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 contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may 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.

Trademarks and service marks

The following terms are trademarks of the IBM Corporation in the United States or other countries or both:

• ClearCase
• IBM
• i5/OS
• iSeries
• Rational
• System i
• WebSphere

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

Microsoft and Windows 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.

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.