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















        

        
        



        June 18, 2001

        This FixPak makes the products it services Year 2000 ready
        
        Build level 14.062
        
        This FixPak applies to:
        
        CSD Level:    XRF4500    Warp Server for e-business (UNI)
        Component ID: 5639A6150
        Version:      4.50
        Type:         0S
        
        CSD Level:    XRF4500    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.

        June 18, 2001 - Warp Server for e-business FixPak XRFE002




        June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

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

















































   
                                                               Contents  iii


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   1.0 TERMS AND CONDITIONS

   Important - please read the following terms and conditions.

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

           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   3.0 INSTALLATION NOTES



















































   
                                                       Installation Notes  3


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

            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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002


   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   6.0 POST INSTALLATION NOTES



















































   
                                                 Post Installation Notes  11


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

        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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002


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

   Label the diskette as

         FixPak XRFE002
   Corrective Service Diskette ?
          (CSF DISK ?)


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

        Examples:

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

           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

       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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

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

           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   11.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS

   Build Level: 14.062

   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:   XRFE002_   (Country = France)
   Pre-requisite CSD Level:  XRF4500_
   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:   XRFE002_   (Country = France)
   Pre-requisite CSD Level:  XRF4500_
   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002


      ..\..\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  16:11     7480  C86477C8
   ATTRIB.EXE    ATTRIB.EX_     10    11/15/2000  23:35    37789  C652FFB9
   BOOTDISK.EXE  BOOTDISK.EX_   10    11/16/2000  02:05    87531  417BBDCD
   CACHE.EXE     CACHE.EX_      10    10/06/2000  18:37    13870  3A020674
   CACHEJFS.EXE  CACHEJFS.EX_   10    11/15/2000  20:03    44218  15A5B71F
   CCHMAIN.EXE   CCHMAIN.EX_     7    11/14/2000  19:38   199408  8D0A6E74
   CDFS.TDF      CDFS.TD_       11    10/06/2000  18:51     2113  785C2068
   CHKDSK.COM    CHKDSK.CO_     10    11/15/2000  23:35    71232  49927664
   CHKDSK.SYS    CHKDSK.SY_     11    10/06/2000  18:38      795  3BAD389C
   CHKDSK32.DLL  CHKDSK32.DL_    8    10/06/2000  18:49   139739  418F3B59
   CHKLGJFS.EXE  CHKLGJFS.EX_    9    11/15/2000  20:03    87495  4788470D
   CLRBBLKS.EXE  CLRBBLKS.EX_   10    11/15/2000  20:03    34982  49C009E8
   CMD.EXE       CMD.EX_         8    11/15/2000  23:37   100108  CDB33A71
   COMMAND.COM   COMMAND.CO_    10    11/15/2000  23:36    43486  C0A8B44D
   CREX.MSG      CREX.MS_       11    09/06/2000  12:42     2865  8188DE0E
   CREXUTIL.DLL  CREXUTIL.DL_    9    09/06/2000  12:42    68119  4D4A96EB
   CREXX.DLL     CREXX2.DL_      7    09/06/2000  12:42   266031  C716AA5F
   DDINSTAL.EXE  DDINSTAL.EX_   10    11/16/2000  01:54    52775  9761DF54
   DEFRAGFS.EXE  DEFRAGFS.EX_   10    11/15/2000  20:03    33994  4FCD4425
   DF_DEB.EXE    DF_DEB.SM_      8    11/15/2000  17:38   143601  9ADC57D6
   DF_DEB.EXE    DF_DEB.UN_      9    11/15/2000  18:05   135989  D2462C66
   DF_RET.EXE    DF_RET.SM_      8    11/15/2000  17:02   143569  2CEDE7DE
   DF_RET.EXE    DF_RET.UN_      9    11/15/2000  16:51   135957  94CF29B8
   DOSCALL1.DLL  DOSCALL1.SM_    6    11/15/2000  18:14   144232  E7B151E0
   DOSCALL1.DLL  DOSCALL1.UN_    8    11/15/2000  18:13   137351  6AAC08F2
   DOSCALL1.SYM  DOSC1SYM.SM_   10    11/15/2000  18:14    43828  5F80AD84
   DOSCALL1.SYM  DOSC1SYM.UN_   10    11/15/2000  18:13    43476  125AC493
   DOSCALL1.TDF  DOSCALL1.TD_   11    11/15/2000  17:01     5534  31B3A11E
   DOSKRNL       DOSKRNL.___    10    11/15/2000  18:14    31529  27D8932B
   DSPIMRI.DLL   DSPIMRI.DL_    10    08/31/2000  13:22    18470  7242032B
   DSPINSTL.EXE  DSPINSTL.EX_    8    10/02/2000  15:46   175640  C6659EB6
   E.EXE         E.EX_           9    11/15/2000  00:29    63383  FCCD0A1A
   EAUTIL.EXE    EAUTIL.EX_     10    11/15/2000  23:38    38000  810645D6
   ENGINE.DLL    ENGINE.DL_     10    11/15/2000  21:01    32950  248E9139
   ETKE603.DLL   ETKE603.DL_     4    11/23/1999  16:02   767421  C176C076
   EXTENDFS.EXE  EXTENDFS.EX_   10    11/15/2000  20:03    29304  2225B10D
   FFIPC.DLL     FFIPC.DL_      10    10/06/2000  14:13    27201  F86DB592
   FIBASE.RSP    FIBASE.RS_     10    11/16/2000  10:52   339448  D94B8D87
   GRE2VMAN.DLL  GRE2VMAN.DL_   10    09/15/2000  22:04    18189  1B1CFBCE
   GSVDAEMN.EXE  GSVDAEMN.EX_   11    07/20/2000  02:35     4880  636E833A
   GSVINST.EXE   GSVINST.EX_    10    11/14/2000  19:01    34351  76E0604E

   
                       FixPak Corrective Service levels and disk layouts  24


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   HELPMGR.DLL   HELPMGR.DL_     7    10/19/2000  13:01   250157  0A772627
   HPFS.IFS      HPFS.IF_        9    10/06/2000  18:35   141890  D57F4803
   HPFS.TDF      HPFS.TD_       11    10/06/2000  18:35     1620  FE70CD53
   INSCFG32.DLL  INSCFG32.DL_   10    11/16/2000  01:37    32098  437C5EAB
   INSPGM32.DLL  INSPGM32.DL_   10    11/16/2000  01:37    41504  872383DD
   INSTALL.EXE   INSTALL.EX_     4    03/16/2000  11:22   658347  D0313509
   JAVA.RSP      JAVA.RS_       11    11/15/2000  19:35    63631  1704D6AC
   JFS.IFS       JFS.IF_         3    11/15/2000  19:47   189688  37600B8D
   JFS.MSG       JFS.MS_        11    11/15/2000  21:03    15703  6105368A
   JFS.TDF       JFS.TD_        11    11/15/2000  19:47    16574  5FBF8A0D
   JFSCHK32.EXE  JFSCHK32.EX_   11    11/15/2000  20:03     6495  D8902DD3
   JFSH.MSG      JFSH.MS_       11    11/15/2000  21:03    10011  65AF5E4B
   KERNEL.SDF    KRNLRSDF.SM_    9    11/15/2000  17:02    59348  621C1EF9
   KERNEL.SDF    KRNLRSDF.UN_    9    11/15/2000  16:51    59155  C9F9282D
   KERNELD.SDF   KRNLDSDF.SM_    9    11/15/2000  17:38    59602  8D4982D3
   KERNELD.SDF   KRNLDSDF.UN_    9    11/15/2000  18:33    59147  E9694F18
   KEYBOARD.DCP  KEYBOARD.DC_   10    10/12/2000  16:03   315109  331280C8
   KRNLRDEV.TDF  KRNLRDEV.TD_   11    11/15/2000  16:48     4232  85F8D8EB
   KRNLRFS.TDF   KRNLRFS.TD_    11    11/15/2000  16:48     4793  AC392226
   KRNLRLDR.TDF  KRNLRLDR.TD_   11    11/15/2000  16:48     5384  771F3021
   KRNLRPG.TDF   KRNLRPG.TD_    11    11/15/2000  16:48     3209  7C235900
   KRNLRSEL.TDF  KRNLRSEL.TD_   11    11/15/2000  16:48     2783  FA49F8D5
   KRNLRSEM.TDF  KRNLRSEM.TD_   11    11/15/2000  16:48     1792  9C4117B3
   KRNLRSM.TDF   KRNLRSM.TD_    11    11/15/2000  16:48     1196  2DE3D9A0
   KRNLRTK.TDF   KRNLRTK.TD_    11    11/15/2000  16:48    12921  7504291B
   KRNLRTOM.TDF  KRNLRTOM.TD_   11    11/15/2000  16:48      984  512D7787
   KRNLRVDM.TDF  KRNLRVDM.TD_   11    11/15/2000  16:48    15405  0C96811A
   KRNLRVM.TDF   KRNLRVM.TD_    11    11/15/2000  16:48     5542  FEA5CC05
   LOGDUMP.EXE   LOGDUMP.EX_     9    11/15/2000  20:03    78786  E181941A
   LVM.DLL       LVM.DL_         7    11/15/2000  21:00   163426  A843C92E
   LVM.EXE       LVM.EX_         7    11/15/2000  20:10    92855  00AC90E0
   LVM.MSG       LVM.MS_        11    11/15/2000  21:01    20272  38BE15F0
   LVMALERT.EXE  LVMALERT.EX_   10    11/15/2000  20:00    22784  0846C0B5
   LVMGUI.CMD    LVMGUI.CM_     11    09/15/2000  18:54     2988  F02C4AFD
   LVMGUI.ZIP    LVMGUI.ZI_      8    11/15/2000  21:01   463876  FD52D91D
   LVMH.MSG      LVMH.MS_       11    11/15/2000  21:01    21111  D3EF096D
   MONCALLS.TDF  MONCALLS.TD_   11    11/15/2000  18:31     1139  A167041D
   NAMEREXX.DLL  NAMEREXX.DL_    8    10/06/2000  15:03    97779  383CD873
   OREXUTIL.DLL  ORXUTIL2.DL_   10    09/06/2000  12:43    41175  9BC71149
   OREXX.DLL     OREXX2.DL_      6    09/06/2000  12:43   490355  38E21AD5
   OS2APIC.PSD   OS2APIC.PS_    10    11/15/2000  17:04    31232  14C4FB78
   OS2CHAR.TDF   OS2CHAR.TD_    11    11/15/2000  16:50    13889  D4E1119B
   OS2DASD.DMD   OS2DASD.DM_    10    11/15/2000  19:43    37421  F9AB0C73
   OS2DUMP       OS2DUMP.___    10    11/15/2000  18:30    15197  13736DFD
   OS2KRNL       OS2KRNL.SM_     3    11/15/2000  16:59   907221  FEA7112B
   OS2KRNL       OS2KRNL.UN_     4    11/15/2000  16:48   845257  CC06E9A7
   OS2KRNLB.SYM  KRNLBSYM.SM_    8    11/15/2000  17:46   191652  44FC4FEE
   OS2KRNLB.SYM  KRNLBSYM.UN_    8    11/15/2000  17:28   184564  644EADA2
   OS2KRNLD.SYM  KRNLDSYM.SM_    2    11/15/2000  17:37   196980  03335C47
   OS2KRNLD.SYM  KRNLDSYM.UN_    8    11/15/2000  17:20   189380  65F49AE7
   OS2KRNLR.SYM  KRNLRSYM.SM_    8    11/15/2000  16:59   171716  3BF3D2C5

   
                       FixPak Corrective Service levels and disk layouts  25


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   OS2KRNLR.SYM  KRNLRSYM.UN_    8    11/15/2000  16:48   167188  CD815A11
   OS2KRNLR.TDF  OS2KRNLR.TD_   11    11/15/2000  16:48    21026  99A7F78C
   OS2LDR        OS2LDR.SM_      1    11/15/2000  18:06    43008  BFC07068
   OS2LDR        OS2LDR.UN_     10    11/15/2000  18:05    45056  3EEF30C2
   OS2LVM.DMD    OS2LVM.DM_     10    11/15/2000  19:44    31483  6AB8EC66
   OSO001.MSG    OSO001.MS_      9    11/14/2000  16:14   188980  A7D284B4
   OSO001H.MSG   OSO001H.MS_     9    11/14/2000  16:14   265968  B1B90F57
   PICV.DLL      PICV.DL_       10    10/19/2000  12:59    26200  59732B53
   PMCTLS.DLL    PMCTLS.DL_      2    10/19/2000  21:02   587798  89320509
   PMCTLS.SYM    PMCTLSYM.SM_   10    10/19/2000  21:02    44660  25EA57AB
   PMCTLS.SYM    PMCTLSYM.UN_   10    10/19/2000  21:02    44660  25EA57AB
   PMDDEML.DLL   PMDDEML.DL_    10    10/19/2000  12:43    27814  81BE1B42
   PMGPI.DLL     PMGPI.DL_       7    10/19/2000  12:38   248446  AF28C795
   PMGPI.TDF     PMGPI.TD_      11    10/19/2000  12:38    12338  18BC9677
   PMGRE.DLL     PMGRE.DL_      11    10/19/2000  12:35     2231  815A9F54
   PMGRE.TDF     PMGRE.TD_      11    10/19/2000  21:04     1062  6013F07E
   PMMERGE.DLL   PMMERGE.DL_     1    10/19/2000  21:04  1268731  E7D4528F
   PMMERGE.SYM   PMMERSYM.SM_    9    10/19/2000  21:04   117508  5754103C
   PMMERGE.SYM   PMMERSYM.UN_    9    10/19/2000  21:04   117508  5754103C
   PMPIC.TDF     PMPIC.TD_      11    10/19/2000  14:34      400  AAA168A3
   PMREXX.EXE    PMREXX.EX_     10    10/06/2000  15:04    78885  E82EA50E
   PMSHAPI.DLL   PMSHAPI.DL_    11    10/19/2000  12:45     4549  84759933
   PMSHAPI.TDF   PMSHAPI.TD_    11    10/19/2000  21:04     6726  D94221E4
   PMSPL.DLL     PMSPL.DL_       7    11/15/2000  00:21   319185  37831FD6
   PMSPL.SYM     PMSPLSYM.SM_   10    11/15/2000  00:21    32340  F1E23ED3
   PMSPL.SYM     PMSPLSYM.UN_   10    11/15/2000  00:21    32340  F1E23ED3
   PMSPL.TDF     PMSPL.TD_      11    11/14/2000  17:58     4491  6397698E
   PMVDMP.TDF    PMVDMP.TD_     11    10/19/2000  21:13     2661  081AC164
   PMVIOP.DLL    PMVIOP.DL_      9    10/19/2000  18:55    64460  CE9C13C1
   PMVIOP.SYM    PMVIOSYM.SM_   11    10/19/2000  18:55     7620  8853994E
   PMVIOP.SYM    PMVIOSYM.UN_   11    10/19/2000  18:55     7620  8853994E
   PMVIOP.TDF    PMVIOP.TD_     11    10/19/2000  21:12     3551  2636316D
   PMWIN.TDF     PMWIN.TD_      11    10/19/2000  21:04     9567  0EC566C5
   PMWINX.DLL    PMWINX.DL_      3    10/19/2000  18:53   530855  1376247A
   PMWP.DLL      PMWP.DL_        2    11/15/2000  03:02  1063363  F0D9A67A
   PMWP.SYM      PMWPSYM.SM_     9    11/15/2000  03:02   103796  576720E0
   PMWP.SYM      PMWPSYM.UN_     9    11/15/2000  03:02   103796  576720E0
   PMWP.TDF      PMWP.TD_       11    11/15/2000  03:02    13825  3CBA6F84
   PMWPMRI.DLL   PMWPMRI.DL_    10    11/15/2000  00:18    58407  14447E75
   PNP.DLL       PNP.DL_        10    11/14/2000  19:35    28297  9CB5FD75
   PNP.SYS       PNP.SY_        11    08/15/2000  08:49     2152  ACA5C6D5
   PRINTPNP.PND  PRINTPNP.PN_   11    06/05/2000  10:55    15227  B1A8F8D3
   PSFILES.EXE   PSFILES.EX_    11    11/15/2000  23:40    10229  D7EADC8D
   PSSEMS.EXE    PSSEMS.EX_     10    11/15/2000  23:40    11717  AD34F58D
   PSTAT.EXE     PSTAT.EX_      10    11/15/2000  23:40    14661  CC51F411
   QUECALLS.DLL  QUECALLS.DL_   11    11/15/2000  18:31     1024  D0C33A19
   QUECALLS.TDF  QUECALLS.TD_   11    11/15/2000  16:50     1299  C1001BC9
   README.CID    README.CI_     10    11/16/2000  01:36    53924  492D740D
   REGEDIT2.EXE  REGEDIT2.EX_    5    11/24/1999  13:45   970752  42E9A152
   REGISTRY.TDF  REGISTRY.TD_   11    11/24/1999  13:02      984  E7DBD106
   REX.MSG       REX.MS_        11    09/06/2000  12:42     2865  603C7657

   
                       FixPak Corrective Service levels and disk layouts  26


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   REXX.DLL      CREXX1.DL_      7    09/06/2000  12:42   266031  42998B8E
   REXX.DLL      OREXX1.DL_      5    09/06/2000  12:43   490355  1A1BA206
   REXX.IMG      REXX.IM_        9    09/06/2000  12:42   283636  D71F239D
   REXXAPI.DLL   REXXAPI.DL_    10    09/06/2000  12:42    40995  14493324
   REXXC.EXE     REXXC.EX_      11    09/06/2000  12:42     2758  D07F5D4F
   REXXCRT.DLL   REXXCRT.DL_     8    09/06/2000  12:42    79348  C14E27D8
   REXXUTIL.DLL  REXXUTIL.DL_    5    09/06/2000  12:42    68119  4D4EA6EB
   REXXUTIL.DLL  ORXUTIL1.DL_   10    09/06/2000  12:43    41175  9BC74649
   RINSTPRN.EXE  RINSTPRN.EX_    7    11/15/2000  00:30   210996  A5FC4C0F
   RIPLINST.EXE  RIPLINST.EX_    9    11/16/2000  02:04   174659  0A66A694
   RSPDDI.EXE    RSPDDI.EX_     10    11/16/2000  01:54    29753  2C264DD6
   RSPDSPI.EXE   RSPDSPI.EX_     9    10/02/2000  15:46   143398  921C6BB1
   RSPIMRI.DLL   RSPIMRI.DL_    10    08/31/2000  13:22    18479  59384235
   RSPINST.EXE   RSPINST.EX_     6    11/16/2000  01:49   478672  35F9ECC1
   SCENTER.DLL   SCENTER.DL_     6    11/15/2000  00:28   295287  F386C6CD
   SEAMLESS.DLL  SEAMLESS.DL_   10    10/19/2000  21:13    49167  F3EDF519
   SESDD32.SYS   SESDD32.SY_     9    10/30/2000  11:26   118834  299CA273
   SESMGR.DLL    SESMGR.DL_     11    11/15/2000  18:31     1536  6534B911
   SESMGR.TDF    SESMGR.TD_     11    11/15/2000  16:50     1877  4D4EC693
   SESSHELL.EXE  SESSHELL.EX_   10    10/30/2000  11:25    29805  86BACFB0
   SHELL.SDF     SHELLSDF.SM_   10    11/15/2000  17:02    21279  130E0D39
   SHELL.SDF     SHELLSDF.UN_   10    11/15/2000  17:02    21279  680E0D39
   SOFTDRAW.DLL  SOFTDRAW.DL_    6    10/19/2000  12:32   416439  5D865DF2
   SYSLEVEL.EXE  SYSLEVEL.EX_   10    11/16/2000  01:38    44800  57B72E15
   SYSLEVEL.FPK  SYSLEVEL.FP_   11    06/13/2001  09:55      165  C4950A3C
   SYSLEVEL.MSG  SYSLEVEL.MS_   11    11/16/2000  01:37     1697  5AF961CF
   TRACE.EXE     TRACE.EX_      10    11/15/2000  23:47    56064  D4F81780
   TRAPDUMP.EXE  TRAPDUMP.EX_   10    10/06/2000  21:17    30236  B9939AA7
   TRC0000.TFF   TRC0000.TF_    11    11/15/2000  16:48      189  4ADB25DA
   TRC0003.TFF   TRC0003.TF_    11    11/15/2000  16:48     1503  E1DD868E
   TRC0004.TFF   TRC0004.TF_    11    11/15/2000  16:48     4754  1262826C
   TRC0005.TFF   TRC0005.TF_    10    11/15/2000  16:48    49321  2063152F
   TRC0006.TFF   TRC0006.TF_    11    11/15/2000  16:48    12356  7D55674E
   TRC0007.TFF   TRC0007.TF_    11    11/15/2000  19:58     3336  601FB047
   TRC0008.TFF   TRC0008.TF_     9    08/15/2000  07:55      544  456B3ED2
   TRC0010.TFF   TRC0010.TF_     4    11/15/2000  16:50    13647  C63AD6DD
   TRC0012.TFF   TRC0012.TF_     8    11/15/2000  18:31     1247  4B138575
   TRC0016.TFF   TRC0016.TF_    11    11/15/2000  16:50     1673  8106FBAA
   TRC0017.TFF   TRC0017.TF_    11    11/15/2000  16:50     5561  28B3BD66
   TRC0018.TFF   TRC0018.TF_    11    11/15/2000  16:50    39488  6DC61365
   TRC00C0.TFF   TRC00C0.TF_    10    10/19/2000  21:04    15970  172D7C66
   TRC00C2.TFF   TRC00C2.TF_    10    10/19/2000  21:04    25994  38380A06
   TRC00C3.TFF   TRC00C3.TF_    11    10/19/2000  21:04     3984  496F4ABD
   TRC00C4.TFF   TRC00C4.TF_     6    10/19/2000  14:34      288  6225B2A4
   TRC00C5.TFF   TRC00C5.TF_    11    10/19/2000  12:38    32994  87067818
   TRC00C6.TFF   TRC00C6.TF_    11    11/14/2000  17:58     7146  F49C8681
   TRC0100.TFF   TRC0100.TF_    11    11/15/2000  16:48     7219  FB080619
   TRC0101.TFF   TRC0101.TF_     3    11/15/2000  16:48     7968  B3E38FEE
   TRC0102.TFF   TRC0102.TF_    10    11/15/2000  16:48    29256  51C17689
   TRC0103.TFF   TRC0103.TF_    11    11/15/2000  16:48     9590  88C37449
   TRC0104.TFF   TRC0104.TF_    11    11/15/2000  16:48     5134  61084CB7

   
                       FixPak Corrective Service levels and disk layouts  27


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   TRC0105.TFF   TRC0105.TF_    11    11/15/2000  16:48    24421  66711FDB
   TRC0106.TFF   TRC0106.TF_    11    11/15/2000  16:48     1549  63DE508F
   TRC0107.TFF   TRC0107.TF_    11    11/15/2000  16:48     4516  9B2B42CB
   TRC0108.TFF   TRC0108.TF_    11    11/15/2000  16:48     9505  42F6DB3A
   TRC0109.TFF   TRC0109.TF_    11    11/15/2000  16:48     2535  CF7CE7E4
   TRC010A.TFF   TRC010A.TF_     5    11/15/2000  16:48     1130  03D8C17E
   TRC0118.TFF   TRC0118.TF_     7    10/06/2000  18:37     2526  47E64B05
   TRC0119.TFF   TRC0119.TF_     2    10/06/2000  18:53     3786  6E22720C
   TRC012C.TFF   TRC012C.TF_    11    10/19/2000  21:13     5361  CD6B9471
   TRC012D.TFF   TRC012D.TF_    11    10/19/2000  21:12     7870  F9F5F2DF
   TRC012E.TFF   TRC012E.TF_    11    11/15/2000  03:02    32972  8DAC7F62
   TRC012F.TFF   TRC012F.TF_    10    11/15/2000  19:47    36373  2CC243F9
   TRCUST.EXE    TRCUST.EX_     10    11/15/2000  23:48    98773  D4109979
   UHPFS.DLL     UHPFS.DL_       9    10/06/2000  18:49   106512  ECC83C27
   UJFS.DLL      UJFS.DL_        6    11/15/2000  20:03   277297  5D328591
   UNPACK2.EXE   UNPACK2.EX_    10    11/16/2000  02:08    79840  CCF5ACF1
   USBMON.EXE    USBMON.EX_     10    11/15/2000  00:31    20105  E417A634
   USBPRT.HLP    USBPRT.HL_     11    11/15/2000  00:31     7274  B27007F9
   USBPRT.PDR    USBPRT.PD_      3    11/15/2000  00:31    41639  99F7C232
   USER.EXE      USER.EX_        1    01/06/2000  05:31   281424  9C2BD73A
   VCU.EXE       VCU.EX_         8    11/15/2000  22:01   130672  DCC8A791
   VCU.MSG       VCU.MS_         1    11/15/2000  21:01     1907  6070E28B
   VMAN.DLL      VMAN.DL_        9    09/15/2000  22:04    46745  AD73BA5A
   VMANWIN.SYS   VMANWIN.SY_    11    07/10/2000  14:07     3040  C2F3E282
   VWIN.SYS      VWIN.SY_       10    11/23/1999  11:50    27104  94AAD2A6
   WINSCLIP.DLL  WINSCLIP.DL_   10    01/06/2000  05:12    14848  063DF8D5
   WINSHELD.EXE  WINSHELD.EX_   10    01/06/2000  05:12    22528  8A7D4C30
   WINSMSG.DLL   WINSMSG.DL_     6    01/06/2000  05:11    28441  ED3A151E
   WPPRINT.DLL   WPPRINT.DL_     5    11/14/2000  19:32   364102  11DB9196
   WPREXX.IMP    WPREXX.IM_     11    09/06/2000  12:42     6313  5075963F
   XCOPY.EXE     XCOPY.EX_      10    11/15/2000  23:41    52400  35E8F320

   ************************************************************************
   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:   XRFE002_   (Country = France)
   Pre-requisite CSD Level:  XRF4500_
   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   ------------  ------------  -----  ----------  -----  -------  --------
   DOSCALL1.DLL  DCALLUNI.___   11    11/15/2000  18:13   137351  6AAC079E
   OS2KRNL       KRNLUNI.___    11    11/15/2000  16:48   845257  CC06E9A7
   OS2LDR        LDRUNI.___     11    11/15/2000  18:05    45056  BEEF30A4
   SESDD32.SYS   SESDD32.SY_    11    10/30/2000  11:26   118834  299C9B13

   ************************************************************************
   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:   XRFE002_   (Country = France)
   Pre-requisite CSD Level:  XRF4500_
   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  18:14   144232  93B151DF
   OS2KRNL       KRNLSMP.___    12    11/15/2000  16:59   907221  FEA7112B
   OS2LDR        LDRSMP.___     11    11/15/2000  18:06    43008  BFC07068
   SESDD32.SYS   SESDD32.SY_    11    10/30/2000  11:30   118834  DBC20912

   ************************************************************************
   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:   XRFE002_   (Country = France)
   Pre-requisite CSD Level:  XRF4500_
   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

           ..\..\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  B5D0947D

   ************************************************************************
   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:   XRFE002_   (Country = France)
   Pre-requisite CSD Level:  XRF4500_
   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  8B295A5A











   
                       FixPak Corrective Service levels and disk layouts  30


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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 26MB     FixPak Archive/Backup for product with CSD level of
                  XRF4500

   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


           June 18, 2001 - Warp Server for e-business FixPak XRFE002

   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
