IBM Books

Readme File


Table of Contents

Introduction

  • Text Versions of the Suite License Located in ibmnt\license
  • WebSphere Application Server
  • Select the Version of IBM HTTP Server to Install When Using Individual Product Install
  • Manually Change the WebSphere Sample Shortcut
  • Sample Applications Considerations
  • Use Sample Application Navigation Links
  • Configuring the Domino Server
  • TCP/IP Port Number Conflict
  • Provide Appropriate Web Server Information for Initial Use of Sample Application
  • DB2 UDB
  • Multiple Copies of ldap.dll Found
  • Correct DB2 Extenders Documentation Shortcuts
  • IBM Suites Web Administration
  • Error 404 (Page cannot be found) When Starting Web Administration
  • Removing A Server Does Not Remove the Drawer in Web Administration
  • IBM SecureWay Directory
  • Set Users to Have the User Right to Log on Locally Attribute
  • Set IBM SecureWay Directory Service to Start Automatically
  • Check Web Administration for SecureWay Directory Log File for Errors
  • Configuring the Directory with SSL Support: Update to Task 2, Step 6 in Getting Started Manual
  • IBM Suites Directory Support
  • Restriction for User and Groups Common Names
  • Populating Users and Groups to SecureWay Directory
  • Synchronizing Users and Groups in SecureWay Directory
  • Update to Task 7: Enable Synchronization in Getting Started Manual
  • Error Removing an Object From the Directory
  • Error Removing a Synchronized Directory
  • Communications Server User ID Cannot be the Same as the Machine Name
  • Location of Log File for Netscape Communicator
  • Ignore Message That HTML File Cannot Be Found
  • Netscape FastTrack Web Server Configured Automatically
  • Install Internet Explorer 4.01 or Later as Default Browser
  • IBM MQSeries
  • MQSeries Requires Internet Explorer Version 4.01 with Service Pack 1 and the Java Virtual Machine Component
  • MQSeries Documentation
  • National Language Considerations
  • IBM Suites Web Administration
  • IBM Suites Directory Support
  • IBM SecureWay Directory
  • Lotus Domino
  • Netscape Communicator
  • Translation Exceptions
  • Copyright Information
  • Trademarks

  • Introduction

    This Readme file applies to the following licensed programs:

    To see the latest information about the suite, hints and tips, workarounds, code fixes and white papers, see web site:

    To access the suite support page, see:

    An HTML version of the suite Getting Started manual is located on CD number 1 in directory \info\<xxx>\, where <xxx> indicates the language code for the version of the software you are installing. You can also access an HTML version of the book by doing one of the following:


    Text Versions of the Suite License Located in ibmnt\license

    After you install the suite, you can find translated text versions of the suite license agreement in directory ibmnt\license.


    WebSphere Application Server

    The following sections are considerations when installing WebSphere.

    Select the Version of IBM HTTP Server to Install When Using Individual Product Install

    When you install WebSphere using Individual Product install, you must select all of the subcomponents you want to install. During the WebSphere installation, on the Choose Application Server Plugins window, check the box next to Version 1.3.3.x under IBM HTTP Server.

    Manually Change the WebSphere Sample Shortcut

    If you configure IBM HTTP Server with a port other than port 80, you must manually update the WebSphere sample shortcut. To change the shortcut, do the following:


    Sample Applications Considerations

    The following sections are considerations when installing the Sample Applications.

    Use Sample Application Navigation Links

    Use the navigation links (for example, Back, Forward) provided with the Sample Applications. Avoid using the browser Back and Forward buttons.

    Configuring the Domino Server

    When you install the Sample Applications, a window containing installation instructions will be displayed. Provide the following information to configure the Domino server.

    1. On page 1, click First Domino Server.
    2. On page 2, click Quick and Easy Setup.
    3. On page 3, click Web Browsers.
    4. On page 4, change password fields on the screen by clicking Edit. Record the server's hostname, the Administrator's first name, last name, and password.
    5. Click OK to proceed, then click Finish.
    6. Record the server's name and exit by clicking Exit Configuration.

    TCP/IP Port Number Conflict

    During installation of the Sample Applications, the Domino web server will be configured to use port 80, and the IBM HTTP Server will be configured to use port 8080 or higher. If the Sample Applications installation detects that port 80 is already in use by another program, an informational message will be displayed prior to the Domino server configuration instructions shown above. If possible, you should reconfigure the other program to use a different port.

    If you must change the Domino Web server's port number, use the Lotus Domino Administrator Client:

    1. Select Start, Programs, Lotus Applications, Lotus Domino Server, and wait for Domino Server to start.
    2. Select Start, Programs, Lotus Applications, Lotus Domino Administrator. If this is the first time the administrator client is run, you will need to supply the information you recorded while configuring the Lotus Domino Server.
    3. Click X next to the Welcome box.
    4. Select Configuration.
    5. Click the twistie next to Server.
    6. Double-click on CurrentServer Document.
    7. Click Edit Server.
    8. Click Ports.
    9. Click Internet Ports.
    10. Change the TCP/IP port number under Web HTTP/HTTPS. A number greater than 8000 is recommended.
    11. Restart the Domino web server. In the Domino server window, enter the following commands:
      tell http quit
      
      load http
      
      

    Provide Appropriate Web Server Information for Initial Use of Sample Application

    The Intranet Sales Manager and the Customer Service applications are based on Domino and utilize the Domino web server. The Employee Information Management and Buyers Club applications are based on WebSphere and utilize the IBM HTTP Server. The first time you run these applications, you may be asked to supply the hostname and port number information for the Domino web server and for WebSphere (IBM HTTP Server). Read the text of the prompt carefully to determine which web server's information should be provided.

    If you enter incorrect hostname and port number information, links to some of the applications will fail. You can correct hostname and port number information by selecting Administrator Information on the Samples' main menu web page.


    DB2 UDB

    The following hints and tips relate to DB2 UDB.

    Multiple Copies of ldap.dll Found

    Depending on the software products that are installed on the same Windows NT server as DB2 UDB, it is possible that several copies of ldap.dll may be present on the machine. If a back level version of ldap.dll is present, you may see the following error when you attempt to run the db2ldcfg command:

    Cannot find ldap_server_free_list in dynamic library ldap.dll  
    
    

    You can correct this error by ensuring that you have installed the IBM SecureWay LDAP client, and that the directory for ldap.dll as provided with that client appears first in the Windows NT system path (before the directories for any other products that include ldap.dll).

    Correct DB2 Extenders Documentation Shortcuts

    To access two of the DB2 Extenders documentation files, correct the shortcut definitions by doing the following:

    You should now be able to access the documents.


    IBM Suites Web Administration

    The following hints and tips relate to IBM Suites Web Administration.

    Error 404 (Page cannot be found) When Starting Web Administration

    If the port that the web server used for Web Administration is not the default port 80, then you must specify the port number when you start Web Administration:

    http://hostName.domainName:portNumber/console
    
    

    Removing A Server Does Not Remove the Drawer in Web Administration

    When you remove a server, the server drawer (if previously added) is not removed from IBM Suites Web Administration. When you log on after uninstalling a server, you get a message indicating the server is no longer present. Click OK and Web Administration works fine. You can then use the Console settings task to manually remove the drawer.


    IBM SecureWay Directory

    The following hints and tips relate to the IBM SecureWay Directory.

    Set Users to Have the User Right to Log on Locally Attribute

    If you install SecureWay Directory on the same machine as your Windows NT Primary Domain Controller (PDC), make sure that the users have the user right to log on locally. To set this attribute, do the following:

    Set IBM SecureWay Directory Service to Start Automatically

    After installing IBM SecureWay Directory and restarting your machine, the IBM SecureWay Directory service does not start automatically. To set the service to start automatically, do the following:

    1. Select Start, Settings, Control Panel, Services.
    2. Click IBM SecureWay Directory, and then click Startup.
    3. Select Automatic under the Startup Type window.
    4. Click OK.

    Check Web Administration for SecureWay Directory Log File for Errors

    When reviewing the Windows NT Event Viewer - Application Log, you may see errors logged for the SecureWay Directory server which begin with the following text:

    The description for Event ID () in Source () could not be found.
    
    

    This is a known problem. To determine if there are any serious errors, see the error log found in the SecureWay Directory Server Web Administration.

    Configuring the Directory with SSL Support: Update to Task 2, Step 6 in Getting Started Manual

    The following information replaces the information provided in the suite Getting Started manual, Chapter 6, Task 2: Configure the directory, Step 6 (configuring the SecureWay Directory to run with or without Secure Sockets Layer (SSL)).

    1. You can configure the SecureWay Directory to run with or without Secure Sockets Layer (SSL) support. SSL provides encryption of data and authentication using public-key certificates. To enable the directory to run with SSL support, complete the following steps on the SecureWay Directory server machine:
      1. Create a new keyring file with a certificate, to be used in authenticating the server in SSL data flows.
        1. Select Start, Programs, IBM Suite for Windows NT, IBM Key Management.
        2. Select Key Database File, New. It is recommended that the LDAP server key database file reside in the x:\<ldapdir>\etc directory, where x:\<ldapdir> is the drive and directory where SecureWay Directory is installed. Use the default Key database type, CMS key database file.
        3. Enter the password for the file. Select the checkbox for "Stash the password to a file?".
        4. From the certificate drop-down list, select Personal Certificates, and then select Create, New Self-Signed Certificates.
          Note:It is possible to obtain a certificate from a public certificate authority to be added to this file, but this is not necessary unless the server is to be accessed from outside the enterprise.
        5. From the Create New Self-Signed Certificate window, enter a key label and the organization, for example, o=finance.
        6. Extract and save the certificate to a <xxx>.arm file, where <xxx> is the file name of your choice, by highlighting the file in the certificate list and clicking Extract certificate. This is necessary so that the certificate and public key can be added to the key rings of LDAP clients that will access this server.
        7. Use the Key Management Utility to add the certificate from the <xxx>.arm file into x:\<ldapdir>\java\ldapkey.class, where x:\<ldapdir> is the drive and directory where SecureWay Directory is installed. This file is used for SSL access to the server from Java programs, including the General Administration drawer of Web Administration.
      2. Click the SecureWay Directory Server drawer from the Web Administration console to access the SecureWay Server Administration. The Server folder contains an SSL enablement task.
        1. Specify whether the server accepts SSL and non-SSL connections (SSL=on), only non-SSL connections (SSL=off), or only SSL connections (SSL=only).
        2. For Authentication method, select Server Authentication. The server should be configured to not require client certificates for authentication, as client certificates are not widely deployed.
        3. You do not need to change the Secure port number.
        4. For Key database path and file name, specify the fully-qualified path to the server's keyring file created in 1a.ii.
        5. If a stash file is used, key password is not required.
        6. To ensure that the desired SSL ciphers are configured, select V3 cipher and select the ciphers that the LDAP server will use when creating secure connections. For maximum security, eliminate the weaker ciphers (for example, the 40-bit ciphers).
      3. Restart the server for SSL support to become active and for automatic startup.
        1. Select Start, Settings, Control Panel, Services.
        2. Click IBM SecureWay Directory, and then click Startup.
        3. Select Automatic under the Startup Type window.
        4. Click OK.

    IBM Suites Directory Support

    The following hints and tips relate to the IBM Suites Directory Support.

    Restriction for User and Groups Common Names

    Users and groups cannot have the common name cn=Domino or cn=NTV4. These names are reserved for use by the SecureWay Directory.

    Populating Users and Groups to SecureWay Directory

    The populate utility populates attributes from Windows NT Domains as follows:
    Directory Attribute Taken from this Windows NT Attribute
    User's Last Name Username
    User's Full Name Username
    User's User ID Username
    Group's Full Name Group name

    Group memberships are preserved.

    Only the global groups for the Windows NT domain are populated. Windows NT local groups are not populated.

    The populate utility populates attributes from a Domino directory as follows:
    Directory Attribute Taken from this Domino Attribute
    User's Last Name Last Name
    User's Full Name User Name
    User's User ID Short Name, if present
    Group's Full Name Group Name

    Group memberships are preserved.

    Domino and Windows NT Populate Command

    The following example for the Domino populate command appears in the suite Getting Started manual, Chapter 6, Task 5.

    Enclose any command arguments that have several parts within quotes. The corrected example follows:

    dom2ldif -i "e:\notes\data\sync.ini" -S domserv1 -D dominom1 -O domino1.ldif 
    
    -G "ou=Marketing,o=Sales,c=US" -U "ou=Marketing,o=Sales,c=US" -A "sys=dominom1,cn=Domino,o=Sales, c=US" 
    
    

    The syntax for the Windows NT domain populate command follows. The nt2ldif command is case sensitive, and all options and parameters must be given in the case shown. This syntax is incorrect in the suite Getting Started manual, Chapter 6, Task 5.

    nt2ldif -D dname -O outputfile -G grouplocation -U userlocation
    
    -A synchdomain -s TRUE
    
    

    In both examples, to find the value for synchdomain, from the General Administration drawer of Web Administration, click Work with synchronized directories and then click Show all. The distinguished name appears on the next window.

    Preparation Needed for Account Validation When Populating Users from Domino

    The account validation utility requires users to provide a user ID and password to validate their new SecureWay Directory account that is created by the populate utility. If the users are populated from a Domino directory, then the user ID and password that is used to validate the account is the user's Domino short name and HTTP password, respectively.

    To set the HTTP password for Domino users, do the following:

    Considerations When Populating from a Domino Directory

    CLI Error While Populating More Than 32,000 Users and Groups

    If you are going to populate more than 32,000 users and groups from a Windows NT Domain or Domino Domain to SecureWay Directory, it is recommended that you add the following stanza to the\sqllib\db2cli.ini file:

    [COMMON]
    
    TempDir=x:\your-directory
    
    

    where x:\your-directory specifies an existing directory on a drive that has space available. DB2 will write temporary files to this directory. The amount of space required depends on the size of the directory entries you are adding or updating, but generally does require more space than the size of the largest entry you are updating.

    If this update is not made to db2cli.ini, the following error may be logged in SecureWay Directory's slapd error log:

    [IBM][CLI Driver] CLI0157E Error opening a file.  SQLSTATE=S1507
    
    

    Synchronizing Users and Groups in SecureWay Directory

    When you initially synchronize with a Windows NT Domain, attributes are synchronized as follows:
    Directory Attribute Goes to this Windows NT Attribute
    User's User ID Username
    User's Password Password
    Group's Full Name Group name
    Group's members Group's members

    No other fields are transferred to Windows NT Domains.
    Note:When you create a new user and synchronize this user with a Windows NT Domain, Windows NT will automatically add this user to the Domain Users group in the Windows NT Domain. This is not automatically done in the SecureWay directory.

    When you initially synchronize with a Domino directory, attributes are synchronized as follows:


    Directory Attribute Goes to this Domino Attribute
    User's First Name First Name
    User's Last Name Last Name
    User's Full Name User Name
    User's Password Password
    User's User ID Short Name
    Group's Full Name Group Name
    Group's members Group's members

    No other fields are transferred to Domino.

    Other Synchronization Considerations

    Synchronization after Population from a Windows NT Domain

    If synchronization is enabled for a Windows NT domain after the SecureWay Directory has been populated from that domain, you must load the LDIF file used in population into the synchronization agent. This must be done before additional changes are made to the contents of the SecureWay Directory. To load the LDIF file, you use the ldapadd command as follows:

    ldapadd -h hostname -p port -D masterdn -w password -c -f ldif_file
    
     
    
    

    where:

    hostname
    The hostname of the Windows NT primary domain controller on which the SecureWay synchronization service is running.

    port
    The port used by that service, as configured in md.conf.

    masterdn
    The distinguished name of the administrator for the service, as configured in md.conf.

    password
    The corresponding password set up using the mdpw utility.

    -c
    Indicates that population of the directory continues even if a given entry cannot be created because it already exists.

    ldif_file
    The file created by the nt2ldif command which was used to populate the SecureWay directory.

    Synchronization with Domino, md.conf File Fields

    To configure the synchronization agent, you edit the md.conf file. For synchronization with Domino, be aware of the following field restrictions.

    inipath
    The full pathname of the INI file created as previously described. The pathname for this file must contain only English characters.

    certpath
    The full pathname of the certifier ID file for this Domino server. The pathname for this file must contain only English characters.

    Account validation for Windows NT Domains

    Account validation for user entries populated from Windows NT domains only works if the server on which the IBM SecureWay directory is running is a member of the Windows NT domain from which population occurred, or if it is a member of a domain with a trust relationship with the Windows NT domain from which population occurred.

    Preventing Unwanted Deletions of Users and Groups From Synchronized Domains

    WARNING! If you use General Administration to remove a synchronized Windows NT or Domino domain for a user or group entry in the SecureWay Directory, the corresponding user or group is deleted from the Windows NT or Domino domain. Also, if you delete a user or group entry from the SecureWay Directory, and that user or group is synchronized with a Windows NT or Domino domain, the corresponding user or group entry in the Windows NT or Domino domain is also deleted.

    If you want to remove synchronized entries from the IBM SecureWay Directory without affecting the corresponding entries in the Windows NT or Domino domain, or if you want to sever the synchronization between certain entries in the SecureWay Directory and any synchronized domains, do the following:

    Blank Screen Appears When Synchronizing a Directory

    If you get a blank screen and a directory failed to synchronize to the SecureWay Directory, close and reopen your web browser, and try the synchronization again.

    Update to Task 7: Enable Synchronization in Getting Started Manual

    To start the IBM Key Management utility described in Task 7: Enable synchronization of users and groups with other directories, step 5a of the suite Getting Started manual, do the following:

    In addition, step 5d of Task 7 states where to add the certificate from the <xxx>.arm file. You should place this file into the keyring created in Task 2, 1a.ii.

    Error Removing an Object From the Directory

    If you receive an error when attempting to remove an object (for example, removing an organizational unit), the problem is that the object has other objects beneath it in the directory tree. Delete all users, groups, or other objects beneath this object in the tree and try again.

    Error Removing a Synchronized Directory

    If you receive an error message when trying to remove a synchronized directory, there may be at least one user or group that is synchronized with this directory. Remove the user or group synchronization from the synchronized directory and try again.


    Communications Server User ID Cannot be the Same as the Machine Name

    When you install eNetwork Communication Server, the user ID you supply must not be the same name as the machine name. Use a different name for this value.


    Location of Log File for Netscape Communicator

    If a component fails to install, a dialog appears at the end of the installation giving you the option to view the log file, IWIIINST.LOG, for any failed component. For Netscape Communicator, this file is located in the \ibmnt\netscape directory. See the suite Getting Started manual for additional information.


    Ignore Message That HTML File Cannot Be Found

    If you receive a message that a shortcut to an HTML file cannot be found, for example a message similar to the following:

     "cannot find 'C:\<filename>\INDEX.HTML' (or config file) file.
    
     
    
    

    Click OK to proceed. Even though the message displays, the requested HTML file displays. To avoid getting this message, you can change the name of the program that opens the HTML shortcut file.

    1. From Windows Explorer, select View, Options, File Types.
    2. Click Netscape Hypertext Document in the list.
    3. Change the name of the program that opens an HTML file from Netscape to NSSHELL.

    Netscape FastTrack Web Server Configured Automatically

    The section Netscape FastTrack Considerations in the IBM Suites Getting Started manual describes how to manually configure the Netscape FastTrack web server. The suite installation program automatically configures this server now.


    Install Internet Explorer 4.01 or Later as Default Browser

    If you plan to use Microsoft Internet Explorer as your default web browser, install Internet Explorer 4.01 or later prior to installing the suite components.


    IBM MQSeries

    MQSeries Requires Internet Explorer Version 4.01 with Service Pack 1 and the Java Virtual Machine Component

    If you have any prior version of Internet Explorer already installed on the server, install Version 4.01 with Service Pack 1 or later on the same drive. Having multiple versions of the same product on a single machine causes installation errors. In addition, MQSeries requires that you install Internet Explorer with the Java Virtual Machine component.

    MQSeries Documentation

    Before you install MQSeries, see the Quick Beginnings manual for more information. PDF versions of the Brazilian Portuguese, English, French, German, Italian, and Spanish manuals are located on CD number 6 in \mqseries\docs\Acrobat\<xx_xx>\, where <xx_xx> indicates the language code for the version of the software you are installing.

    In addition, you can access all language versions (including Japanese, Korean, Simplified Chinese, and Traditional Chinese) of the Quick Beginnings manual plus several other MQSeries publications in \mqseries\HTMLHelp\<xx_xx>\, where <xx_xx> indicates the language code for the version of the software you are installing. You must install the HTML Help tool to view this documentation (see \mqseries\Prereqs\HTMLHelp\).

    If installed, you have access to the following information from the MQSeries for Windows NT entry on Windows:

    In addition, see web sites:


    National Language Considerations

    This section defines national language considerations for the suite components:

    IBM Suites Web Administration

    The following topics are national language considerations for IBM Suites Web Administration.

    Using Web Administration with Simplified Chinese Version of Netscape Navigator

    If you use Web Administration with the Simplified Chinese (CHS) version of Netscape Navigator 4.51, you may find the fonts too small for productive use. You can set the variable width and fixed width font size from the Netscape Navigator dialogs by selecting Edit, Preferences, open the Appearance category, and click Fonts.

    Running Web Administration on a Traditional Spanish Machine

    If you run Web Administration from a machine with a locale setting of Traditional Spanish, you may see English instead of Spanish text in some places. Either use Microsoft Internet Explorer instead of Netscape Navigator or change your default locale to Mexico.

    IBM Suites Directory Support

    The following topics are national language considerations for IBM Suites directory support:

    Account Validation

    You cannot use the account validation utility to set the initial password for an account populated from Windows NT or Domino, if the original user ID or password contained DBCS characters. You must use the user management forms in the General Administration drawer in the IBM Suites Web Administration to set the password.

    Store md.conf File in the UTF-8 Codepage

    When you edit the md.conf file to enable directory synchronization, you must ensure that this file is stored in the UTF-8 codepage. This is automatic if all file contents are in US English characters, because the UTF-8 representation of US English characters is the same as the Windows native representation. This is not true for the character sets of most other languages.

    IBM SecureWay synchronization agent includes a utility to convert files from the Windows native codepage for the active locale to UTF-8. Instead of using this utility, we recommend that you edit and save the file using Netscape Composer by doing the following.

    1. Create a backup copy of md.conf. Copy md.conf to mdconf.txt.
    2. Start Netscape Composer.
    3. Open mdconf.txt file as text.
    4. Change character code set to UTF-8 (from the menu bar, select View, Character Set, Unicode(UTF-8)).
    5. Edit mdconf.txt (password field is blank).
    6. Save the file as a text file.
    7. Copy mdconf.txt to md.conf.

    Use Locale Format for certificateexpirationdate Field in md.conf File

    If you are setting up synchronization with a Domino domain, be careful to put the certificateexpirationdate in a format appropriate to the locale. For the United states, the expiration date might be 12/31/2000, but the same date must be written 31/12/2000 for most European locales, and 2000/12/31 for Japan, China, and some other locales.

    IBM SecureWay Directory

    If you use SecureWay Directory as your directory server, refer to the SecureWay Directory documentation for information regarding national language support considerations.

    For data entry and storage, SecureWay Directory only supports characters contained in the codepages associated with the following languages:

    The default locale for machines on which the SecureWay Directory server and the browser used for either IBM Suites Web Administration or SecureWay Directory Administration must be set for one of these languages or another language which uses one of the same codepages. In addition, your browser must also be configured to accept and display character data for the default locale. For example, Dutch characters can be used as long as Dutch is set as the default locale since both Dutch and English use the same codepage.

    This limitation also applies to character information entered using IBM Suites Web Administration when used in conjunction with a SecureWay Directory. This includes information related to users, groups, suffixes, organization units, organizations, domains, and localities.

    Lotus Domino

    If you use Domino as your directory server, refer to the Domino documentation for information regarding national language support considerations.

    Netscape Communicator

    The following topics are national language considerations for Netscape Communicator:

    Installation of Netscape Communicator on DBCS Versions of Windows NT May Hang

    In some cases, when you install Netscape Communicator on DBCS language versions of the Windows NT operating system, the installation may stop or hang during the installation of the RealPlayer component. If this occurs, cancel the suite installation, uninstall Netscape Communicator using Add/Remove Programs, and reinstall Netscape Communicator using Individual Product install. When the Netscape Setup Type window appears, select Custom and then click Next. On the Netscape Communicator 4.51 Options window, deselect the RealPlayer 5.0 component. Click Next and then proceed normally through the remaining installation panels.


    Translation Exceptions

    The installation program and the server and client components in the suite are translated into all languages listed in the suite Getting Started manual with the following additional exceptions:


    Copyright Information

    (C) Copyright IBM Corporation and others 1985, 1999. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

    This page may contain other proprietary notices and copyright information, the terms of which must be observed and followed.


    Trademarks

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

    The following terms are trademarks of other companies:

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