<        Installation instructions for Warp Server for e-business FixPak
        XR_E003















        

        
        



        February 18, 2002

        This FixPak makes the products it services Year 2000 ready
        
        Build level 14.088
        
        This FixPak applies to:
        
        CSD Level:    XR_4500    Warp Server for e-business (UNI)
        Component ID: 5639A6150
        Version:      4.50
        Type:         0S
        
        CSD Level:    XR_4500    Warp Server for e-business (SMP)
        Component ID: 5639A5550
        Version:      4.50
        Type:         0S
        
        Requires Corrective Service Facility release f.143 or later
        
        OS/2 Fix Distribution
        Personal System Products
        Austin, Tx
        
        
        (c) Copyright International Business Machines Corporation, 1981, 1998.
        All rights Reserved.

        February 18, 2002 - Warp Server for e-business FixPak XR_E003




      February 18, 2002 - Warp Server for e-business FixPak XR_E003

   CONTENTS


     1.0 Terms and Conditions  . . . . . . . . . . . . . . . . . . . . . . 1

     2.0 Do not use your system  . . . . . . . . . . . . . . . . . . . . . 2

     3.0 Installation Notes  . . . . . . . . . . . . . . . . . . . . . . . 3

     4.0 Out of memory or System error SYS0008   . . . . . . . . . . . . . 4

     5.0 Platform Specific Drivers (PSDs)  . . . . . . . . . . . . . . . . 5
       5.0.1 Please use Fixtool f.143 or later   . . . . . . . . . . . . . 7
       5.0.2 OS2DUMP split into two versions   . . . . . . . . . . . . . . 7
       5.0.3 Using Display Recovery Choices  . . . . . . . . . . . . . . . 8
       5.0.4 No products found   . . . . . . . . . . . . . . . . . . . . . 8
       5.0.5 Previous installation interrupted   . . . . . . . . . . . . . 9
       5.0.6 Unable to open Archive directory  . . . . . . . . . . . . . . 9
       5.0.7 CSF0208 No products were found on the target ...   . . . . . 10
       5.0.8 CSF0249 Error opening or creating archive file.    . . . . . 10
       5.0.9 Printer installation process change  . . . . . . . . . . . . 10
       5.0.10 Configuration Installation Distribution ( CID )   . . . . . 10

     6.0 Post Installation Notes  . . . . . . . . . . . . . . . . . . . . 11

     7.0 New Function   . . . . . . . . . . . . . . . . . . . . . . . . . 12
     7.1 New RAS Utilities added  . . . . . . . . . . . . . . . . . . . . 12
     7.2 JFS lazywrite parameters on the IFS= line in config.sys  . . . . 12
     7.3 Graphics Adapter Device Drivers (GRADD)  . . . . . . . . . . . . 13
     7.4 REXX New Function  . . . . . . . . . . . . . . . . . . . . . . . 13
     7.5 Other README files   . . . . . . . . . . . . . . . . . . . . . . 14

     8.0 Corrective Service Facility  . . . . . . . . . . . . . . . . . . 15
       8.0.1 Required CSF level   . . . . . . . . . . . . . . . . . . . . 15
       8.0.2 Where you can find CSF code  . . . . . . . . . . . . . . . . 15
       8.0.3 Creating FixPak diskettes  . . . . . . . . . . . . . . . . . 16
     8.1 Read-Only files  . . . . . . . . . . . . . . . . . . . . . . . . 16
     8.2 SYSLEVEL file locations  . . . . . . . . . . . . . . . . . . . . 17
     8.3 Relocated Warp Server for e-business file support  . . . . . . . 17

     9.0 Installation Process   . . . . . . . . . . . . . . . . . . . . . 19
     9.1 Before installation  . . . . . . . . . . . . . . . . . . . . . . 19
     9.2 Method 1: Install from booted OS/2 partition.    . . . . . . . . 19
     9.3 Method 2: Install from alternate bootable media  . . . . . . . . 20
     9.4 Additional Corrective Service Facility information   . . . . . . 21

     10.0 CSD level of SYSLEVEL.OS2   . . . . . . . . . . . . . . . . . . 22
     10.1 VER /R output   . . . . . . . . . . . . . . . . . . . . . . . . 22
       10.1.1 FixPak Syslevel File  . . . . . . . . . . . . . . . . . . . 22

     11.0 FixPak Corrective Service levels and disk layouts   . . . . . . 23

   
                                                                Contents  ii


         February 18, 2002 - Warp Server for e-business FixPak XR_E003


     12.0 Space Utilization   . . . . . . . . . . . . . . . . . . . . . . 33
       12.0.1 Recovering FixPak ARCHIVE and BACKUP space  . . . . . . . . 33
       12.0.2 TRADEMARKS  . . . . . . . . . . . . . . . . . . . . . . . . 34
















































   
                                                               Contents  iii


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   1.0 TERMS AND CONDITIONS

   Important - please read the following terms and conditions.

   Downloading the Service Fixes included in FixPak XR_E003 for Warp Server
   for e-business indicates your acceptance of the following terms and
   conditions:

   1. You must be, and agree that you are, a current licensee of Warp Server
      for e-business.
   2. You may make copies of the Warp Server for e-business Service Fixes
      equal to the number of licensed copies of Warp Server for e-business
      you possess.
   3. You may only use the Warp Server for e-business Service Fixes included
      with FixPak XR_E003 for maintenance purposes.
   4. All other terms and conditions of your Warp Server for e-business
      license agreements apply to the Service Fixes; however, this does not
      extend any warranty and/or services, including but not limited to the
      "Initial Installation" period, outlined in such agreements.

































   
                                                     Terms and Conditions  1


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   2.0 DO NOT USE YOUR SYSTEM

   Once you begin a FixPak installation, do not try to use your system for
   any other purpose. Doing so may yield unexpected problems which can cause
   the FixPak installation to fail.















































   
                                                   Do not use your system  2


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   3.0 INSTALLATION NOTES



















































   
                                                       Installation Notes  3


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   4.0 OUT OF MEMORY OR SYSTEM ERROR SYS0008

   Customers who have had an "Out of memory" or SYS0008 problems on systems
   using Java should add the following line to the CONFIG.SYS file:

   þ  SET JAVA_HIGH_MEMORY=1

   This will allow Java to move it't buffers to a lesser-used region of
   memory and may alleviate some memory constraints. There are no known
   unwanted side-effects to doing this.










































   
                                    Out of memory or System error SYS0008  4


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   5.0 PLATFORM SPECIFIC DRIVERS (PSDS)

   In Warp Server for e-business SMP, we have removed all the platform
   specific code from the operating system, and placed it into platform
   specific drivers.  These drivers provide an abstraction layer for the
   underlying hardware by allowing the OS to call generic functions to
   perform platform specific operations without worrying about the actual
   hardware implementation.  This allows us to support new platforms without
   modifying the operating system.

   PSD's are specified in CONFIG.SYS by using the PSD keyword, and must
   conform to the 8.3 file naming convention (e.g. PSD=BELIZE.PSD). They
   cannot contain either drive, or path information because OS/2 cannot
   process such information at the stage of the startup sequence when the
   PSD statements are processed.  The root directory of the startup
   partition is first searched for the specified file name, then the \OS2
   directory of the startup partition. If drive or path information is
   included in a PSD statement, an error is generated.

   PSD parameters may be specified after the PSD's name, and may be a
   maximum of 1024 characters long. The parameter string is not interpreted,
   or parsed by OS/2, it is passed verbatim, as an ASCIIZ string when the
   PSD's Install function is invoked.

   If multiple PSD statements are encountered. OS/2 will load each PSD in
   the order listed in CONFIG.SYS, and call the PSD's install function. The
   first PSD which successfully installs, will be the one OS/2 uses.

   PSD statements are processed before BASEDEV, IFS, and DEVICE statements.

   Please note that any time you add or make changes to the CONFIG.SYS file,
   you must restart the system in order for the changes to become effective.
   The CONFIG.SYS file is read only during system startup. Anything added to
   this file after system initialization does not work until you restart the
   system.

   This PSD has the following syntax for its argument line:

   [/apic] [/p=<n>] [/nmi=[l]int<n>] [/pic=[l]int<n>] [/prec=<pstr>]

   Where:
    /apic   indicates that the PSD should enable symetric interrupt
            mode.

    /p      indicates that the system should be configured for <n>
            processors where <n> is a decimal number (ie 5, 8, 12).

    /nmi    indicates to the system a default signal route for NMIs.
            This allows the route to be specified for NMIs if there
            isn't one defined by the MP configuration tables set up
            by BIOS.

   
                                         Platform Specific Drivers (PSDs)  5


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

            By using the /prec option (see below), it is possible to
            override what is in the MP configuration tables in the
            event that they have been built incorrectly by the BIOS.

            The argument is "int<n>" or "lint<n>".  The first case
            indicates the interrupt pin number to which the NMI signal
            is wired on the I/O apic.  The second case indicates the
            interrupt poin number to which the NMI signal is wired on
            the local apic.  <n> is a decimal number (ie 0, 3, 12).

    /pic    indicates to the system a default signal route for the
            8259 interrupt controller when the system is running in
            "virtual wire" mode.  This allows the route to be specified
            for the interrupt controller if there isn't one defined by
            the MP configuration tables set up by BIOS.  By using the
            /prec option (see below), it is possbile to override what is
            in the MP configuration tables in the event that they have
            been built incorrectly by the BIOS.

    /prec   indicates to the system the precedence order to be used in
            determining the routing for the NMI signal and the
            interrupt signal from the interrupt controller.  This
            allows control over the choosing of a routing entry when
            there is more than one entry.

            There are three (3) possible entries that can describe a
            route:
                    route to the I/O APIC
                    route to the Local APIC
                    route described by argument(s) to the PSD

            The first two may be specified in the MP configuration tables
            that are built by the BIOS.  The third may be specified on the
            argument line to the PSD.

            Each type of route is described by one letter.  "i" for the
            I/O APIC routes, "l" for the local APIC routes, and "d" for
            the routes described by the argument line to the PSD.

            The precedence string is *exactly* 3 characters long.  The
            first character indicates the type of routes to be considered
            first, the second indicates the routes to be considered next
            and the third indicates the routes that are to be considered
            last.

            As an example, "ild" indicates that I/O APIC routes are to
            considered first, followed by local APIC routes and finally
            routes specified on the argument line.  In contrast, "dil"
            indicates that routes on the argument line are to be considered
            first, then the I/O APIC and finally the local APIC.


   
                                         Platform Specific Drivers (PSDs)  6


         February 18, 2002 - Warp Server for e-business FixPak XR_E003


   Note: The arguments to the PSD are NOT case sensitive.


   5.0.1 PLEASE USE FIXTOOL F.143 OR LATER

   For Warp Server for e-business FixPak 01, you must use Corrective Service
   Facility f.143 or later.

   If you try to use a CSF level prior to f.143 you may get a "CSF0208 No
   products were found on the target system to service" message.


   5.0.2 OS2DUMP SPLIT INTO TWO VERSIONS

   OS2Dump has been split into two versions. If you are installing this
   FixPak on micro channel hardware without PCI Bus, like a PS/2 model 9595,
   use the OS2DUMP version located on the last diskette image of this
   FixPak.  Also, if you are running older hardware (486s or early
   Pentiums), you may wish to use the OS2Dump located on the last diskette
   image of this FixPak.

   We have encountered some problems with early implementations of the PCI
   Bus BIOS extensions (INT 1A) on certain processors and BIOS levels. We
   are not sure how many different machines and BIOSes are affected. We do
   know many of the PS/2 model 9595s have the problem. The end result of
   this is that the version of OS2Dump which supports PCI Bus machines does
   not work on some older hardware.  In order to continue to support the
   full range of hardware that OS/2 runs on, we have divided OS2Dump into a
   PCI version and an non-PCI version. If you are running fairly recent
   hardware, the PCI version of OS2Dump will work on your machine whether or
   not it has a PCI bus. All BIOS problems have been worked out.

   To reiterate, the problem occurs only on older hardware. If you are
   running a 486 or early Pentium (P60 or less), you may wish to use the
   non-PCI version located on the last diskette image of this FixPak. If you
   are running on hardware, like a PS/2 model 9595, you must use the non-PCI
   version located on the last diskette image of this FixPak.

    If, after installing this FixPak, you encounter problems taking a
   standalone dump and your system fits description above, perform the
   following steps to install the non-PCI version of OS2DUMP located on last
   disk of this FixPak:

   1. Open an OS/2 window.
   2. Change to drive letter where OS/2 is installed.
   3. Enter "cd\" to get to the root directory.
   4. Enter OS/2 command "attrib -s -h -r os2dump" to unhide OS2DUMP.
   5. Enter "ren os2dump os2dump.pci"; save PCI version of OS2DUMP.
   6. Insert last disk of FixPak in drive A.
   7. Copy a:\os2dump

   
                                         Platform Specific Drivers (PSDs)  7


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   8. Enter OS/2 command "attrib +r +s +h os2dump" to hide OS2DUMP.
   9. Reboot system.



   5.0.3 USING DISPLAY RECOVERY CHOICES

   If you have the "Display Recovery Choices at each system startup"
   function active on your system, you need to disable it before you apply a
   FixPak if

   þ  The system is running
   þ  The boot partition will be serviced.

   The problem with using this function is that the Corrective Service
   Facility (CSF) updates the current CONFIG.SYS with entries to run the
   Locked File Device Driver (LFDD) the next time you boot the system. This
   is done to replace files that are currently in use (locked) by the
   system.

   The Recovery choices function replaces the current CONFIG.SYS with the
   one that is associated with the recovery choice you select, wiping out
   the LFDD entries. This means the LFDD does not run at boot time and the
   deferred files will not get updated, therefore the FixPak does not get
   completely applied.

   Note: It is not necessary to disable this function if you install a
   FixPak by booting from the CSF disks or from another OS/2 partition.


   5.0.4 NO PRODUCTS FOUND

   If you see a "No products were found on the target system to service"
   message while applying this FixPak, there is probably a mismatch between
   the data in \OS2\INSTALL\SYSLEVEL.OS2 and what is supported by this
   FixPak.

   Compare the data for the Warp Server for e-business Base Operating System
   from the SYSLEVEL command output with the same values listed at the end
   of this document in the "FixPak Corrective Service levels and disk
   layouts" section.  They must be identical.

   If these values are correct, check for the following files on any OS/2
   boot drive in the \OS2\INSTALL directory.

      LOGF0000.OS2
      LOGSTART.OS2
      LOGARCH.OS2




   
                                         Platform Specific Drivers (PSDs)  8


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   Check for the following files in your MMOS2\INSTALL directory.

      LOGF0000.MPM
      LOGSTART.MPM
      LOGARCH.MPM


   Also check for the following file:

      C:\CSF_SEL.000


   If these files exist, rename them and try the FixPak installation again.
   Delete the renamed files after the FixPak has been applied.


   5.0.5 PREVIOUS INSTALLATION INTERRUPTED

   If you get a message that the previous installation of a FixPak was
   interrupted (whether true or not), check for the following files and
   directory on all drives:

     Files:
        FIXSTART
        IBMCSFLK.LST
        IBMCSFLK.CSF
        CSF_*

     Directory:
        IBMCSFLK


   If any exist, rename them and try the FixPak installation again.  Delete
   the renamed files after the FixPak has been applied.


   5.0.6 UNABLE TO OPEN ARCHIVE DIRECTORY

   If you get a message about problems with the Archive directory (for
   example, cannot find or unable to open), then the most probable cause is
   that you applied a previous FixPak and have since deleted the FixPak
   ARCHIVE or BACKUP directory.

   To recover from this, follow the "No files to service" and "Previous
   installation interrupted" steps listed above.







   
                                         Platform Specific Drivers (PSDs)  9


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   5.0.7 CSF0208 NO PRODUCTS WERE FOUND ON THE TARGET ...

   This means no SYSLEVEL files was found that had a CSD Level, COMPID,
   Version and Type that matched any of the SYSLEVEL files supported by this
   FixPak. Run the SYSLEVEL command and record the output for SYSLEVEL.OS2
   in the OS2/INSTALL directory on your boot drive. Compare this data with
   the data contained in the README.1ST file on FixPak disk 1.

   To recover from this, rename the existing SYSLEVEL.OS2 file to SYSL.OS2
   and copy SYSLEVEL.OS2 from your Warp Server for e-business found on
   installation DISK 1.


   5.0.8 CSF0249 ERROR OPENING OR CREATING ARCHIVE FILE.

   Typically this means the FixPak Archive directory has been deleted but
   the files that point to it still exist. You need to delete the
   LOGF000.OS2 and LOGSTART.OS2 files from your OS2/INSTALL directory.
   LOGSTART.OS2 has the R/O attribute set and it needs to be reset before
   the file can be deleted.  There may also be a LOGARCH.OS2 file that needs
   to be deleted.

   This can also occur for Multi Media Presentation Manager/2 (MMPM). You
   would then need to delete the LOGF0000.MPM and LOGSTART.MPM files from
   the \MMOS2\INSTALL directory and possibly LOGARCH.MPM if it exists.


   5.0.9 PRINTER INSTALLATION PROCESS CHANGE

   If you install a new printer by clicking MB2 on the Printer icon in the
   templates folder then clicking on Install, the printer object will now be
   created in the Printer folder, not on the Desktop.


   5.0.10 CONFIGURATION INSTALLATION DISTRIBUTION ( CID )

   Read the README.CID on Disk # 1 for an example of how to set up a
   response file to do a CID install.














   
                                        Platform Specific Drivers (PSDs)  10


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   6.0 POST INSTALLATION NOTES



















































   
                                                 Post Installation Notes  11


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   7.0 NEW FUNCTION

   It is our policy not to include new function in FixPaks. However, as with
   any policy there may be exceptions. If any exception occurs in the
   future, we will communicate them to you in this section of the
   README.1ST.


   7.1 NEW RAS UTILITIES ADDED

   Two new RAS utilities are included for Pak 01: PSFILES.EXE and
   PSSEMS.EXE.

   PSFILES.EXE can dump out information about open files on the system.  By
   default, it dumps out the information for all processes. Alternately,
   "PSFILES xxx" will dump out information for PID xxx (xxx is a hex number,
   e.g. from PSTAT).

   PSSEMS.EXE can dump out information about open 32 bit semaphores on the
   system By default it prints out all the shared (i.e. system-wide)
   semaphores.  Usage is:  pssems [/n] [hex_pid | /a] ; where /n suppresses
   shared semaphores and /a prints pruivate sems for all system processes.

   Note: These RAS Utilities are added to the OS2 directory on your system.


   7.2 JFS LAZYWRITE PARAMETERS ON THE IFS= LINE IN CONFIG.SYS

       IFS=jfs.ifs /L:OFF
       IFS=jfs.ifs /L:synctime,maxage,bufferidle


   (JFS ignores any characters between the L (or l) and the colon, so valid
   flags are /L: /LAZY: /LW: /lazywrite: etc.)

   OFF forces asynchonous writes to be immediately initiated.

   synctime is the interval at which the sync thread runs. Default = 64

   maxage is the longest time that a frequently modified file is kept in
   cache
           default = synctime*4

   bufferidle is the time indicating a "recent" change.  Changes newer than
           this value are not written unless the last write was older than
           maxage.  default = MIN(1,synctime/8)

   (All parameters in seconds)




   
                                                            New Function  12


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

        IFS=C:\OS2\JFS.IFS /L:64

        synctime = 32, maxage = 128, bufferidle = 4

        IFS=C:\OS2\JFS.IFS /LW:10,60,5

        synctime = 10, maxage = 60, bufferidle = 5

        IFS=C:\OS2\JFS.IFS /LAZYWRITE:4,60

        synctime = 4, maxage = 60, bufferidle = 1

        IFS=C:\OS2\JFS.IFS /lazy:off

        All writes initiated immediately (synctime=1, maxage=bufferidle=0)
        Note: sync thread still runs since trivial things like marking an
        inode accessed are still deferred.


   The cachejfs.exe command allows the lazywrite parameters to be changed
   immediately.  The syntax is to the IFS line, except that the /L: prefix
   is optional.  In addition, the cachejfs command can modify the minimum
   and maximum number of free cache buffers to be maintained.  Calling
   cachejfs with no parameters reports the current settings.

   CACHEJFS [[/LAZYWRITE:]{OFF|syncTime[,maxAge[,bufferIdle]]}]
   /MINFREE:minfree
            /MAXFREE:maxfree


   7.3 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)

   Future updates for GRADD and other video drivers (when they are released)
   will be found via the internet at:

   þ  http://service.software.ibm.com/pslaunch.html



   7.4 REXX NEW FUNCTION

   New Function has been added in REXX. Please see the "Other README Files"
   for documentation pointers. This new function was added to FP 1 and
   later.








   
                                                            New Function  13


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   7.5 OTHER README FILES

   There are other README files containing information you may want to
   review.  All README files are found on the first FixPak disk and are not
   copied to your system when the Fixpak is installed.

   File           Use

   README2        Problems fixed in each FixPak (APAR list)

   README.CID     Installing FixPaks via CID

   README.DBG     Description of Debug files for Warp Server for e-business
                  debugging.

   READREXX.TXT   New RexxUtil Function documentation added in this FixPak.




































   
                                                            New Function  14


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   8.0 CORRECTIVE SERVICE FACILITY



   8.0.1 REQUIRED CSF LEVEL

   You should use release level f.143 or later of the OS/2 Corrective
   Service Facility to install this FixPak.

   Bootable diskettes are no longer provided starting with the F.138B CSF
   build. Instead, you now get a self-extracting ZIP file which contains the
   following:

      archctl.cmd
      build.lvl
      csfpans.dll
      filefix.dll
      fpinst.cmd
      fservice.exe
      fservice.msg
      ibmcsflk.dll
      ibmcsflk.exe
      ibmcsflk.msg
      ibmcsflk.sys
      msg.dll
      nls.dll
      pack.exe
      read.me
      readme.inf
      response.lan
      response.wp3
      response.wp4
      service.exe
      service.hlp
      shpiinst.dll
      unpack.exe
      unpack2.exe
      viocalls.dll


   Follow the directions in the READ.ME file to use the new CSF code. It
   covers the use of SERVICE.EXE and FSERVICE.EXE from a booted partition or
   from one of several alternative boot methods.


   8.0.2 WHERE YOU CAN FIND CSF CODE

   The Corrective Service Facility code is available from many places,
   including, but not limited to, the following:

   Source         How to access

   
                                             Corrective Service Facility  15


         February 18, 2002 - Warp Server for e-business FixPak XR_E003


   Internet(FTP)  Anonymous FTP to ftp.software.ibm.com in the
                  "/ps/products/os2/fixtool" directory.

   Internet(WWW)  Point your Web Browser at
                  ftp://service.boulder.ibm.com/ps/products/os2/fixtool

   Intranet(FTP)  Anonymous FTP to os2service.austin.ibm.com in the
                  "g:\fixpacks\fixtool" directory.



   8.0.3 CREATING FIXPAK DISKETTES

   Use LOADDSKF.EXE to create the diskettes. For each disk image, place a
   2MB HD (1.44MB formatted) diskette in A:.

   Warning: DO NOT use a 1MB (720KB formatted) diskette because you might
   have problems trying to install this FixPak.

   For each diskette image in the FixPak, do the following:

   Enter LOADDSKF XR_E003.?DK A: /F  (? can be 1 through 9, A through Z).

   Label the diskette as

         FixPak XR_E003
   Corrective Service Diskette ?
          (CSF DISK ?)


   Note: For diskette images ADK through ZDK, use the numbers 10 through 35.

        Examples:

        XR_E003.ADK = 10
        XR_E003.FDK = 15
        XR_E003.LDK = 21
      etc.




   8.1 READ-ONLY FILES

   Some files being updated by this FixPak may have the Read-Only attribute
   set. If you are using the A:SERVICE method to install this FixPak you
   will be asked if you want the files replaced.

   Press the "OK" button.


   
                                             Corrective Service Facility  16


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   8.2 SYSLEVEL FILE LOCATIONS

   This FixPak will service directories based on the location of a supported
   SYSLEVEL.OS2 file.  Please check your system to make sure extra copies of
   this file are not located in directories other than:

     \OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s)


   If additional copies of these files are found in other locations on your
   hard disk then CSF will try to service files as follows:

   For \OS2\INSTALL\SYSLEVEL.OS2

     ..\..\           all files in a directory two levels above (toward the
                      root). This should be the root directory of your boot
                      drive.

     ..\*             all files in a directory one level above (toward the root)
                      and all subdirectories below. This should be the OS2
                      directory and subdirectories.

     ..\..\VT\*       all files in the VT directory and subdirectories.

     ..\..\PSFONTS\*  all files in the PSFONTS directory and subdirectories.

     ..\..\LANGUAGE\* all files in the LANGUAGE directory and subdirectories.

     ..\..\OPENDOC\*  all files in the OPENDOC directory and subdirectories.




   8.3 RELOCATED WARP SERVER FOR E-BUSINESS FILE SUPPORT

   If you have moved Warp Server for e-business files or directories to a
   drive other than the one the SYSLEVEL.OS2 file is on, do the following in
   order to have them serviced:

   þ  Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of the
      Warp Server for e-business partition to be serviced.

      In this file, place the full path to the directories you want to be
      serviced. Assuming your boot drive is C: and you installed Multimedia
      on the D: drive and manually moved WINOS2 support to the E: drive:







   
                                             Corrective Service Facility  17


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

       D:\MMOS2
       D:\MMOS2\DLL
       D:\MMOS2\DSP
       D:\MMOS2\HELP
       D:\MMOS2\IMAGES
       D:\MMOS2\INETTEMP
       D:\MMOS2\INSTALL
       D:\MMOS2\MACROS
       D:\MMOS2\MOVIES
       D:\MMOS2\SOUNDS
       D:\MMOS2\SOUNDS\DESKTOP
       D:\MMOS2\SOUNDS\GARDEN
       D:\MMOS2\SOUNDS\OCEAN
       D:\MMOS2\SOUNDS\SPACE
       E:\OS2\MDOS\WINOS2
       E:\OS2\MDOS\WINOS2\SYSTEM
       E:\OS2\MDOS\WINOS2\TEMP


   Note: Leave this file for any future Warp Server for e-business FixPaks
   you might apply. The easy way to create this file is to use the DIR
   command with the /A:D /S /B parameters and pipe the output to a file.

      dir d:\mmos2 /a:d /s /b > anyfile


   Then copy that data into the USERDIRS.OS2 file.

   With CSF release level F.143 or later, you can use wildcards, so your
   USERDIRS.OS2 file would be much simpler and would look like:

       D:\MMOS2\*
       E:\OS2\MDOS\WINOS2\*



















   
                                             Corrective Service Facility  18


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   9.0 INSTALLATION PROCESS



   9.1 BEFORE INSTALLATION

   Before installing any FixPak, run CHKDSK /F against all drives on your
   system to correct any file system errors that might be present. You
   cannot do this while OS/2 is active. You must shut down and run CHKDSK by
   one of the following methods:

   þ  Boot from your Installation, DISK 1 and DISK 2 diskettes.  If your
      file system is HPFS, then put the diskette with CHKDSK and UHPFS.DLL
      on it in your A: drive before issuing the CHKDSK command.
   þ  Boot from the Utilities disk you created via the "Create Utility
      Diskettes" icon in the System Setup folder.
   þ  Boot from a different OS/2 partition.

   Once CHKDSK has completed, reboot your system then shutdown all running
   applications before starting the FixPak installation.


   9.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION.

   Note: CS_???.EXE below means CS_143 or later.

   Follow the instructions in the READ.ME file that comes in the CS_???.EXE
   self-extracting zip file.  This explains how to use the CS_???.EXE file
   and the various ways you can install a FixPak with this level of CSF
   code.

   Here are some additional notes:

   Follow the displayed instructions.  When prompted to insert Corrective
   Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XR_E003
   Corrective Service Diskette 1 in drive A. Repeat for the rest of the
   FixPak disks when requested to do so.

   It can take a considerable length of time for the Corrective Service
   Facility to scan your hard disk for serviceable files.  In some cases, it
   has taken as long as 40 minutes.  Please be patient and allow this
   process to complete.

   If this is the first OS/2 Warp FixPak you have applied to this system,
   then enter the path to the directory where a copy of replaced files will
   be stored (for example, D:\ARCHIVE or E:\FIXPAK\ARC, etc.)

   Note: This ARCHIVE directory is not related to the ARCHIVES directory
   built into OS/2 Warp 3 and Warp 4. Please specify a different path.  You
   must specify a different ARCHIVE directory for each product to be
   serviced.

   
                                                    Installation Process  19


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   If this is not the first OS/2 Warp FixPak, then enter the path to the
   BACKUP directory where a copy of replaced files will be stored (for
   example, D:\BACKUP).

   Note: You must specify a different BACKUP directory for each product to
   be serviced.

   Make sure there is sufficient space available on the drive you specify
   for archive or backup.  Even though these files are kept in compressed
   (PACK2) format, they can take up a lot of space on the drive.

   During the installation process you may see messages about Archiving,
   Updating and Deferring service.

   þ  Archiving saves a compressed copy of the original file in the ARCHIVE
      or BACKUP path you specified.
   þ  Updating means the original files are replaced with the new ones from
      this FixPak.
   þ  Deferring service means the file to be updated is currently in use by
      the system and cannot be updated.  The new files from the FixPak are
      placed in unpacked format in the \IBMCSFLK\FIX directory on the drive
      with the most free space.  They are processed by the locked file
      device driver during reboot after you shut down the system.

   See the section "FixPak Corrective Service levels and disk layouts" for
   the CSD levels this FixPak applies to.

   You will see the following during reboot of the system if you applied
   service to the OS/2 partition you were booted from.

      The locked file driver is loaded.

             Processing locked files

             Processing complete


   The system will do one automatic reboot after the Locked File Device
   Driver has completed.


   9.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA

   Note: CS_???.EXE below means CS_143 or later.

   Follow the instructions in the READ.ME file that comes in the CS_???.EXE
   self-extracting zip file.  This explains how to use the CS_???.EXE file
   and the various ways you can install a FixPak with this level of CSF
   code.



   
                                                    Installation Process  20


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   Here are some additional notes:

   This method does not prompt the user for any information.  No interaction
   with the user takes place other than requests to put the next diskette in
   drive A. All serviceable partitions on your system will be updated
   automatically unless you have modified the default response file.  Be
   especially careful of extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using
   this method because they can cause CSF to apply service to directories
   you do not want serviced.

   See the section "FixPak Corrective Service levels and disk layouts" for
   the CSD levels this FixPak applies to.

   Note: It can take a considerable length of time for the Corrective
   Service Facility to scan your hard disk for serviceable files.  Please be
   patient and allow this process to complete.

   Note: You can edit the response file to control some of the actions taken
   by FSERVICE.EXE while applying a FixPak.  See the READ.ME file or use the
   VIEW command to look at the file README.INF.  They are part of
   CS_???.EXE.


   9.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION

   Additional information on the Corrective Service Facility, like how to
   backout a FixPak, is available from the README.INF file on the first
   Corrective Service Facility disk.  To view this file, place CSF disk 1 in
   drive A and enter VIEW A:\README.INF.

   There is also some additional information in the READ.ME file.





















   
                                                    Installation Process  21


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   10.0 CSD LEVEL OF SYSLEVEL.OS2

   The Current CSD level field of the SYSLEVEL.OS2 file in each serviced
   partition will be updated with the name of the FixPak when it is applied.

   All fix information is recorded in SERVICE.LOG. Look at the file

      \OS2\INSTALL\SERVICE.LOG


   on your boot drive for information relating to the installation of
   FixPaks on your system.


   10.1 VER /R OUTPUT

   You can use the VER /R command from a OS/2 or DOS session to see the
   current revision of OS/2 installed.  The response will look like the
   following for this FixPak:

   The Operating System/2 Version is 4.50
   Revision 14.088


   The first page of this document has a line that looks like:

   Build Level: n.nnn


   This reflects the build level of the OS2KRNL which should match that
   shown by the ver /r output.


   10.1.1 FIXPAK SYSLEVEL FILE

   A SYSLEVEL.FPK will be added to the OS2\INSTALL directory when this
   FixPak is installed. It is titled "OS/2 Warp Server for e-business
   Service Level".  It contains the name of the currently installed FixPak
   in both the Current and Previous CSD level fields and is located in the
   same directory the SYSLEVEL.OS2 file is located in which should be
   \OS2\INSTALL.

   The easiest way to look at SYSLEVEL information is to use the SYSLEVEL
   command and redirect the output to a file then edit the file and search
   for SYSLEVEL.FPK.







   
                                               CSD level of SYSLEVEL.OS2  22


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   11.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS

   Build Level: 14.088

   Product location on CSD:  A:\FIX\OS2.1
   Product name:  "Warp Server for e-business Base Operating System (UNI)"
   Standard Edition  4.50
   Fixpak name:   XR_E003_   (Country = Generic)
   Pre-requisite CSD Level:  XR_4500_
   System Id:  1000
   Component Id:  5639A6150
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "Warp Server for e-business Base Operating System (SMP)"
   Standard Edition  4.50
   Fixpak name:   XR_E003_   (Country = Generic)
   Pre-requisite CSD Level:  XR_4500_
   System Id:  1000
   Component Id:  5639A5550
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\*
           ..\..\MMOS2
           ..\..\MMOS2\*
           ..\..\VT
           ..\..\VT\*
           ..\..\TOPOBJ
           ..\..\TOPOBJ\*
           ..\..\PSFONTS
           ..\..\PSFONTS\*
           ..\..\LANGUAGE
           ..\..\LANGUAGE\*
   Will create the following directories
      ..\..\   Stub File:  @ROOTDIR

      ..\..\OS2   Stub File:  @OS2DIR

      ..\..\OS2\BOOT   Stub File:  @BOOTDIR

      ..\..\OS2\DLL   Stub File:  @DLLDIR

      ..\..\OS2\HELP   Stub File:  @HELPDIR

      ..\..\OS2\INSTALL   Stub File:  @INSTDIR

      ..\..\OS2\INSTALL\UNI   Stub File:  @UNIDIR

      ..\..\OS2\INSTALL\SMP   Stub File:  @SMPDIR

   
                       FixPak Corrective Service levels and disk layouts  23


         February 18, 2002 - Warp Server for e-business FixPak XR_E003


      ..\..\OS2\MDOS\WINOS2\SYSTEM   Stub File:  @WINSYS

      ..\..\OS2\SYSTEM   Stub File:  @SYSTDIR

      ..\..\OS2\SYSTEM\TRACE   Stub File:  @TRCDIR

      ..\..\OS2\PDPSI\PMDF\WARP45_U   Stub File:  @WARP45U

      ..\..\OS2\PDPSI\PMDF\WARP45_S   Stub File:  @WARP45S


   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   ANSI.SYS      ANSI.SY_       14    09/24/2001  15:49     7480  C85407C8
   ARCINST.EXE   ARCINST.EX_    14    10/23/2001  13:55    17962  DE75422B
   ARCRECOV.EXE  ARCRECOV.EX_   13    10/23/2001  13:55    24723  E0824C6F
   ASIACOL.DLL   ASIACOL.DL_    10    10/03/2001  06:37   158758  3FBDA86D
   ATTRIB.EXE    ATTRIB.EX_     13    02/14/2002  09:41    37789  B3FC5FB9
   BACKPRN.EXE   BACKPRN.EX_    13    10/02/2001  17:49    40582  9B146A71
   BDVIEW.DLL    BDVIEW.DL_      5    10/23/2001  13:53    39496  272F6707
   BDVIEWER.EXE  BDVIEWER.EX_   13    10/23/2001  13:53    39866  312AF061
   BDWPCLS.DLL   BDWPCLS.DL_    13    10/23/2001  13:52    24832  01F8F34F
   BOOTDISK.EXE  BOOTDISK.EX_   12    02/13/2002  16:32    88145  55C367E2
   BOOTDISK.HLP  BOOTDISK.HL_   14    10/26/2001  10:24    12571  414DD662
   CACHE.EXE     CACHE.EX_      14    10/02/2001  18:20    13870  9ABF613A
   CACHEJFS.EXE  CACHEJFS.EX_   13    10/16/2001  13:30    44310  2986D0ED
   CCHMAIN.EXE   CCHMAIN.EX_     8    10/23/2001  14:01   273248  D0EC7B6C
   CCHUSER.DLL   CCHUSER.DL_    11    10/23/2001  14:01   121443  722CF728
   CDFS.IFS      CDFS.IF_       13    10/02/2001  18:34    45159  D1FF7267
   CDFS.TDF      CDFS.TD_       14    10/02/2001  18:34     2113  8080F3F6
   CHGQUE.EXE    CHGQUE.EX_     13    10/02/2001  17:49    35401  74E6BDBD
   CHKDSK.COM    CHKDSK.CO_     12    02/14/2002  09:42    70720  77DCA15A
   CHKDSK.SYS    CHKDSK.SY_     14    10/02/2001  18:21      795  57FB3E87
   CHKDSK32.DLL  CHKDSK32.DL_    1    10/02/2001  18:32   147268  358B131A
   CHKDSK32.EXE  CHKDSK32.EX_   14    10/02/2001  18:21     6417  47331C60
   CHKLGJFS.EXE  CHKLGJFS.EX_   12    10/16/2001  13:44    87283  6EDC421E
   CLIPOS2.EXE   CLIPOS2.EX_    14    10/02/2001  17:46    16755  BC5A1721
   CLRBBLKS.EXE  CLRBBLKS.EX_   13    10/16/2001  13:43    35343  3396BAE4
   CMD.EXE       CMD.EX_        11    02/14/2002  09:44   100108  8C401D05
   COMETRUN.EXE  COMETRUN.EX_   14    10/16/2001  16:11    28560  2F6163FB
   COMMAND.COM   COMMAND.CO_    13    02/14/2002  09:43    42763  CB27F1A2
   CREX.MSG      CREX.MS_       14    09/06/2000  12:42     2865  8188DE0E
   CREXUTIL.DLL  CREXUTIL.DL_   12    09/06/2000  12:42    68119  4D4A96EB
   CREXX.DLL     CREXX2.DL_     10    09/06/2000  12:42   266031  C716AA5F
   DDINSTAL.EXE  DDINSTAL.EX_   13    02/13/2002  16:26    52263  F0B2E9E9
   DEFRAGFS.EXE  DEFRAGFS.EX_   13    10/16/2001  13:43    34006  2059906A
   DF_DEB.EXE    DF_DEB.SM_     11    02/13/2002  15:12   143595  19574B28
   DF_DEB.EXE    DF_DEB.UN_     11    02/13/2002  15:11   135479  19647CDB

   
                       FixPak Corrective Service levels and disk layouts  24


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   DF_RET.EXE    DF_RET.SM_      8    02/13/2002  14:22   143563  ABBF2F04
   DF_RET.EXE    DF_RET.UN_     11    02/13/2002  14:13   135447  F1F4EA96
   DOSCALL1.DLL  DOSCALL1.SM_   10    02/13/2002  14:21   144387  E2D6BF8B
   DOSCALL1.DLL  DOSCALL1.UN_   10    02/13/2002  14:12   137445  44BCBD46
   DOSCALL1.SYM  DOSC1SYM.SM_   13    02/13/2002  14:21    43828  7FF7880A
   DOSCALL1.SYM  DOSC1SYM.UN_   13    02/13/2002  14:12    43476  BED7692E
   DOSKRNL       DOSKRNL.___    13    02/13/2002  14:13    31497  F124F669
   DRVONDSK.DLL  DRVONDSK.DL_   14    10/23/2001  13:59    29288  6DFC0FAE
   DSPIMRI.DLL   DSPIMRI.DL_    14    10/27/2001  16:02    17446  F223045C
   DSPINSTL.EXE  DSPINSTL.EX_   11    10/27/2001  16:02   175640  D88260CC
   E.EXE         E.EX_           3    10/02/2001  17:47    68277  ABA60750
   EAUTIL.EXE    EAUTIL.EX_     13    02/14/2002  09:45    38000  4A9C15D3
   EJECT.EXE     EJECT.EX_      14    09/24/2001  15:54    37426  F096E8BE
   ENGINE.DLL    ENGINE.DL_     13    10/16/2001  13:27    32513  477BFAD9
   ETKE603.DLL   ETKE603.DL_     6    09/14/2001  16:20   767421  E4F505D6
   EXTENDFS.EXE  EXTENDFS.EX_   13    10/16/2001  13:43    29348  4D841928
   EZPLAY2.DLL   EZPLAY2.DL_    11    10/23/2001  14:05    98185  617E5327
   FFIPC.DLL     FFIPC.DL_      13    02/13/2002  16:35    27201  F8680592
   FIBASE.RSP    FIBASE.RS_     13    11/07/2001  22:59   447705  F50548D4
   FORMAT.COM    FORMAT.CO_     12    02/14/2002  09:45    72064  D81895F0
   GDI.EXE       GDI.EX_         9    10/24/2001  11:09   225776  EAC8D781
   GLOCALE.EXE   GLOCALE.EX_    12    10/03/2001  06:34   157048  89EC7283
   GRE2VMAN.DLL  GRE2VMAN.DL_   14    09/14/2001  15:59    18765  EEDA92B9
   GSVDAEMN.EXE  GSVDAEMN.EX_   14    10/25/2001  16:27     4848  187ECB28
   GSVINST.EXE   GSVINST.EX_    13    10/23/2001  13:31    38841  7B9CB686
   HELPMGR.DLL   HELPMGR.DL_     9    10/16/2001  13:54   250157  0A787EA7
   HPFS.IFS      HPFS.IF_       11    10/02/2001  18:18   141378  1A1F60B2
   HPFS.TDF      HPFS.TD_       14    10/02/2001  18:18     1620  FE70CB13
   INSCFG32.DLL  INSCFG32.DL_   13    02/13/2002  16:29    32098  E77B866D
   INSPGM32.DLL  INSPGM32.DL_   13    02/13/2002  16:19    41504  5787ABC9
   INSTALL.EXE   INSTALL.EX_     2    03/16/2000  08:07   407227  5981418C
   INSTPRT.EXE   INSTPRT.EX_    14    10/23/2001  13:59    12800  8255D1B6
   JAVA.RSP      JAVA.RS_       14    06/15/2001  14:48    63630  4B6A668F
   JFS.IFS       JFS.IF_         9    10/16/2001  13:28   190052  2F741AB4
   JFS.MSG       JFS.MS_        14    10/16/2001  13:28    12619  476435FE
   JFS.TDF       JFS.TD_        14    10/16/2001  13:28    16519  693AE1E5
   JFSCHK32.EXE  JFSCHK32.EX_   14    10/16/2001  13:43     6495  D8902707
   JFSH.MSG      JFSH.MS_       14    10/16/2001  13:28     9515  99028C3C
   JPGENDC.DLL   JPGENDC.DL_    10    07/26/2001  15:51   148773  4F326E6A
   KERNEL.SDF    KRNLRSDF.SM_   12    02/13/2002  14:22    59500  077C7E5E
   KERNEL.SDF    KRNLRSDF.UN_   12    02/13/2002  14:13    59227  BA3AACF6
   KERNELD.SDF   KRNLDSDF.SM_   12    02/13/2002  15:45    59443  214D1D7F
   KERNELD.SDF   KRNLDSDF.UN_   11    02/13/2002  15:45    59419  019F15AC
   KEYBOARD.DCP  KEYBOARD.DC_   13    10/03/2001  06:45   315109  DBD280C7
   KRNLRDEV.TDF  KRNLRDEV.TD_   14    02/13/2002  14:10     4232  E995802D
   KRNLRFS.TDF   KRNLRFS.TD_    14    02/13/2002  14:10     4793  2DE6B4AE
   KRNLRLDR.TDF  KRNLRLDR.TD_   14    02/13/2002  14:10     5384  589E0B2C
   KRNLRPG.TDF   KRNLRPG.TD_    14    02/13/2002  14:10     3209  D604DAB4
   KRNLRSEL.TDF  KRNLRSEL.TD_   14    02/13/2002  14:10     2783  E48571AA
   KRNLRSEM.TDF  KRNLRSEM.TD_   14    02/13/2002  14:10     1792  1215B7D8
   KRNLRSM.TDF   KRNLRSM.TD_    14    02/13/2002  14:10     1196  56A47975

   
                       FixPak Corrective Service levels and disk layouts  25


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   KRNLRTK.TDF   KRNLRTK.TD_    14    02/13/2002  14:10    12971  946EA79A
   KRNLRTOM.TDF  KRNLRTOM.TD_   14    02/13/2002  14:11      984  B642462E
   KRNLRVDM.TDF  KRNLRVDM.TD_   14    02/13/2002  14:11    15405  480BBF7C
   KRNLRVM.TDF   KRNLRVM.TD_    14    02/13/2002  14:11     5542  6B096FBD
   LIBCM.DLL     LIBCM.DL_       9    11/22/1999  11:45   210916  5BC599EE
   LIBCN.DLL     LIBCN.DL_      12    11/22/1999  11:45    57340  676A0B04
   LIBCS.DLL     LIBCS.DL_       9    11/22/1999  11:45   192386  7E2C4E24
   LIBUNI.DLL    LIBUNI.DL_     12    10/03/2001  06:45    80766  E487FB8D
   LOCALE.DLL    LOCALE.DL_     11    10/03/2001  06:42   108353  FA9ECED6
   LOGDUMP.EXE   LOGDUMP.EX_    11    10/16/2001  13:30    79021  3A8427EA
   LVM.DLL       LVM.DL_        10    10/16/2001  13:25   166141  327C5E63
   LVM.EXE       LVM.EX_        11    10/16/2001  13:41    92878  9D88C990
   LVM.MSG       LVM.MS_        14    10/16/2001  13:26    18184  68BF9189
   LVMALERT.EXE  LVMALERT.EX_   13    10/16/2001  13:26    22828  15E0F1E6
   LVMGUI.CMD    LVMGUI.CM_     14    09/14/2001  20:24     1628  8EC04293
   LVMGUI.ZIP    LVMGUI.ZI_     10    10/16/2001  13:26   462271  379DE364
   LVMH.MSG      LVMH.MS_       14    10/16/2001  13:26    21126  8DB8059E
   MAIN.CPL      MAIN.CP_       11    10/24/2001  11:13   147680  858F843E
   MAKEINI.EXE   MAKEINI.EX_    13    10/16/2001  13:37    65024  02BC8522
   MINXOBJ.DLL   MINXOBJ.DL_    13    10/23/2001  13:56    32292  99B6FF75
   MMPARTS.DLL   MMPARTS.DL_     1    07/26/2001  15:52  1535740  BB19375C
   MODE.COM      MODE.CO_       13    02/14/2002  09:46    64401  B2F54E09
   MONCALLS.TDF  MONCALLS.TD_   14    02/13/2002  15:43     1139  A16702B7
   MPPMNEW.EXE   MPPMNEW.EX_    14    07/26/2001  14:32     6486  6E6D69D4
   NAMEEXT.EXE   NAMEEXT.EX_    14    09/14/2001  16:05    24064  0CCC0C41
   NAMEREXX.DLL  NAMEREXX.DL_   11    09/06/2000  12:45    97811  93EAB604
   NWIAPI.DLL    NWIAPI.DL_     14    10/23/2001  13:58    15378  357DD01A
   OREXUTIL.DLL  ORXUTIL2.DL_   13    09/06/2000  12:43    41175  9BC71149
   OREXX.DLL     OREXX2.DL_      7    03/06/2001  13:59   491299  DBAB973D
   OS2APIC.PSD   OS2APIC.PS_    14    02/13/2002  14:23    31232  CD86A06D
   OS2CHAR.TDF   OS2CHAR.TD_    14    02/13/2002  14:12    13889  63BFDA39
   OS2DASD.DMD   OS2DASD.DM_    13    10/16/2001  13:24    37431  378ECC00
   OS2DUMP       OS2DUMP.___    14    02/13/2002  15:09    14989  DD96FA59
   OS2KRNL       OS2KRNL.SM_     5    02/13/2002  14:19   909146  4E47BCF2
   OS2KRNL       OS2KRNL.UN_     6    02/13/2002  14:10   847335  A281AE9A
   OS2KRNL.TDF   OS2KRNL.TD_    14    02/13/2002  14:10    21026  D90A44EF
   OS2KRNLB.SYM  KRNLBSYM.SM_   10    02/13/2002  14:55   192004  8A665E50
   OS2KRNLB.SYM  KRNLBSYM.UN_   10    02/13/2002  14:42   184964  6170C1D2
   OS2KRNLD.SYM  KRNLDSYM.SM_   10    02/13/2002  14:48   196532  9B683B73
   OS2KRNLD.SYM  KRNLDSYM.UN_   10    02/13/2002  14:36   188996  0A60B730
   OS2KRNLR.SYM  KRNLRSYM.SM_   11    02/13/2002  14:19   173012  D485F295
   OS2KRNLR.SYM  KRNLRSYM.UN_   11    02/13/2002  14:10   168532  4A5953A4
   OS2LDR        OS2LDR.SM_     13    02/13/2002  15:14    42496  92974023
   OS2LDR        OS2LDR.UN_     13    02/13/2002  15:13    44544  3296E7F7
   OS2LVM.DMD    OS2LVM.DM_     13    10/16/2001  13:25    31483  078551AD
   OS2OM30.DLL   OS2OM30.DL_     9    09/25/2001  13:14   254392  E7B37B45
   OS2OOOC.DLL   OS2OOOC.DL_     3    09/25/2001  13:15  1256949  5B29197A
   OS2OOR3U.DLL  OS2OOR3U.DL_   14    09/25/2001  13:15    19497  EB2F4737
   OSO001.MSG    OSO001.MS_     12    10/29/2001  19:22   175354  F80FBD2E
   OSO001H.MSG   OSO001H.MS_    12    10/29/2001  19:23   240256  CCA7FFE7
   PARALLEL.PDR  PARALLEL.PD_   14    10/02/2001  17:45    16412  698E490D

   
                       FixPak Corrective Service levels and disk layouts  26


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   PICV.DLL      PICV.DL_       14    10/16/2001  15:00    26200  59356B53
   PMCLIP.DLL    PMCLIP.DL_     14    10/16/2001  15:35    21527  28798804
   PMCTLS.DLL    PMCTLS.DL_      4    10/16/2001  21:53   587798  580AC471
   PMCTLS.SYM    PMCTLSYM.SM_   13    10/16/2001  21:53    44660  25EA5E6F
   PMCTLS.SYM    PMCTLSYM.UN_   13    10/16/2001  21:53    44660  25EA5E6F
   PMDDEML.DLL   PMDDEML.DL_    13    10/16/2001  13:36    27814  AFFE1B42
   PMGPI.DLL     PMGPI.DL_       9    10/16/2001  13:31   248446  7728C79B
   PMGPI.TDF     PMGPI.TD_      14    10/16/2001  13:31    12338  D1BC9677
   PMGRE.DLL     PMGRE.DL_      14    10/16/2001  14:46     2231  C27A9F54
   PMGRE.TDF     PMGRE.TD_      14    10/16/2001  21:54     1062  C1410F62
   PMMERGE.DLL   PMMERGE.DL_     2    10/16/2001  21:54  1269479  23CA55BE
   PMMERGE.SYM   PMMERSYM.SM_   12    10/16/2001  21:54   117524  8C108380
   PMMERGE.SYM   PMMERSYM.UN_   11    10/16/2001  21:54   117524  8C108380
   PMMRGRES.DLL  PMMRGRES.DL_   11    10/16/2001  13:44   134144  86E82AC3
   PMPIC.TDF     PMPIC.TD_      14    10/16/2001  15:00      400  AAA089A3
   PMPRINT.QPR   PMPRINT.QP_    14    10/02/2001  17:39    11813  048B618F
   PMPRNTXT.QPR  PMPRNTXT.QP_    6    10/02/2001  17:39    15511  ED695338
   PMREXX.EXE    PMREXX.EX_     13    09/25/2001  13:13    78885  BCB22E9A
   PMSHAPI.DLL   PMSHAPI.DL_    14    10/16/2001  13:38     4549  9B959933
   PMSHAPI.TDF   PMSHAPI.TD_    14    10/16/2001  21:54     6726  F0F8A082
   PMSHELL.EXE   PMSHELL.EX_    14    10/23/2001  13:20     6484  B30FB37D
   PMSPL.DLL     PMSPL.DL_       8    10/02/2001  17:38   280283  AC7727FA
   PMSPL.SYM     PMSPLSYM.SM_   14    10/02/2001  17:38    32340  9E28733E
   PMSPL.SYM     PMSPLSYM.UN_   14    10/02/2001  17:38    32340  9E28733E
   PMSPL.TDF     PMSPL.TD_      14    10/02/2001  17:38     4491  68EEC650
   PMSPOOL.EXE   PMSPOOL.EX_    14    10/23/2001  12:43    10574  D731FA0D
   PMVDMP.DLL    PMVDMP.DL_     12    10/16/2001  13:57    45317  31B7500A
   PMVDMP.TDF    PMVDMP.TD_     14    10/16/2001  22:03     2661  08148964
   PMVIOP.DLL    PMVIOP.DL_     12    10/16/2001  13:57    64242  DAB487B1
   PMVIOP.SYM    PMVIOSYM.SM_   14    10/16/2001  13:57     7620  FB31959A
   PMVIOP.SYM    PMVIOSYM.UN_   14    10/16/2001  13:57     7620  FB31959A
   PMVIOP.TDF    PMVIOP.TD_     14    10/16/2001  22:03     3551  2D0F6860
   PMWIN.TDF     PMWIN.TD_      14    10/16/2001  21:54     9567  F1E8D808
   PMWINX.DLL    PMWINX.DL_      5    10/16/2001  13:52   531027  2D08D442
   PMWP.DLL      PMWP.DL_        4    10/23/2001  13:55  1067033  5F6AFF2A
   PMWP.SYM      PMWPSYM.SM_    12    10/23/2001  13:55   103796  F087D718
   PMWP.SYM      PMWPSYM.UN_    12    10/23/2001  13:55   103796  F087D718
   PMWP.TDF      PMWP.TD_       14    10/23/2001  13:55    13825  139BAE38
   PMWPMRI.DLL   PMWPMRI.DL_    12    10/02/2001  17:34    54311  2B6898B4
   PNP.DLL       PNP.DL_        13    10/23/2001  13:59    28347  BAB91AA7
   PNP.SYS       PNP.SY_        14    10/25/2001  17:51     2152  ACA60079
   PORTPLUG.DLL  PORTPLUG.DL_   14    10/23/2001  13:58    26200  5F518C09
   PRINTPNP.PND  PRINTPNP.PN_   14    06/05/2000  10:55    15227  B1A8F8D3
   PRTRLIST.DLL  PRTRLIST.DL_   14    10/23/2001  13:58    31840  F0155FCD
   PSFILES.EXE   PSFILES.EX_    14    02/14/2002  09:46    10229  07B6DF47
   PSSDMON.EXE   PSSDMON.EX_    13    10/18/2001  20:22    43581  25B221C2
   PSSEMS.EXE    PSSEMS.EX_     14    02/14/2002  09:46    11717  B1784C2B
   PSTAT.EXE     PSTAT.EX_      14    02/14/2002  09:46    14661  9485824B
   QUECALLS.DLL  QUECALLS.DL_   14    02/13/2002  15:43     1024  D0C2E099
   QUECALLS.TDF  QUECALLS.TD_   14    02/13/2002  14:12     1299  25360127
   README.CID    README.CI_     14    10/10/2001  08:39    49648  F1DB0169

   
                       FixPak Corrective Service levels and disk layouts  27


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   REGCONV.EXE   REGCONV.EX_    12    09/14/2001  16:03    54294  C152A35B
   REGEDIT2.EXE  REGEDIT2.EX_    7    09/14/2001  16:05   984576  6F27430E
   REGISTRY.TDF  REGISTRY.TD_   14    09/14/2001  16:09      984  063D45B7
   RESTPRN.EXE   RESTPRN.EX_    13    10/02/2001  17:49    42059  FADA0114
   REX.MSG       REX.MS_        14    09/06/2000  12:42     2865  603C7657
   REXX.DLL      CREXX1.DL_     10    09/06/2000  12:42   266031  42250B8E
   REXX.DLL      OREXX1.DL_      3    03/06/2001  13:59   491299  7D4A0EF1
   REXX.IMG      REXX.IM_        2    09/06/2000  12:42   283636  D71F239D
   REXXAPI.DLL   REXXAPI.DL_    13    09/06/2000  12:42    40995  14493324
   REXXC.EXE     REXXC.EX_      14    09/06/2000  12:42     2758  D07F5D4F
   REXXCRT.DLL   REXXCRT.DL_    12    09/06/2000  12:42    79348  C14E27D8
   REXXUTIL.DLL  REXXUTIL.DL_    9    09/06/2000  12:42    68119  4D4EA6EB
   REXXUTIL.DLL  ORXUTIL1.DL_   13    09/06/2000  12:43    41175  9BC74649
   RINSTPRN.EXE  RINSTPRN.EX_    9    10/02/2001  17:49   211873  4C46192E
   RIPLINST.EXE  RIPLINST.EX_   12    02/13/2002  16:32   174339  1A83FDA5
   RJAPPLET.EXE  RJAPPLET.EX_   14    10/02/2001  17:44    24478  A2C42E3E
   RSPDDI.EXE    RSPDDI.EX_     14    02/13/2002  16:26    29753  F3C59FCA
   RSPDSPI.EXE   RSPDSPI.EX_    12    10/27/2001  16:02   143910  73A79117
   RSPIMRI.DLL   RSPIMRI.DL_    14    10/27/2001  16:02    17455  71B4F4BD
   RSPINST.EXE   RSPINST.EX_     8    02/13/2002  16:23   478064  FE80264E
   RXVIDCFG.DLL  RXVIDCFG.DL_   14    09/10/2001  16:17    16789  FDAA50FF
   SBFILTER.DLL  SBFILTER.DL_   14    09/10/2001  16:19    15405  727E0225
   SCENTER.DLL   SCENTER.DL_     8    10/02/2001  17:46   300183  E1B1915E
   SEAMLESS.DLL  SEAMLESS.DL_   13    10/16/2001  22:03    49167  C22DF519
   SERIAL.PDR    SERIAL.PD_     14    10/02/2001  17:36    19596  C1DF893F
   SESDB.DLL     SESDB.DL_      14    10/18/2001  20:22    23555  DDE3DAC5
   SESDD32.SYS   SESDD32.SY_    12    10/18/2001  20:23   100402  69AF8F7C
   SESDMON.EXE   SESDMON.EX_    14    10/18/2001  20:23    42238  F25AE9C0
   SESMGR.DLL    SESMGR.DL_     14    02/13/2002  15:43     1536  6534B7AB
   SESMGR.TDF    SESMGR.TD_     14    02/13/2002  14:12     1877  62252096
   SESSHELL.EXE  SESSHELL.EX_   14    10/18/2001  20:22    30941  C79948BB
   SGMLPARS.DLL  SGMLPARS.DL_   13    10/23/2001  13:58    58880  9A1722C5
   SHELL.SDF     SHELLSDF.SM_   13    02/13/2002  14:22    21279  E82E0DF5
   SHELL.SDF     SHELLSDF.UN_   13    02/13/2002  14:22    21279  E82E0DF5
   SOFTDRAW.DLL  SOFTDRAW.DL_    8    10/16/2001  13:24   416735  F2AC3A07
   SPL1B.DLL     SPL1B.DL_      14    10/23/2001  12:43     7125  DDF4EDE9
   SPOOLCP.DLL   SPOOLCP.DL_    14    10/23/2001  12:48    10210  23AFE75B
   SYSLEVEL.EXE  SYSLEVEL.EX_   13    02/13/2002  16:19    45024  231AF33C
   SYSLEVEL.FPK  SYSLEVEL.FP_   14    01/08/2002  10:48      165  DA950A25
   SYSLEVEL.MSG  SYSLEVEL.MS_   14    10/26/2001  10:05     1452  46B8E4BD
   TRACE.EXE     TRACE.EX_      13    02/14/2002  09:52    56064  D4A6E780
   TRAPDUMP.EXE  TRAPDUMP.EX_   14    02/13/2002  16:39    30236  D7C1118F
   TRC0000.TFF   TRC0000.TF_    14    02/13/2002  14:10      189  78DB25E7
   TRC0001.TFF   TRC0001.TF_    14    09/14/2001  16:09     1370  17FE1D51
   TRC0003.TFF   TRC0003.TF_    14    02/13/2002  14:10     1503  2525868F
   TRC0004.TFF   TRC0004.TF_    14    02/13/2002  14:10     4754  19E2826C
   TRC0005.TFF   TRC0005.TF_    14    02/13/2002  14:10    49321  00631531
   TRC0006.TFF   TRC0006.TF_    14    02/13/2002  14:10    12356  84D5674E
   TRC0007.TFF   TRC0007.TF_    14    10/16/2001  13:39     3336  602C8047
   TRC0008.TFF   TRC0008.TF_    14    10/25/2001  16:22      544  47593ED2
   TRC0010.TFF   TRC0010.TF_     8    02/13/2002  14:12    13647  C63BC6DD

   
                       FixPak Corrective Service levels and disk layouts  28


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   TRC0012.TFF   TRC0012.TF_    13    02/13/2002  15:43     1247  4B10B975
   TRC0016.TFF   TRC0016.TF_    14    02/13/2002  14:12     1673  81070AAA
   TRC0017.TFF   TRC0017.TF_    14    02/13/2002  14:12     5561  28B3BD75
   TRC0018.TFF   TRC0018.TF_    14    02/13/2002  14:12    39488  5DC61366
   TRC006D.TFF   TRC006D.TF_    14    07/26/2001  14:42    24181  FB8B4228
   TRC00C0.TFF   TRC00C0.TF_     2    10/16/2001  21:54    15970  2A3D7C66
   TRC00C2.TFF   TRC00C2.TF_    14    10/16/2001  21:54    25994  78380A52
   TRC00C3.TFF   TRC00C3.TF_    14    10/16/2001  21:54     3984  596F4AD0
   TRC00C4.TFF   TRC00C4.TF_     9    10/16/2001  15:00      288  6209D2A4
   TRC00C5.TFF   TRC00C5.TF_    14    10/16/2001  13:31    32994  870C4018
   TRC00C6.TFF   TRC00C6.TF_    14    10/02/2001  17:38     7146  F49D6681
   TRC0100.TFF   TRC0100.TF_    14    02/13/2002  14:10     7219  FB080691
   TRC0101.TFF   TRC0101.TF_    14    02/13/2002  14:10     7968  B3EB0FEE
   TRC0102.TFF   TRC0102.TF_    14    02/13/2002  14:11    29256  51C176E7
   TRC0103.TFF   TRC0103.TF_    14    02/13/2002  14:10     9590  88CAF449
   TRC0104.TFF   TRC0104.TF_    14    02/13/2002  14:10     5134  61085437
   TRC0105.TFF   TRC0105.TF_    14    02/13/2002  14:10    24543  BE0A6573
   TRC0106.TFF   TRC0106.TF_    14    02/13/2002  14:10     1549  9FDE508F
   TRC0107.TFF   TRC0107.TF_    14    02/13/2002  14:10     4516  9B2B468B
   TRC0108.TFF   TRC0108.TF_    14    02/13/2002  14:11     9505  42F6DE2A
   TRC0109.TFF   TRC0109.TF_    14    02/13/2002  14:10     2535  CF7D05E4
   TRC010A.TFF   TRC010A.TF_     7    02/13/2002  14:11     1130  7BD8C17F
   TRC0118.TFF   TRC0118.TF_    14    10/02/2001  18:20     2526  479E4B05
   TRC0119.TFF   TRC0119.TF_    14    10/02/2001  18:36     3786  6E1DF20C
   TRC012C.TFF   TRC012C.TF_    14    10/16/2001  22:03     5361  4D6B940E
   TRC012D.TFF   TRC012D.TF_    14    10/16/2001  22:03     7870  CDF5F2BD
   TRC012E.TFF   TRC012E.TF_    14    10/23/2001  13:55    32972  8DB6B212
   TRC012F.TFF   TRC012F.TF_    14    10/16/2001  13:28    36249  FCBE6A1C
   TRCUST.EXE    TRCUST.EX_      7    02/14/2002  09:53    98773  B0DC62C5
   UCONV.DLL     UCONV.DL_      13    10/03/2001  06:45    23331  56842F12
   UHPFS.DLL     UHPFS.DL_      12    10/02/2001  18:32   104976  3D7BA582
   UJFS.DLL      UJFS.DL_        6    10/16/2001  13:43   286488  3DEFA214
   UNICODE.SYS   UNICODE.SY_    14    10/03/2001  06:35    20014  0DC8302E
   UNIKBD.DLL    UNIKBD.DL_     13    10/03/2001  06:42    29027  10C8295E
   UNPACK2.EXE   UNPACK2.EX_    12    02/13/2002  16:34    79888  5EAA2DBF
   USBMON.EXE    USBMON.EX_     14    10/02/2001  17:50    19389  BFCB36A6
   USBPRT.HLP    USBPRT.HL_     14    10/02/2001  17:50     6293  E154289C
   USBPRT.PDR    USBPRT.PD_     13    10/02/2001  17:50    41541  523CD7D3
   USER.EXE      USER.EX_        5    10/24/2001  11:19   281120  E0DE702B
   VCU.EXE       VCU.EX_         4    10/16/2001  15:29   131347  C6DE100A
   VCU.MSG       VCU.MS_        14    10/16/2001  13:26     1760  7E73D71E
   VIDEOCFG.DLL  VIDEOCFG.DL_   13    09/10/2001  16:17    37966  FB329EB3
   VMAN.DLL      VMAN.DL_       12    09/10/2001  21:16    49401  E44ED365
   VMANWIN.SYS   VMANWIN.SY_    10    09/10/2001  15:34     3312  5010574E
   VWIN.SYS      VWIN.SY_       14    04/30/2001  16:39    27088  11C7741D
   WELCOME.EXE   WELCOME.EX_    14    10/23/2001  14:06    10240  D791635C
   WINCFG.DLL    WINCFG.DL_     14    10/23/2001  13:56    13423  5F124563
   WINSCLIP.DLL  WINSCLIP.DL_   14    10/24/2001  11:11    14848  063DFDB5
   WINSHELD.EXE  WINSHELD.EX_   14    10/24/2001  11:11    22528  F17A620D
   WINSMSG.DLL   WINSMSG.DL_    14    10/24/2001  11:11    28441  ED55951E
   WPCONFIG.DLL  WPCONFIG.DL_    8    10/02/2001  17:36   268430  E09AD74F

   
                       FixPak Corrective Service levels and disk layouts  29


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   WPDSACTV.EXE  WPDSACTV.EX_   14    10/23/2001  13:27    14093  4D8665F9
   WPDSERV.DLL   WPDSERV.DL_    14    10/23/2001  13:27     5037  53BE2A0C
   WPDSINIT.EXE  WPDSINIT.EX_   13    10/23/2001  13:27    26453  B74D8199
   WPDSRVP.DLL   WPDSRVP.DL_    14    10/23/2001  12:48    16378  702DDB3E
   WPNLS.DLL     WPNLS.DL_      12    10/23/2001  14:06    45546  FD0380B8
   WPPRINT.DLL   WPPRINT.DL_     7    10/23/2001  13:57   366652  40B02624
   WPREXX.IMP    WPREXX.IM_     11    09/06/2000  12:42     6313  5075963F
   XCOPY.EXE     XCOPY.EX_      13    02/14/2002  09:47    52576  7F190D02

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.2
   Product name:  "Warp Server for e-business Base Operating System (UNI)"
   Standard Edition  4.50
   Fixpak name:   XR_E003_   (Country = Generic)
   Pre-requisite CSD Level:  XR_4500_
   System Id:  1000
   Component Id:  5639A6150
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\..\
           ..\..\OS2\dll

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   DOSCALL1.DLL  DOSCALL1.DL_   14    02/13/2002  14:12   137445  44BCBD46
   DOSCALL1.TDF  DOSCALL1.TD_   14    02/13/2002  14:12     5534  08239A1E
   OS2KRNL       OS2KRNL.___    15    02/13/2002  14:10   847335  A281AE9A
   OS2LDR        OS2LDR.___     14    02/13/2002  15:13    44544  3296E7F7

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.3
   Product name:  "Warp Server for e-business Base Operating System (SMP)"
   Standard Edition  4.50
   Fixpak name:   XR_E003_   (Country = Generic)
   Pre-requisite CSD Level:  XR_4500_
   System Id:  1000
   Component Id:  5639A5550
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\..\
           ..\..\OS2\dll

   Files contained in Fixpak for product:

   
                       FixPak Corrective Service levels and disk layouts  30


         February 18, 2002 - Warp Server for e-business FixPak XR_E003


   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   DOSCALL1.DLL  DOSCALL1.DL_   14    02/13/2002  14:21   144387  E2D6BF8B
   DOSCALL1.TDF  DOSCALL1.TD_   14    02/13/2002  14:21     5534  9EF2E693
   OS2KRNL       OS2KRNL.___    16    02/13/2002  14:19   909146  4E47BCF2
   OS2LDR        OS2LDR.___     14    02/13/2002  15:14    42496  92974023

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.4
   Product name:  "Warp Server for e-business Base Operating System (UNI)"
   Standard Edition  4.50
   Fixpak name:   XR_E003_   (Country = Generic)
   Pre-requisite CSD Level:  XR_4500_
   System Id:  1000
   Component Id:  5639A6150
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\*
           ..\..\MMOS2
           ..\..\MMOS2\*
           ..\..\VT
           ..\..\VT\*
           ..\..\TOPOBJ
           ..\..\TOPOBJ\*
           ..\..\PSFONTS
           ..\..\PSFONTS\*
           ..\..\LANGUAGE
           ..\..\LANGUAGE\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   PMDF.EXE      PMDF.EX_       14    02/13/2002  16:38   393804  28EE9948

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.5
   Product name:  "Warp Server for e-business Base Operating System (SMP)"
   Standard Edition  4.50
   Fixpak name:   XR_E003_   (Country = Generic)
   Pre-requisite CSD Level:  XR_4500_
   System Id:  1000
   Component Id:  5639A5550
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

   
                       FixPak Corrective Service levels and disk layouts  31


         February 18, 2002 - Warp Server for e-business FixPak XR_E003


           ..\*
           ..\..\MMOS2
           ..\..\MMOS2\*
           ..\..\VT
           ..\..\VT\*
           ..\..\TOPOBJ
           ..\..\TOPOBJ\*
           ..\..\PSFONTS
           ..\..\PSFONTS\*
           ..\..\LANGUAGE
           ..\..\LANGUAGE\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   PMDF.EXE      PMDF.EX_       15    02/13/2002  16:04   391208  D522D9D8


































   
                       FixPak Corrective Service levels and disk layouts  32


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   12.0 SPACE UTILIZATION

   The FixPak installation process requires free space on the following
   drives:

   Space needed   Drive
   Up to 2MB      C:
   Up to 2MB      Boot drive (4MB if boot is C:)
   Up to 22MB     Drive with most free space, holds deferred files if
                  A:SERVICE method used.
   Up to 32MB     FixPak Archive/Backup for product with CSD level of
                  XR_4500

   Note: The lines labeled "FixPak Archive/Backup for product with CSD level
   of" will be on the drive you specify and will occupy up to the size
   indicated for the Archive and for the Backup directories. If, for
   example, the indicated size is 30MB then the space actually occupied on
   the drive can be up to 60MB.


   12.0.1 RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE

   Warning: Make sure you read and understand the following before removing
   the Archive and Backup files and directories.

   You can recover the space used for FixPak Archive and Backup files as
   long as you understand that doing this prevents you from being able to
   backout to the previous Backup or Archive level. If it becomes necessary
   at a later time to backout a FixPak, the only way you can do this is to
   reinstall Warp.

   Do the following to delete the FixPak Backup and Archive files and remove
   the files used by CSF to keep track of what service has been applied to
   your system.

   1.  Delete every instance of the following files on your system
       (search every drive and every directory they contain).
       þ   LOGF0000.*   (can be OS2 or MPM)
       þ   LOGSTART.*   (can be OS2 or MPM)
       þ   LOGARCH.*    (can be OS2 or MPM)
       þ   CSF_*.*
       þ   FIXSTART
   2.  Delete the files in the FixPak Archive and Backup directories on
       your harddisk.
   3.  Remove the FixPak Archive and Backup directories with the RMDIR
       command.






   
                                                       Space Utilization  33


         February 18, 2002 - Warp Server for e-business FixPak XR_E003

   12.0.2 TRADEMARKS

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

   þ  IBM
   þ  OS/2
   þ  WorkSpace On-Demand

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









































   
                                                       Space Utilization  34
