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















        

        
        



        January 18, 2001

        This FixPak makes the products it services Year 2000 ready
        
        Build level 14.062
        
        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.

        January 18, 2001 - Warp Server for e-business FixPak XR_E002




       January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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.0.1 FixPak Syslevel File  . . . . . . . . . . . . . . . . . . . 22

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


   
                                                                Contents  ii


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

     12.0 Space Utilization   . . . . . . . . . . . . . . . . . . . . . . 31
       12.0.1 Recovering FixPak ARCHIVE and BACKUP space  . . . . . . . . 31
       12.0.2 TRADEMARKS  . . . . . . . . . . . . . . . . . . . . . . . . 32

















































   
                                                               Contents  iii


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   1.0 TERMS AND CONDITIONS

   Important - please read the following terms and conditions.

   Downloading the Service Fixes included in FixPak XR_E002 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_E002 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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   3.0 INSTALLATION NOTES



















































   
                                                       Installation Notes  3


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

            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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002


   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   6.0 POST INSTALLATION NOTES



















































   
                                                 Post Installation Notes  11


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

        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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002


   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
                  "f:\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_E002.?DK A: /F  (? can be 1 through 9, A through Z).

   Label the diskette as

         FixPak XR_E002
   Corrective Service Diskette ?
          (CSF DISK ?)


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

        Examples:

        XR_E002.ADK = 10
        XR_E002.FDK = 15
        XR_E002.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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

       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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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_E002
   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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.

   Additionally, you can use the VER /R command 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.040


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

   Build Level: n.nnn


   That is the number you should see for this FixPak when you issue the VER
   /R command.


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

         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   11.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS

   Build Level: 14.040

   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_E002_   (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_E002_   (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\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

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

   
                       FixPak Corrective Service levels and disk layouts  23


         January 18, 2001 - Warp Server for e-business FixPak XR_E002


      ..\..\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_       11    09/11/2000  09:47     7480  C86B16C8
   ATTRIB.EXE    ATTRIB.EX_     10    11/15/2000  19:33    37789  BE701FB9
   BOOTDISK.EXE  BOOTDISK.EX_   10    11/15/2000  20:02    87019  0A736FFB
   CACHE.EXE     CACHE.EX_      10    10/06/2000  13:51    13870  C758044D
   CACHEJFS.EXE  CACHEJFS.EX_   10    11/15/2000  20:03    44218  15A5BC97
   CCHMAIN.EXE   CCHMAIN.EX_     7    11/14/2000  19:38   199408  310A6E78
   CDFS.TDF      CDFS.TD_       11    10/06/2000  14:05     2113  77B94068
   CHKDSK.COM    CHKDSK.CO_     10    11/15/2000  19:33    70720  F7DCA373
   CHKDSK.SYS    CHKDSK.SY_     11    10/06/2000  13:52      795  3BAC2440
   CHKDSK32.DLL  CHKDSK32.DL_    8    10/06/2000  14:03   139227  DC293DF5
   CHKLGJFS.EXE  CHKLGJFS.EX_    9    11/15/2000  20:03    87495  4788540D
   CLRBBLKS.EXE  CLRBBLKS.EX_   10    11/15/2000  20:03    34982  11C009EE
   CMD.EXE       CMD.EX_         8    11/15/2000  19:34   100108  33896EFE
   COMMAND.COM   COMMAND.CO_    10    11/15/2000  19:34    42763  79B1986E
   CREX.MSG      CREX.MS_       11    09/06/2000  12:42     2865  81976E0E
   CREXUTIL.DLL  CREXUTIL.DL_    9    09/06/2000  12:42    68119  4D4A9A8F
   CREXX.DLL     CREXX2.DL_      7    09/06/2000  12:42   266031  C73C6A5F
   DDINSTAL.EXE  DDINSTAL.EX_   10    11/15/2000  19:52    52263  59B2EA29
   DEFRAGFS.EXE  DEFRAGFS.EX_   10    11/15/2000  20:03    33994  4FD08425
   DF_DEB.EXE    DF_DEB.SM_      9    11/15/2000  17:38   143601  9ADE29D6
   DF_DEB.EXE    DF_DEB.UN_      9    11/15/2000  18:05   135989  52462CDB
   DF_RET.EXE    DF_RET.SM_      8    11/15/2000  17:02   143569  3B7DE7DE
   DF_RET.EXE    DF_RET.UN_      9    11/15/2000  16:51   135957  94D0FBB8
   DOSCALL1.DLL  DOSCALL1.SM_    8    11/15/2000  17:01   144208  550F452F
   DOSCALL1.DLL  DOSCALL1.UN_    8    11/15/2000  16:50   137327  AAF5609D
   DOSCALL1.SYM  DOSC1SYM.SM_   10    11/15/2000  17:01    43828  5F7B2C14
   DOSCALL1.SYM  DOSC1SYM.UN_   10    11/15/2000  16:50    43476  125A8A7C
   DOSCALL1.TDF  DOSCALL1.TD_   11    11/15/2000  16:50     5534  69AE23E1
   DOSKRNL       DOSKRNL.___    10    11/15/2000  16:51    31497  032B625D
   DSPIMRI.DLL   DSPIMRI.DL_    10    09/15/2000  16:24    17446  F1DD005C
   DSPINSTL.EXE  DSPINSTL.EX_    8    10/02/2000  15:46   175640  C6659F76
   E.EXE         E.EX_           5    11/14/2000  18:09    63383  98035DAA
   EAUTIL.EXE    EAUTIL.EX_     10    11/15/2000  19:34    38000  6D2A15D3
   ENGINE.DLL    ENGINE.DL_     10    11/15/2000  19:46    32950  248EB421
   ETKE603.DLL   ETKE603.DL_     4    11/23/1999  16:02   767421  C17E0876
   EXTENDFS.EXE  EXTENDFS.EX_   10    11/15/2000  20:03    29304  2226810D
   FFIPC.DLL     FFIPC.DL_      10    10/06/2000  14:13    27201  F86E2A12
   FIBASE.RSP    FIBASE.RS_     10    11/16/2000  04:57   339320  406BD45E
   GRE2VMAN.DLL  GRE2VMAN.DL_   10    09/15/2000  22:04    18189  2264FBCE
   GSVDAEMN.EXE  GSVDAEMN.EX_   11    07/19/2000  11:27     4848  7336CB27
   GSVINST.EXE   GSVINST.EX_    10    11/14/2000  19:01    34351  F6E060C2

   
                       FixPak Corrective Service levels and disk layouts  24


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   HELPMGR.DLL   HELPMGR.DL_     7    10/19/2000  13:01   250157  0A772A63
   HPFS.IFS      HPFS.IF_        9    10/06/2000  13:49   141378  4A2AC275
   HPFS.TDF      HPFS.TD_       11    10/06/2000  13:49     1620  1E70C4B1
   INSCFG32.DLL  INSCFG32.DL_   10    11/15/2000  19:37    32098  4802A6AB
   INSPGM32.DLL  INSPGM32.DL_   10    11/15/2000  19:38    41504  EBA3842D
   INSTALL.EXE   INSTALL.EX_     5    03/16/2000  08:07   407227  5A6A418C
   JAVA.RSP      JAVA.RS_       11    11/15/2000  19:35    63631  4704D67D
   JFS.IFS       JFS.IF_         3    11/15/2000  19:47   189688  E5600B8E
   JFS.MSG       JFS.MS_        11    11/15/2000  19:47    12619  47649BCB
   JFS.TDF       JFS.TD_        11    11/15/2000  19:47    16574  9FBF8A47
   JFSCHK32.EXE  JFSCHK32.EX_    6    11/15/2000  20:03     6495  F8902DF0
   JFSH.MSG      JFSH.MS_       11    11/15/2000  19:47     9515  62228C49
   KERNEL.SDF    KRNLRSDF.SM_    9    11/15/2000  17:02    59348  AA1C1F00
   KERNEL.SDF    KRNLRSDF.UN_    9    11/15/2000  16:51    59155  CA16482D
   KERNELD.SDF   KRNLDSDF.SM_    9    11/15/2000  17:38    59602  8E3282D3
   KERNELD.SDF   KRNLDSDF.UN_    9    11/15/2000  18:33    59147  E9695DA8
   KEYBOARD.DCP  KEYBOARD.DC_   10    10/12/2000  16:03   315109  346280C8
   KRNLRDEV.TDF  KRNLRDEV.TD_   11    11/15/2000  16:48     4232  9488D8EB
   KRNLRFS.TDF   KRNLRFS.TD_    11    11/15/2000  16:48     4793  AC3930B6
   KRNLRLDR.TDF  KRNLRLDR.TD_   11    11/15/2000  16:48     5384  771F33C5
   KRNLRPG.TDF   KRNLRPG.TD_    11    11/15/2000  16:48     3209  7C236048
   KRNLRSEL.TDF  KRNLRSEL.TD_   11    11/15/2000  16:48     2783  FA4A6D55
   KRNLRSEM.TDF  KRNLRSEM.TD_   11    11/15/2000  16:48     1792  DC4117ED
   KRNLRSM.TDF   KRNLRSM.TD_    11    11/15/2000  16:48     1196  6DE3D9DA
   KRNLRTK.TDF   KRNLRTK.TD_    11    11/15/2000  16:48    12921  75042AED
   KRNLRTOM.TDF  KRNLRTOM.TD_   11    11/15/2000  16:48      984  513C0787
   KRNLRVDM.TDF  KRNLRVDM.TD_   11    11/15/2000  16:48    15405  103A811A
   KRNLRVM.TDF   KRNLRVM.TD_    11    11/15/2000  16:48     5542  FEA60645
   LOGDUMP.EXE   LOGDUMP.EX_     9    11/15/2000  20:03    78786  E181AE1A
   LVM.DLL       LVM.DL_         7    11/15/2000  19:44   163288  F58135F0
   LVM.EXE       LVM.EX_         8    11/15/2000  20:10    92855  80AC9154
   LVM.MSG       LVM.MS_        11    11/15/2000  19:45    18184  CD769189
   LVMALERT.EXE  LVMALERT.EX_   10    11/15/2000  20:00    22784  084A64B5
   LVMGUI.CMD    LVMGUI.CM_     11    09/15/2000  18:54     2988  F02E1CFD
   LVMGUI.ZIP    LVMGUI.ZI_      8    11/15/2000  19:45   456828  FDC863BD
   LVMH.MSG      LVMH.MS_       11    11/15/2000  19:45    21126  8E84979E
   MONCALLS.TDF  MONCALLS.TD_   11    11/15/2000  18:31     1139  45670421
   NAMEREXX.DLL  NAMEREXX.DL_    8    09/06/2000  12:45    97811  93EAB604
   OREXUTIL.DLL  ORXUTIL2.DL_   10    09/06/2000  12:43    41175  DBC71183
   OREXX.DLL     OREXX2.DL_      6    09/06/2000  12:43   490355  38E237F5
   OS2APIC.PSD   OS2APIC.PS_    10    11/15/2000  17:04    31232  14D38B78
   OS2CHAR.TDF   OS2CHAR.TD_    11    11/15/2000  16:50    13889  DC29119B
   OS2DASD.DMD   OS2DASD.DM_    10    11/15/2000  19:43    37421  FA6B0C73
   OS2DUMP       OS2DUMP.___    10    11/15/2000  18:30    15197  13736E51
   OS2KRNL       OS2KRNL.SM_     3    11/15/2000  16:59   907221  D0A7112D
   OS2KRNL       OS2KRNL.UN_     4    11/15/2000  16:48   845257  CC4129A7
   OS2KRNLB.SYM  KRNLBSYM.SM_    8    11/15/2000  17:46   191652  44C46FEE
   OS2KRNLB.SYM  KRNLBSYM.UN_    8    11/15/2000  17:28   184564  644EAE4C
   OS2KRNLD.SYM  KRNLDSYM.SM_    2    11/15/2000  17:37   196980  A7335C4A
   OS2KRNLD.SYM  KRNLDSYM.UN_    8    11/15/2000  17:20   189380  65F4A22F
   OS2KRNLR.SYM  KRNLRSYM.SM_    8    11/15/2000  16:59   171716  3BF4BBC5

   
                       FixPak Corrective Service levels and disk layouts  25


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   OS2KRNLR.SYM  KRNLRSYM.UN_    7    11/15/2000  16:48   167188  EAA15A11
   OS2KRNLR.TDF  OS2KRNLR.TD_   11    11/15/2000  16:48    21026  29A7F79B
   OS2LDR        OS2LDR.SM_     10    11/15/2000  18:06    43008  BFC0DFE8
   OS2LDR        OS2LDR.UN_     10    11/15/2000  18:05    45056  BEEF30A4
   OS2LVM.DMD    OS2LVM.DM_     10    11/15/2000  19:44    31483  6AB9EC66
   OSO001.MSG    OSO001.MS_      9    11/14/2000  15:59   175354  92DF69E1
   OSO001H.MSG   OSO001H.MS_     9    11/14/2000  15:59   240256  14A7FD24
   PICV.DLL      PICV.DL_       10    10/19/2000  12:59    26200  59752153
   PMCTLS.DLL    PMCTLS.DL_      2    10/19/2000  21:02   587798  8932EE09
   PMCTLS.SYM    PMCTLSYM.SM_   10    10/19/2000  21:02    44660  45EA57C8
   PMCTLS.SYM    PMCTLSYM.UN_   10    10/19/2000  21:02    44660  45EA57C8
   PMDDEML.DLL   PMDDEML.DL_    10    10/19/2000  12:43    27814  836C1B42
   PMGPI.DLL     PMGPI.DL_       7    10/19/2000  12:38   248446  E968C795
   PMGPI.TDF     PMGPI.TD_      11    10/19/2000  12:38    12338  20049677
   PMGRE.DLL     PMGRE.DL_      11    10/19/2000  12:35     2231  82699F54
   PMGRE.TDF     PMGRE.TD_      11    10/19/2000  21:04     1062  4913F07F
   PMMERGE.DLL   PMMERGE.DL_     1    10/19/2000  21:04  1268731  EF1C528F
   PMMERGE.SYM   PMMERSYM.SM_    9    10/19/2000  21:04   117508  578E503C
   PMMERGE.SYM   PMMERSYM.UN_    9    10/19/2000  21:04   117508  578E503C
   PMPIC.TDF     PMPIC.TD_      11    10/19/2000  14:34      400  AAA16FEB
   PMREXX.EXE    PMREXX.EX_     10    10/06/2000  14:50    78885  4B1B864E
   PMSHAPI.DLL   PMSHAPI.DL_    11    10/19/2000  12:45     4549  855E9933
   PMSHAPI.TDF   PMSHAPI.TD_    11    10/19/2000  21:04     6726  D9429664
   PMSPL.DLL     PMSPL.DL_       7    11/14/2000  17:58   277251  B522C52E
   PMSPL.SYM     PMSPLSYM.SM_   10    11/14/2000  17:58    32340  F1E52D1B
   PMSPL.SYM     PMSPLSYM.UN_    4    11/14/2000  17:58    32340  F1E52D1B
   PMSPL.TDF     PMSPL.TD_      11    11/14/2000  17:58     4491  7227698E
   PMVDMP.TDF    PMVDMP.TD_     11    10/19/2000  21:13     2661  081AFBA4
   PMVIOP.DLL    PMVIOP.DL_      9    10/19/2000  13:03    64204  753A6BC1
   PMVIOP.SYM    PMVIOSYM.SM_   11    10/19/2000  13:03     7620  E5739940
   PMVIOP.SYM    PMVIOSYM.UN_   11    10/19/2000  13:03     7620  E5739940
   PMVIOP.TDF    PMVIOP.TD_     11    10/19/2000  21:12     3551  26364E8D
   PMWIN.TDF     PMWIN.TD_      11    10/19/2000  21:04     9567  0EC583E5
   PMWINX.DLL    PMWINX.DL_      3    10/19/2000  12:58   530827  BB1645D5
   PMWP.DLL      PMWP.DL_        2    11/15/2000  03:02  1063363  2B19A67B
   PMWP.SYM      PMWPSYM.SM_     9    11/15/2000  03:02   103796  FB6720E3
   PMWP.SYM      PMWPSYM.UN_     9    11/15/2000  03:02   103796  FB6720E3
   PMWP.TDF      PMWP.TD_       11    11/15/2000  03:02    13825  3CBA8CA4
   PMWPMRI.DLL   PMWPMRI.DL_    10    11/14/2000  17:52    54311  470D09D1
   PNP.DLL       PNP.DL_        10    11/14/2000  19:35    28297  9CB637B5
   PNP.SYS       PNP.SY_        11    08/14/2000  18:56     2152  2CA5E7B5
   PRINTPNP.PND  PRINTPNP.PN_   11    06/05/2000  10:55    15227  B1A958D3
   PSFILES.EXE   PSFILES.EX_    11    11/15/2000  15:34    10229  00B5EF64
   PSSEMS.EXE    PSSEMS.EX_     10    11/15/2000  15:34    11717  1073B0FE
   PSTAT.EXE     PSTAT.EX_      10    11/15/2000  15:34    14661  5BED22F0
   QUECALLS.DLL  QUECALLS.DL_   11    11/15/2000  18:31     1024  D0C33B3B
   QUECALLS.TDF  QUECALLS.TD_   11    11/15/2000  16:50     1299  C1002A59
   README.CID    README.CI_     10    11/03/2000  17:33    47293  9E176A17
   REGEDIT2.EXE  REGEDIT2.EX_    5    11/24/1999  13:10   970240  4306FD06
   REGISTRY.TDF  REGISTRY.TD_   11    11/24/1999  13:02      984  E7DBD2D8
   REX.MSG       REX.MS_        11    09/06/2000  12:42     2865  60599657

   
                       FixPak Corrective Service levels and disk layouts  26


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   REXX.DLL      CREXX1.DL_      7    09/06/2000  12:42   266031  42998B8E
   REXX.DLL      OREXX1.DL_      5    09/06/2000  12:43   490355  1A1BDC46
   REXX.IMG      REXX.IM_        6    09/06/2000  12:42   283636  D720F59D
   REXXAPI.DLL   REXXAPI.DL_    10    09/06/2000  12:42    40995  14837324
   REXXC.EXE     REXXC.EX_      11    09/06/2000  12:42     2758  D07F6BDF
   REXXCRT.DLL   REXXCRT.DL_     9    09/06/2000  12:42    79348  C14FF9D8
   REXXUTIL.DLL  REXXUTIL.DL_    9    09/06/2000  12:42    68119  4D4EAA8F
   REXXUTIL.DLL  ORXUTIL1.DL_   10    09/06/2000  12:43    41175  DBC74683
   RINSTPRN.EXE  RINSTPRN.EX_    7    11/14/2000  18:11   205268  2B30ED57
   RIPLINST.EXE  RIPLINST.EX_    9    11/15/2000  20:02   174339  22695DA5
   RSPDDI.EXE    RSPDDI.EX_     10    11/15/2000  19:52    29753  F5264E46
   RSPDSPI.EXE   RSPDSPI.EX_     9    10/02/2000  15:46   143398  921C88D1
   RSPIMRI.DLL   RSPIMRI.DL_    10    08/31/2000  12:46    17455  71B614E5
   RSPINST.EXE   RSPINST.EX_     6    11/15/2000  19:48   476592  10ACC079
   SCENTER.DLL   SCENTER.DL_     6    11/14/2000  18:08   294781  7AACB299
   SEAMLESS.DLL  SEAMLESS.DL_   10    10/19/2000  21:13    49167  F14FF519
   SESDD32.SYS   SESDD32.SY_     8    10/30/2000  11:26   118834  299CA25B
   SESMGR.DLL    SESMGR.DL_     11    11/15/2000  18:31     1536  5134B915
   SESMGR.TDF    SESMGR.TD_     11    11/15/2000  16:50     1877  4D4EE3B3
   SESSHELL.EXE  SESSHELL.EX_   10    10/30/2000  11:25    29805  86F08FB0
   SHELL.SDF     SHELLSDF.SM_   10    11/15/2000  17:02    21279  130E0D39
   SHELL.SDF     SHELLSDF.UN_   10    11/15/2000  17:02    21279  510E0D3A
   SOFTDRAW.DLL  SOFTDRAW.DL_    4    10/19/2000  12:32   416439  5D869C32
   SYSLEVEL.EXE  SYSLEVEL.EX_    1    11/15/2000  19:38    44736  CF31867A
   SYSLEVEL.FPK  SYSLEVEL.FP_   11    08/15/2000  14:21      165  2A150A40
   SYSLEVEL.MSG  SYSLEVEL.MS_   11    09/05/2000  16:49     1445  FA94E61D
   TRACE.EXE     TRACE.EX_      10    11/15/2000  19:39    56064  D4E7EB80
   TRAPDUMP.EXE  TRAPDUMP.EX_   10    10/06/2000  21:17    30236  B993AF97
   TRC0000.TFF   TRC0000.TF_    11    11/15/2000  16:48      189  A6DB25D9
   TRC0003.TFF   TRC0003.TF_    11    11/15/2000  16:48     1503  E925868E
   TRC0004.TFF   TRC0004.TF_    11    11/15/2000  16:48     4754  134B826C
   TRC0005.TFF   TRC0005.TF_    10    11/15/2000  16:48    49321  5AA3152F
   TRC0006.TFF   TRC0006.TF_    11    11/15/2000  16:48    12356  7E3E674E
   TRC0007.TFF   TRC0007.TF_    11    11/15/2000  19:58     3336  602024C7
   TRC0008.TFF   TRC0008.TF_    11    08/14/2000  18:04      544  468186D2
   TRC0010.TFF   TRC0010.TF_    11    11/15/2000  16:50    13647  C63AF3FD
   TRC0012.TFF   TRC0012.TF_    11    11/15/2000  18:31     1247  4B138CBD
   TRC0016.TFF   TRC0016.TF_    11    11/15/2000  16:50     1673  8106FCA4
   TRC0017.TFF   TRC0017.TF_    11    11/15/2000  16:50     5561  FAB3BD67
   TRC0018.TFF   TRC0018.TF_    11    11/15/2000  16:50    39488  8AE61365
   TRC00C0.TFF   TRC00C0.TF_    11    10/19/2000  21:04    15970  17A1FC66
   TRC00C2.TFF   TRC00C2.TF_    11    10/19/2000  21:04    25994  0A380A08
   TRC00C3.TFF   TRC00C3.TF_    11    10/19/2000  21:04     3984  BDEF4ABD
   TRC00C4.TFF   TRC00C4.TF_    11    10/19/2000  14:34      288  62269BA4
   TRC00C5.TFF   TRC00C5.TF_    11    10/19/2000  12:38    32994  8706B258
   TRC00C6.TFF   TRC00C6.TF_    11    11/14/2000  17:58     7146  F49C8A25
   TRC0100.TFF   TRC0100.TF_    11    11/15/2000  16:48     7219  8B080628
   TRC0101.TFF   TRC0101.TF_     3    11/15/2000  16:48     7968  B3E478EE
   TRC0102.TFF   TRC0102.TF_    10    11/15/2000  16:48    29256  F5C1768C
   TRC0103.TFF   TRC0103.TF_    11    11/15/2000  16:48     9590  88C45D49
   TRC0104.TFF   TRC0104.TF_    11    11/15/2000  16:48     5134  61084DA0

   
                       FixPak Corrective Service levels and disk layouts  27


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   TRC0105.TFF   TRC0105.TF_    11    11/15/2000  16:48    24421  6DB91FDB
   TRC0106.TFF   TRC0106.TF_    11    11/15/2000  16:48     1549  6B26508F
   TRC0107.TFF   TRC0107.TF_    11    11/15/2000  16:48     4516  1B2B4340
   TRC0108.TFF   TRC0108.TF_    11    11/15/2000  16:48     9505  62F6DB57
   TRC0109.TFF   TRC0109.TF_    11    11/15/2000  16:48     2535  CF7CEB88
   TRC010A.TFF   TRC010A.TF_    10    11/15/2000  16:48     1130  0D48C17E
   TRC0118.TFF   TRC0118.TF_    11    10/06/2000  13:51     2526  46D1EF05
   TRC0119.TFF   TRC0119.TF_    11    10/06/2000  14:07     3786  6E212C4C
   TRC012C.TFF   TRC012C.TF_    11    10/19/2000  21:13     5361  716B9475
   TRC012D.TFF   TRC012D.TF_     5    10/19/2000  21:12     7870  35F5F2E5
   TRC012E.TFF   TRC012E.TF_    11    11/15/2000  03:02    32972  8DAC8DF2
   TRC012F.TFF   TRC012F.TF_    10    11/15/2000  19:47    36373  2CC27E39
   TRCUST.EXE    TRCUST.EX_     10    11/15/2000  15:41    98773  19080961
   UHPFS.DLL     UHPFS.DL_       9    10/06/2000  14:03   104976  A095AC30
   UJFS.DLL      UJFS.DL_        6    11/15/2000  20:03   277297  5D32BFD1
   UNPACK2.EXE   UNPACK2.EX_    10    11/15/2000  20:05    79888  766A2DC9
   USBMON.EXE    USBMON.EX_     10    11/14/2000  18:12    20105  137C2635
   USBPRT.HLP    USBPRT.HL_     11    11/14/2000  18:12     6293  E1545189
   USBPRT.PDR    USBPRT.PD_      3    11/14/2000  18:12    41351  304F27B8
   USER.EXE      USER.EX_        1    12/02/1999  16:42   281088  4540367A
   VCU.EXE       VCU.EX_         8    11/15/2000  22:01   130672  DCCA4791
   VCU.MSG       VCU.MS_         2    11/15/2000  19:45     1760  5E73E3F4
   VMAN.DLL      VMAN.DL_       10    09/15/2000  22:04    46745  BD23BA5A
   VMANWIN.SYS   VMANWIN.SY_     4    07/10/2000  14:07     3040  A2F3E298
   VWIN.SYS      VWIN.SY_       10    11/23/1999  09:21    27104  94AE6FC6
   WINSCLIP.DLL  WINSCLIP.DL_   10    12/02/1999  16:27    14848  263E039A
   WINSHELD.EXE  WINSHELD.EX_   10    12/02/1999  16:27    22528  F180472D
   WINSMSG.DLL   WINSMSG.DL_     9    12/02/1999  16:27    28441  ED6D299E
   WPPRINT.DLL   WPPRINT.DL_     6    11/14/2000  19:32   364102  31DB91B3
   WPREXX.IMP    WPREXX.IM_      7    09/06/2000  12:42     6313  50EA163F
   XCOPY.EXE     XCOPY.EX_      10    11/15/2000  19:36    52576  1B190D49

   ************************************************************************
   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_E002_   (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

   
                       FixPak Corrective Service levels and disk layouts  28


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   ------------  ------------  -----  ----------  -----  -------  --------
   DOSCALL1.DLL  DCALLUNI.___   11    11/15/2000  16:50   137327  AADBA09D
   OS2KRNL       KRNLUNI.___    11    11/15/2000  16:48   845257  CC4129A7
   OS2LDR        LDRUNI.___     11    11/15/2000  18:05    45056  FEEF30D2
   SESDD32.SYS   SESDD32.SY_    11    10/30/2000  11:26   118834  299CA25B

   ************************************************************************
   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_E002_   (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:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   DOSCALL1.DLL  DCALLSMP.___   11    11/15/2000  17:01   144208  54BA452F
   OS2KRNL       KRNLSMP.___    12    11/15/2000  16:59   907221  D0A7112D
   OS2LDR        LDRSMP.___     11    11/15/2000  18:06    43008  BFC0DFE8
   SESDD32.SYS   SESDD32.SY_    11    10/30/2000  11:30   118834  6BC20921

   ************************************************************************
   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_E002_   (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\*

   
                       FixPak Corrective Service levels and disk layouts  29


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

           ..\..\PSFONTS
           ..\..\PSFONTS\*
           ..\..\LANGUAGE
           ..\..\LANGUAGE\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   PMDF.EXE      PMDF.EX_       12    10/06/2000  21:16   393388  F010947D

   ************************************************************************
   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_E002_   (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\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   PMDF.EXE      PMDF.EX_       12    10/06/2000  14:17   390792  1B295A69











   
                       FixPak Corrective Service levels and disk layouts  30


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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 25MB     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  31


         January 18, 2001 - Warp Server for e-business FixPak XR_E002

   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  32
