RU/2: Форум. Общение пользователей и разработчиков OS/2 (eCS). : HPFS386 update


Список сообщений | Написать новое | Ответить на сообщение | Домой Поиск:
Предыдущее сообщение | Следующее сообщение
From : ???
To : All
Subj : HPFS386 update

386 HPFS UPGRADE FOR OS/2 WARP SERVER FOR E-BUSINESS README
===========================================================

386 HPFS is available as a separate feature for OS/2 Warp
Server for e-business. You must install OS/2 Warp Server for
e-business before you install the 386 HPFS file system, Fault
Tolerance, and Local Security components.

For information about installing OS/2 Warp Server for e-business,
see the "Quick Beginnings" book.

-----------------------------------------------------------

A copy of this README is available from the IBM Technical
Databases and might include additional information that was not
available at the time the OS/2 Warp Server for e-business
documentation was written.

To view this README from the IBM Technical Databases:

1. Go to ps.software.ibm.com

2. Click Technical Databases.

3. Click Technical Documents Database.

4. Click Documents by Product and then OS/2 Warp Server for
e-business.

5. Click 386 HPFS Upgrade for OS/2 Warp Server for e-business
README.

CONTENTS
________

1.0 About 386 HPFS Upgrade for OS/2 Warp Server for e-business
1.1 Fault Tolerance
1.2 Local Security
1.3 Language Abbreviations
2.0 Installing 386 HPFS Upgrade from the CD
2.1 Installing Fault Tolerance Support
2.2 Installing Local Security
2.3 Log Files Created during Installation
3.0 Installing 386 HPFS Upgrade using the CID Method
3.1 Thin386 Changes
3.2 New Response File Keyword
3.3 Tuning Assistant
4.0 After Installation
4.1 Determining the Cache Size
4.2 PREPACL Command
4.3 AIC78U2.ADD Device Driver
4.4 Existing ACLs
5.0 Trademarks and Notices


1.0 ABOUT 386 HPFS UPGRADE FOR OS/2 WARP SERVER FOR E-BUSINESS
_______________________________________________________________

386 HPFS is a server-optimized variant of HPFS. It provides improved
access to large disk volumes, and it optimizes performance in a server
environment where many files are opened simultaneously from clients.

If 386 HPFS is installed, all HPFS volumes are managed by 386 HPFS.
If you have already installed 386 HPFS on your system, the volume is
formatted with 386 HPFS if you select the file system type of HPFS.

If you plan to install OS/2 Warp Server for e-business using the
Server Pak Installation CD or installation diskettes that you
created, see section 2.0 for instructions on installing 386 HPFS Upgrade
from the 386 HPFS Upgrade CD.

If you plan to install OS/2 Warp Server for e-business using the
CID method, see section 3.0 for instructions on installing 386 HPFS
Upgrade using the CID method.

1.1 Fault Tolerance
--------------------

Fault Tolerance lets your server handle disk hardware problems without
significantly interrupting system performance or losing system data.
Fault Tolerance provides drive mirroring and duplexing, as well as
error logging, alerting, and monitoring of disk activity. Drive mirroring
and drive duplexing provide duplication of data stored on disk, thereby
improving data integrity.

If you install Fault Tolerance Support, you must run the FTSETUP
utility after completing the 386 HPFS installation to enable
and configure Fault Tolerance. For more information about
installing and configuring Fault Tolerance, see the "Network
Administrator Tasks" book.

1.2 Local Security
-------------------

Local Security allows you to restrict access by local users (users working
at the server itself) to files on the server and on HPFS volumes.

1.3 Language Abbreviations
---------------------------

HPFS 386 Upgrade is available in several language versions. The
following two-character abbreviations indicate the language
versions that are available:

o br Brazilian Portuguese
o cx Simplified Chinese
o de German
o dk Danish
o en English
o es Spanish
o fi Finnish
o fr French
o it Italian
o jp Japanese
o nl Dutch
o no Norwegian
o sv Swedish
o tw Traditional Chinese


2.0 INSTALLING 386 HPFS UPGRADE FROM THE CD
____________________________________________

To install 386 HPFS:

1. Close all applications on the server.

2. Open an OS/2 window.

3. Stop the server by typing NET STOP SERVER.

4. Insert the 386 HPFS Upgrade for OS/2 Warp Server for e-business CD
into the CD-ROM drive.

NOTE: Do not remove the 386 HPFS Upgrade for OS/2 Warp Server
for e-business CD from the CD-ROM drive until the installation
is complete.

5. Type e: and press Enter, where e: is the CD-ROM drive letter.

6. Type cd\xx\install and press Enter, where xx is the two-character
abbreviation of the language version you are installing. See
section 1.3 for a list of abbreviations.

7. Type install and press Enter.

The OS/2 Warp Server for e-business Setup and Installation window
is displayed.

8. Select 386 HPFS, and then click More.

If you want to install support for the Fault Tolerance component
now, select it.

You cannot select the Local Security component until 386 HPFS is
installed.

9. Click Next to continue the installation.

The Configuration window is displayed, allowing you to configure
the Cache, Lazy Write, and Heap settings.

10. Click Install, and then click OK to complete the installation
of 386 HPFS.

The server is restarted twice during the 386 HPFS
installation process.

2.1 Installing Fault Tolerance Support
---------------------------------------

You can install Fault Tolerance Support during installation of
386 HPFS Upgrade (see section 2.0).

If you did not install Fault Tolerance Support during the installation
of 386 HPFS Upgrade, use the instructions in section 2.0 of this
README file to install it. When you see the Fault Tolerance
Support component checkbox, select it and continue the installation
as prompted.

2.2 Installing Local Security
------------------------------

If you want to use the Local Security component, you must install
it after 386 HPFS Upgrade is installed.

To install Local Security, use the instructions in section 2.0
of this README file. When you see the Local Security
component checkbox, select it and continue the installation
as prompted.

2.3 Log Files Created during Installation
------------------------------------------

The following log files are created in the IBMINST\LOGS\HPFS386
directory during installation of 386 HPFS:

o FS386ERR.LOG
o FS386HST.LOG


3.0 Installing 386 HPFS Upgrade using the CID Method
_____________________________________________________

CID installation gives you the ability to install 386 HPFS Upgrade,
Fault Tolerance Support, and the Local Security component.

These components, which were normally installed as part of the IBM
LAN Server installation (LANINSTR) on OS/2 Warp Server Advanced
and previous IBM LAN server versions, must be installed separately
from the IBM LAN server component during OS/2 Warp Server for
e-business installation.

NOTE: These components must be installed AFTER the IBM LAN server
component installation. If these components are installed before
LAN server is installed, the system might become inoperable.

Use the Feature Installer and the CLIFI utility to install
these components. You need to provide CLIFI two response
files as input parameters: fs386cid.rsp and fs386.rsp. The first
file, fs386cid.rsp, might need modifications. Do not modify the
fs386.rsp file.

To install 386 HPFS from a CID Code Server:

1. Xcopy the files from the files from the HPFS386
directory to the CID\SERVER\HPFS386 directory on
the code server.

If you are upgrading a system which already has 386 HPFS installed
on it, proceed directly to step 3. Otherwise, continue to step 2.

2. You must modify the CID response file fs386cid.rsp located in the
HPFS386 directory. The keyword values must be updated to
appropriate values for which component to install (386 HPFS,
Local Security, or Fault Tolerance).

NOTE: Local Security may be installed only after 386 HPFS
is installed and running. For the install keywords, the value
must be 1 to install the component and 0 to not install
the component.

3. Change fs386cid.rsp to meet your requirements.

NOTE: For Local Security support, 386 HPFS must first be
installed, and the installation needs to be done
in two phases.

The following steps provide an example of modifying the
fs386cid.rsp file to install 386 HPFS, Fault Tolerance
Support, and Local Security.

a. Update the following information to fs386cid.rsp:

Install386HPFS.Selection=1
InstallFaultTolerance.Selection=1
InstallLocalSecurity.Selection=0
WkStaDeterminesCacheSize.Selection=1
WkStaDeterminesHeapSize.Selection=1
ConfigLazyWrite.Selection=1
...
HPFS386_Top.InstallDrive=<C:>
...
HPFS386_Top.isIntegratedInstall=NO
...

where <C:> is the drive where 386 HPFS will be installed.

b. Copy the changed fs386cid.rsp file to another file name, and
modify this new file for Local Security support. (If you do
not need Local Security support, you can skip this step.)
Make the following changes to the file:

Install386HPFS.Selection=0
InstallFaultTolerance.Selection=0
InstallLocalSecurity.Selection=1
WkStaDeterminesCacheSize.Selection=0
WkStaDeterminesHeapSize.Selection=0
ConfigLazyWrite.Selection=0
...
HPFS386_Top.InstallDrive=<C:>
...

where <C:> is the drive where 386 HPFS (with Local
Security support) will be installed.

c. Run CLIFI to install 386 HPFS and Fault Tolerance Support
using the fs386cid.rsp file modified in step a. If you
want to install Local Security support, reboot your system
and run CLIFI again, using the response file created in step b.

Sample CLIFI invocation:
clifi /a:c
/r:<x:>\cid\server\hpfs386\fs386.rsp
/l1:<c:>\os2\install\fs386err.log
/l2:<c:>\os2\install\fs386his.log
/s:<x:>\cid\server\hpfs386
/b:<c:>
/r2:<x>\cid\server\hpfs386\fs386cid.rsp
where <x:> is the server drive and <c:> the boot drive.

NOTE: If you want to reinstall 386 HPFS, you must first uninstall it.

3.1 Thin386 Changes
--------------------

If you are using the Thin386 utility, note the addition of a
new switch called /386Path. This switch should be used to point
to the directory where the 386 HPFS files are installed (Example: C:\IBM386FS).

3.2 New Response File Keyword
------------------------------

The following keyword specifies the location of LAN Server:

HPFS386_TOP.LanDrv=E: (where E: is the drive where LAN Server
is installed)

The default value for this keyword is the drive where the
operating system is installed. Use this keyword if LAN Server is
installed on a different drive than the operating system.

3.3 Tuning Assistant
---------------------

If you install 386 HPFS using CID and plan to run the Tuning
Assistant, and if you want the Tuning Assistant to consider 386
HPFS when it tunes your system, you must create a file named
NPCONFIG.CFG in the \OS2\INSTALL directory on the root drive of
your system. This file contains information about 386 HPFS that
the Tuning Assistant uses.

To create a NPCONFIG.CFG file:

1. Create a blank document with a text editor.

2. Add the following two lines:

All_Products=HPFS386
HPFS386_WSDetermineCacheSize=[parameter]

The parameters for the second line are as follows:

0 For a new install of 386 HPFS, use the cachesize
specified by the HPFS386_TOP.Config386Cache keyword in
the 386 HFPS response file.

For a migration of a system that already had 386 HPFS
installed, do not change the HPFS386.INI cachesize.

NOTE: If the current cachesize is larger than the
calculated size, it will be updated to the
calculated size.

1 Update the HPFS386.INI cachesize with the calculated
value.

NOTE: You can add to the "All_Products" line other products,
separated by spaces, that you want the Tuning Assistant
to consider in its calculations. The following products
can be added:

PPPSRV (Remote Access Services)
PSNS (Personally Safe 'n' Sound)
PSF (Advanced Print Services)

3. Save the file as C:\OS2\INSTALL\NPCONFIG.CFG (where C: is the
drive letter you installed to).


4.0 AFTER INSTALLATION
_______________________

4.1 Determining the Cache Size
-------------------------------

386 HPFS uses a default cache size if one is not specified.
To view the cache size, type the following at the command line:

CACHE386 /O

The cache size is controlled by settings in the file
\IBM386FS\HPFS386.INI.

4.2 PREPACL Command
---------------------

On some systems, especially those with MMOS2 installed, you might
have a problem running PREPACL, a 386 HPFS command. To determine
if you will have this problem, run PREPACL with no parameters:

PREPACL

If no help text is displayed, the system is not finding the
correct LSI.MSG file. To work around this problem, type the
following command at a command prompt and press Enter:

DPATH d:\IBMLAN\INSTALL;%DPATH%

where d: is the directory where \IBMLAN is located.

4.3 AIC78U2.ADD Device Driver
------------------------------

If your system configuration requires the AIC78U2.ADD device driver
and if you install 386 HPFS, download the latest version of the
driver from the Adaptec Web page, www.adaptec.com.

4.4 Existing ACLs
------------------

Any existing Access Control Lists (ACLs) that reference HPFS drives
before the installation of 386 HPFS Upgrade are removed and saved in
<LAN Drive>\IBMLAN\ACCOUNTS\<Drive>.acl.

One of these files is created for every drive with ACLs that
is formatted for HPFS. After installation, you may restore the ACLs
using the PREPACL command with syntax similar to the following:

PREPACL /R /B:<LAN Drive>\IBMLAN\ACCOUNTS\<Drive>.acl /L1:<error log path> /L2:<history log path>


5.0 TRADEMARKS AND NOTICES
___________________________

The following terms are registered trademarks of the IBM
Corporation in the United States, or other countries, or both:

o IBM
o OS/2

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

THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.
IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR
IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT
TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT,
IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.

(c) Copyright IBM Corporation 1999. All rights reserved.

Look and read and try:

warphpfs.zip

Fri 12 Mar 2004 13:32 Mozilla/4.61 [en] (OS/2; U)




Programmed by Dmitri Maximovich, Dmitry I. Platonoff, Eugen Kuleshov.
25.09.99 (c) 1999, RU/2. All rights reserved.
Rewritten by Dmitry Ban. All rights ignored.