IBM (R) OS/2 (R) Warp Server for e-business General README This README contains the latest information on installing and using OS/2 Warp Server for e-business, also referred to as "OS/2 Warp Server." A copy of this README is available from the IBM Technical Databases and might include additional information that was not available at the time the OS/2 Warp Server for e-business documentation was written. To view this README from the IBM Technical Databases: 1. Go to http://ps.software.ibm.com 2. Click Technical Databases. 3. Click Technical Documents Database. 4. Click Documents by Product and then OS/2 Warp Server for e-business. 5. Click OS/2 Warp Server for e-business README. ____________ CONTENTS ____________ PART I. INSTALLATION 1.0 Installing OS/2 Warp Server over a Previous Version of OS/2 1.0.1 CHKINST 1.0.2 CONFIG.SYS File 1.0.3 IBMPEER 1.0.4 LAN Distance Connection Server 1.0.5 Japanese Printer Drivers 1.0.6 OS/2 2.11 1.0.7 PCMCIA 1.0.8 386 HPFS 1.1 Installing a Previous Version of OS/2 after Installing OS/2 Warp Server 1.2 Installing Remote Client with Serviceability and Diagnostic Aids 1.3 Installing Multimedia Device Support 1.4 Installing on an IBM ThinkPad 1.5 Customizing Installation through a Command File 1.6 Troubleshooting Installation 1.6.1 Bootable CD Problems 1.6.2 Volume and Partition Errors PART II. AFTER INSTALLATION 2.0 Additional Information Included with This Product 2.0.1 README Files 2.0.2 Books 2.1 Application and Component Considerations 2.1.1 Alias Sharing 2.1.2 DOS LAN Services (DLS) 4.0 2.1.3 FTP 2.1.4 Java 1.1.7 2.1.5 Lightweight Directory Access Protocol (LDAP) 2.1.6 Lotus Domino Go Webserver and IBM WebSphere Application Server 2.1.7 Lotus SmartSuite 97 2.1.8 Multiple Server Names 2.1.9 Netscape Communicator 4.04 for DBCS Systems 2.1.10 OS/2 Window Default Size and Position 2.1.11 PPP Server 2.1.12 Products That Add Locked Device Driver Statements 2.1.13 Screen Savers on Security-Enabled Servers 2.1.14 TCPBEUI on a DHCP Client 2.1.15 TCP/IP 2.1.16 Tivoli Management Agent 2.1.17 TME 10 Distributed Monitoring 2.1.18 WorkSpace On-Demand 2.1.19 386 HPFS 2.2 Remote IPL 2.2.1 DBCS RIPL Clients 2.2.2 OS/2 Clients 2.2.3 RIPL Disk Space 2.2.4 RIPL Removal 2.3 Commands, CONFIG.SYS Statements, and Messages 2.3.1 Kernel File Message 2.3.2 PREPACL 2.3.3 VIRTUALADDRESSLIMIT 2.3.4 XCOPY 2.4 Associated Bitmap-Fonts 2.5 Hardware Device and Device Driver Considerations 2.5.1 Adaptec Adapter 2.5.2 CPU Initialization on a Compaq 4500 2.5.3 Device Driver Adapters 2.5.4 IBM Token-Ring Adapters 2.5.5 IBM ISDN Co-Processor Adapters 2.5.6 PCMCIA Flash Memory and Hard Disk Support 2.5.7 Universal Serial Bus Devices 2.5.8 802.2 RIPL with a DOS Network Adapter Device Driver 2.6 Printing 2.6.1 LAN Notification and PSF/2 2.6.2 Multiple Printers 2.6.3 Online Documentation 2.6.4 PSF/2 Print Submitter and Print Queues Not Connected to PSF/2 2.6.5 PSF/2 Uninstall 2.6.6 QREADER.NLM PART III TRADEMARKS ____________________________ PART I. BEFORE INSTALLATION ____________________________ ATTENTION: The following sections provide important information about the installation of OS/2 Warp Server. Read these sections prior to installing this product. 1.0 INSTALLING OS/2 WARP SERVER OVER A PREVIOUS VERSION OF OS/2 _______________________________________________________________ Read the following information if you are installing OS/2 Warp Server over a previous version of OS/2. For detailed information about migrating to OS/2 Warp Server, see the "Migrating to OS/2 Warp Server for e-business" that is included with this product. 1.0.1 CHKINST -------------- If CHKINST, a migration utility that scans your system for potential migration problems (such as corrupt partitions or LVM-incompatible volumes), fails, check that: 1. Syntax and parameters passed to CHKINST are correct. 2. VCU.EXE and VCU.MSG are in the directory where you are using CHKINST. If these files are not in the directory, copy them from the root directory of the Server Pak CD. 1.0.2 CONFIG.SYS ----------------- If you are installing OS/2 Warp Server over a previous version of OS/2, the installation process automatically migrates your existing CONFIG.SYS file. However, if you changed any of the following statements, the changes are not migrated. o BUFFERS o FILES o IFS o IOPL o SET o AUTOSTART o SET RESTARTOBJECTS o Other statements that have been added by applications In audio device driver statements, parameters added after the Device Name parameter are not migrated. For example, in a Pro Audio Spectrum device driver statement, parameters after PAS161$ are not migrated. To preserve your changes to these statements you must manually migrate your CONFIG.SYS file. 1.0.3 IBMPEER -------------- IBMPEER must be removed before installing OS/2 Warp Server. To remove IBMPEER: 1. Double-click System Setup. 2. Double-click Install/Remove. 3. Double-click File and Print Client Install/Remove. 4. Select Remove OS/2 Peer from this workstation and click OK. 5. Shut down and restart your computer. NOTE: Do not remove MPTS if you have Netware installed and plan to migrate it to OS/2 Warp Server. 1.0.4 LAN Distance Connection Server ------------------------------------ o OS/2 Warp Server cannot be installed over a previously installed LAN Distance (R) Connection Server or LAN Distance Remote Server. Run LDREMOVE to remove LAN Distance Connection Server before installing OS/2 Warp Server. o If you plan to upgrade an installed LAN Distance Connection Server, you must backup your current security user definition file before you run LDREMOVE. The existing user definition file will be overwritten during the installation process. To backup the user definition file, copy the file named WCBUSRF.ISF from the WAL directory onto a diskette. (This file contains the user definitions.) After the installation of OS/2 Warp Server is completed, copy the backed up file from the diskette into the WAL directory. 1.0.5 Japanese Printer Drivers ------------------------------- If you are using Japanese 16-bit printer drivers (DESKJET.DRV, EPSON.DRV,ESCPAGE.DRV, PMLIPS3.DRV or PSCRIPT.DRV) on your current systemand you plan to migrate your system to OS/2 Warp Server without formatting, you must manually replace the 16-bit drivers with 32-bit drivers. All the printers supported by 16-bit drivers are supported by 32-bit drivers. Below are the 16-bit printer drivers and their newer equivalents: 16 bit driver 32-bit driver -------------- ---------------- DESKJET.DRV --> OMNI.DRV EPSON.DRV --> OMNI.DRV ESCPAGE.DRV --> OMNI.DRV PMLIPS3.DRV --> OMNI.DRV PSCRIPT.DRV --> PSCRIPT2.DRV To install the 32-bit drivers during installation, select from the proper printer model in printer selection panel and continue to install. To install the 32-bit drivers after installation, use "Selective installation" and select the appropriate printer model you want. NOTE: OS/2 clients and printers must use the same level printer drivers. The latest client FixPak contains the newest printer drivers. 1.0.6 OS/2 2.11 ---------------- In some cases, installing OS/2 Warp Server over OS/2 2.11 might fail with the following symptoms: o LVM shows the file system of the OS/2 2.11 volume as "unformatted" or "FAT," even if the volume is HPFS. o You are not given the "Do not format the volume" option during installation. If either of these problems occur, you might be able to migrate over OS/2 2.11 with the following steps: 1. Backup the OS/2 2.11 volume. NOTE: Do not use backup utilities that create an image of the drive instead of backing up individual files. Your backup utility must also have standalone restore capability. 2. Start the system with the OS/2 Warp Server installation diskettes or the OS/2 Warp Server for e-business Server Pak Installation CD. 3. When prompted, press F3 to exit to an OS/2 Window. 4. Change to the \OS2IMAGE\DISK_3 directory on the OS/2 Warp Server for e-business Server PAK CD. 5. Reformat the installation volume. Use the same file system that is currently on the OS/2 2.11 volume. 6. Restore the OS/2 2.11 volume from the backup. 7. Restart the installation of OS/2 Warp Server. 1.0.7 PCMCIA ------------- Before installing OS/2 Warp Server over an existing version of OS/2 on a system with PCMCIA support installed, edit the CONFIG.SYS file and remove or comment out lines that contain any of the following driver names: o PCMSSDIF.SYS o PCM2SRAM.SYS o FLSH2MTD.SYS o PCM2FLSH.SYS o PCM2ATA.ADD o OS2PCARD.SYS To comment out a line in the CONFIG.SYS file, add the keyword "REM" to the beginning of the line. Save the changed CONFIG.SYS file, and then shut down and restart the system. If any of these drivers are present, the file and print sharing client installation program will fail. 1.0.8 386 HPFS ---------------- The old version of 386 HPFS file system must be removed before migrating the operating system. To remove 386 HPFS: 1. Stop the server by issuing the following command: NET STOP SERVER 2. Type the following command to remove 386 HPFS: PREPACL /P /B:FILENAME /D:DRIVELETTER where /B:FILENAME specifies a temporary file name to save the access controls to and /D:DRIVELETTER specifies the drive where the access controls currently reside. 3. Shut down and restart your computer. NOTES: o Some systems might experience problems with PREPACL. Refer to section 2.3.2 for more information. o When removing 386 HPFS, specify a unique output file for PREPACL. If you specify a file you've already used, PREPACL overwrites the file and loses the ACL information you stored when you first ran PREPACL. 1.1 INSTALLING A PREVIOUS VERSION OF OS/2 AFTER INSTALLING OS/2 WARP SERVER ________________________________________________________________ OS/2 Warp Server uses the Logical Volume Manager (LVM) to configure and manage disk drives on the system. LVM replaces FDISK. Because of this, if you want to install an older version of OS/2 (such as OS/2 Warp 4.0) on the same computer as OS/2 Warp Server, you need to use both LVM and FDISK during installation. After installation, use LVM on OS/2 Warp Server for all disk management. To install a previous version of OS/2 on the same computer as OS/2 Warp Server: 1. From OS/2 Warp Server, use LVM to create an installable volume for the OS/2 version you want to install. For information on performing any of these steps, refer to the "Quick Beginnings" book that came with OS/2 Warp Server. a. Start LVM by typing the following command at the command line: lvm /si:fs /size:120 b. Install Boot Manager, if it is not already installed. c. Create a compatibility volume for the OS/2 version. d. Mark the compatibility volume as "installable." e. Save your changes and exit LVM. 2. Locate the installation diskettes for the OS/2 version. Replace all of the device drivers on the diskettes with the OS/2 Warp Server counterparts. Do not replace any of the device managers (.DMD files). 3. Add the following line to the CONFIG.SYS file on the OS/2 installation diskettes: SET COPYFROMFLOPPY=1 4. Install the OS/2 version. a. Boot the system using the OS/2 installation diskettes you updated in step 2. Begin the installation process. b. When you are asked to select a drive for the installation, do not accept the default. FDISK is displayed. c. Find the FDISK partition you marked installable with LVM. (It will appear with "--> LVM*" next to the name.) d. Use FDISK to mark this partition installable. Press F1 for help instructions on using FDISK. ATTENTION: Do not use FDISK to do anything other than mark the partition installable. e. Save and exit FDISK. The installation window is displayed. f. Accept the default drive and continue with the installation. ATTENTION: FDISK is not supported as part of OS/2 Warp Server. Any use of it beyond the scope of these instructions could harm your system. Use LVM on OS/2 Warp Server for any disk management. 1.2 INSTALLING REMOTE CLIENT WITH SERVICEABILITY AND DIAGNOSTIC AIDS ________________________________________________________________ Remote Client requires that the Serviceability and Diagnostic Aids be installed. Do not deselect this installation option. The following message might be displayed after a reboot if you deselect this option: (SYS1718) The System cannot find the file: \OS2\LOG.SYS and \OS2\MDOS\LPTDD.SYS and \OS2\SYSTEM\LOGDAEM.EXE 1.3 INSTALLING MULTIMEDIA DEVICE SUPPORT ________________________________________ The installation process does not automatically detect multimedia devices (audio cards); therefore, you must manually select the Multimedia Device Support option during installation if you want to install support for your device and configure its settings. If you choose not to install support for your multimedia device during installation, you can set OS/2 Warp Server to automatically detect the device and configure its settings after installation, as follows: 1. Delete the AUDFSAFE.TXT file from the OS2\INSTALL directory in the installation volume. For example, if you installed OS/2 Warp Server on volume D:, delete the AUDFSAFE.TXT file from the D:\OS2\INSTALL directory. 2. From the Desktop, double-click OS/2 System. 3. Double-click System Setup. 4. Double-click Install/Remove. 5. Double-click Selective Install. The System Configuration window is displayed. 6. Click Multimedia Device Support to install multimedia device drivers and configure the settings. Click Next. Continue through the subsequent windows until the installation has completed. 1.4 INSTALLING ON AN IBM THINKPAD __________________________________ The following IBM ThinkPad installation options are not supported on OS/2 Warp Server: o Warm Docking support o Infrared support 1.5 CUSTOMIZING INSTALLATION THROUGH A COMMAND FILE ____________________________________________________ ATTENTION: This procedure is for an experienced REXX programmer. To automatically update or add additional device drivers and other system files during the initial installation and to prevent these device drivers from being replaced by older versions, write a REXX command file, INSTEXIT.CMD. This command file is executed at defined points during the installation process, accesses the hard disk of the target machine, and can make additional configuration changes or copy additional files. The INSTEXIT.CMD can be placed on any of the installation diskettes (and therefore is not applicable if you install using the OS/2 Warp Server for e-business Server Pak Installation CD). Installation Phases -------------------- The INSTEXIT.CMD file is called during the different phases of installation. Those phases are described below: Phase 1: The installation volume is selected and formatted. The base OS/2 operating system files are copied. Phase 2: Hardware, software, and networking products are selected and configured. The remainder of the operating system is installed. Phase 3: Networking products are installed. INSTEXIT Calls during Installation ----------------------------------- The INSTEXIT.CMD file is called two times during installation. It is also called once during Selective Install for Networking. o Phase 1: The installation program calls the INSTEXIT.CMD file before the first reboot during installation. The following three parameters are passed: 1. The target drive letter (example C). 2. The CD-ROM drive letter (example E). 3. The word PHASE1 to indicate the exit is being called in phase 1 of installation. Example call: instexit.cmd C E PHASE1 1>nul 2>&1 The INSTEXIT.CMD return code is logged in \IBMINST\LOGS\CONINST.LOG. After INSTEXIT.CMD is completed, installation continues. o Phase 3: The installation program calls the INSTEXIT.CMD file at the end of Phase 3 if the file exists in the root directory of the installation volume. If the file is found, the install shield is disabled. The following three parameters are passed: 1. The target drive letter (example C). 2. The CD-ROM drive letter (example E). 3. The word PHASE3 to indicate the exit is being called in Phase 3 of installation. Example call: instexit.cmd C E PHASE3 The INSTEXIT.CMD return code is logged in \OS2\INSTALL\NPINST.PRD. After INSTEXIT.CMD is completed, the install shield is restored and the system automatically restarts. o Selective Install for Networking: The installation program calls the INSTEXIT.CMD file at the end of Selective Install if the file exists in the root directory of the installation volume. If the file is found, the install shield is disabled. The following three parameters are passed: 1. The target drive letter (example C). 2. The CD-ROM drive letter (example E). 3. The word SELECT to indicate the exit is being called by Selective Install for Networking. Example call is instexit.cmd C E SELECT The INSTEXIT.CMD return code is logged in \OS2\INSTALL\NPINST.PRD. After INSTEXIT.CMD is completed, the install shield is restored and the system automatically restarts. NOTES: 1. You must remove the exit command at the end of installation or properly use the third input parameter to ensure proper processing in the exit for all three types of calls (Phase 1, Phase 3, and Selective Install for Networking). 2. During the call in Phase 3, some files for products installed might be locked until the system is restarted. 3. During Phase 1, user input prompts must be written using VIO calls. During Phase 3 and Selective Install for Networking, input can be made using REXX I/O methods. Alternately, REXX can call a program executable file to do user prompting. 4. The install shield is disabled during Phase 3 and Selective Install for Networking so your exit command can prompt users to insert your device driver diskette or provide other instructions. When the install shield is disabled, users can see the OS/2 Warp Server Desktop. Discourage users from accessing the Desktop when the install shield is disabled. Sample INSTEXIT.CMD File ------------------------- You can use the following sample file as a template. -------------------------Sample file--------------------------- /* REXX COMMAND FILE */ /* Installation Exit */ parse arg targetdrive cddrive installphase if installphase = 'PHASE1' then do /* phase 1 processing */ end if installphase = 'PHASE3' | installphase = 'SELECT' then do /* phase 3 and selective install for networking processing */ end if installphase = 'PHASE3' then do /* phase 3 specific processing */ end return 0 --------------------------endfile------------------------------- 1.6 TROUBLESHOOTING INSTALLATION _________________________________ This section describes problems that could occur during installation and how to recover from them. 1.6.1 Bootable CD Problems -------------------------- If you have problems installing OS/2 Warp Server with the Server Pak Installation CD, follow the instructions about creating and using installation diskettes in the "Quick Beginnings" book. 1.6.2 Volume and Partition Errors --------------------------------- You might experience problems during installation if your system BIOS is unable to handle Logical Block Addressing (LBA) for drives over a particular size. This may cause the following errors: o LVM does not allow bootable volumes to be created past the first 1024 cylinders of a disk, even though LBA mode is enabled in the BIOS. An error message might appear stating that bootable partitions must reside within the first 1024 cylinders of the disk. o Installation proceeds normally through the phase 1 (text mode). When you reboot the system as instructed, any the following errors might occur. - "Missing operating system. System halted" message appears - Boot Manager reports "selected partition not formatted," even though the partition is formatted and can be accessed when the system is booted from diskettes. - Systems hangs at blinking cursor. "## OS/2" logo never appears. If any of these problems occur, try the following solutions: o Make sure LBA mode is enabled within the system BIOS for your system. See the documentation that came with your system for details on how to do this. NOTE: If you make changes to the LBA settings in BIOS, you must repartition the hard disk. o Contact the system manufacturer for a BIOS update. o Common drive "limits" are 4.3GB and 8.4GB for newer systems. Check with the documentation that came with your system or with your system manufacturer to determine the largest bootable device that your system supports. o Put the boot volume within the first 2GB of the drive. o Disable LBA in the system BIOS, and ensure that the boot volume resides within the first 500M of the drive. NOTE: If you make changes to the LBA settings in BIOS, you must repartition the hard disk. o Some drives have jumpers that can be set to overcome incompatible BIOS. Check the drive documentation for details. NOTE: Setting these jumpers typically reduces the usable space on the drive and requires you to repartition the drive. ____________________________ PART II. AFTER INSTALLATION ____________________________ The following sections provide information about restrictions and potential problems that might occur after you have installed this product. 2.0 ADDITIONAL INFORMATION INCLUDED WITH THIS PRODUCT ______________________________________________________ Information for OS/2 Warp Server includes README files on the diskettes and CDs, a printed book, and several online books. 2.0.1 README Files ------------------- In addition to this README file, other README files are located on the diskettes and CDs that are included with this product. To find these README files, issue the command DIR /S README* from the root directory of the diskette or CD. README.CID ----------- This file is located on the Server Pak CD in the OS2UG\DISK_0 directory and contains instructions for installing this product using the configuration, installation, and distribution (CID) process. INDEX.HTM ---------- These files are located in the root directory of the Client Connect Pak CDs and link to other README files for components in the OS/2 Warp Server for e-business Client Connect Pak. Open these files in your Web browser and select the JavaScript or non-JavaScript version of the README. 2.0.2 Books ------------ The product library includes one printed book, "Quick Beginnings: Installing OS/2 Warp Server for e-business." This book describes the planning, installation, and configuration processes. It also contains descriptions of the new OS/2 Warp Server for e-business components, such as the journaled file system (JFS) and the Logical Volume Manager (LVM). The product library also includes several online books. Refer to "Using Online Information" in the Assistance Center on your desktop for summaries of each book. In addition to the books in the library, the Server Pak CD contains the following books: o "Migrating to OS/2 Warp Server for e-business (SG24-5135)" o "OS/2 Debugging Handbook" These books are located in the \BOOKS directory on the Server Pak CD. Several formats are available: HTML, PDF, PostScript, and INF. For information on viewing and printing these books, refer to "Quick Beginnings." Information related to these books is available on the Web at http:\\www.redbooks.ibm.com. 2.1 APPLICATION AND COMPONENT CONSIDERATIONS _____________________________________________ Read the following sections for information about OS/2 Warp Server components and applications. 2.1.1 Alias Sharing ------------------- If you want to change the path of an alias that is already being shared, you must first stop sharing that alias and then change the path in the Properties notebook of the alias. To change the path of an alias: 1. View the users connected to the share by typing NET SHARE at an OS/2 Window. 2. If no users are connected, type NET SHARE /D to stop sharing the alias. 3. In the LAN Server Administration folder, right-click the alias definition icon, and from the pop-up menu, click Properties. 4. Type the resource path for the alias in the path field. 5. Close the Properties notebook. If the alias is shared at server startup, it is automatically restarted. 2.1.2 DOS LAN Services (DLS) 4.0 -------------------------------- Run TCPSTOP before installing OS/2 Warp Server Client Connect Pak on a computer that already has DLS 4.0 and IBM TCP/IP for DOS installed. If you do not stop IBM TCP/IP for DOS, a TRAP exception will occur when the installation program for DLS 5.0 starts. For more information about DOS LAN Services, see the DLS README on the Client Connect Pak CD 1. 2.1.3 FTP ---------- Some clients might have difficulty displaying directory information correctly when connecting to an OS/2 Warp Server ftp server. In particular, the following problems might occur: o Directory listings might appear empty, even if there are files in the directory. o File names might appear as numbers. o File names in a directory might be missing or incorrect. To avoid these problems, try the following on the client: o Configure the server type in the client's preferences as "OS/2." If the OS/2 choice is not available or does not resolve the problem, try using one of the other system types. o If the ftp client does not have the above options, or if the problem still exists, have the client use FTP from the command line. 2.1.4 Java 1.1.7 ---------------- OS/2 Warp Server includes Java (TM) 1.1.7, which is frequently updated. To update Java 1.1.7, use the following steps. NOTES: o If you plan to use Lotus WebSphere Application Server, you must update Java 1.1.7. o Stop any JVMs that use files in the \JAVA11 directory before updating Java 1.1.7. 1. After OS/2 Warp Server installation, copy RUNTIME.EXE from the root directory of the Server Pak CD to the root directory where Java 1.1.7 is installed. For example, if Java 1.1.7 is installed in the D:\JAVA11 directory, copy RUNTIME.EXE to D:\. 2. Type the following command from an OS/2 Window to run RUNTIME.EXE: runtime -o The Java 1.1.7 directories and files are automatically updated. NOTE: RUNTIME.EXE is updated fairly regularly. A newer version might be available from the following ftp site: ftp://ftp.hursley.ibm.com/pub/java/fixes 2.1.5 Lightweight Directory Access Protocol -------------------------------------------- Multiple copies of Lightweight Directory Access Protocol (LDAP) are not supported on OS/2 Warp Server for e-business. 2.1.6 Lotus Domino Go Webserver and IBM WebSphere Application Server -------------------------------------------------------------- Lotus Domino Go Webserver and IBM WebSphere Application Server are available on a CD that is included with OS/2 Warp Server. NOTE: Lotus Domino Go Webserver and IBM WebSphere Application Server require file systems that can handle long file names. For information about Lotus Domino Go Webserver and IBM WebSphere Application Server, including installation instructions, see "Quick Beginnings." IBM WebSphere Application Server 1.1 Upgrade --------------------------------------------- If you have IBM eNetwork On-Demand Server with the initial release of IBM WebSphere Application Server 1.1, and you want to upgrade it to the version included with OS/2 Warp Server for e-business, you must perform the following steps. To upgrade to the OS/2 Warp Server version of IBM WebSphere Application Server 1.1: 1. Copy the following files from the \WEBSPHERE\APPSERVER\PROPERTIES\SERVER\SERVLET\SERVLETSERVICES\ directory to a diskette: JVM.PROPERTIES SERVER.PROPERTIES SERVLET.PROPERTIES 2. After installing IBM WebSphere Application Server 1.1, copy the files from the diskette into the \WEBSPHERE\APPSERVER\PROPERTIES\SERVER\SERVLET\SERVLETSERVICES\ directory. NOTE: To use the OS/2 Warp Server version of IBM WebSphere Application Server 1.1, you must install the latest version of Java 1.1.7. See section 2.1.4 "Java 1.1.7." for information about upgrading Java 1.1.x. 2.1.7 Lotus SmartSuite 97 ------------------------- For Lotus SmartSuite 97 on SMP machines, you need to run EXECMODE against each of the following applications: o Lotus 1-2-3 (TM) o Lotus Freelance Graphics (TM) o Lotus WordPro (TM) o Lotus Approach (TM) o Lotus Organizer To run this exec, type the following at the command line: execmode xxxxxx.exe where xxxxxx.exe is the name of executable file for the application. 2.1.8 Multiple Server Names ---------------------------- OS/2 Warp Server provides support for multiple server names. If you implement this support, you need to tune your server for the number of server names multiplied by the number of clients using those names. For example, if you have 20 clients that each connect to the server using two server names, tune the server as though 40 clients are connecting to it. If you have 50 clients, half of which connect to the server using one server name and the other half using two server names, tune the server as though 75 clients are connecting to it. For more information about multiple server names, see the "Network Administrator Tasks" book included with this product. For information about tuning the server, refer to the "Server Performance Tuning" book and the "Command Reference." 2.1.9 Netscape Communicator 4.04 for DBCS Systems -------------------------------------------------- On DBCS systems, uninstalling Netscape Communicator 4.04 using the Netscape Installation Utility might fail. If this happens, you can delete the Netscape files manually. 2.1.10 OS/2 Window Default Size and Position -------------------------------------------- In OS/2 Warp 4.0 and later versions, an OS/2 Window opens to a default size and position. If you run customized applications that require the window to open to a specific size and position, you can remove these defaults. To remove the default window size and position: 1. Open an OS/2 command window. 2. Move the mouse pointer to the restore icon in the upper right corner of the window. 3. Press and hold the Shift key and right-click the restore icon. 4. Release the Shift key. 2.1.11 PPP Server ------------------ The following sections contain information about PPP Server, also referred to as "Remote Access Services" and "LAN Distance." PPP Server and Incomplete TCP/IP ARP Table ------------------------------------------ You must verify that your TCP/IP ARP table is correctly initialized before you start the PPP Server. To do this, type the following at a command prompt and press Enter: NETSTAT -p This command displays the ARP table entries. If any of your entries are marked as "(incomplete)," you must PING your routers to fill in the ARP table entries. If you do not know the IP addresses of your routers, you can get the IP addresses from the route commands at the bottom of the SETUP.CMD file, normally located in the MPTN\BIN directory. After you ping your routers, type NETSTAT -p again to verify that none of the entries are marked as "(incomplete)." Remote Access Services (PPP Server) Error Message WCL0567 ---------------------------------------------------------- If you have your LAN Distance logical adapter incorrectly configured, message WCL0567 might be displayed. In some cases, when you click OK, your system might hang. If this happens, Remote Access Services (PPP Server) might automatically start after you reboot your system. If this is true, do not click OK when the message is displayed again. Ignore the message and reconfigure your machine as needed. See the "Troubleshooting" chapter in the LAN Distance Advanced Guide for information on Message WCL0567 and how to reconfigure your machine. If DHCP/DDNS is not Enabled in TCP/IP after it has been Installed -------------------------------------------------------- If you install the DHCP/DDNS client code, complete the following steps after installation: 1. Double-click the TCP/IP folder. 2. Open the TCP/IP Configuration Program. 3. On the Network page, select the "Automatically Using DHCP" and "Also Using DDNS (if required)" check boxes to enable this code. Problem with Lowercase in LAN Distance User ID and Password ------------------------------------------------------------ When you use the integrated installation to install LAN Distance, the default user ID and password that you specify are forced to all uppercase letters (for example, "Password" becomes "PASSWORD"). After installation, be sure to use all uppercase letters when you are first asked for the LAN Distance administrator user ID and password. When you change the user ID or password (as described in the following section), the letter case remains as you type it. The restriction does not apply to extended ASCII characters (decimal codes 128-255). Extended ASCII characters are used to create diacritical marks in some languages. Change the Password for LAN Distance Connection Server/Remote Access -------------------------------------------------------------- After installation, LAN Distance requires a password of at least eight characters. After installation, start LAN Distance/Remote Access. You will be prompted for an ID and password. Use the ID and password you created during the installation. When prompted to create a new passphrase, specify one that is at least eight characters. 2.1.12 Products That Add Locked File Device Driver Statements -------------------------------------------------------------- If you are installing a product (such as IBM eNetwork Communications Server V5.0) that adds locked file device driver statements to the CONFIG.SYS file, change the order of these statements before you restart your system. Locked file device driver statements must come after all IFS statements. For example, if you are installing IBM eNetwork Communications Server V5.0, your CONFIG.SYS file contains the following lines: IFS=C:\OS2\JFS.IFS /AUTOCHECK:* /CACHE:37272 DEVICE=C:\OS2\INSTALL\CMLIB\IBMCMLK.SYS C:\OS2\INSTALL\CMLIB\REBOOT.LST RUN=C:\OS2\INSTALL\CMLIB\IBMCMLK.EXE C:\OS2\INSTALL\CMBLIB\REBOOT.LST IFS=C:\OS2\HPFS.IFS\ /CACHE:2048 /CRECL:4 /AUTOCHECK:C Move the DEVICE and RUN statements after the IFS statements: IFS=C:\OS2\JFS.IFS /AUTOCHECK:* /CACHE:37272 IFS=C:\OS2\HPFS.IFS\ /CACHE:2048 /CRECL:4 /AUTOCHECK:C DEVICE=C:\OS2\INSTALL\CMLIB\IBMCMLK.SYS C:\OS2\INSTALL\CMLIB\REBOOT.LST RUN=C:\OS2\INSTALL\CMLIB\IBMCMLK.EXE C:\OS2\INSTALL\CMBLIB\REBOOT.LST NOTE: Each entry should be on only one line. The lines above are split for printability. 2.1.13 Screen Savers on Security-Enabled Servers ------------------------------------------------ On security-enabled servers, PM lockup/autodim function is disabled. To restore autodim function to guard against display phosphor burn-in, you can specify a sequence of up to 100 bitmaps to be displayed. Currently, the following line in the CONFIG. SYS file causes OS/2 Security Enabling Services to display the bitmap continuously while awaiting logon.: SET BACKGROUNDBITMAP="bitmap.BMP" where "bitmap.BMP" is the fully qualified name of a bitmap file. If no file is specified, then a default OS/2 logo bitmap will be used. To enable Screen Saver function, add the following line to your CONFIG.SYS file: SET BACKGROUNDBITMAP2="bitmap.BMP" where "bitmap.BMP" is the fully qualified name of another bitmap you want to use. If the file name is in the form "bitmapNN," where NN represents digits 00-99, the file name specifies that it is the first of a sequence of files to be displayed cyclically. To specify the delay interval between the bitmaps, add the following lines to your CONFIG.SYS file: SET BACKGROUNDBITMAPDELAY=300 SET BACKGROUNDBITMAPDELAY2=60 where the BACKGROUNDBITMAPDELAY value is the amount of time, in seconds, to display the BACKGROUNDBITMAP file before displaying the first bitmap in the sequence. The default is 300 seconds or 5 minutes. The BACKGROUNDBITMAPDELAY2 value is the amount of time, in seconds, to delay between the display of the bitmap sequence designated by BACKGROUNDBITMAP2. The default is 60 seconds or 1 minute. The minimum delay values for both statements are 1 second, and the maximum values 3999 seconds. To minimize processing overhead, the bitmaps should be small in size and the display interval time fairly long. 2.1.14 TCPBEUI on a DHCP Client -------------------------------- o To configure TCPBEUI protocol on a server, use a static host name and IP address in the TCP/IP configuration. To configure TCPBEUI protocol on a server that is a DHCP client, use a NetBIOS Name Server to allow your TCPBEUI clients to resolve the IP address of the server. o Assign the TCPBEUI parameter "Seconds to pause between TCP/IP interface checks" a value of 1 (or INTERFACERATE = 1, in the protocol.ini file). The default value is 300. See the "MPTS Configuration Guide" for more information. 2.1.15 TCP/IP -------------- The following sections contain information about TCP/IP. Remote IPL Support for TCP/IP V4.2.1 -------------------------------------- Use of TCP/IP V4.2.1 (included with this product) is not supported for OS/2 Warp 3 Remote IPL clients. You can configure OS/2 Warp 4 Remote IPL clients to use a copy of TCP/IP from the server. Refer to RIPLSETD in the "Command Reference" for more information. TCP/IP NFS and IBM VisualAge C++ Compatibility Problem ------------------------------------------------------- If you receive a SYS3175 error when starting NFSD.EXE and you have VisualAge C++ installed, remove \IBMCPP\LOCALE from the SET LOCPATH statement in the CONFIG.SYS file and reboot your system. 2.1.16 Tivoli Management Agent ------------------------------ When you uninstall Tivoli (TM) Management Agent, you will receive an incorrect EPFIE231 error message. Ignore this error. Also, if you uninstall TMA, not all the files are removed. You must manually remove the files in the \TIVOLI subdirectory. 2.1.17 TME 10 Distributed Monitoring ------------------------------------- If you are using TME 10 Distributed Monitoring to monitor an OS/2 Warp Server, you might receive an "Exit Code 1001" message. If this occurs, contact Tivoli support for the fix to Tivoli PMR 82307. 2.1.18 WorkSpace On-Demand --------------------------- The following sections contain information about WorkSpace On-Demand. Installing Public Applications ------------------------------- If you installed LAN Server RIPL support in a volume (other than 386 HPFS) and you want to install public applications (such as Lotus Notes) that use IBM Software Installer on a WorkSpace On-Demand client, you need to set the EPFINSTDIR parameter of the application's installation object to a directory where the client has write access. To set the EPFINSTDIR parameter: 1. Double-click LAN Server Administration. 2. Right-click the application's installation object. 3. On the Parameters page, set the EPFINSTDIR parameter to a directory where the WorkSpace On-Demand client has write access. For example, if a WorkSpace On-Demand client has the following FIT file entry: Z:\EPFTEMP \\\\ set the EPFINSTDIR parameter to Z:\EPFTEMP. WorkSpace On-Demand (Initial Release) ------------------------------------- For information on using WorkSpace On-Demand (Initial Release) with OS/2 Warp Server, contact your IBM representative. WorkSpace On-Demand Documentation ---------------------------------- If you are using OS/2 Warp Server to remotely administer WorkSpace On-Demand servers and want access to the WorkSpace On-Demand documentation, you can copy the "WorkSpace On-Demand 2.0 Administrator's Guide" from the WorkSpace On-Demand 2.0 CD (\INSTALL\SERVER\A4E11MST.INF). You can also view this information online at http://www.software.ibm.com/workspace. 2.1.19 386 HPFS ---------------- You must install OS/2 Warp Server before you install 386 HPFS. 386 HPFS is available as a separate feature. For information about 386 HPFS, see the README on the 386 HPFS Upgrade for OS/2 Warp Server for e-business CD. 2.2 REMOTE IPL ______________ The following sections contain information about troubleshooting for Remote IPL. 2.2.1 RIPL for DBCS Clients ---------------------------- To use RIPL on DBCS OS/2 Warp 4.0 systems, perform the following steps in the server RPL tree (IBMLAN\RPL\OS2.40): 1. Install OS/2 Warp 4.0 FixPak FX05005 and the PTF for your country from the list below using the directions that accompanied them. Japan: PTF JR12961 Taiwan: PTF TW99002 China: PTF CN99002 2. Delete the OS2DBCS and OS2DBCS.FNT files. To obtain the OS/2 Warp 4.0 FixPak FX05005 and the correct PTF, contact your IBM representative. 2.2.2 OS/2 Clients ------------------ If you installed the \IBMLAN\RPL or the \IBMLAN\RPLUSER directories on a non-386 HPFS volume, your OS/2 RIPL clients might not boot. To fix this, the \IBMLAN\IBMLAN.INI file must be updated to increase the MAXOPENS parameter in the [server] section. The recommended values are as follows: For OS/2 only MAXOPENS = (# of RIPL clients) * 70 For OS/2 + CM/2 MAXOPENS = (# of RIPL clients) * 115 Other applications that use RIPL clients and have their file trees located in the \IBMLAN\RPL directory tree (or somewhere else on the FAT volume), also contribute to the number of open files and must be accounted for in the MAXOPENS parameter. 2.2.3 RIPL Disk Space ---------------------- For this version, disk space for RIPL is not checked. RIPL can put Rpldrive and Rpluserdrive on different drives than LAN Server itself. Rpldrive needs 70MB and Rpluserdrive needs 40MB (110MB total). WorkSpace On-Demand clients can consume more disk space. 2.2.4 RIPL Removal ------------------ If you want to remove RIPL, make sure that the following things are true of the machine from which RIPL is being removed: o The machine has no RIPL clients o WorkSpace On-Demand 2.0 is not installed. If it is, follow the directions in 6.3.4, "WorkSpace On-Demand 2.0 Removal." 2.3 COMMANDS, CONFIG.SYS STATEMENTS, AND MESSAGES __________________________________________________ The following section contain information about OS/2 commands, CONFIG.SYS statements, and error messages. 2.3.1 Kernel File Message ------------------------- If you receive the error message 'A kernel file is missing from the disk,' the missing file is one of the following: OS2KRNL, OS2LDR, OS2BOOT. These files are hidden in the root directory of the server. You will receive this message if you have deleted one of these files or if your disk becomes corrupt. If your disk is corrupted, replacing the files might or might not fix the problem. 2.3.2 PREPACL ------------- On some systems, especially those with MMOS2 installed, you might have a problem running PREPACL, a 386 HPFS command. To determine if you will have this problem, run PREPACL with no parameters: PREPACL If no help text is displayed, the system is not finding the correct LSI.MSG file. To work around this problem, type the following command at a command prompt and press Enter: DPATH d:\IBMLAN\INSTALL;%DPATH% where d: is the directory where \IBMLAN is located. 2.3.3 VIRTUALADDRESSLIMIT -------------------------- The default value of the VIRTUALADDRESSLIMIT CONFIG.SYS statement has been changed from 2048 (2 gigabytes) to 1024 (1 gigabyte). 2.3.4 XCOPY ----------- In the XCOPY command syntax using the /S and /E parameters together, if a source is specified without a trailing backslash "\", (for example XCOPY d:\aaa), then that source could be either a file or a directory. Because of this, if the source cannot be found, the root directory tree is replicated on the target. This occurs even if the source not found is a file. For more information about XCOPY, refer to the "Command Reference." 2.4 ASSOCIATED BITMAP-FONTS ____________________________ NOTE: This feature is available only for the following languages: o Japanese o Traditional Chinese o Simplified Chinese The Associated Bitmap-fonts feature displays higher quality characters in small point sizes by using bitmap fonts instead of outline fonts. It also improves the rendering performance because the bitmap fonts display more quickly. NOTE: Install all DBCS bitmap fonts for this feature to work effectively. The following limitations and restrictions apply to Associated Bitmap-fonts: o If you want to print output that is identical to your screen layout, disable Associated Bitmap-fonts. To disable this feature: 1. From the System properties notebook (OS/2 System --> System Setup --> System), click the Font page. 2. Click the + symbol to move to the second Font page. 3. Clear the "Activate" check box. 4. Close the properties notebook and reboot the system. o Unicode fonts are not supported. o The sample characters in the OS/2 font dialog box cannot switch to a bitmap font. o The IME Conversion String cannot switch to a bitmap font. Japanese users can refer to the "Japanese User's Guide (Nihongo-ban Goshiyou no Tebiki)" for more information. 2.5 HARDWARE DEVICE AND DEVICE DRIVER CONSIDERATIONS _____________________________________________________ The following sections contain information about hardware devices and device drivers. 2.5.1 Adaptec Adapter ---------------------- If you want to install OS/2 Warp Server on a computer that has an Adaptec adapter, enable Greater Than 1 Gigabyte support in the Adaptec SCSI BIOS settings. For information about the Adaptec SCSI BIOS settings, refer to the documentation that came with the adapter. 2.5.2 CPU Initialization on a Compaq 4500 ------------------------------------------ If a CPU is removed from a Compaq 4500 computer with multiple CPUs (leaving a gap), OS/2 Warp Server will not see the remaining CPUs that sequentially are after the removed CPU. For example, if the number 2 CPU is removed from a machine containing 4 CPUs, then after a reboot, the remaining CPUs will be initialized, but CPUs 3 and 4 will not be seen or used by the software. Only CPU 1 will be used. 2.5.3 Device Driver Adapters ----------------------------- o Refer to the Device Driver Pak Online for information regarding device drivers and to download device drivers. Go to the following Web site for more information: http://service.software.ibm.com/os2ddpak/ You can check the LSI Logic Web page for information about LSI Logic (formerly symBIOS) device drivers: http:\\www.lsilogic.com. There you may find READMEs and FAQs. o The SYM8XX driver is included on Installation Diskette 1. If you need this driver, add the following statement to the CONFIG.SYS file on Installation Diskette 1: BASEDEV=SYM8XX.ADD o The SYM_HI driver is included in the scsiadds bundle on the Server Pak CD in the \os2image\disk_7 directory. If you need this driver, unpack it from the bundle and replace SYM8XX.ADD on Installation Diskette 1 with SYM_HI.ADD. Then add the following statement to the CONFIG.SYS file on Installation Diskette 1: BASEDEV=SYM_HI.ADD o The IBM EtherStreamer MC32 Adapter is not supported. 2.5.4 IBM Token-Ring Adapters ------------------------------ Certain IBM token-ring adapters might cause a system to hang when the remote IPL client downloads the 802.2 RIPL Boot record. This problem might occur with the following adapters: o Turbo 16/4 Token-Ring ISA adapter o Auto Wake Token-Ring ISA adapter o Auto 16/4 Token-Ring ISA adapter When the system hangs, the screen usually displays a value of 0001 or 0002 for SF count, and a value of 0001 for SN count. If this occurs: 1. Go to the Web site http://www.networking.ibm.com for an update of the microcode for the token-ring adapter. 2. Follow the directions on the Networking Tech Support pages to download the IBM Auto 16/4 Token-Ring Network ISA Adapter. 3. Download the files in the flash update package. 4. Follow the instructions in the flash documentation file to install the flash update. You can use a temporary workaround until the adapter microcode can be updated: 1. Modify the remote IPL control file that describes the remote IPL boot block for adapters that are compatible with the IBM token-ring. The path and name of this file is d:\IBMLAN\RPL\OS2xxNTR.CNF, where xx is 30 or 40. 2. Make a backup copy of the original file, and then use an ASCII text editor to modify the file. Move the 'RPL DOS\RPLBOOT.SYS' statement down so that it follows the 'DAT DOS\UFSD.SYS' statement. 3. After you update the network token-ring adapter microcode on all remote IPL clients, restore the original version of the OS2xxNTR.CNF file. 2.5.5 IBM ISDN Co-Processor Adapters -------------------------------------- Intermittent problems can occur on systems with more than two IBM ISDN co-processor adapters. A message may indicate that an adapter has stopped responding. Attempts to restart the adapter, through Call and Port Management, may result in an error message stating that an internal processing error has occurred in the ISDN Co-Processor Support Program. 2.5.6 PCMCIA Flash Memory and Hard Disk Support ----------------------------------------------- If you installed PCMCIA support and selected either "PCMCIA Hard Disk" or "PCMCIA Flash," you need to remove REM from the following statements in the CONFIG.SYS file to enable support for these devices: DEVICE=C:\OS2\BOOT\PCMSSDIF.SYS ;Memory Card discriminator DEVICE=C:\OS2\BOOT\PCM2SRAM.SYS ;Linear SRAM driver DEVICE=C:\OS2\BOOT\FLSH2MTD.SYS ;Memory Technology driver DEVICE=C:\OS2\BOOT\PCM2FLSH.SYS ;FLASH memory driver BASEDEV=PCM2ATA.ADD /S:2 /!DM /NOBEEP ;ATA PCMCIA driver BASEDEV=OS2PCARD.DMD ;Device Manager for ATA/Memory cards 2.5.7 Universal Serial Bus Devices ---------------------------------- For information about Universal Serial Bus (USB) devices, refer to the IBM Technical Databases. To get to the IBM Technical Databases, refer to the instructions at the beginning of this README. 2.5.8 802.2 RIPL with a DOS Network Adapter Device Driver --------------------------------------------------------- When you use the 802.2 Remote IPL method to boot a new machine, your client system may hang after loading the DOS network adapter device driver. If you experience this problem, contact the network adapter manufacturer and obtain the latest version of the DOS device driver for the network adapter. Copy the new device driver to the \IBMLAN\DOSLAN\LSP\DOS directory on the drive where IBMLAN is installed. 2.6 PRINTING ____________ The following sections contain information about printing using PSF/2. 2.6.1 LAN Notification and PSF/2 --------------------------------- If LAN notification is activated and a job is printed successfully, a message is sent to the user who submitted the print job; but the message erroneously states that the print job was deleted and did not print. This message appears only when PSF/2 has printed the job successfully and has removed it from the print queue. If the print job cannot be printed successfully by PSF/2, the user receives no notification from the LAN. 2.6.2 Multiple Printers ------------------------ If you want to operate multiple printers using PSF/2, and you choose to store print resources on a network drive attached to a remote file server, you will need to change the values of two parameters in the IBMLAN.INI file on the remote file server. The two parameters are MAXOPENS and MAXSESSOPENS. The default value for MAXOPENS is 64, and the default for MAXSESSOPENS is 50. To each value add: 30 * (the number of DPF spools + the number of PSF/2 printer objects) For example, if MAXOPENS is 64, and MAXSESSOPENS is 50, and if you want to have 16 DPF spools and 10 PSF/2 printer objects, then set MAXOPENS to 844 and MAXSESSOPENS to 830. If you do not increase these values, you might receive the following error messages on the screen: o AIN0228E: PSF/2 cannot open the resource in the file . Make sure that this file exists and that the drive is available. o AIN0585E: All attempts to open resource in file failed. 2.6.3 Online Documentation --------------------------- The following sections contain information about printing online documentation. Online Documentation Printing Problems --------------------------------------- Make sure the default printer for online documentation is not a PSF/2 defined printer. Printing Online Help to a PSF/2 Printer Object ----------------------------------------------- If you want to print online help to a print queue, follow the instructions below to make sure that the print data is created correctly. You might want to follow these instructions if you have trouble printing from other applications. 1. Right-click the printer object to display its pop-up menu. 2. Open the Settings view of the object and select the Queue options tab. 3. Select the Printer-specific format check box and then close the settings view of the printer object. You should now be able to print successfully to a print queue from the Help Facility. 2.6.4 PSF/2 Print Submitter and Print Queues Not Connected to PSF/2 -------------------------------------------------------------------- If the PSF/2 Print Submitter or APRINT command is used to print a job on a printer object that uses the PMPRINT queue processor, the following message will appear from the PMPrint Spooler Queue Processor: Unrecognized queue driver parameter. The print job will be printed using the default parameters. (PMV0612) In most cases, ASCII print jobs submitted this way still print. Note: AFPDS print jobs will not print correctly if they are submitted to a print queue that is not connected to PSF/2. 2.6.5 PSF/2 Uninstall --------------------- To uninstall PSF/2, type the following command: c:\psf2\install\install.exe /s:c:\psf2\install /l1:c:\err.log /l2:c\hist.log After typing this command, manually remove the files from the PSF/2 subdirectory. 2.6.6 QREADER.NLM ------------------ When using QREADER.NLM and NWPSF2.EXE to transfer large jobs from the NetWare server to the PSF/2 system, and the spool runs out of space, QREADER.NLM will cause the NetWare server to fail. Do not use QREADER.NLM on NetWare 4.02. It cannot open the queue and read the job, and eventually it may hang the server. If you have NetWare 4.02 or if you encounter the problem described above, stop using QREADER.NLM and NWPSF2.EXE and start using NetWare's PSERVER.NLM on the NetWare server and the Novell Network Printer Support that is located on the Novell object on the PSF/2 system. The problems should also be reported to PSF/2 Software Support. _____________________ PART III. TRADEMARKS _____________________ The following terms, are registered trademarks of the IBM Corporation in the United States, or other countries, or both: o IBM o LAN Distance o OS/2 o WebSphere o WIN-OS/2 The following terms are trademarks of other companies: Approach, Freelance Graphics, Lotus, Lotus Notes, Lotus Organizer, Lotus SmartSuite, and WordPro are trademarks of Lotus Development Corporation in the United States, other countries, or both. Tivoli is a trademark of Tivoli Systems Inc. in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. 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. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. (c) Copyright IBM Corporation 1999. All rights reserved.