2.2.10 Panel-Driven Installation or CID-Based?

2.3 Special Considerations

This section details circumstances that may impact your system during migration.

2.3.1 FDISK Command Not Available

In OS/2 Warp Server for e-business, the FDISK command has been replaced by the LVM command to add the support for sticky drive letters and logical volumes. If you use self-written REXX procedures that make use of the FDISK command, you need to modify those to apply the LVM command.

2.3.2 Windows NT Coexistence on Same Machine

Installation of OS/2 Warp Server for e-business on a machine that already has Windows NT installed is not officially supported. In some configurations, the existing NT system might not be bootable after an OS/2 Warp Server for e-business installation.

OS/2 LVM writes information about assigned drive letters to the last sector of the boot drive, and it changes the master boot record to mark all the existing partitions as compatibility volumes. Windows NT's boot process detects this change and stops. It then displays a message that the kernel cannot be found.

We have successfully installed Windows NT on the same machine after OS/2 Warp Server for e-business has been installed. However, this is not a recommended or supported configuration but might be useful for some test scenarios.

2.3.3 Some 386 HPFS Features Not Available with JFS

DASD Limits

The current version of JFS shipped with OS/2 Warp Server for e-business does not support DASD limits.

Depending on your requirements, there are several possible workarounds.

  1. Keep the resources that need directory limits on a 386 HPFS formatted volume.

  2. Use CHKSTOR as a replacement if it is sufficient to send an alert to the Administrator when the limit is exceeded.
Fault Tolerance

There is no replacement for the 386 HPFS Fault Tolerance feature in JFS. Current server machines usually come with RAID adapters that can be used to perform this function as a hardware solution.

If you still need to rely on the software disk mirroring provided by 386 HPFS the only option is to keep 386 HPFS.

2.3.4 Drive Letters Referenced in CONFIG.SYS

Although LVM usually can change a drive letter dynamically without rebooting, your applications still might rely on the letter that was previously assigned.

Examples are references in the PATH, LIBPATH, DPATH. For Java applications, CLASSPATH variables. In this case, you have several options.

Another example is a device driver installed for an application. A reboot might not be necessary immediately, but to ensure that the driver is still loaded on the next reboot, do one of the following:

2.3.5 CD-ROM Drive Letter Changes Requiring Reboot

The CD-ROM is assigned the first free drive letter. Depending on the drive letters chosen in your setup, the CD-ROM drive can even be mapped as C:.

If you are assigning the drive letter that is currently used by the CD-ROM drive to a volume using LVM or LVMGUI, the system will prompt you to reboot.

The RESERVEDRIVELETTER statement in CONFIG.SYS can help to avoid unnecessary reboots when reassigning the drive letters. It can be used to force the CD-ROM to a convenient letter.

The syntas for RESERVEDRIVELETTER is
RESERVEDRIVELETTER=<letter>

where:

<letter>
specifies the upper drive letter that needs to be reserved for system use.

This line can be added anywhere in the CONFIG.SYS file. The CD-ROM drive will get the next drive letter after <letter> upon the next reboot.

2.3.6 Naming and LVM

LVM introduces a new level of abstraction from the underlying disk structures and allows you to name each of the elements.

As far as naming these elements is concerned, you should avoid situations that might lead to confusion, for example, when identical names are used for different elements, thus, making it hard to distinguish them.

We suggest the following naming rules:


Table 8: Named Elements in LVM

While the last proposition might seem like a unnecessary duplication, we have found that it helps manage the hard disk space in a dynamic environment.

2.3.7 Windows NT Server Integration

The IBM Networks Account Manager for managing Windows NT servers as additional servers in an OS/2 Warp Server for e-business domain only works with Windows NT V4.0. It does not work with Windows NT 3.51.

The Network Account Manager relies on an OS/2 Warp Server for e-business Primary Domain controller. This might impact the order in which you migrate your servers.

2.3.8 WorkSpace On-Demand V1.0

It is not recommended to install OS/2 Warp Server for e-business on a server that has WorkSpace On-Demand, Version 1.0 installed. OS/2 Warp Server for e-business supports WorkSpace On-Demand, Version 2.0.

If you wish to install OS/2 Warp Server for e-business over an existing WorkSpace On-Demand, Version 1.0, you should first back-up all ACLs (Access Control Lists) prior to the installation (these ACLs must be reinstalled after the migration to OS/2 Warp Sever for e-business has completed). Next, you will have to modify several system files before migrating to Warp Server for e-business as outlined in the following procedure:

  1. Copy the WorkSpace On-Demand, Version 1.0 CD-ROM to a temporary directory on your hard drive. 
    XCOPY *.* :\TEMP /S /E /V /H /O /T /R

  2. Remove the read-only attribute from the file REVFIX.CMD. 
    ATTRIB \TEMP\SERVICE\TOOLS\REVFIX.CMD -R

  3. Edit REVFIX.CMD. Add 14.037 to the line. 
    build_list='8.260 8.259 8.258 8.257 8.256 8.255', '8.254 8.253 8.252 8.251 8.250 8.249 8.248 8.247 8.246 7.029'


    Note

    You should check the final version of OS/2 Warp Server for e-business to determine the revision level with the VER /R command.



  4. Copy the file SYSLEVEL.OS2 from a OS/2 Warp Server system that is at the appropriate fixpak level (OS/2 Warp Fixpak 22 or above) to a diskette. 
    COPY \OS2\INSTALL\SYSLEVEL.OS2

  5. On the Warp Server for e-business system, make a backup copy of the file OS2\INSTALL\SYSLEVEL.OS2. 
    COPY \OS2\INSTALL\SYSLEVEL.OS2 SYSLEVEL.BAK

  6. Remove the read-only attribute from the file SYSLEVEL.OS2 on the OS/2 Warp Server for e-business system. 
    ATTRIB \OS2\INSTALL\SYSLEVEL.OS2 -R

  7. Copy the SYSLEVEL.OS2 file from the diskette to the OS/2 Warp Server for e-business system. 
    COPY A:\SYSLEVEL.OS2 \OS2\INSTALL

  8. Replace the read-only attribute on the file SYSLEVEL.OS2. 
    ATTRIB \OS2\INSTALL\SYSLEVEL.OS2 +R

  9. Change to the temporary directory and enter INSTALL.

  10. After successful installation of WorkSpace On-Demand R1.0, remove the read-only attribute from the SYSLEVEL.OS2 file. Copy SYSLEVEL.BAK to SYSLEVEL.OS2. Put the read-only attribute back on the SYSLEVEL.OS2 file. You are now done.

2.3.9 Backup Software and JFS

JFS now supports larger files under OS/2 than any previous OS/2 version. It also has the feature to support sparse files. Make sure that your backup software can handle these features before you start to exploit them. The PSnS Backup and Recovery Services, included in OS/2 Warp Server for e-business, does support very large files (see Section 1.3.9 Backup and Recovery Services). Sparse files that are backed up with software that does not support them may become dense files upon restore. That is, they may expand to their perceived size by the software.

2.3.10 Components Not in OS/2 Warp Server for e-Business

While most components listed below were not shipped with previous OS/2 Warp Server or OS/2 LAN Server versions, you should be aware that the installation process will delete the listed products if they are found. Of course, you will be warned prior to deletion.


Table 9: Software Removed by OS/2 Warp Server for e-business Installation

CHKINST.EXE on the OS/2 Warp Server for e-business CD-ROM will search for these products and generate a report for you. For more on this see Section 2.2.2.1 Run CHKINST.

2.4 Migration Examples and Model Scenarios Tested