                      Welcome to IBM CLARE 4.0 (beta)
                           ( November 28, 1994 )

This README file contains important information about beta version
4.0 of CLARE.

This file will help you prepare your workstations (clients) for the
benchmark run.  As this information is quite long and will require
many changes to your AUTOEXEC.BAT and CONFIG.SYS file, we suggest you
print this file.

    /-----------------------------------------------------------------/
    /                      ** IMPORTANT **                            /
    /  You must follow the instructions carefully.  Failure to        /
    /  implement any one of the following steps will prevent the      /
    /  successful execution of CLARE on your network.                 /
    /                                                                 /
    /  CLARE is made available as an aid to customers and is not an   /
    /  official IBM Product.  CLARE is available on CompuServe and    /
    /  IBM VM Networks.  No support is available for CLARE.  However, /
    /  we will respond to discussion on CompuServe and IBM Forums     /
    /  as best as we can.                                             /
    /-----------------------------------------------------------------/

                            Table of Contents:


                        1.0 - General Information

                        2.0 - Installing CLARE 4.0 (MASTER CLIENT)

                        2.1 - Installing CLARE 4.0 (OTHER CLIENTS)

                        3.0 - Preparing the MASTER CLIENT

                        4.0 - Preparing the OTHER CLIENTS

                        5.0 - Sample AUTOEXEC.BAT

                        6.0 - Starting CLARE

                        7.0 - Running CLARE on a standalone system

                        8.0 - Getting Results


        ***********************************************************
                    Section 1.0 - GENERAL INFORMATION:
        ***********************************************************

If you downloaded CLARE from a BBS, COMPUSERV, INTERNET or any other on-line
service, you must first create a diskette for the installation.  To create a
diskette, copy the following files to the root directory of a fresh formatted
diskette:
        (1) INSTALL.EXE
        (2) INSTALLD.DAT
        (3) INSTHELP.DAT
        (4) MI_INST.EXE
        (5) CI_INST.EXE
        (6) CD_INST.EXE


This version of CLARE must run in DOS 5.0 or greater with or without
NETBIOS installed.  The server can be an OS/2, Netware, or MicroSoft NT,
server, but the MASTER CLIENT and the OTHER CLIENTS must be DOS
based.  ***There are KNOWN Problems with the CC:Mail Script when
using OS/2 LAN Server.  All other scripts should execute without
problem on LAN Server. (12/7/94)***

For LAN file server benchmarks, a minimum of 10 workstations is needed to
produce adequate system load.  However, it is preferable to have a
configuration with 16 or more workstations in order to stress the server.

The MASTER CLIENT is the workstation on which CLARE installed.  The
MASTER CLIENT controls the synchronization of all the OTHER CLIENTS, and
controls the execution of the benchmark on those clients.

Since the MASTER CLIENT will be running CLARE, we strongly suggest
that you load an expanded memory manager such as HIMEM.SYS, and place as
many programs as possible, (i.e. DOS, MOUSE, NET...) in high memory.

If you are using a mouse, MOUSE.COM must be loaded before starting
CLARE.  Again, we suggest you load MOUSE.COM in HIGH memory.

CLARE requires a minimum configuration of:

    IBM 386 and above or compatible machine.
    2MB memory.
    500K free conventional memory after all drivers and OS are loaded.
    VGA Monitor (color or monochrome).
    5MB free DASD space on local drive.


        ***********************************************************
            Section 2.0 - INSTALLING  CLARE 4.0 (MASTER CLIENT)
        ***********************************************************

(1) Insert the diskette in the diskette drive of the workstation on your
    LAN which will be designated as the MASTER CLIENT.

(2) Switch to the diskette drive by typing
        A: <enter>

(3) Type INSTALL

(4) Select MASTER CLIENTS.

(5) You cannot enter a client number.  The MASTER CLIENT number is ALWAYS 1.

(6) Select the local drive where you want CLARE installed to.  Note this drive
    letter must be the same for all clients.

(7) Select the NETWORK DRIVE of the file server that will be used in the
    benchmark.  Note this drive letter must be the same for all clients.

(8) Press the OK button.

(9) When the installation is complete, three new directories will exist on
    the local hard disk.  They are:
                          <local drive:>\CLARE
                          <local drive:>\CLARE\ENGINE
                          <local drive:>\CLAREDAT


        ***********************************************************
             Section 2.1 - INSTALLING  CLARE 4.0 (OTHER CLIENTS)
        ***********************************************************

All OTHER CLIENTS, except for the MASTER CLIENT, must follow this
procedure.

(1) Insert the diskette in the diskette drive of the workstation on your
    LAN which will be designated an OTHER CLIENT for the benchmark.

(2) Switch to the diskette drive by typing
        A: <enter>

(3) Type INSTALL

(4) Select OTHER CLIENTS.

(5) Enter a client number for this client.  Client numbers for the OTHER
    CLIENTS must start at 2 and work consecutively up to a maximum of 128.

(6) Select the local drive where you want CLARE installed to.  Note this drive
    letter must be the same for all clients including the MASTER CLIENT.

(7) Select the NETWORK DRIVE of the file server that will be used in the
    benchmark.  Note this drive letter must be the same for all clients
    including the MASTER CLIENT.

(8) Repeat steps 1 through 7 for all clients that will participate in the
    test.  Remember to increment the client number with each new client.  The
    number must start at 2 increment consecutively to a maximum of 128.

(9) When the installation is complete, two new directories will exist on
    the local hard disk of each client.  They are:

                          <local drive:>\CLARE
                          <local drive:>\CLAREDAT

        ***********************************************************
                Section 3.0 - PREPARING THE MASTER CLIENT.
        ***********************************************************

(1) CLARE must be installed on the local hard drive on the MASTER CLIENT
    See section 2.0 for information on installing CLARE.
    See section 7.0 information on running CLARE on a standalone system.

(2) The install program will update your CONFIG.SYS file to include the
    the following statement:
    FILES=20

    If you elected not to have the install program make this change
    automatically, you must enter the statement, FILES=20, yourself.

(3) The install program will attempt to update the AUTOEXEC.BAT file to
    contain the following statements:
    SHARE
    SET MCH_NAME=W001
    SET COMSPEC=C:\COMMAND.COM
    PATH=your path;<local drive:>\CLARE;

                                The actual drive letters will vary
                                depending on which LOCAL drive
                                you selected during the install.

    If the install program was unable to add these lines, you must
    manually update AUTOEXEC.BAT.

(4) We assume that the AUTOEXEC.BAT contains the network sign-on and
    login statements that are appropriate for your configuration.

(5) You may optionally insert a PAUSE command immediately preceding the
    network sign-on and login statements.

(6) After modifying AUTOEXEC.BAT and CONFIG.SYS, reboot the MASTER CLIENT.

        ***********************************************************
                 Section 4.0 - PREPARING THE OTHER CLIENTS
        ***********************************************************

The following steps must be performed on all OTHER CLIENTS except the MASTER
CLIENT.

(1) The install program will update your CONFIG.SYS file to include the
    the following statement:
    FILES=20

    If you elected not to have the install program make this change
    automatically, you must enter the statement, FILES=20, yourself.

(2) The install program will attempt to update the AUTOEXEC.BAT file to
    contain the following statements:
    SHARE
    SET COMSPEC=C:\COMMAND.COM
    PATH=your path;<local drive:>\CLARE;

                                The actual drive letters will vary
                                depending on which LOCAL drive
                                you selected during the install.

    If the install program was unable to add these lines, you must
    manually update AUTOEXEC.BAT.
    SET MCH_NAME=W<nnn>

                   The actual value of <nnn> is dependent on the value you
                   entered during the install procedure.
                   Each client must be assigned a UNIQUE MCH_NAME and the
                   clients names must start at W002 and continue
                   consecutively to a maximum of W128. This parameter
                   must start with a capital W followed by three digits.
                   For example:

                                SET MCH_NAME=W004 is correct
                                SET MCH_NAME=W04  is not correct
                                SET MCH_NAME=W4   is not correct
                                SET MCH_NAME=w004 is not correct

    <local drive:>\CLARE\DSKSCHED /W:<network_drive>

                    This puts the client in a loop to await CLARE
                    startup. DO NOT PERFORM THIS STEP ON THE MASTER CLIENT.


    If the install program was unable to add these lines, you must
    manually update AUTOEXEC.BAT.

        ***********************************************************
            Section 4.0 - PREPARING THE OTHER CLIENTS (cont'd)
        ***********************************************************

(3) We assume that the AUTOEXEC.BAT contains the network sign-on and
    login statements that are appropriate for your configuration.

(4) A PAUSE command should be coded immediately preceding the
    sign-on and login statements to give the user the opportunity to verify
    that the Network is up and available.

(5) Reboot each client and ensure that each client is logged on.
    If the Server is ready, press any key on each client, and the
    message "Dsksched" will appear, indicating that the client is
    waiting for instructions from the MASTER CLIENT to begin the
    benchmark.


        ***********************************************************
                     Section 5.0 - SAMPLE AUTOEXEC.BAT
        ***********************************************************

                **********************************************************
                 This sets the PATH to the LOCAL DRIVE (in this example, the
                 LOCAL DRIVE for the benchmark is drive C:   You should
                 replace C: with the actual drive that you will be using).
                **********************************************************
path=your_path;C:\CLARE

                **********************************************************
                 This sets the COMSPEC (in this example, COMMAND.COM is
                 located on drive C in the subdirectory \DOS.  You should
                 replace this with the location of your COMMAND.COM )
                **********************************************************
SET COMSPEC=C:\DOS\COMMAND.COM

                **********************************************************
                 This sets the MCH_NAME variable. Each client must have a
                 unique MCH_NAME.  In this example, we are defining
                 client W002
                **********************************************************
set MCH_NAME=W002

                **********************************************************
                 Optional PAUSE statements.
                **********************************************************
@echo Hit any key to start
pause
                **********************************************************
                 Enter required network signon commands here.  These commands
                 will change based on your environment.
                **********************************************************
c:\nw311\ipx164
timer /d0:0:5
c:\nw311\netx ps=server_a
c:\nw311\netbios
@echo on
F:
login server_a/%MCH_NAME%

                **********************************************************
                 MAP to the NETWORK (server) drive that will be used for the
                 benchmark.  In our example, we are going to use drive L: for
                 the test.  Your drive letter may be different.
                **********************************************************
map L: =SERVER_A/DATA:

                **********************************************************
                 Switch to the server drive that will be used in the benchmark.
                 Again, we are using drive L: for this benchmark, yours may be
                 different.
                **********************************************************
L:

                **********************************************************
                 This puts the client in a loop to await CLARE startup.
                        DO NOT PERFORM THIS STEP ON THE MASTER CLIENT.
                 Again, we are using drive L: for this benchmark, yours may be
                 different.
                **********************************************************
<local drive:>\CLARE\DSKSCHED /W:L


        ***********************************************************
                   Section 6.0 - STARTING CLARE
        ***********************************************************
(1) To start the CLARE benchmark:  change to the CLARE
    directory on the local hard drive of the MASTER CLIENT
    (CD \CLARE)

(2) CLARE can be started in one of two modes: Demonstration or
    Benchmark.

    To start in Demonstration mode enter the command:  'CLARE /demo'

    To start in Benchmark mode enter the command:      'CLARE'

    Demonstration mode can be used to test your installation. Use the
    /demo switch if you would like to perform a "dry run" to see if the
    install worked correctly, especially if you installed on a standalone
    system.  You can also run in /demo mode on a LAN, especially if you
    just want to function test your LAN to make sure all the connections
    are operational.  DO NOT rely on the performance data produced in /demo
    mode.  The benchmark application scripts do not run for a sufficient
    amount of time to produce repeatable and reliable data.

    FURTHER, IF YOU USED THE /DEMO MODE TO CREATE BENCHMARK TEST FILES, YOU
    MUST REFORMAT YOUR SERVER DRIVE AND CREATE THE BENCHMARK TEST FILES
    AGAIN BEFORE RUNNING LIVE FILE SERVER BENCHMARKS.  THE /DEMO MODE
    SWITCH CREATES A SMALLER DATABASE, WHICH IS NOT COMPATIBLE WITH NORMAL
    BENCHMARK MODE.


          ***********************************************************
            Section 7.0     - RUNNING CLARE ON A STANDALONE SYSTEM
          ***********************************************************

CLARE can be run on a standalone system.  This may be useful to see if you
have installed, and configured CLARE correctly.  To do so,
perform the following steps

(1) Pick the client that you want to benchmark, this workstation
    will be the MASTER CLIENT.

(2) Configure this client as detailed in the section "PREPARING THE MASTER
     CLIENT" above.

(3) Start CLARE by typing 'CLARE /demo'

(4) From the CONFIGURATION menu, select DEFINE CLIENTS, enter 1 client.
                               CLICK OK (ALT_O).

(5) From the CONFIGURATION menu, select RUN SELECTION, enter 1 in the
    Benchmark Run #1 field.
                               CLICK OK (ALT_O).

(6) From CONFIGURATION menu, select SCRIPT SELECTION.  Choose either DOS or
    WINDOWS scripts.
                               CLICK OK (ALT_O).
(7) From the CONFIGURATION menu, select DASD options and click on the
    local hard disk of the MASTER CLIENT.
                               CLICK OK (ALT_O).

(8) From the CONFIGURATION menu, select NOTEPAD and complete the
    fields.
                               CLICK OK (ALT_O).

(9) From MAIN WINDOW, select START BENCHMARK.  Select CREATE FILES AND RUN
BENCHMARK. Enter a FILENAME and a DESCRIPTION.
                               CLICK OK (ALT_O).

        ***********************************************************
                        Section 8.0 - GETTING RESULTS
        ***********************************************************

After CLARE completes, the results can be found in the RESULTS
directory of the drive you specified.  In addition, an additional copy is
written to the RESULTS directory of the MASTER CLIENT.  The report format
is a ASCII formatted text file.  This file can be used in any word processor,
spreadsheet or text editor.

You should check the $ERR directory on the selected SERVER's disk(shared drive),
any file with a file size greater then zero (0) indicates that an error was
reported.  You can view this file with any text editor.  The format for the
filenames is CLxxxyyy where xxx is the last three digits of the client name
and yyy is the number of clients that participated in the benchmark run.
For example, Client W005 would create a file CL005036.ERR if a 36 client
benchmark was requested.  The error messages can also be viewed from the
RESULTS directory mentioned above.  The extension of the error files is
.err.

    Note:  CLARE uses PKZIP in order to compress some of the raw
    .DAT files.  Normally, you don't need these files.  However, for
    problem determination, they may be useful.

PKZIP is a very useful utility written and copyrighted by PKWARE INC.
If you don't have PKZIP, you will still get your results.  However, you
will not get the compressed .log files.


        ***********************************************************
                 Section 9.0 - IMPORTANT RUNTIME NOTES
        ***********************************************************
This version of CLARE contains several new application scripts.
All scripts have been tested for accuracy and repeatability.  However,
anytime you utilize this tool for product evaluation, you should make
several runs on your configuration with the mix of applications you are
planning to evaluate to determine repeatability of the results.
For some low-end server configurations, the default runtime is insufficent
to produce repeatable results.  The solution is to increase the runtime
for any script that produces results that vary more than 2 - 3 percent.
Increase runtime by 30 - 50% each time until repeatability is achieved.
