Windows NT Super Tune-Up Kit/PIE-WindowsNTSuperTuneUpKit-1997.iso/BNCHMARK/SVRBENCH/OS2WS.TXT

Text File | 1996-03-14 | 161.4 KB | 3,461 lines

Licensed MaterialProperty of Ziff-Davis Publishing Company

Licensed MaterialProperty of Ziff-Davis Publishing Company














    Installing ServerBenchr 3.0 on OS/2r Warp Server

 LICENSE AGREEMENT FOR ZIFF-DAVIS' SERVERBENCHr VERSION
                           3.0
READ  THIS  AGREEMENT  CAREFULLY  BEFORE  USING  THE  SOFTWARE
EMBODIED IN THE SERVERBENCHr 3.0 CD-ROM, DISKETTE(S),  OR,  IF
PRELOADED  ON  YOUR HARD DRIVE, DOWNLOADED OR IF  PROVIDED  AS
PART  OF  A COLLECTION, THE PRELOADED, DOWNLOADED OR COLLECTED
FILE(S)  (the "Media"). Embodied in the ServerBench 3.0  Media
is  the  ServerBench version 3.0 computer programs and related
documentation (the "Software"). Ziff-Davis Publishing Company,
having  a place of business at One Park Avenue, New York,  New
York 10016 ("Ziff-Davis") is the licensor under this Agreement
and  you are the licensee. By using the Software, in whole  or
in part, you agree to be bound by the terms of this Agreement.
If  you  do not agree to the terms of this Agreement, promptly
return  the Software to the Ziff-Davis Benchmark Operation  at
1001  Aviation Parkway, Suite 400, Morrisville, North Carolina
27560 (or, if downloaded, delete the Software, or if preloaded
on  your  hard  drive or if provided as part of a  collection,
cease  use  of  the Software). Title to the Software  and  all
copyrights, trade secrets and other proprietary rights therein
are  owned  by  Ziff-Davis. All rights therein,  except  those
expressly  granted to you in this Agreement, are  reserved  by
Ziff-Davis.
1. Limited License
This  Agreement  grants you only limited  rights  to  use  the
Software.   Ziff-Davis  grants  you  a   non-exclusive,   non-
transferable  license to use the Software  on  a  file  server
networked  with multiple PC computers for the sole purpose  of
conducting  benchmark  tests  to measure  the  performance  of
computer  hardware  and operating system  configurations.  You
have  the  right  to make a single copy of  the  Software  for
archival  purposes and the right to transfer  a  copy  of  the
Software across an internal local area network only to the  PC
computers  attached to such network; provided,  however,  that
all  such  copies are considered Software hereunder, that  all
uses  of  such copies are governed by the terms and conditions
of  this  Agreement and that you shall be responsible for  all
uses  of  such copies in violation of the terms and conditions
of  this Agreement. Ziff-Davis hereby grants you the right  to
publish,  except  in  any country where a third  party  claims
during  the  term  of  this  license  that  such  distribution
infringes  that  party's  proprietary rights,  benchmark  test
results obtained by you from your use of the Software provided
that with the publication of each such result you:
A.Identify  Ziff-Davis,  the name and version  number  of  the
  benchmark Software used and the name of the test suite  used
  in the test (e.g., Ziff-Davis' ServerBenchr version 3.0 with
  the standard system test suite SYS_60.TST);
B.Identify for the applications server the exact name,  number
  of  processors, processor speed (including clock speed)  and
  type(s),  amount of RAM, amount of secondary RAM  cache  (if
  any), size of hardware hard disk cache, (if any), number and
  type of hard disk controller(s), type of I/O bus, number and
  type  of hard disks, hard disk size, driver version  of  the
  disk   controller(s),  type  of  disk  organization   (e.g.,
  mirrored),  number  and type of network controllers,  driver
  version of network controller, network operating system name
  and  version, and any relevant modifications to the  default
  network  operating system parameters (e.g., WXY Corp.  Model
  466  with 1 66-MHz Intelr 486DX2-66 CPU, 64MB of RAM,  256KB
  CPU  cache, WXY Integrated Drive Array disk controller, EISA
  I/O  bus,  2  ABC  520MB disk drives, a xxxxx386.dsk  12,621
  4/29/92  disk  driver,  hardware striping,  WXY  32-bit  ABC
  controller,   a  xxxxxxx.lan  40,905  9/11/92  net   driver,
  NetWarer 4.1, and the following NOS parameters: set  maximum
  physical receive packet size = 4202);
C.Identify  for the test bed the network type, the  number  of
  clients, the client operating system version (e.g., Windowsr
  95),  the number and type of hubs/concentrators, the  number
  of  clients  per segment, the client CPU type and  speed  in
  percentages,  client  network  software  name  and   version
  (drivers  and  protocols), the size of  the  client  network
  cache,  if  any  (e.g.,  10Base-T with  32  clients,  2  XYZ
  Ethernet  Hubs, 16 clients per segment, 75% of  the  clients
  are  486/25  and 25% of the clients are 386/20, 75%  of  the
  clients have ABC NE2000 network cards and 25% of the clients
  have  GHI  network cards, Microsoftr Windows  95,  Microsoft
  TCP/IP using Windows Sockets Version 1.1,  enhanced mode 32-
  bit NDIS driver);
D.    Identify the controller operating system version  (e.g.,
  Microsoft Windows 95) and network software and version;
E.State  that  all  products used in the  test  were  shipping
  versions available to the general public;
F.State  that  the  test  was  performed  without  independent
  verification  by  Ziff-Davis and that  Ziff-Davis  makes  no
  representations or warranties as to the results of the test;
  and
G.Follow  proper  trademark usage and acknowledge  Ziff-Davis'
  trademark rights (e.g., "[ ] achieved a ServerBenchr overall
  score  of  X  transactions  per  second.  ServerBench  is  a
  registered  trademark or trademark of Ziff-Davis  Publishing
  Company in the U.S. and other countries.").
This  Agreement and your rights hereunder shall  automatically
terminate  if  you fail to comply with any provision  of  this
Agreement. Upon such termination, you agree to cease  all  use
of  the  Software,  cease the transfer of any  copies  of  the
Software  and cease the publication of benchmark test  results
obtained  by you from use of the Software. Further, you  agree
to  delete the Software and to destroy all tangible copies  of
the  Software and other materials related to the  Software  in
your  possession or under your control, or, if  downloaded  or
preloaded  on  your hard drive or if provided  as  part  of  a
collection, to cease use of and destroy any and all copies  of
the Software in your possession or under your control.
2. Additional Restrictions
A.You  shall  not  (and  shall not  permit  other  persons  or
  entities  to)  rent,  lease, sell,  sublicense,  assign,  or
  otherwise  transfer  the  Software or  this  Agreement.  Any
  attempt to do so shall be void and of no effect.
B.You  shall  not  (and  shall not  permit  other  persons  or
  entities   to)  reverse  engineer,  decompile,  disassemble,
  merge,  modify, include in other software or  translate  the
  Software,  or use the Software for any commercial  purposes,
  except  for  the  publication of test results,  as  provided
  above.
C.You  shall  not  (and  shall not  permit  other  persons  or
  entities   to)  remove  or  obscure  Ziff-Davis'  copyright,
  trademark or other proprietary notices or legends  from  any
  of the materials contained in this package or downloaded.
D.    You  acknowledge that the Software contains  Ziff-Davis'
  trade  secret information and you agree not to  disclose  or
  disseminate such information other than as provided herein.
3. Limited Warranty and Limited Liability
THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION,  ANY
WARRANTY  OF  MERCHANTABILITY AND  FITNESS  FOR  A  PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE  OF
THE  SOFTWARE  IS  ASSUMED  BY YOU,  AND  ZIFF-DAVIS  AND  ITS
AUTHORIZED  DISTRIBUTORS  ASSUME  NO  RESPONSIBILITY  FOR  THE
ACCURACY  OR  APPLICATION OF OR ERRORS  OR  OMISSIONS  IN  THE
SOFTWARE.  IN  NO  EVENT SHALL ZIFF-DAVIS  OR  ITS  AUTHORIZED
DISTRIBUTORS  BE  LIABLE  FOR ANY DIRECT,  INDIRECT,  SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE  OR
INABILITY  TO  USE  THE SOFTWARE, EVEN IF  ZIFF-DAVIS  OR  ITS
AUTHORIZED DISTRIBUTORS HAVE BEEN ADVISED OF THE LIKELIHOOD OF
SUCH   DAMAGES   OCCURRING.  ZIFF-DAVIS  AND  ITS   AUTHORIZED
DISTRIBUTORS  SHALL  NOT BE LIABLE FOR ANY  LOSS,  DAMAGES  OR
COSTS,  ARISING  OUT OF, BUT NOT LIMITED TO, LOST  PROFITS  OR
REVENUE,  LOSS  OF  USE  OF  THE SOFTWARE,  LOSS  OF  DATA  OR
EQUIPMENT,   THE  COSTS  OF  RECOVERING  SOFTWARE,   DATA   OR
EQUIPMENT, THE COST OF SUBSTITUTE SOFTWARE OR DATA, CLAIMS  BY
THIRD PARTIES, OR OTHER SIMILAR COSTS.
THE  ONLY  WARRANTY  MADE  BY ZIFF-DAVIS  AND  ITS  AUTHORIZED
DISTRIBUTORS IS THAT ANY ORIGINAL PHYSICAL MEDIA IN WHICH  THE
SOFTWARE IS EMBODIED AND WHICH IS DISTRIBUTED BY ZIFF-DAVIS OR
ITS  AUTHORIZED  DISTRIBUTORS SHALL  BE  FREE  OF  DEFECTS  IN
MATERIALS  AND  WORKMANSHIP. ZIFF-DAVIS'  AND  ITS  AUTHORIZED
DISTRIBUTORS' ENTIRE LIABILITY AND THE USER'S EXCLUSIVE REMEDY
SHALL  BE  LIMITED TO THE REPLACEMENT OF THE ORIGINAL PHYSICAL
MEDIA  IF  DEFECTIVE. THE WARRANTIES AND  REMEDIES  SET  FORTH
HEREIN  ARE  EXCLUSIVE  AND IN LIEU OF  ALL  OTHERS,  ORAL  OR
WRITTEN, EXPRESS OR IMPLIED. NO ZIFF-DAVIS DISTRIBUTOR,  AGENT
OR  EMPLOYEE,  OR  THIRD  PARTY, IS  AUTHORIZED  TO  MAKE  ANY
MODIFICATION OR ADDITION TO THIS WARRANTY.
SOME  STATES DO NOT ALLOW EXCLUSION OR LIMITATION  OF  IMPLIED
WARRANTIES  OR  LIMITATION  OF  LIABILITY  FOR  INCIDENTAL  OR
CONSEQUENTIAL DAMAGES; SO THE ABOVE LIMITATIONS OR  EXCLUSIONS
MAY NOT APPLY TO YOU.
4. U.S. Government Restricted Rights
The  Software  is licensed subject to RESTRICTED RIGHTS.  Use,
duplication or disclosure by the Government or any  person  or
entity acting on its behalf is subject to restrictions as  set
forth  in  subdivision (c)(1)(ii) of the Rights  in  Technical
Data  and  Computer Software Clause at DFARS (48 CFR  252.227-
7013)  for DoD contracts, in paragraphs (c)(1) and (2) of  the
Commercial Computer Software-Restricted Rights clause  in  the
FAR  (48 CFR 52.227-19) for civilian agencies, or in the  case
of  NASA, in Clause 18-52.227-86(d) of the NASA Supplement  to
the   FAR,   or  in  other  comparable  agency  clauses.   The
contractor/manufacturer is the Ziff-Davis Benchmark Operation,
1001  Aviation Parkway, Suite 400, Morrisville, North Carolina
27560.
5. General Provisions
Nothing  in  this Agreement constitutes a waiver of Ziff-Davis
rights  under U.S. copyright laws or any other Federal, state,
local  or  foreign law. You are responsible for  installation,
management,  and  operation of the  Software.  This  Agreement
shall  be  construed, interpreted and governed under New  York
law.  If  any provision of this Agreement shall be held  by  a
court  of  competent  jurisdiction to be illegal,  invalid  or
unenforceable, the remaining provisions shall remain  in  full
force and effect.



Trademarks
MacBench, NetBench, ServerBench, WinBench, and Winstone are
  registered trademarks and
  ZD Net is a trademark of Ziff-Davis Publishing Company.
CompuServe is a registered trademark of CompuServe, Inc.
Digital and Alpha are trademarks of Digital Equipment
  Corporation.
Microsoft, MS-DOS, and Windows are registered trademarks and
  Windows NT is a trademarks of Microsoft Corporation.
NetWare and Novell are registered trademarks and NetWare
  ClientÖ and NetWare Client 32Ö are trademarks of Novell,
  Inc.
MIPS is a registered trademark of MIPS Technologies, Inc.
OS/2 is a registered trademark and PowerPC is a trademark of
  IBM Corporation.
SCO and UnixWare are registered trademarks and SCO OpenServer
  is a trademark of The Santa Cruz Operation, Inc.








Table of Contents




  Goal of This Manual                                   1
     Some quick reminders about ServerBench             1

  ServerBench on  OS/2 Warp Server                      3
     What's new about ServerBench on OS/2 Warp Server   3
     ServerBench's structure on OS/2 Warp Server        3

  Chapter 1 ~ The Installation Overview                 5
     The hardware and software requirements             5
          The server requirements:                      5
          The controller requirements:                  6
          The client requirements:                      6
     Set up your system before you install              7
     Create a test network for ServerBench              7
     Keep the background activity to a minimum          7
     Getting the ServerBench files to the right machines8
     The installation process (in brief)                8
          The basic installation steps                  8

  Chapter 2 ~ Installing ServerBench on Your Server    13
     Step 1: Check your server's hardware and software 13
     Step 2: Modify your server's setup                13
     Step 3: Install the server files                  14
     Step 4: Verify your installation                  16
     Step 5: Set up the TCP/IP addresses               17
     Step 6: Make sure the machines are talking        18
     Create directories for data files (optional)      18

  Chapter 3 ~ Setting TCP/IP Up on the Controller and Clients
  19
     Options for setting up TCP/IP                     19
          Installing a Microsoft Windows 95 TCP/IP stack20
          Installing a Windows for Workgroups 3.11 TCP/IP
          stack                                        20
          Installing an OnNet 2.0 for Windows TCP/IP stack
          21
          General Guidelines for any third-party TCP/IP stack
          22
     Make sure the TCP/IP stack is installed correctly 22
     Setting up multiple NICs                          23

  Chapter 4 ~ Installing ServerBench on Your Controller25
     Step 1: Check the controller's hardware and software  25
     Step 2: Install the controller files              25
          Step-by-step instructions for installing ServerBench
          on the controller                            26
     Step 3: Verify your installation                  27
     Step 4: Install the TCP/IP stack                  28
     Step 5: Make sure Excel can work with ServerBench 28

  Chapter 5 ~ Installing ServerBench on Your Clients   30
     Step 1: Check the clients' hardware and software  30
     Step 2: Select the client names and numbers       30
     Step 3: Install the client files                  31
          Step-by-step instructions for installing ServerBench
          on a client                                  31
     Step 4: Verify your installation                  34
     Step 5: Install the TCP/IP stack                  34
     Creating your own client configuration file       34
     Modifying the client command line                 36

  Chapter 6 ~ Running ServerBench                      39
     Starting ServerBench                              39

  Chapter 7 ~ Troubleshooting and Error Messages       43
     What to check if you have problems                43
     If clients are stuck in a test's R stage, check these
     things                                            44
     The way ServerBench reports errors                44
     Server error messages                             45
          Server network error messages                45
          Server kernel error messages                 46
          Server file error messages                   46
          Server settings error messages               47
          Server executing error messages              48
     Error messages generated by the client            48
     Error messages generated by the controller        50

  Chapter 8 ~ Contacting ZDBOp                         57
     If a problem occurs, look here for possible solutions 57
     Here's how you get in touch with ZDBOp            57
          Getting copies of benchmarks from ZD Net     58
          Requesting the benchmark CD-ROMs from ZDBOp  58

  Index                                                59

  Problem Report Form

  Benchmark Request Form







Goal of This Manual


     The goal behind this manual is to give you a relatively
     short document that helps you install ServerBench 3.0 on
     OS.2 Warp Server. This manual focuses on the installation
     steps.
     For more information about ServerBench and your options
     for running ServerBench, see Understanding and Using
     ServerBench 3.0. Also, if you just want to quickly run
     ServerBench, look at your results, and use some of
     ServerBench's basic features, such as setting up a
     disclosure database, see the ServerBench  Quick Start
     Handbook. Both Understanding and Using ServerBench 3.0
     and ServerBench  Quick Start Handbook contain generic
     information about ServerBench.

     Some quick reminders about ServerBench:
              ServerBench is a Ziff-Davis benchmark program
              that measures the performance of application
              servers in a client/server environment. To run
              ServerBench, you need a minimum of three
              machines:
     A
     server
     The machine running the server software. For
     ServerBench's purposes, a server consists of the machine
     running the server software, the network protocol used
     to communicate with the clients, and the different
     subsystems (disk, processor, and network) that the
     server uses in order to perform the work requested by
     the clients. You install ServerBench's server program on
     the server.
     A Controller
     A PC running Windowsr 95, Windows for Workgroups
     3.11, or Windows NTÖ 3.51 that you use to set up,
     start, stop, and monitor the ServerBench tests.
     The controller, unlike the clients, does not
     affect the server's overall score. You install
     ServerBench's controller program on the
     controller.

     Clients
     One of several PCs running Windows 95 or Windows
     for Workgroups 3.11. The clients are the ones
     that actually run the ServerBench tests and send
     requests for work to the server. You install
     ServerBench's client program on each client in
     your testbed.










     ServerBench on
     OS/2 Warp Server



     Here's some specific information about how ServerBench
     3.0 works on OS/2 Warp Server.

What's new about ServerBench on OS/2 Warp Server

     ServerBench 3.0 on OS/2 Warp Server contains several
     changes from the previous version of ServerBench on OS/2.
     They include:
       ServerBench now supports both Windows 95 clients and
       Windows for Workgroups 3.11 clients. Previous versions
       of ServerBench only supported Windows for Workgroups
       clients.
       ServerBench for OS/2 now uses TCP/IP as the network
       transport. Previous versions of ServerBench for OS/2
       used NetBIOS. TCP/IP provides better performance and
       more flexible client configurations. The ServerBench
       OS/2 controller and client now support any TCP/IP stack
       that is Winsock 1.1 compliant. For more information
       about the TCP/IP stacks ServerBench accepts, see
       Chapter 3.
       NOTE:   ServerBench doesn't supply any network interface
            hardware or software. You must supply that yourself.
     For quick summary of all of ServerBench 3.0's new
     features, see the section "What's New in ServerBench 3.0"
     in the Understanding and Using ServerBenchr 3.0 manual.

ServerBench's structure on OS/2 Warp Server

     ServerBench takes advantage of the multi-threading
     capabilities of OS/2 Warp Server by using multiple
     "service" threads to handle requests from the clients.
     On OS/2 Warp Server, ServerBench uses one service thread
     per client. ServerBench starts a thread for each client
     that connects to the server. This thread will handle that
     client's requests during the test.
     The steps that follow show the basic way in which
     ServerBench on OS/2 Warp Server handles client/server
     transactions. (For simplicity's sake, we're only listing
     the general steps and omitting the details.)
     1.Once you've started the controller, execute the
       ServerBench program on the OS/2 Warp Server. The
       ServerBench application creates a master thread, which
       establishes a connection with the controller.
     2.The master thread  listens for connections from the
       clients.
     3.When you start ServerBench on a client, the client
       connects with the master thread on the server.
     4.The master thread creates a service thread for that
       client. The master thread turns control of the client
       over to the service thread. The client and the service
       thread maintain their connection for the duration of
       the test.
     5.Steps 3 and 4 repeat until all the clients are running
       the ServerBench client program and each client has its
       own service thread.
     6.After all the clients are connected, the controller
       sends the mix to the master thread.
     7.The master thread gives the mix information to the
       service threads and those threads send the mix
       information to the clients.
     8.Once all the clients have received the mix information,
       each client sends a request to its service thread to
       initialize it for the test. The service threads
       allocate the memory required for the tests and create
       each client's test data file on the server.
     9.After the initialization ends, the clients begin the
       test. While the test executes, the clients send
       requests to the server.
     10.       The client's service thread executes a request
       on the server and then returns the reply to the client.
     11.       When the test completes, the clients send their
       results to the service threads.
     12.       The master thread gets the results and sends
       them to the controller.
     13.       If  you've configured the controller to pause
       between mixes, Steps 2 through 12 continue until all
       the mixes end. If you didn't specify the pause feature,
       only steps Steps 6 through 12 repeat.
     14.       Now, if you choose quit at the controller, the
       clients disconnect from the server, which frees up
       their service threads. Once all the clients disconnect,
       the server and controller applications shut down.
     In this model, the client keeps the same service thread
     as long as the client is connected to the server.

        End of "ServerBench on OS/2 Warp Server"








     Chapter 1 ~
     The Installation Overview



     This chapter gives you the basics of what you need to do
     before you install ServerBench. It contains a complete
     list of ServerBench's hardware and software requirements
     for the server, controller, and clients. In addition, it
     provides some tips on installing ServerBench as well as a
     quick overview of the installation process.

The hardware and software requirements

     The following is a list of the hardware and software that
     ServerBench requires. We've divided the list into three
     categories: server, controller, and clients.

     The server requirements:
       OS/2 Warp Server with at least the following components
       installed:
       °  File and Print Services
       °  TCP/IP Services.
       At least 16 MB of RAM plus half a megabyte of RAM for
       each client you will run with ServerBench. For example,
       if you have 30 clients, you will need an additional 15
       MB of RAM. So your total RAM requirements in this
       example will be 31 MB.
       NOTE:   While you can run ServerBench on servers with
            less RAM, the paging activity caused by the limited
            memory will lower your scores.
       Approximately 2 MB of free space on your hard disk for
       the ServerBench software. You will need additional free
       space for each client. The amount of free space you
       might need will vary based on the number of clients you
       include in each test and the initial size of the disk
       test file for each client. ServerBench's standard test
       suites use 20 MB data files for the disk tests.
       This means that, if you have 50 clients and the initial
       size of the disk test file for each client is 20 MB,
       you will need 50 * 20 MB, or 1000 MB, of additional
       free disk space. If your mixes include the Append test,
       then you will need even more free disk space.
       One or more network interface cards and their drivers.
       NOTE:   Make sure you have the most current network
            adapter and disk controller drivers installed. Check
            with the vendor who supplied your drivers to make
            sure you're using the most recent ones.

     The controller requirements:
       Either Microsoftr Windowsr 95, Windows for Workgroups
       3.11, or Windows NTÖ 3.51 with an x86-compatible
       processor. If you're using Windows for Workgroups,
       you'll also need
       MS-DOSr 5.0 or later.
       Microsoft Excel 5.0 for Windows or later. If your
       controller is running Windows for Workgroups, you need
       to include the Excel directory in the PC's PATH
       statement. For information on the PATH statement, refer
       to your user's manual.
       An 80486 (or compatible) or higher processor.
       A minimum of 8 MB of RAM.
       About 10 MB of free space on your hard disk. This
       includes about 3.5 MB for the ServerBench software, 500
       KB for the standard test suites, about 5 MB for
       documentation, and additional space for ServerBench to
       generate its results files. (The amount of free space
       you'll need will vary based on the size and number of
       results files you accumulate.)
       A network interface card and driver.
       The Winsock 1.1-compliant TCP/IP software and hardware
       components your network system needs in order for the
       server, controller, and clients to communicate with
       each other.
       A high resolution video adapter. ServerBench will work
       on any video adapter with a horizontal resolution of at
       least 800 pixels and a vertical resolution of at least
       600 pixels. For the controller, we recommend you have a
       15-inch or larger monitor.
       A CD-ROM reader. (You don't need to have one attached
       to the controller, but you do need to have one
       somewhere if you are getting your installation files
       off of the Ziff-Davis Server Benchmarks CD-ROM.)

     The client requirements :
       Either Microsoft Windows  95 or Windows for Workgroups
       3.11. If you're using Windows for Workgroups, you'll
       need MS-DOS 5.0 or later.
       NOTE:   Unlike the controller, the client doesn't work on
            Windows NT. There is a problem in the Windows NT 16-
            bit timer emulation.
       An 80386 (or compatible) or higher processor.
       8 MB of RAM.
       On each client, approximately 1 MB of free space on the
       client's hard disk to install ServerBench.
       A network interface card and its driver.
       The Winsock 1.1-compliant TCP/IP software and hardware
       components your network system needs in order for the
       server, controller, and clients to communicate with
       each other.
       A 9-inch or larger VGA monitor (either monochrome or
       color).

Set up your system before you install

     If you want to run ServerBench, you'll need at a minimum,
     a network applications server connected to two PCs, one
     of which is your controller and the other is your client:
       The server is a PC-based system running OS/2 Warp
       Server. ServerBench can test only one server in a
       network at a time.
       The controller is a PC running Microsoft Windows 95,
       Windows for Workgroups 3.11, or Windows NT for x86-
       compatible processors. You start test suites and
       monitor the test run from the controller. The
       controller does not run any tests.
       The clients are PCs running Microsoft Windows 95 or
       Windows for Workgroups 3.11. These are the PCs that
       actually send the transaction requests to the server.
     You'll want to make sure your ServerBench test system is
     set up correctly before you begin the actual
     installation. This means you need to have the following
     items installed:
       Your OS/2 Warp Server operating system on your server.
       Microsoft Windows 95, Windows for Workgroups 3.11, or
       Windows NT for x86-compatible processors and Microsoft
       Excel 5.0 or higher on your controller.
       Microsoft Windows 95 or Windows for Workgroups 3.11 on
       each of your clients.
       The TCP/IP software and hardware components your
       network system needs in order for the server,
       controller, and clients to communicate with each other.
       This software must be up and running before you start
       ServerBench on the controller and clients.
       NOTE:   ServerBench does not provide any network
            software.

Create a test network for ServerBench

     You should always create a closed, test network for
     ServerBench. By test network, we mean one that other
     people are not using and that has only what it needs
     loaded. Running ServerBench on a test network is one of
     the most important things you can do to improve your
     results.
     If you run ServerBench on a production network, you'll
     probably wind up with some users who are very annoyed
     about the way performance on the server has degraded. The
     combination of the traffic your regular users generate
     and the traffic ServerBench generates produces
     bottlenecks (i.e., congestion) that slows down the server
     and, more importantly from the ServerBench standpoint,
     causes your server's scores to worsen.

Keep the background activity to a minimum

     In addition to using a test network for ServerBench,
     you'll also want to make sure you don't have any other
     non-critical applications running on the server or the
     clients when you execute ServerBench. You don't want to
     be doing anything else while ServerBench is running on
     the server or the clients.
     If you execute ServerBench with background applications
     running, such as screen saver programs, you run the risk
     of distorting your results or causing problems for
     ServerBench as it tests the server.

Getting the ServerBench files to the right machines

     You can install ServerBench from:
     ·  The Ziff-Davis Server Benchmarks CD-ROM. The server
       files are in the directory \SB30\OS2WS\SERVER, the
       controller files are in \SB30\OS2WS\CONTROLR, and the
       client files are in \SB30\OS2WS\CLIENT.
     ·  A network directory.  This directory should contain
       three subdirectories: one each for ServerBench's server
       files, controller files, and client files. If you
       downloaded ServerBench from ZD Net, these subdirectories
       should contain the files you downloaded. You'll need to
       expand the controller self-extracting executable
       OS2WSCO.EXE and client self-extracting executable
       OS2WSCL.EXE before you can install the controller and
       client programs. Simply copy the server file OS2WSS.EXE
       to a ServerBench directory you create on the server and
       expand it then.
     ·  A set of installation diskettes you make. You'll need
       one diskette each for the server and client files and two
       diskettes for the controller files. If you like, you can
       use the MAKEBAT.EXE utility to create the diskettes. See
       the README.TXT file in the directory \DISKETTE\SB30\OS2WS
       on the CD-ROM for information on how to use that utility.

The installation process (in brief)

     When you install ServerBench, you install files on two
     types of machines: a server and the controller/client
     PCs. For specific information on which files each machine
     needs, see the installation chapter for that machine. For
     a quick summary of the installation steps, see the next
     section.

     The basic installation steps
     The following is a very brief summary of what you're
     going to do to install ServerBench. This is just an
     overview of the steps you'll need to follow once you've
     made sure your system meets all the ServerBench hardware
     and software requirements. Detailed instructions for
     installing ServerBench on your server are in Chapter 2;
     your controller, Chapter 4; and your clients, Chapter 5.
     1.Install ServerBench on your server. To do this:
       a.If you're running OS/2 LAN Server, you'll need to
          rename the STARTUP.CMD file and set the cachesize
          parameter and useallmen parameter in the HPFS286.INI
          file.
       b.Create the ServerBench main directory. You might
          call it \SB30.
       c.Change to the ServerBench directory you just
          created.
       d.Copy OS2WSS.EXE from the CD-ROM, from a networked
          drive, or from a server installation diskette you
          created into your ServerBench directory.
       e.Execute OS2WSS.EXE in the ServerBench directory on
          your server.
       f.Optionally, create directories for the disk test
          data files (if you decide you don't want to use
          ServerBench's default of having the directories in
          the installation directory). If you perform this
          step, you'll need to go to the Mix Definition window
          on the controller and change the path names to these
          directories.
       See Chapter 2 "Installing ServerBench on Your Server"
          for more information.
     3.Make sure you have a Winsock 1.1 compliant TCP/IP stack
       installed on the controller and the clients.
       Optionally, set up multiple network interface cards (if
       your server had more than one network interface card).
       See Chapter 3 "Setting TCP/IP Up on the Controller and
       Clients" for more information.
     4.Install ServerBench on the controller.
       a.Execute SETUP.EXE from the controller directory on
          the CD-ROM, from a networked drive, or from the
          controller installation diskettes you created.
          SETUP.EXE automatically creates a ServerBench
          directory on the controller and installs the
          controller files there. The default name for this
          directory is C:\SB30, but you can give it any name
          you choose. If you're running Windows 95 on your
          controller, the SETUP.EXE program creates a shortcut
          to your controller program, which it places in a
          Ziff-Davis Benchmarks program group. If you're
          running Windows for Workgroups or Windows NT, the
          SETUP.EXE program creates a ServerBench icon in the
          Ziff-Davis Benchmarks program group. (If you don't
          have this program group, ServerBench creates it as
          well.)
       b.Check to make sure your controller can talk to the
          server.
       c.Check your Excel setup to make sure it has all the
          features ServerBench needs.
       See Chapter 4 "Installing ServerBench on Your
          Controller" for more information.
     4.Install ServerBench on the clients.
       a.Execute SETUP.EXE from the client directory on the
          CD-ROM, from a networked drive, or from a client
          installation diskette you created. SETUP.EXE
          automatically creates a ServerBench directory on the
          client and installs the client files there. The
          default name for this directory is C:\SB30, but you
          can give it any name you choose. If you're running
          Windows 95 on the client, the SETUP.EXE program
          creates a shortcut to the client program, which it
          places in a Ziff-Davis Benchmarks program group. If
          you're running Windows for Workgroups, the SETUP.EXE
          program creates a ServerBench icon in the Ziff-Davis
          Benchmarks program group. (If you don't have this
          program group, ServerBench creates it as well.)
       b.The SETUP.EXE program will also ask you for the
          client name. If you want to use the client
          configuration file we provide, name each client
          sequentially beginning with c1 and continuing up to
          c60. Remember, each client must have a unique name.
       c.If you choose not to use the default CLIENT.CFG file
          that comes with ServerBench, create or modify your
          own CLIENT.CFG file and place it on each client.
       d.Check to make sure your client can talk to the
          server.
          See Chapter 5 "Installing ServerBench on Your
            Clients" for more information.

                     End of chapter


















     _Chapter 2 ~
     Installing ServerBench on Your Server



     This chapter steps you though the process of installing
     ServerBench on your server.

Step 1: Check your server's hardware and software

     Check the list of server requirements in Chapter 1 to
     make sure your server meets ServerBench's software and
     hardware requirements.

Step 2: Modify your server's setup

     We recommend that you make the following modifications to
     your OS/2 Warp Server configuration in order to get the
     best performance.
     ·  Disable the start up of the server and requester
       process during boot. You can do this by renaming the
       STARTUP.CMD file in the root directory to STARTUP.SAV. If
       you don't make this change, ServerBench will compete with
       the LAN Server requester and server processors for
       resources.
     ·  Adjust the cachesize parameter in the HPFS386.INI
       file. You can use the following formula to determine the
       optimum cachesize for use with ServerBench:
       cachesize = y - ((x * 500) + 12288)
       where:
       y equals the total system memory in Kbytes.
       x equals the total number of clients in the test.
       For example, if you have a server with 128 Mb of RAM
       and you're testing with 60 clients,  you would use the
       following formula:
       cachesize = 131072 - ((60 * 500) + 12288)
       which gives you a cache size of 88784. To set your
       cache size, you'd enter the line:
       cachesize = 88784
     ·  Set the useallmem parameter in the HPFS386.INI file
       to YES. This allows OS/2 to use memory above the 16 MB
       boundary.
       useallmem = yes
        NOTE:  You can only set this option if you have a 32-bit
            disk controller.

Step 3: Install the server files

     To install ServerBench's server files, you'll need to
     create a ServerBench directory on your server and run the
     self-extracting server executable OS2WSS.EXE. This
     executable places ServerBench's server files in the
     directory.
     Here're the steps for installing the server files.
     1.Create a ServerBench installation directory on your
       server.  We suggest you call the directory \SB30. For
       example, if your server is on drive F, you'd enter:
       F:
       MD \SB30
               Tip:
               The standard test suites create the disk test
               data files in ServerBench's installation
               directory.  So, when you create an installation
               directory, make sure you have enough space on
               the volume to accommodate the disk test data
               files (about 20 MB per client). If you want the
               test suites to create the disk test data files
               in a different directory, you'll need to modify
               the path names in the Mix Definition Window. See
               the section "Create directories for data files
               (optional)" later in this chapter for more
               information.

     3.Change to ServerBench directory \SB30 you just created
       by entering:
       CD \SB30
     4.Copy the OS/2 Warp Server ServerBench server executable
       OS2WSS.EXE to this directory.
       NOTE:   To make the examples easier to read, we specify
            certain drive designations, such as D for a CD-ROM
            drive. Make sure you use the correct drive
            designations for your system.
       ·  If you're installing from a CD-ROM:
            Put the CD-ROM in the correct drive and copy
            ServerBench's self-extracting server program to
            the ServerBench directory on your server. For
            example, you might enter the following command:
            COPY D:\SB30\OS2WS\SERVER\OS2WSS.EXE
       ·  If you're installing from a network drive:
            Copy ServerBench's self-extracting server program
            to the ServerBench directory on your server. For
            example, if the server program is in a directory
            called OS2WS on your G drive and you want to move
            it to a server directory on your F drive, you
            might enter the following commands:
            COPY G:\OS2WS\OS2WSS.EXE
       ·
          If you're installing from an installation diskette you
          created:
            Put the diskette in the correct drive and copy
            ServerBench's self-extracting server program to
            the ServerBench directory on your server. For
            example, if your diskette drive is A, you might
            enter the following command:
            COPY A:\OS2WSS.EXE
     5.   From the ServerBench directory on your server, run
       the self-extracting server executable OS2WSS.EXE. Enter
       the command:
       OS2WSS
             Tip:
             OS2WSS.EXE is a self-extracting archive that
             requires you to have DOS support enabled on your
             server. If you can't execute the file on your
             server, you must either set PROTECTMODEONLY = NO
             in your CONFIG.SYS file or extract the files on a
             DOS machine and then copy them to the server.
     When you execute this file, it extracts ServerBench's
     server files and places them in the current directory.
     You should now have all the server files you need in your
     ServerBench  directory on the server you're planning to
     test.
             Tip:
             Now that you've expanded OS2WSS.EXE, you can
             delete it. You no longer need this file.


Step 4: Verify your installation

     After you execute the OS2WSS.EXE file, you need to make
     sure the installation worked correctly and you have all
     the files you need in the \SB30 directory on your server.
     To do this, use the DIR command to display the contents
     of the directory.  Your directory should look like this:
       SVR.EXE
       SVB_SEED.DAT
       SVB_PROC.DAT
     ServerBench uses or creates the following files on the
     server when it runs. These files include binary
     executables and data files. You place the permanent files
     on the server during installation. Different processes
     create temporary files as you run ServerBench.
     Binary executable files:
       SVR.EXE.  This is the ServerBench application program.
       You execute this file to run ServerBench on the
       server..
     Data files:
       SVB_SEED.DAT. This is a 1 MB data file ServerBench uses
       to create client data files for the disk tests.
       SVB_PROC.DAT. This is a 350 KB data file ServerBench
       uses when running a mix with the processor test.
       Data files.  These are temporary files that ServerBench
       creates when it executes a mix with transactions
       containing disk tests. ServerBench normally deletes
       these files at the end of a ServerBench session. If the
       server hangs or crashes at any point after these files
       have been created, you'll need to delete them manually.
       The size of the data files depends on the value
       specified for the Disk test file initial size
       parameter, which you enter at the Mix Definition window
       when you create a mix. The standard system suite uses
       20 MB data files for each client.
     Text file:
       SVR.TXT. This is a file the ServerBench application
       recreates each time you execute ServerBench. It
       contains the version numbers for the program, the
       operating system, the client software, and the server
       disclosure. In addition, it contains the client name,
       the client ID number, the group number, an index number
       starting with 0, and the network address for each
       connected client. ServerBench creates the SVR.TXT file
       when you execute SVR.EXE.

Step 5: Set up the TCP/IP addresses

     For the ServerBench server to communicate with the
     controller and clients, you must set up IP addresses for
     the server, controller, and clients. This section lists
     the instructions for setting up the IP address for the
     server.  (Chapter 3 contains instructions on setting up
     the IP addresses on the controller and clients.)
      To set up the IP addresses on OS/2 Warp Server:
      1.  Run the TCP/IP configuration utility TCPCFG.EXE on
       the server.
     2.   From the Network panel, enter an IP address for each
       network card in the server that you plan to use.  Be
       sure to enable the interface for each adapter. You'll
       need to set the same IP addresses that you set on the
       server on the clients as well (see Chapter 3 for
       information on how to identify the server IP addresses
       to the client).
     3.   Next, you need to add the controller's name and IP
       address to the server's hosts file.
       a.Select the "Hostnames" tab in the TCP/IP
          configuration utility.
       b.Select page two.
       c.Select the Add button to add the controller's name
          and IP address to the hosts file.
               Tip:
               We recommend you use the name controller for in
               the hosts file. If you use a different name for
               your controller PC, you'll need to enter that
               name each time you enter the ServerBench command
               line.


Step 6: Make sure the machines are talking

     Before you move on, it's a good idea to make sure your
     network is working correctly. To do this, use the  ping
     utility that comes with OS/2 Warp Server. If you have
     already installed TCP/IP on your controller and clients,
     you can use this utility to see if your server can talk
     to these machines. If you haven't installed TCP/IP on
     your clients and controller, you'll need to wait until
     you complete your TCP/IP installation before you can
     perform this step.

Create directories for data files (optional)

     If a mix contains disk tests, ServerBench creates a data
     file on the server for each client running that mix. By
     default, ServerBench's standard mixes put the client data
     files in the ServerBench installation directory. However,
     you can tell ServerBench to create these files in another
     directory by including the path name to that directory
     when you create the test mix.
             Reminder:
             Whether you specify a separate directory for the
             test data files or use the default directory, you
             need to make sure ServerBench has enough space to
             create these files. To calculate how much space
             ServerBench needs, multiply the number of clients
             running the mix by the size of the disk files as
             specified by the Disk Test File Initial Size
             parameter. (You set this parameter at the Mix
             Definition window; see Understanding and Using
             ServerBench 3.0 for more details.) Thus, if you
             have 30 clients and the initial size of the disk
             files is 1 MB, you'll need 30 MB of space in the
             directory where ServerBench creates these files.
     If you don't use the default path names for the data
     files, you'll need to create those directories before you
     run any mixes containing disk tests. For example, if you
     create a mix and specify \sb30\data\data1 and
     \sb30\data\data2 as the path names of the data files for
     the first two clients, you must create the directory data
     before you run the mix.
     To change the data file path names, you'll need to
     install ServerBench on the controller and start
     ServerBench. From the main ServerBench window, choose the
     Create or Modify Test Suites button. From the Create or
     Select Test Suite dialog box, choose the test suite you
     want to modify and click on OK. From the Mixes in Test
     Suite dialog box, highlight the mix you want to edit and
     click on the Edit button. This takes you to the Mix
     Definition window. Once you change the path names in one
     mix, you can apply that change to all the mixes in that
     test suite by choosing the Advanced menu and selecting
     the Copy mix fields across this suite option. At the
     Duplicate Mix Fields Across Suite dialog box, click on
     the Pathnames option and then click on OK. For detailed
     information on modifying mixes, see Understanding and
     Using ServerBenchr 3.0.

                     End of chapter









     Chapter 3 ~
     Setting TCP/IP Up on the Controller and Clients



     Both the controller and the clients use TCP/IP to
     communicate with the server. This chapter gives you some
     guidelines on how to set up TCP/IP on the controller and
     client PCs. It also provides an example of how you set up
     multiple network interface cards (NICs) on your server.
             Reminder:
             You'll need to make sure the IP (or Internet)
             addresses are set up correctly for the
             controller and the clients. Each PC you use in
             the ServerBench test must have a unique IP
             address. The PC gets its IP address during the
             OS/2 Warp Server and client TCP/IP stack
             installation. You'll need to include the
             controller's IP address when you edit the hosts
             file on the server. For more information on IP
             addressing, see your OS/2 Warp Server and TCP/IP
             manuals.

Options for setting up TCP/IP

     The server, controller, and clients communicate via the
     TCP/IP protocol. ServerBench accepts any TCP/IP protocol
     that is Winsock 1.1 compliant. Here are some general
     guidelines for installing your TCP/IP stack on PCs
     running Windows 95 or Windows for Workgroups.
             Tip:
             Because a variety of TCP/IP stacks are Winsock
             1.1. compliant, we can't give you detailed
             instructions on how you should set up your version
             of TCP/IP. These are some general tips. For
             detailed instructions, please consult the
             documentation for your system's TCP/IP protocol.



     Installing a Microsoft Windows 95 TCP/IP stack
     From the Network Icon in the Control Panel:
     1.Open the Network icon in the Control Panel and  choose
       Add -> Protocol -> Microsoft -> TCP/IP
     2.Choose OK to add the protocol.
     3.From the Network window highlight "TCP/IP" and choose
       Properties.
     4.From the TCP/IP Properties window, choose the IP
       Address folder. Make sure you select "Specify an IP
       address."
     5.Now edit the hosts file in the Windows 95 installation
       directory to include the server's IP address. The
       Windows 95 TCP/IP stack needs this information so that
       the controller can talk to the server.
       Generally, you can edit the hosts file by executing the
       NOTEBOOK.EXE application and opening the hosts file in
       the Windows 95 installation directory (for example,
       \windows\hosts). If the hosts file doesn't exist,
       you'll need to create it.
       When the hosts file is open, add the line:
         xxx.xxx.xxx.xxxserver
       where
          ·  xxx.xxx.xxx.xxx  is the IP address of your server.
          ·  server is the name you use for your server.

     Installing a Windows for Workgroups 3.11 TCP/IP stack
     To install the TCP/IP stack on Windows for Workgroups,
     you'll need to purchase Microsoft's TCP/IP-32 stack. We
     recommend that you upgrade the stack to version 3.11a.
     You'll find this update on the Microsoft FTP server. The
     files INDEX.TXT and UPDATE.TXT should contain
     instructions for how to download version 3.11a and how to
     use it to upgrade the Microsoft TCP/IP-32 stack.
     Once you've installed the Microsoft TCP/IP-32 stack,
     you'll need to set two additional attributes:
     ·  The IP address of the machine on which the stack is
       installed.
     ·  The server's IP address in the hosts file on the
       Windows for Workgroups PC.
     You probably set the IP address of the machine with the
     TCP/IP stack when you installed TCP/IP. If you didn't or
     if you need to change it, then:
     1.From the Network group, choose the Network Setup icon.
     2.Choose the Drivers button.
     3.Choose NetWork Drivers. You'll see information on your
       network interface card and the network protocols used
       on that NIC.
     4.Select TCP/IP-32 3.11.
     5.Choose the Setup button. In the menu that appears,
       you'll be able to set up your IP address.
     You can generally edit the hosts file by executing the
     NOTEBOOK.EXE application and opening the hosts file in
     the Windows for Workgroups installation directory (for
     example, \wfw\hosts). When the hosts file is open, add
     the line:
         xxx.xxx.xxx.xxxserver
     where
     ·  xxx.xxx.xxx.xxx  is the IP address of your server.
     ·  server is the name you use for your server.
             Tip:
             If the hosts file doesn't exist, you'll need to
             create it. One way to create this file is by
             editing the sample file in the Windows
             installation directory (for example,
             \wfw\hosts.sam) and using the name hosts when you
             save the file.


     Installing an OnNet 2.0 for Windows TCP/IP stack
     You'll find the details on how you install OnNet 2.0 on
     PCs running Windows 95 and Windows for Workgroups in the
     Advanced User's Guide: OnNet for Windows and PC/TCP for
     DOS Network Software. You must use this information when
     you install OnNet 2.0. In addition to that information,
     here're some general guidelines:
     ·  Choose either the Express or Custom installation
       method.
·  If you choose the Express installation method, you'll
automatically get the "virtual device driver" (VxD)
implementation of the PC/TCP kernel.
·  If you choose the Custom installation method, you'll
need to select Windows (VxD Kernel) at the Network
Connectivity dialog box. By choosing this option, you'll
get the "virtual device driver" (VxD) implementation of
the PC/TCP kernel. This implementation uses less memory
and provides better performance in Windows than the
"terminate-and-stay-resident" (TSR) implementation of the
PC kernel does.
·  If you choose the Custom installation method, you can
omit the optional PC/TCP components.
             Tip:
             We recommend you upgrade your OnNet 2.0 software
             by obtaining the latest winsock.dll from FTP
             Software. The version of OnNet for Windows Version
             2.0 that we used in our testing contained a bug
             that caused our tests to fail frequently. The
             latest winsock.dll resolved this problem.  You can
             contact FTP Software for details on how to get
             this file.
             In addition, there's a problem in some versions of
             the VXDPCTCP.386 file in OnNet 1.1 and 2.0 that
             causes page faults. Make sure that the version you
             have of this file has the date: 9/16/94 10:11:22
             a.m (or later).
     When you've got OnNet installed, you'll need to set two
     additional attributes:
     ·  The IP address of the machine on which the stack is
       installed.
·  The server's IP address in the hosts file on the PC.
     You probably set the IP address you installed OnNet. If
     you didn't or if you need to change it, then:
     1.From the WinApps Program group, choose the Configure
       icon.
     2.From the Config dialog box, choose Internet Addresses.
     3.In the dialog box that appears, select your IP address.
     Now you'll need to modify the hosts file in the OnNet 2.0
     directory to add a line containing the server's IP
     address. Usually, you can execute the NOTEBOOK.EXE
     application and open the hosts file in the OnNet 2.0
     directory. If the hosts file doesn't exist, you'll need
     to create it.
     When the HOSTS file is open, add the line:
         xxx.xxx.xxx.xxxserver
     where
     ·  xxx.xxx.xxx.xxx  is the IP address of your server.
·  server is the name you use for your server.
     Now you'll need to edit the file pctcp.ini so that it
     contains the full path name to your HOSTS file. You'll
     find the file pctcp.ini in your OnNet 2.0 directory.
     You'll need to add the path name to the [pctcp kernel]
     section of the pctcp.ini file. For example, if your OnNet
     2.0 directory is called  c:\onnet20, then you'll edit the
     file c:\onnet20\pctcp.ini. Go to the [pctcp kernel]
     section and add the line:
       host-table=c:\onnet20\hosts

     General Guidelines for any third-party TCP/IP stack
     Basically, once you've got a TCP/IP stack correctly
     installed, you'll need to set two additional attributes
     in order to run ServerBench:
     ·  The IP address of the machine on which the stack is
       installed. You must set the machine's IP address before
       it will work with ServerBench. Sometimes you'll set this
       attribute when you install the TCP/IP stack. If you don't
       set it then, you'll probably be able to set it using a
       graphical utility that comes with the stack or by
       manually editing a .INI file. See the documentation that
       comes with your TCP/IP software for more information.
·  The server's IP address in the hosts file on the PC.
Doing this enables the ServerBench client application to
talk to the server. Normally, you'll simply add a line to
the hosts file to include the server's IP address. We
recommend that you use the default ServerBench naming
scheme of:
         xxx.xxx.xxx.xxxserver
       The location and name of the hosts file is usually
       specified in a .INI file. In general, the name of the
       file is hosts and it resides in the same directory
       where the stack was installed.

Make sure the TCP/IP stack is installed correctly

     Before you move on, it's a good idea to make sure you've
     installed your TCP/IP stack correctly. To do this,  you
     can use the ping utility that comes with the stack. If
     you haven't already rebooted your PC, do so now. Once the
     machine has rebooted, use the ping utility to contact
     the server.  If the ping utility succeeds, then the
     server and the PC should be able to communicate when you
     run ServerBench. You should perform this check from the
     controller PC and each client PC.




Setting up multiple NICs

     This section contains an example of how to set up your
     server when it has more than one network interface card
     (NIC). You can also see from this example how much easier
     setting up ServerBench is if you use the default
     ServerBench naming conventions of controller for your
     controller and server for your server. Let's assume the
     server has four network segments with the following IP
     addresses.
          NIC1  192.0.1.100
          NIC2  192.0.2.100
          NIC3  192.0.3.100
          NIC4  192.0.4.100
     Your controller, which is attached to segment NIC1, has
     the following IP address:
          192.0.1.101
     You have eight clients, which are attached in the
     following way:
     NIC1 c1 192.0.1.1
          c5 192.0.1.2
     NIC2 c2 192.0.2.1
          c6 192.0.2.2
     NIC3 c3 192.0.3.1
          c7 192.0.3.2
     NIC4 c4 192.0.4.1
          c8 192.0.4.2
     When you use the ServerBench 3.0 default naming scheme,
     here's how you need to set up your files for the server
     and the clients:
     ·  Server. You must have the following entry for the
       controller in the hosts file:
       192.0.1.101 controller
     ·  Clients. For c1 and c5, you must have the following
       entry in the client's TCP/IP stack's hosts file:
       192.0.1.100 server
       For c2 and c6, you need this entry:
       192.0.2.100    server
       For c3 and c7, you need this entry:
       192.0.3.100 server
       For c4 and c8, you need this entry:
       192.0.4.100    server
     Because you're using the default names, you don't have to
     modify the client command line. Also, you don't need to
     specify the name for the controller when you start the
     ServerBench server executable.
     However, if clients c1 and c5 used a different naming
     scheme for the server,  such as:
       192.0.1.100 foobar
     you'd have to modify the client command line so that it
     specified the server name. See the section "Modifying the
     client command line" in Chapter 5 for more information.

                     End of chapter








Chapter 4 ~
     Installing ServerBench
     on Your Controller



     This chapter steps you through the process of installing
     ServerBench on your controller.


Step 1: Check the controller's hardware and software

     Check the list of controller requirements in Chapter 1 to
     make sure your server meets ServerBench's software and
     hardware requirements.

Step 2: Install the controller files

     You can easily install the ServerBench's controller files
     by running the controller SETUP.EXE program. To execute
     SETUP.EXE from Windows 95 choose Start -> Run and enter
     the path name to SETUP.EXE (for example
     D:\SB30\OS2WS\CONTROLR\SETUP). To execute SETUP.EXE from
     Windows for Workgroups, use the Run option from the
     Windows File Manager or Program Manager.
     You can run SETUP.EXE from:
     ·  The Ziff-Davis Server Benchmarks CD-ROM (the directory
       \SB30\OS2WS\CONTROLR).
·  A directory on a network drive where you copied the
controller files.
·  Installation diskettes you created.
     The screens that SETUP.EXE displays are self-explanatory.
     They will ask you for the installation directory and
     client name. Just follow the prompts and you'll have
     ServerBench installed.
     NOTE:  Don't install ServerBench 3.0 on top of
          ServerBench 2.0. Always install ServerBench in a new
          directory.
     If you'd like step-by-step instructions for installing
     ServerBench's controller files, read the next section.

     Step-by-step instructions for installing ServerBench on
     the controller
     Here're the details on how you install ServerBench's
     controller files. If you have questions during the
     installation procedure, choose the Help button. Remember,
     you must be running Windows 95, Windows for Workgroups,
     or Windows NT 3.51 when you install ServerBench on the
     controller.
     1.At the PC you will use as the ServerBench controller,
       execute the controller SETUP.EXE file.
       NOTE:   In these examples, we use the designations A for
            a diskette drive, D for a CD-ROM drive, and F for a
            network drive. You should use the correct
            designations for your drives.
       If you're installing from:
         The CD-ROM, put the CD-ROM in the correct drive and
          enter:
         D:\SB30\OS2WS\CONTROLR\SETUP
       ·  A network drive, enter the path name to SETUP.EXE. For
          example:
         F:\SB30\OS2WS\CONTROLR\SETUP
         Installation diskettes you created, put the first
          diskette in the correct drive and enter:
         A:SETUP
       ·  ServerBench files downloaded from ZD Net onto the
          controller PC, enter the path name to the controller's
          SETUP.EXE file.
     2.At the screen that appears, choose OK.
     3.        When the Starting ServerBench 3.0 Setup screen
       appears, click on Continue.
               Reminder:
               You can halt the installation procedure at this
               point by selecting Exit. ServerBench will then
               display a Quit screen that says the installation
               is incomplete and give you the opportunity to
               resume the installation by selecting Continue.
               To halt the installation, select Exit again.
               ServerBench will display a screen telling you
               that the benchmark has not been properly
               installed. Select OK. ServerBench will terminate
               the installation procedure and you can ignore
               the rest of these steps.

     4.In the ServerBench 3.0 Drive and Directory window,
       enter the name of the directory in which you want to
       install ServerBench. The default directory is C:\SB30.
       You can enter another directory name if you choose or
       accept the default directory.
       If you accept this directory, ServerBench will actually
       create a subdirectory called OS2WS and install the
       controller files in that directory (i.e., your
       ServerBench controller files will be in C:\SB30\OS2WS).
       This way, if you're using your test bed for more than
       one port of ServerBench, you can keep the different
       ports separate.
       NOTE:   Don't install ServerBench 3.0 on top of
            ServerBench 2.0. Always install ServerBench in a new
            directory.
     5.Select Continue to go to the next window.
       ServerBench displays a progress window so you can see
       how far along the installation is.
     6.When the installation finishes, ServerBench displays a
       window indicating that the installation was successful.
       Click on OK to end the installation process.
     During the installation, ServerBench creates a program
     group on the controller called Ziff-Davis Benchmarks. If
     you're running Windows 95, ServerBench places this group
     in Start -> Programs on the Task Bar. If you're running
     Windows for Workgroups or Windows NT, ServerBench places
     the ServerBench controller icon in the Ziff-Davis
     Benchmarks program group.
             Tip:
             If you want to change the controller properties
             and you're running Windows 95, you'll find the
             shortcut to ServerBench's controller program by
             starting the Explorer and following
             C:\windows\start menu\Programs\Ziff-Davis
             Benchmarks.
             NOTE:   This example uses windows as the name of
                  the Windows 95 directory. If your
                  installation directory has different name,
                  use that name instead.
             Select the controller shortcut and then modify the
             properties however you choose.


Step 3: Verify your installation

     After you run SETUP.EXE,  you need to make sure
     everything installed correctly and you have all the files
     you need on the controller. If everything worked right,
     you should have the following files in the \SB30\OS2WS
     directory on your controller:
       SB30A.EXE. This is the controller executable file.
       SB30B.EXE. The SBC30A.EXE file uses this executable
       when it displays the controller window.
       BWCC.DLL. This is the Borland C dynamic-link library
       (DLL) that ServerBench uses to produce the user
       interface on the controller. It does not affect your
       test results.
       SVRBENCH.XLA. This file provides the graphing and
       printing capabilities ServerBench uses in connection
       with its results spreadsheets.
       RESULTS.XLM. This is an Excel macro file that
       ServerBench uses to create its results spreadsheets.
     ·  GENERAL.HLP. This help file contains generic
       ServerBench information found in the manual Understanding
       and Using ServerBenchr 3.0 manual. This is a
       comprehensive help file for all platforms of ServerBench.
     ·  PORT.HLP. This help file contains specific information
       about setting up and using ServerBench's OS/2 Warp Server
       port. We use the manual you're currently reading to
       produce this help file.
     You should also have three subdirectories in the
     \SB30\OS2WS directory: DOCS, RESULTS, and SUITES.
       The DOCS subdirectory contains the Microsoft Word for
       Windows version of this ServerBench installation
       manual, the ServerBench 3.0 Quick Start Handbook, and
       the Understanding and Using ServerBench 3.0 manual.
       The RESULTS subdirectory is the directory where
       ServerBench by default stores its test suites results.
       (You can, however, specify different directories.)
       The SUITES subdirectory contains ServerBench's standard
       test suites. You can use these test suites when you run
       ServerBench.
       NOTE:   Ziff-Davis publications use these same suites
            when they run ServerBench and report ServerBench
            results in their reviews.

Step 4: Install the TCP/IP stack

     If you haven't already done so, now's a good time to
     install the TCP/IP stack on your controller. See Chapter
     3 "Setting TCP/IP Up on the Controller and Clients" for
     guidelines on how to do this.

Step 5: Make sure Excel can work with ServerBench

     ServerBench uses the Microsoft Excel for Windows macro
     RESULTS.XLM to display test results as Excel
     spreadsheets.
     You need to make sure Excel is set up and working
     correctly on the controller before trying to display
     ServerBench's results.
     If you followed the normal, complete Excel setup when you
     installed the application, then you shouldn't need to
     change Excel now.
             Tip:
             If you're running Windows for Workgroups on the
             controller, we strongly recommend that you include
             Excel in your AUTOEXEC.BAT file's PATH statement.
             See the user's manuals that came with your
             operating system for information on your PATH
             statement.
     For more information on how ServerBench displays results,
     see the Understanding and Using ServerBench 3.0 manual.

                     End of chapter







Chapter 5 ~
     Installing ServerBench on Your Clients



     This chapter steps you though the process of installing
     ServerBench on your clients.
     Installing ServerBench on the clients requires a little
     more thought than installing ServerBench on the
     controller does. This is because you'll need to supply a
     name for each client. This name, as well an ID number and
     group number for each client goes in the CLIENT.CFG file.
     You must make sure each client has a CLIENT.CFG file in
     its installation directory.
     We supply a CLIENT.CFG file you can use if you enter
     ServerBench's default client names. See the section "Step
     2: Select the client names and numbers" for more
     information.
     If you don't use ServerBench's default server name,
     you'll need to modify the client command line. See the
     section "Modifying the client command line" for more
     information.

Step 1: Check the clients' hardware and software

     Check the list of client requirements in Chapter 1 to
     make sure your server meets ServerBench's software and
     hardware requirements.

Step 2: Select the client names and numbers

     You'll need to supply a unique name for each client when
     you install ServerBench on that client. The client name
     must match a name in the client configuration file. The
     name you supply for the client can be up to 19
     alphanumeric characters long without any spaces or tabs.
     ServerBench doesn't care what the name is as long as it
     is unique to that client.
             Our prescription is:
             Use the naming and numbering scheme of c1 for the
             client with ID number 1, c2 for the client with ID
             number 2 and so on up to c60 for the client with
             ID number 60. These are the names we use in the
             default CLIENT.CFG file that comes with
             ServerBench.

     ServerBench will use the client name to look up the
     client's ID number and group number in the client
     configuration file. Each client must have a unique ID
     number; however, multiple clients can have the same group
     number.
     For information about client ID numbers and group
     numbers, see the section "Creating your own client
     configuration file" later in this chapter. For more
     details, see Understanding and Using ServerBench 3.0.

Step 3: Install the client files

     You can easily install the ServerBench's client files by
     running the client SETUP.EXE program.  To execute
     SETUP.EXE from Windows 95 choose Start -> Run and enter
     the path name to SETUP.EXE (for example
     D:\SB30\OS2WS\CLIENT\SETUP). To execute SETUP.EXE from
     Windows for Workgroups, use the Run option from the
     Windows File Manager or Program Manager.
     You can execute SETUP.EXE from:
     ·  The Server Benchmarks CD-ROM (the directory
       \SB30\OS2WS\CLIENT).
·  A directory on a network drive where you copied the
client files.
·  Installation diskette you created.
     The screens that SETUP.EXE displays are self-explanatory.
     They will ask you for the installation directory and the
     client name. Just follow the prompts and you'll have
     ServerBench installed.
     NOTE:  Don't install ServerBench 3.0 on top of
          ServerBench 2.0. Always install ServerBench in a new
          directory.
     If you'd like step-by-step instructions for installing
     ServerBench's client files, read the next section.

     Step-by-step instructions for installing ServerBench on a
     client
     Here're the details on how you install ServerBench's
     client files. If you have questions during the
     installation procedure, choose the Help button. Remember,
     you must be running Windows 95 or Windows for Workgroups
     when you install ServerBench on the client.
     1.At each PC you will use as a ServerBench client,
       execute the client SETUP.EXE file.
       NOTE:   In these examples, we use the designations A for
            a diskette drive,  D for a CD-ROM drive, and F for a
            network drive. You should use the correct
            designations for your drives.
       If you're installing from:
         The CD-ROM, put the CD-ROM in the correct drive and
          enter:
         D:\SB30\OS2WS\CLIENT\SETUP
       ·  A network drive, enter the path name to the client's
          SETUP.EXE program. For example:
         F:\SB30\OS2WS\CLIENT\SETUP
         An installation diskette you created, put the
          diskette in the correct drive and enter:
         A:SETUP
       ·  ServerBench files downloaded from ZD Net onto a client
          PC,  enter the path name to the client's SETUP.EXE
          program.
     2.At the screen that appears, choose OK.
     3.        Click on Continue in the Starting ServerBench
       3.0 Setup window.
                Reminder:
                You can halt the installation procedure at this
                point by selecting Exit. ServerBench will then
                display a Quit screen that says the
                installation is incomplete and give you the
                opportunity to resume the installation by
                selecting Continue. To halt the installation,
                select Exit again. ServerBench will display a
                screen telling you that the benchmark has not
                been properly installed. Select OK. ServerBench
                will terminate the installation procedure and
                you can ignore the rest of these steps.
     4.Enter the name of the directory in which you want to
       install ServerBench in the ServerBench 3.0 Drive and
       Directory  window. You can accept the default or enter
       your own directory name. The default directory is
       C:\SB30. If you accept this directory, ServerBench will
       actually create a subdirectory called TCPIP and install
       the client files in that directory (i.e., your
       ServerBench client files will be in C:\SB30\ TCPIP).
       This way, if you're using your test bed for more than
       one port of ServerBench, you can keep the different
       ports separate.
       NOTE:   Don't install ServerBench 3.0 on top of
            ServerBench 2.0. Always install ServerBench in a new
            directory.
     5.ServerBench asks you to enter the client name. Enter a
       different name for each client. We recommend that you
       use the same client names we use in the default
       CLIENT.CFG file. These names include the client ID
       number as part of the name; for example, c1, c2, c3,
       and so on.
       NOTE:   If you don't use the naming convention we use in
            the default CLIENT.CFG file, you'll need to copy
            your client configuration file to each ServerBench
            client directory. See the section "Creating your own
            client configuration file" later in this chapter for
            information on how to set up a client configuration
            file.
     6.Once you've typed in the client name, select Continue
       to go to the next window.
       The Installing ServerBench 3.0 files window appears. In
       this window, ServerBench displays information about the
       progress of the installation, such as which file it is
       copying into the ServerBench installation directory and
       how much of the ServerBench code it has installed.

       When the installation finishes, ServerBench displays a
       window indicating that the installation was successful.
     7.Click on OK to end the installation process.
     8.Repeat these steps for each PC you want to use as a
       client in the test.
     During the installation, ServerBench creates a program
     group on the client called Ziff-Davis Benchmarks. If
     you're running Windows 95, ServerBench places this group
     in Start -> Programs on the Task Bar. If you're running
     Windows for Workgroups,  ServerBench places the
     ServerBench client icon in the Ziff-Davis Benchmarks
     program group.

             Tip:
             If you want to change the client properties and
             you're running Windows 95, you'll find the
             shortcut to ServerBench's client program by
             starting the Explorer and following
             C:\windows\start menu\Programs\Ziff-Davis
             Benchmarks.
             NOTE:   This example uses windows as the name of
                  the Windows 95 directory. If your
                  installation directory has different name,
                  use that name instead.
             Select the client shortcut and then modify the
             properties however you choose.


Step 4: Verify your installation

     When you install ServerBench on a client, it places the
     following files in the \SB30\TCPIP directory:
       CLIENT.EXE. This is the executable program you use to
       connect each client to the server so that it can run
       ServerBench.
       SVB_SEED.DAT. The client uses this file for sending
       information to the server in the client-to-server
       network test.
       CLIENT.CFG. This is a sample client configuration file.
       You can use it as it is or as a model for creating your
       own CLIENT.CFG file.

Step 5: Install the TCP/IP stack

     If you have not done so now is a good time to install the
     TCP/IP stack on your client.  Please see Chapter 3
     "Setting TCP/IP Up on the Controller and Clients" for
     more information on how to do this.

Creating your own client configuration file

     Each client must have a client configuration file in its
     ServerBench installation directory. This is a text file
     that contains the client's name, ID number, and group
     number.
             Our prescription is:
             You can actually create a separate CLIENT.CFG
             file for each client. However, we recommend you
             create one file with all  the clients in it and
             then just copy that one file to each client.
     When you run SETUP.EXE, ServerBench places its default
     client configuration file, CLIENT.CFG, in that client's
     directory.
     You can use the default file or create your own client
     configuration.
     The steps for creating a client configuration file
     To create a new client configuration file:
     1.Create a text file and name it CLIENT.CFG.
               Tip:
               You can name this file anything, but we
               recommend you use the name CLIENT.CFG file. If
               you use a name other than CLIENT.CFG, you'll
               have to specify additional parameters when you
               start the client program. Otherwise,
               ServerBench will display an error message
               stating it can't find the CLIENT.CFG file.
     2.Enter the client name, client ID number, and client
       group number on a single line.
       ·  The client name can be up to 19 alphanumeric
          characters (but no spaces or tabs).
       ·  The ID number can be any unique number from 1 to 1000.
                  Tip:
                  We recommend that you number the clients
                  consecutively. Each client ID number
                  corresponds to a square in the controller
                  window's client grid. ServerBench chooses
                  the size of the client grid based on the
                  largest client number  either 77, 160, 260,
                  400, or 1,000.
                  In addition, we've found that using the ID
                  number as part of the client name is useful.
                  This is the naming scheme we use in the
                  default client configuration file where the
                  client named C1 has ID 1, C2 has ID 2, and
                  so on.
       ·  The group number can be from 1 to 50.
                  Our prescription is:
                  We go down the line and assign the clients to
                  groups 1, 2, 3, and 4. So C1 is in group 1;
                  C2, group 2; C3, group 3; C4, group 4; C5,
                  group 1; C6, group 2; and so on.
                  Just remember that, if you create a test mix
                  that specifies only certain group numbers run
                  the mix, clients in those groups need to be
                  connected to the server. If you try to execute
                  a mix where no clients with the correct group
                  numbers are running ServerBench, ServerBench
                  aborts the mix.
       Both the client name and ID number must be unique;
       however, multiple clients can have the same group
       number. Separate each item by a space or a tab. Press
       carriage return after you enter the client group
       number. For example, you might have a line that reads:
       client12     12     1
       for a client with a name of client12, an ID number of
       12, and a group number of 1.
                Reminder:
                Even if you don't plan to use the group
                number feature, you must enter all three
                arguments. ServerBench will display an error
                message if you supply a client configuration
                file that does have a client name, client ID
                number, and client group number on each
                line.
     3.Continue entering separate lines of client information
       in the file until you have a line for each client.
     4.End the file with a carriage return.
     5.Place the file in the ServerBench installation
       directory on each client.
                  Additional Information:
                  ServerBench always chooses clients with the
                  lowest ID numbers when selecting clients to
                  run a mix. If a mix uses certain groups, then
                  ServerBench checks the ID numbers of all the
                  clients within those groups and chooses the
                  clients with the lowest ID numbers.
                  For example, suppose MIX_A wants a total of
                  10 clients from groups 1, 2, 3, and 4.
                  Currently, 20 clients (ID numbers 1 through
                  20 and group numbers 1 through 5) are running
                  ServerBench. Group 1 has clients with ID
                  numbers 12, 13, 15, and 20; Group 2 has
                  clients 2, 6, 10, and 16; Group 3 has clients
                  1, 3, 7, and 5; Group 4 has clients 4, 8, 9,
                  and 11; and Group 5 had clients 14, 17, 18,
                  and 19. ServerBench would run the mix with
                  clients 1, 2, 3, 4, 5, 6, 7, 8, 9, 10. It
                  wouldn't use any clients from Group 1 because
                  that group had clients with higher ID numbers
                  than the other connected clients. It wouldn't
                  use any clients from Group 5 because that
                  group was not one of the groups specified by
                  the mix.
                  What this means to you is that, anytime you
                  have more clients connected to the server
                  than a mix needs,  ServerBench will always
                  run that mix using the same set of clients _
                  those with the lowest ID numbers. It does not
                  rotate clients and say, "hey, client 60
                  hasn't run in while; I'll give client 1 a
                  rest and let 60 take its place."
     For more information on client names and numbers, see
     Understanding and Using ServerBench 3.0.

Modifying the client command line

     When you run SETUP.EXE, ServerBench automatically creates
     a client icon with a command line that includes the
     client name you entered during the installation. If you
     use ServerBench's defaults of:
     ·  A server name of server in the HOSTS file.
     ·  A client configuration file named CLIENT.CFG.
     you won't need to change the client command line.
     However, if you change any of these values, you'll need
     to update the client command line associated with the
     ServerBench client icon. The command line uses the
     format:
     client.exe client_name -f config_file -s server_name
     where
     ·  client.exe is the executable for the ServerBench
       program.
·  client_name is the name of that client.
·  -f config_file is an optional parameter you can use to
specify the name of your client configuration file if you
don't use ServerBench's default name of CLIENT.CFG.
·  -s server_name is an optional parameter you can use to
specify the name of the server as it appears in the hosts
file if you didn't use the default name of server.
                  Additional Information:
                  To tell the client to look for a different
                  server port number, edit the services file
                  that comes with your TCP/IP stack.

     The steps for modifying the client command line
     To change the command line on a Windows 95 client:
     1.Open the Ziff-Davis Benchmarks folder and, using the
       right mouse button, click on the client shortcut icon.
     2.Using the left mouse button, click on Properties.
     3.Choose the Shortcut tab.
     4.Modify the text in the target box to reflect the name
       of the client and the command line parameters. For
       example, if you're at CLIENT4 and you're using the
       client configuration file MYCLIENT.CFG and your
       server's name is SERVER1, the text in the target box
       should look like:
       c:\sb30\tcpip\client.exe client4 -f myclient.cfg -s server1
     5.Click OK to save your changes
     To change the command line on a Windows for Workgroups
     client:
     1.From the Windows Program Manager, choose the
       ServerBench client icon (located in the
       Ziff-Davis Benchmarks program group).
     2.Select Properties from the Program Manager's drop-down
       File menu. Windows displays the Program Item Properties
       dialog box.
     3.Modify the text in the box next to command line to
       reflect the name of the client and any other value that
       doesn't use the ServerBench defaults. For example, if
       you're at CLIENT4 and you're using the name
       MYCLIENT.CFG and your server's name is SERVER1, the
       text in the target box should look like:
       c:\sb30\tcpip\client.exe client4 -f myclient.cfg -s server1
     4.Click on OK. Windows will update the command line
       associated with that client icon.

                     End of chapter








     Chapter 6 ~
     Running ServerBench



     This chapter quickly steps you through the process of
     running ServerBench's system test suite, SYS_60.TST, and
     then looking at your results.

             Reminder:
             You must agree to the License Agreement and
             register your copy of ServerBench before you run
             any tests. The License Agreement and registration
             screens appear the first time you start ServerBench
             after installing it. These screens will continue to
             appear until you agree to the License Agreement and
             register your copy of ServerBench. These screens
             are self-explanatory.


Starting ServerBench

     The following steps tell you how to run ServerBench's
     standard test suite SYS_60.TST. This test suite starts
     with 1 client and reaches a maximum of 60 clients (each
     mix adds more clients than the previous mix). By default,
     ServerBench creates the client data files for the Disk
     tests in the ServerBench installation directory on the
     server. (If you need to change the path names for the
     data files or the number of clients, edit these fields in
     the Mix Definition window on the controller.)
              Reminder:
              You must always start ServerBench on the
              controller first; the server, second; and the
              clients last.
     1.Start the ServerBench on the controller.
        a.     Start the ServerBench controller program.
          On a controller running Windows 95, choose:
          Start -> Programs -> Ziff-Davis Benchmarks ->
          ServerBench 3.0 Controller
          On a controller running Windows for Workgroups or
          Windows NT, choose the controller icon from the Ziff-
          Davis Benchmarks program group.
        b.     When the main ServerBench window appears,
          choose the Start Test button.
        c.     When the controller window appears, choose the
          Start button.
                  Tip:
                  If you get either of the following error
                  messages when you press Start Test at the
                  main ServerBench window or Start in the
                  controller window:
                   File Error: Cannot Find winsock.dll
                   Error 4: Cannot initiate network connection
                  you probably have an uninstalled TCP/IP
                  stack. You'll need to install your TCP/IP
                  stack before you can run ServerBench.

     2.Start ServerBench on the server.
                    Tip:
                    We recommend you reboot your server before
                    you run any test suites Rebooting before
                    each ServerBench session helps minimize the
                    variations in the results.
        a.     Go to the system console and change to the
          directory where you installed ServerBench.
        b.     Start the ServerBench program by entering the
          command:
         svr
          You can also use the following options on your
          command line:
         drive:\PATH\svr -c controller_name -f
          where:
          ·  drive:\PATH is the path name to your  ServerBench
            installation directory.
          ·  -c controller_name is an optional parameter  that
            tells ServerBench to use the controller you specify in
            the controller_name argument. This name must match the
            name of the controller in the server's hosts file. (See
            the section "Step 5: Set up the TCP/IP addresses" in
            Chapter 2 for more information.)
          ·  -f  is an optional parameter  that tells ServerBench
            to delete the disk test data files each time a mix ends.
            As a result, ServerBench will recreate the data files for
            each mix that includes a disk test.
     3.When the Connect Clients message appears on the
       controller window, start ServerBench on the clients.
        a.     Start the ServerBench client program.
          On a Windows 95 client, choose:
          Start -> Programs -> Ziff-Davis Benchmarks ->
          ServerBench 3.0 TCPIP
          On a Windows for Workgroups client, choose the
          client icon from the Ziff-Davis Benchmarks program
          group.
                    Tip:
                    If you get the one of the following error
                    messages (either in a pop-up box or on the
                    client screen) when you start ServerBench on
                    a client:
                    File Error: Cannot Find winsock.dll
                    Cannot initialize TCP/IP stack
                    you probably have an uninstalled TCP/IP
                    stack. You'll need to install your TCP/IP
                    stack before you can run ServerBench.

       b.After ServerBench is running on each client, return
          to the controller. You'll notice that ServerBench
          has highlighted a square on the client grid for each
          client you connected.  Click on OK in the Connect
          Clients dialog box.
     4.Answer Yes to the dialog box in the controller window
       that asks if you want to select a test suite.
     5.When the Choose Test Suites dialog box appears, go to
       the directory containing SYS_60.TST and highlight that
       test suite.
     6.Choose OK.
                Tip:
                While ServerBench has other standard test
                suites, we recommend you use SYS_60.TST. if
                you want to get an overall indication of how
                well your server performs. This system test
                suite performs a variety of tests involving
                your server's processor, disk, and network
                subsystems. If you want to determine how well
                a specific server subsystem is performing,
                you can run one of ServerBench's other
                standard test suites. The D_60.TST test suite
                performs only disk tests, the P_60.TST test
                suite performs only processor tests, and the
                N_60.TST test suite performs only network
                tests. Of course, because the client requests
                must travel across the network, the speed of
                the network has an affect on all ServerBench
                tests.

     7.At the Selected Test Suites dialog box, enter a name
       for the results file and enter any comments in the
       comments box. For example, you might name the results
       file SYS_60_1 and enter the comment: Added one
       processor for this test run. (You can also enter a path
       name for the results file in this dialog box. If you
       don't supply a path name, ServerBench will place your
       results file in the controller's RESULTS subdirectory.)
     8.Choose OK. ServerBench will start running the test
       suite. You can monitor the test run from the controller
       window.
                Tip:
                Running SYS_60.TST takes about four to five
                hours.
     9.When the test suite ends, go to the main ServerBench
       window and choose the View Results function button.
     10.       At the Select Results dialog box, choose
       SYS60_1.TLG (or whatever name you gave the results file
       for the test suite you ran) and click on OK.
                Tip:
                To keep this example simple, we're assuming
                you're using ServerBench's defaults, such as
                the Results directory. You can actually put
                your results anywhere you like. Also, we're
                just telling you how to view your results;
                we're not explaining how to use all the
                features of the View Results dialog box and
                setting up a disclosure database. For more
                information about those features see the
                ServerBench Quick Start Handbook or
                Understanding and Using ServerBench 3.0.

     11.       At the View Results window, choose the database
       snapshot file, choose the options you want, and choose
       the Worksheets (i.e., tables) you want to see. You'll
       need to click on the More button to see all of your
       options. If this is the first time you've run a test
       suite, you may want to set up the database snapshot
       file by choosing Edit Disclosure. This option lets you
       enter information about how your server and clients are
       configured and then save the information to a snapshot
       file that you can use with other sets of results run on
       the same testbed. ServerBench uses this information to
       create the server and client disclosure tables in the
       results workbook.
       NOTE:   If you want to automatically save the results
            spreadsheet, choose the option "Save Workbook with
            results name" (or the Save As option when you're in
            Excel). If you select the "Delete files" option,
            ServerBench will delete the results log files it
            uses to generate the results tables after it creates
            the results spreadsheets. Then, if you don't save
            the spreadsheet using Excel, you won't be able to
            view those results again. In addition, if you didn't
            tell ServerBench to create all the results tables,
            you won't be able to generate them.
     12.       Choose View. ServerBench launches Excel (if
       it's not already running) and displays your results as
       tables in an Excel workbook. You'll find the overall
       score for your server in Table 1: ServerBench summary.
     13.       To exit from ServerBench, quit Excel. Now
       choose the Quit button from the main ServerBench window
       (if the controller window is still open, you'll need to
       close that window).

                     End of chapter








     Chapter 7 ~
     Troubleshooting and Error Messages



     Normally, ServerBench runs without problems.
     Occasionally, however, you may encounter a problem when
     you run the benchmark. This chapter gives you some basic
     information about what to do if you do encounter a
     problem. It also lists messages you may receive when
     running ServerBench for OS/2 Warp Server and tells you
     what to do when you receive those messages.
     If you cannot resolve your problem after reading this
     chapter, write down any error message on the server,
     controller, and/or client completely, note what
     ServerBench was doing at the time you received the
     message (for example, was it initializing a mix), and
     then contact ZDBOp's ServerBench technical support as
     described in Chapter 8 of this manual.

What to check if you have problems

     If ServerBench encounters a serious problem, in most
     cases it will exit as gracefully as it can. Occasionally,
     however, ServerBench may stop running (or "hang") during
     its test. If you have problems, you should follow a few
     basic steps before you contact technical support:
       Verify that all your machines (server, controller, and
       clients) meet the hardware and software requirements
       for running ServerBench. See Chapter 1 for a list of
       hardware and software requirements. Also, check to be
       sure you've set up the machines correctly. Make sure
       your server has any necessary patches. See Chapters 2,
       3, 4, and 5 for that information.
       Verify you have no applications running in the
       background on the server or clients (such as a screen
       saver).
       If ServerBench seems to hang during a test or some
       operation and is not responding to any input, you may
       need to reboot your server, clients, and/or controller.
       Once you reboot, restart ServerBench and see if the
       problem persists. If so, contact ServerBench technical
       support at ZDBOp (see Chapter 8 "Contacting ZDBOp").




If clients are stuck in a test's R stage, check these things

     During your testing , you may hit a problem where some
     clients appear to be stuck in the run (R) stage of a test
     while others are in the blocked (B) stage. At this time,
     you may also see error messages on the server and
     controller that indicate the server could not receive
     data from or send data to one or more of its clients.
     These errors usually indicate some type of network
     infrastructure problem.  What has probably happened is
     that at least one data packet was dropped during a server-
     to-client or client-to-server transmission. This problem
     can occur for several reasons, such as:
       An old or outdated network interface card (NIC) driver
       on one or more of the clients. Check with your NIC
       supplier to make sure you have the latest driver
       available.
       A network interface card that is set to autodetect
       transmission speeds on your LAN, but does so
       incorrectly. Verify that the NIC is correctly detecting
       the speed of your network. NICs usually have status
       lights indicating the speed at which they are running.
       Verify that those status lights correctly indicating
       the speed of your network (for example, 10 Mbps or 100
       Mbps).
       A TCP/IP stack component needs to be updated. Check
       with your TCP/IP vendor to make sure you have the
       latest available versions of all these software
       components.
       A TCP/IP configuration issue. Contact your TCP/IP
       vendor, state the hardware/software platform(s) on
       which your clients are running and ask if there are any
       special configuration settings that should be changed
       or initialized.
       You may have bad hardware such as cables, network
       interface cards, hubs, and so on.
     ·  You may want to try and change the size of the TCP
       receive window on each client to 10240 bytes.  Consult
       your TCP/IP stack documentation as to how to do this.
     In addition, if you are using FTP Software's OnNet for
     your TCP/IP stack, you may want to try the following on
     each client:
     1.Upgrade the client to the latest winsock.dll.  Call FTP
       Software's technical support for instructions on how to
       do this.
     2.  Increase the size of the TCP window to 10240 bytes.
       To increase the TCP window size, add these lines to the
       pctcp.ini file on each client:
       [pctcp kernel-vxd]
         window = 10240

The way ServerBench reports errors

     ServerBench tries to report error messages on the most
     appropriate machines, which means that, in addition to
     reporting the message on the machine with the problem, it
     also reports many server and client error messages on the
     controller. This is because the controller is the machine
     you may be monitoring.
     When the controller reports an error that occurred on the
     server, it uses the following format:
       Error on server:  text:  detail
     where
       text tells you what the error is, for example, "Cannot
       open file," or "Cannot allocate memory," or "Cannot
       receive data."
       detail provides more specific information about the
       error, such as which file could not be opened, how much
       memory could not be allocated, or why data could not be
       received.
     When the controller reports an error that occurred on a
     client or that occurred on the server but pertains to a
     specific client, it uses this format:
       Error on client client-name ID:  text:  detail
     where
       client-name is the unique name assigned to client.
       ID is that client's unique identification number (the
       same number that appears in the client grid in the
       controller window).
     NOTE:  Sometimes the controller can't report an error
          that occurred on the server or a client. For
          example, if the server cannot connect to the
          controller, only the server will report the error.
          In these cases, the machine experiencing the error
          is the only one reporting the error.
     The server displays its own error messages as well as
     some that occur on the clients. And the client displays
     its own error messages.

Server error messages

     These error messages appear on the controller's screen.
     Also, ServerBench displays error messages to the server
     and clients screen when appropriate. You would see an
     error message on the client, for example, if the client
     couldn't connect to the server.
     The error messages in this section are ones ServerBench
     for OS/2 Warp Server can generate on the server. They
     have the following format:
       progname error text : [system error text]
     where:
     ·  progname is the name of the ServerBench executable
       file.
·  error text is the ServerBench error message text.
·  system error text is additional error information
retrieved from the operating system.
     We've divided the server error messages into five
     categories:
     Network          Errors communicating on the network.
     Kernel Errors requesting system resources.
     File   Errors during file I/O.
     Settings         Errors in the ServerBench installation
     or setup.
     Execution        Errors that occur during test execution.
     The following sections break the error messages into the
     above categories and describe the error text that you
     might see.

     Server network error messages
     The network error messages that ServerBench can generate
     appear in this section. If one of these errors occurs,
     ServerBench will also append additional system error text
     to these messages.
     Cannot connect
       ServerBench was not able to connect to the controller.
       The controller must be up and running before you start
       the server. Verify that the controller is running and
       that the network software is properly set up for
       ServerBench. You must have the controller defined in
       the server's TCP/IP hosts file. See the section "Step
       5: Set up the TCP/IP addresses" in Chapter 2 for
       instructions on adding the controller's name and IP
       address to the hosts file.
     Cannot listen for calls
       This error occurs when you are connecting clients. The
       system error text may indicate a specific TCP/IP
       resource shortage.  Review your server's TCP/IP setup.
       If the problem always occurs when you're connecting a
       specific client,  make sure that client's network
       software has been properly installed.
     Cannot send data
       The server attempted to send data to a client and
       received an error. If a specific client is consistently
       losing its connection, verify that the client's network
       software installation and configuration is correct.
     Cannot receive data
       The server attempted to receive data from a client and
       received an error. If a specific client is consistently
       losing its connection, verify that the client's network
       software installation and configuration is correct.
     Buffer too small for message received
       The server attempted to receive data into a buffer that
       was to small to handle the message that was sent from
       the client.  This typically means that the server is
       out of sync with the client due to some error.  Check
       for other error messages on the server, controller, and
       clients.

     Server kernel error messages
     This next section contains the kernel error text that
     ServerBench can generate.  ServerBench will also append
     any available system error text to these messages.
     Cannot allocate memory
       ServerBench was unable to allocate memory.  You must
       make more memory available for ServerBench or the
       current resource load on the server must be reduced.
     Cannot allocate semaphore
       ServerBench was unable to allocate a semaphore.  This
       error can occur because the server has run out of
       memory or there are too many semaphores allocated
       system wide.
     Cannot create thread
       ServerBench couldn't start a service thread. The server
       does not have enough resources to create another
       thread. You can increase the number of threads OS/2
       Warp Server allows by using the THREADS statement in
       the CONFIG.SYS file.

     Server file error messages
     The following error messages relate to problems that
     might occur with files. ServerBench will also append any
     available system error text to these messages.
     Cannot open file SVB_SEED.DAT
       ServerBench couldn't open the file SVB_SEED.DAT.  Make
       sure this file is in the ServerBench installation
       directory on the server.
     Cannot open file SVB_PROC.DAT
       ServerBench couldn't open the file SVB_PROC.DAT.  Make
       sure this file is in the ServerBench installation
       directory on the server.
     Cannot open file <data file>
       ServerBench couldn't open or create the specified data
       file.  Verify:
       1)  That the directory being used for the test data
       files exists.
       2)  That there is enough disk space available to create
       the data files.
     Cannot move file pointer
       ServerBench received and error during a file seek.
       Verify that there is free space available on the volume
       you are testing. The system error text that accompanies
       this message will provide additional information about
       the cause of the error.
     Cannot read from file
       ServerBench couldn't  read from a file. The system
       error text that accompanies this message will provide
       additional information about  the cause of the error.
     Cannot write to file
       ServerBench couldn't write to a file. Verify that there
       is free space available on the volume where ServerBench
       is executing. The system error text that accompanies
       this message will provide additional information about
       the cause of the error.

     Server settings error messages
     This section contains the error messages ServerBench
     might generate that deal with settings.
     Missing command line argument following
       You entered an incomplete command line argument. See
       Chapter 5 "Running ServerBench" for information for
       information on valid server command line arguments.
     Cannot find controller in hosts table
       The name controller, which is either "controller" or a
       name specified after the -c command line switch, isn't
       defined in the TCP/IP hosts file. See the section "Step
       5: Set up the TCP/IP addresses" in Chapter 2 for
       instructions on how to add the controller name to the
       hosts file.
     Invalid command line argument
       You entered an invalid command line argument. See
       Chapter 5 "Running ServerBench" for information for
       information on valid server command line arguments.
     Client ID out of range (1 - 1000)
       A client that connected to the server used a client ID
       number that was out of the accepted range.  Each client
       ID must be unique and fall between 1 and 1000.
     Duplicate client ID
       A client that connected to the server used a client ID
       number that was already in use by another client.  Each
       client must be configured to use a unique ID. Check
       your client configuration file to make sure you don't
       duplicate any ID numbers.
     Group ID out of range (1 - 50)
       A client that connected to the server used a group ID
       number that was out of the accepted range.  The group
       number must be between 1 and 50.
     Invalid mix definition
       The server received a mix from the controller that
       contained invalid test information.  Review the mix at
       the controller.
     Invalid transaction request
       A client requested an invalid transaction. Try to rerun
       the test.

     Server executing error messages
     The following are the error messages ServerBench can
     generate while executing.
     Operator requested termination
       The operator at the controller requested that the test
       be aborted.
     Invalid processor test
       The validation check on a processor test failed.  Try
       to rerun the test. If the problem persists, contact
       ZDBOp.
     Invalid disk test
       The validation check on a disk test failed.  Try to
       rerun the test. If the problem persists, contact ZDBOp.
     Invalid client to server test
       The validation check on a client to server test failed.
       Try to rerun the test. If the problem persists, contact
       ZDBOp.
     Invalid server to client test
       The validation check on a server to client test failed.
       Try to rerun the test. If the problem persists, contact
       ZDBOp.

Error messages generated by the client

     The following are error messages that can occur on the
     client.
     Could not initialize TCP/IP stack
       A fundamental error has occured when the client tryed
       to start up the TCP/IP stack.  This usually indicates
       that the TCP/IP stack has not been installed correctly.
       See Chapter 3 "Setting TCP/IP Up on the Controller and
       Clients" for a general guideline on how to install a
       TCP/IP stack.
     Cannot find server name in host table:  server
       The name, server, wasn't found in the hosts file of the
       TCP/IP stack.  See Chapter 3 "Setting TCP/IP Up on the
       Controller and Clients" for more information about this
       file.
     Cannot connect
       The client couldn't establish a connection with the
       server.  Make sure that you start ServerBench on the
       server before starting ServerBench on the client. See
       Chapter 6, "Running ServerBench" for a description of
       how to start ServerBench on the server.
       If you specified a port number other than the default
       port number on the server, make sure you specify the
       same port number in the TCP/IP protocol file on the
       client and vice versa. See your TCP/IP documentation
       for information on working with the protocol file.
       Make sure the network portions of the IP addresses of
       the client and the server match.
       Use the ping utility to determine whether the client
       and the server are connected to a common network
       segment.
     Cannot send data
       The client attempted to send data to the server and
       failed.  Verify that the client is configured according
       to the installation instruction.
     Cannot receive data
       The client got an error while it was waiting of data
       from the server. This usually indicates that something
       went wrong with the connections between the client and
       the server. Verify that the client is configured
       according to the installation instructions. The
       following problems can cause the error:
       ·  A error occurred on the server that caused it to
          terminate or the server is hung.
·  The network infrastructure has a physical problem (bad
cable, network card, and so on).
·  There's an error on the client's TCP/IP stack. Reboot
the client PC and try to start it again.
       If the problem persists, see the section "Some tips for
       handling network problems" earlier in this chapter.
     Buffer too small for message received:  buffer = b,
     received = r
       The client received a message from the server that was
       too large to fit into the receive buffer.  Check the
       server for error messages.
     Cannot allocate memory:  b bytes
       The client attempted to allocate memory but was unable
       to.  Make more memory available on the client.
     Cannot open file:  client.cfg
       The client cannot open the client configuration file,
       client.cfg.  If there is no client configuration file
       (CLIENT.CFG) in the same directory as CLIENT.EXE,
       create one there.  See Chapter 5 "Installing
       ServerBench on Your Clients" for a description of the
       client configuration file.
     Cannot open file:  svb_seed.dat
       The client was unable to open the file SVB_SEED.DAT.
       This file must exist in the same directory as the
       client executable, CLIENT.EXE.
     Cannot read from file:  file
       The client attempted to read from the file, file, and
       failed.  Check to be sure there is available free space
       on the client disk and that the file is not in use by
       another application.
     Cannot find server name in host table:  server
       The server name (either the default "server" or the
       name you specified on the client command line) wasn't
       found in the hosts file of the TCP/IP stack.  See
       Chapter 3 "Setting TCP/IP Up on the Controller and
       Clients" for more information about this file.
     Cannot find client name in client file:  client
       The name, client, which is specified as the first
       argument of the command line for starting ServerBench
       on the client, is not in the client configuration file
       (CLIENT.CFG).  Add client to CLIENT.CFG along with a
       client ID and a group ID or specify a name already in
       CLIENT.CFG in the command line for starting ServerBench
       on the client.
     Client ID out of range (1 - 1000):  n
       The client ID after the client name in the client
       configuration file (CLIENT.CFG), n, is not in the range
       from 1 to 1000, inclusive. Correct the client ID in
       CLIENT.CFG on the client.
     Group ID out of range (1 - 50):  n
       The group ID after the client name and client ID in the
       client configuration file (CLIENT.CFG), n, is not in
       the range from 1 to 50, inclusive.  Correct the group
       ID in CLIENT.CFG on the client.
     Negative transaction time
       When the client received the response to a transaction
       request, its millisecond clock time was less than it
       was when it sent the transaction request.
     Invalid processor test
       The client detected an error in the response it
       received from the server for a transaction request that
       specified the processor/memory test.
     Invalid disk test
       The client detected an error in the response it
       received from the server for a transaction request that
       specified a disk test.
     Invalid server to client test
       The client detected an error in the data it received
       for a server to client test.

Error messages generated by the controller

     ServerBench reports most errors to the controller. These
     are some error messages you may see at the controller.
     Error 0: Network open error
     Error 1: Secondary network open error
     Error 2: Network close error
     Error 3: Secondary network close error
     Error 4: Cannot initiate network connection
     Error 5: Unable to establish second connection to server
     Error 6: Cannot send to server
     Error 7: Undefined error
     Error 8: Undefined suberror
     Error 9: Network asynchronous error
     Error 10:   Network receive error
     Error 11:   Network listen error
     Error 12:   Network initiate error
     Error 13:   Network arrival error
     Error 14:   Network description error
     Error 15:   Network read error
     Error 16:   Network write error
     Error 17:   Network error getting server address
       These errors indicate that your protocol stack has
       encountered problems. This may be due to a bug in the
       stack, incorrect drivers for the network card, or an
       improperly configured network. Try re-installing your
       protocol stack.
     Error 18:   Unable to register for socket CLOSE notification
       This error, which can occur when you're using the TCP/IP
       protocol, indicates that the stack is probably low on
       resources or has encountered other errors.
     Error 19:   NetWare error: Cannot Advertise Service via SAP
     Error 20:   NetWare error: Cannot Query Service via SAP
       This error, which can occur when you're using the NetWare
       protocol stack, indicates that the stack has not been
       properly installed or that the PC isn't attached to any
       servers. Check to be sure the PC's attached to a server.
       If that's not the problem, try re-installing your
       protocol stack.
     Error 21:   No clients connected. Press OK to Abort session,
     CANCEL to add
             clients
       You've attempted to proceed from a connect clients dialog
       box without having connected any clients.  You must
       either connect some clients or exit the controller.
     Error 22:   Invalid message format received
       The server transmitted a ServerBench packet that has not
       been correctly delivered to the controller. This may be
       due to a faulty hardware setup or an improperly
       configured network stack.
     Error 23:   Test suite file has errors
       The test suite that you selected has been corrupted.  Try
       to edit the test suite through the Mix Definition window.
       If that fails, delete the suite from the hard disk.
     Error 24:   Failed to allocate animation timer
     Error 25:   Failed to allocate window timer
     Error 26:   Cannot load bitmap
       Windows couldn't perform the necessary timer or bitmap
       creation operations. This is usually due to insufficient
       system resources.  Close all non-essential programs, any
       special desktop shells, and try running the controller
       again.
       Error 27:   Cannot open test suite output file
       Error 28:   Cannot open log file
       Error 29:   Cannot open order output file
       Error 30:   Cannot open results file
       Error 31:   Cannot open error output file
       Error 32:   Cannot open trace file
     Error 33:   Cannot read test suite file
     Error 34:   Could not read mix
     Error 35:   Cannot open paths file.
       These errors indicate that either the selected file has
       been locked by another process (possibly Excel) or you're
       performing some kind of operation on the file itself.
       Another possibility is that you're out of disk space. Or
       these errors could mean your file system is corrupt and
       must be scanned for errors.
     Error 36:   You have not properly registered ServerBench.
     Please run
             SB30A.EXE.
     Error 37:   Fill in your name and optionally your
     organization's name
       You must start ServerBench on the controller and register
       ServerBench by entering you name and, optionally, your
       organization.  The controller window won't appear
       otherwise.
     Error 38:   Unable to open SVRBENCH.INI file to store
     registration
             information
       This error indicates that you've either locked the
       SVRBENCH.INI file with a text editor somewhere else, you
       don't have enough disk space, or the file system is
       corrupt.
     Error 39:   Could not read suite
     Error 40:   Could not read results path
     Error 41:   Could not read comment
       An error has occurred while reading the SESSION.INF file.
       ServerBench can't determine the name of the test suite or
       its results path or a comment in the Test Suite History
       window.
     Error 42:   The results directory <x> is no longer valid.
       The directory where ServerBench created your last results
       has been removed from the hard disk.  Select another
       directory.
     Error 43:   Do you want to convert to version 3.0?
       You've selected a test suite from the 1.1 version of
       ServerBench. You can convert the suite if you wish.
     Error 44:   The total number of seconds must be greater than
     the sum of
             the ramp up and ramp down
       Ramp up and ramp down are a part of length so the value
       for the length parameter must be greater than their sum.
       Length must also be long enough to finish a minimum of
       one complete iteration of the mix. Otherwise, you won't
       have any results for this test mix. As the load on your
       server increases, the amount of time you've entered may
       not be sufficient.
     Error 45:   Test <x> total size is greater than the disk
     test file   initial size and/or the I/O range field is zero
       This error means that the test <x> has a total size that
       is greater than the Disk Test File Initial Size parameter
       and/or the test has a blank I/O Range parameter. This
       error only applies to mixes that have Disk tests. You'll
       need to change the value of the Disk Test File Initial
       Size parameter so that it's equal to or greater than the
       Total Size parameter. You also need to make sure you
       enter a value greater than 0 for the I/O Range parameter.
     Error 46:   Test <x> request size is greater than total size
       This error message appears if you included a test that
       had a value for Total Size that is less than the value of
       Request Size.  This error usually indicates a corrupted
       test suite definition file.
     Error 47:   Test <x> has an invalid type
       The test type can be P, RR, RW, SR, SW, A, CS, or SC.
       This error may indicate a corrupted test suite definition
       file.
     Error 48:   Test list invalid--not terminated by blank test
       A mix within the suite has been incorrectly stored.
       Please verify that the mixes have the correct name for
       their respective test types (P, SR, SW, RR, RW, A, SC,
       CS).
     Error 49:   Test suite must have at least one mix defined
       This error message appears if a test suite file has no
       mixes defined. This error usually indicates a corrupted
       test suite definition file. See the chapter on "Creating
       Your Own Test Suites" in the Understanding and Using
       ServerBenchr 3.0 manual for information on how to set up
       test suites.
     Error 50:   Invalid groups
       You can enter a group number of from 1 to 50. When you
       specify groups in a mix, make sure some clients in that
       group are connected before you run the test suite.
     Error 51:   Must be an integer between <x> and <y>
       Make sure the value you enter is within the specified
       limits.
     Error 52:   May have up to 3 decimal places. Must be between
     <x>
             and <y>
       Make sure the value you enter is within the specified
       limits.
     Error 53:   Client number <x> has a NULL datafile pathname
       This error message appears if a mix that included disk
       tests had at least one client with a blank data file path
       name. See the chapter "Creating Your Own Test Suites" in
       the Understanding and Using ServerBenchr 3.0 manual for
       information on how to set up test suites.
     Error 54:   The client pathname buffer has been exceeded.
             Please reduce the pathnames by <x> characters.
       The path name you entered at the Mix Definition window
       for a client is too large.
     Error 55:   Ramp up is blank
     Error 56:   Ramp down is blank
     Error 57:   Length is blank or 0
     Error 58:   Delay time is blank
     Error 59:   Think time is blank
     Error 60:   Number of clients is blank or 0
     Error 61:   No tests defined
       You must enter a value for each of these fields; they
       cannot be not be blank.
     Error 62:   x client(s) require paths, as disk tests have
     been
             specified.
       If you specify a Disk test in a transaction, you must
       provide a client path name to the Disk test data file on
       the server.
     Error 63:   Must be greater than 0
       You must always supply a positive number as the value for
       this parameter.
     Error 64:   Must be greater than or equal to 0
       You must always supply a positive number as the value for
       this parameter.
     Error 65:   The mix length does not fall within specified
     parameters.
       The minimum value you can enter for the mix length is 30
       seconds.
     Error 66:   Length must be greater than Ramp Up + Ramp Down.
       Ramp up and ramp down are a part of length so the value
       for the length parameter must be greater than their sum.
       Length must also be long enough to finish a minimum of
       one complete iteration of the mix. Otherwise, you won't
       have any results for this test mix. As the load on your
       server increases, the amount of time you've entered for
       Length may not be sufficient.
     Error 67:   The Disk test file initial size cannot be blank
     or zero
             when disk tests have been specified.
       You must always supply a value for this parameter when
       you're setting up a Disk test.
     Error 68:   The Disk test I/O Range cannot be blank or zero
     when disk
             tests have been specified.
       You must always supply a value for this parameter when
       you're setting up a Disk test.
     Error 69:   Disk test file Initial Size and I/O Range cannot
     be zero as
             disk tests have been specified.
       You must always supply a value for this parameter when
       you're setting up a Disk test.
     Error 70:   The Disk test I/O Range cannot be greater than
     the Disk
             test file initial size.
       You've entered an I/O range that is greater than the
       Initial Disk Test File Size. The I/O range must be less
       than or equal to the value in the Initial Disk Test File
       Size parameter.
     Error 71:   <x> tests with Total Size > I/O Range.
       The Total Size for each disk test file must be less than
       the value you enter for the I/O Range parameter. You've
       entered a value for the Total Size parameter that exceeds
       the value for the I/O Range parameter.
     Error 72:   Total size must be >= Request size
       This error message appears if you included a test that
       had a value for Total Size that is less than the value of
       Request Size.  This error usually indicates a corrupted
       test suite definition file.
     Error 73:   x incomplete test descriptions
       None of the fields on the Mix Definition window can be
       blank.  They must either contain tests or client path
       names.
     Error 74:   Total number tests MUST equal sum of transaction
     iterations
       An internal mix count variable has been corrupted.  Re-
       enter  your transactions.
     Error 75:   A mix cannot contain more than 100 transactions
       You've entered a total number of transactions that
       exceeds our limit of 100.
       Error 76:   The sum of all Transaction Iterations per mix
       cannot
             exceed 1024
       There's a limit of 1024 on the number of total
       transaction iterations you can have in a mix.
     Error 77:   The total number of tests must be equal to the
     sum of
             the # of Test Iterations
       An internal mix count variable has been corrupted.  Re-
       enter  your transactions.
     Error 78:   Include transaction type and # iterations in
     transaction
             definition
       When you set up a transaction, you must always enter
       values for the transaction name and the number of
       iterations.
     Error 79:   The first test must be either a Transaction or a
     Singleton.
       Your first entry in the Transaction Definitions section
       must be either a value for the Transaction Iterations or
       the Transaction Name, which can be a singleton.
       Otherwise, you don't have transaction but a test, which
       ServerBench does not allow as the FIRST entry in the box.
     Error 80:   An incomplete test has been defined after a
     Singleton.
       You've attempted to add a test after a singleton. A
       singleton, by definition, is a one-test transaction that
       you create by entering a test type (P, SR, SW, RR, RW, A,
       SC, or CS) as the transaction name.
     Error 81:   The next test makes a singleton invalid here.
       You get this message if  you attempt to add a singleton
       in the middle of a multiple test transaction. Insert the
       singleton outside of the transaction.  Singletons can
       only be placed above other Singletons or Transactions.
     Error 82:   Unable to start test.  Some components may be
     missing.
       You may have removed some protocol specific .dll files
       from your hard disk that ServerBench needs to run the
       controller window.  Reinstall your protocol stacks.
     Error 83:   Excel load failure.  Excel may not be installed
     properly,
             or ServerBench failed to locate it.
       The association for an Excel (.xlm) macro isn't correct.
       It may have been corrupted. Excel should have set this up
       automatically. Make sure your installation of Excel is
       correct. You can resolve this problem by re-installing
       Excel. Or you can re-associate Excel yourself.
       (If you can't re-associate Excel, you need to add Excel
       in your Path statement.)
     Error 84:   The RESULTS.XLM file is missing from the
     installation
             directory. You will not be able to generate results.
             Please re-install to continue.
       You'll need to re-install ServerBench on your controller.
     Error 85:   Unable to start SB30A.EXE.  It may be missing
     from the
             ServerBench Directory.
     Error 86: <x> is missing from the installation directory.
     You must
             re-install to continue.
       The SB30A.EXE and SB30B.EXE (error 86) files are missing.
       You must
       re-install ServerBench to continue.
     Error 87:   Unable to allocate memory for client structure
     Error 88:   Unable to re-allocate memory for client, client
     information
             is lost
       The operating system is out of system resources or there
       isn't enough memory.  Shut down all non-essential
       programs.
     Error 89:   There are no clients that are members of the
     groups
             specified in mix <x>.
       You've attempted to run a test without having any clients
       connected to the server that are members of the groups
       specified in the mix.
     Error 90:   Unable to replicate the field across the mix.
     Verify file
             system integrity before trying again.
     Error 91:   An error occurred during the re-ordering
     process.
             Please verify the suite is not locked or corrupted.
     Error 92:   Unable to copy selected mixes. Check system
     resources and
             file system integrity before trying again.
       These respective features have failed, probably due to a
       corrupted file system or a locked test suite file.
     Error 93:   Error editing log file.  Verify your editor
     path.
       The path to your text editor may be invalid. Select
       another text editor.
       Error 94:   You have selected an invalid snapshot file.
       Press Retry to
               select another.
     Error 95:   Results set <x> has already been selected.
     Please select
             another set.
     Error 96:   You have already selected this test suite.
     Please select
             another.
     Error 97:   You have selected an invalid results file. Press
     Retry to
             select another.
     Error 98:   You have selected an invalid test suite file.
     Press Retry
             to select another.
     Error 99:   You have selected an invalid path file. Press
     Retry to
             select another.
       You've selected files that have an invalid format
       (probably an incorrect extension). You can't select the
       same test suite for editing or the same set of results
       for displaying.
     Error 100:  Snapshot transfer failed.  Press OK to continue.
     Error 101:  Unable to update clients to snapshot file.
       The snapshot operations failed.  This may be due to
       insufficient memory or corrupted snapshot and .DLG files.

                     End of chapter








     Chapter 8 ~
     Contacting ZDBOp



     This chapter tells you how to get in touch with ZDBOp.
     You may want to get  in touch with ZDBOp because you have
     questions or comments about ServerBench, you've
     encountered an unexpected problem with ServerBench, or
     you want to know how to get a copy of it or the other
     benchmarks Ziff-Davis provides.
If a problem occurs, look here for possible solutions

     If a problem occurs while you're running ServerBench,
     here're some places to look for solutions:
     ·  Check the on-line ServerBench manual for your server
       operating system. It contains some troubleshooting tips
       as well as any error messages you might see.
·  Look in the README.TXT file for your ServerBench
platform. This file contains any late-breaking
information that did not make it into the manual. You'll
find a copy of this file in the controller installation
directory and on the CD-ROM in the directory that
contains ServerBench for your operating system.
     ·  Check the FAQ file for ServerBench, which we post on
       ZD NetÖ/CompuServe Edition. (ZD Net is a Ziff-Davis on-
       line service. Access to CompuServe is available for a
       fee.)
·  Read the messages in the ZDBENCH forum on ZD
Net/CompuServe Edition to see if anyone else has had a
similar problem.

Here's how you get in touch with ZDBOp

     If you have technical questions about ServerBench that
     you can't find answers to in any of the documentation,
     fill out the Problem Report that is at the back of this
     manual and send it to us. If you have an Internet e-mail
     address, please include it when you get in touch with us.
     Here're some ways to get in touch with ZDBOp:
       If you have a modem and communications software, you
       can reach ZDBOp via its forum (GO ZDBENCH) on ZD
       Net/CompuServe Edition.
       The address for our World Wide Web page is:
        http://www.zdnet.com/zdbop
       You can also send an on-line version of the Problem
       Report to us via e-mail to:
       [e-mail]
       You can fax the Problem Report and any questions and
       comments you have directly to ServerBench Technical
       Support at the ZDBOp fax number
       919-380-2879.
       You can mail the Problem Report and any questions and
       comments you have to ZDBOp at the following address:
       Ziff-Davis Benchmark Operation
       1001 Aviation Parkway, Suite 400
       Morrisville, NC 27560
       Attn:  ServerBench Technical Support

     Getting copies of benchmarks from ZD Net
     You'll find copies of ServerBench and other Ziff-Davis
     benchmarks on ZD Net/CompuServe Edition and ZD Net/World
     Wide Web Edition.
     NOTE:  You'll need to pay your usual connection fees when
          you download the benchmarks.
     When you download ServerBench, you'll need to download
     three files for your server platform _ one each for the
     server program, the controller program, and the client
     program. We provide a different set of files for each
     server platform ServerBench runs on.
     To identify these files, we use the following naming
     scheme:
       <port-name>s.<exe or tar> for the server file.
       <port-name>co.exe for the controller file.
       <port-name>cl.exe for the client file.
     where port-name is an abbreviated name we use to indicate
     that server operating system for that platform of
     ServerBench.

     Requesting the benchmark CD-ROMs from ZDBOp
     We distribute our server and PC benchmarks free of charge
     on CD-ROMs. The Server Benchmarks
     CD-ROM contains ServerBench and NetBenchr (Ziff-Davis'
     industry-standard file server benchmark program). The
     Ziff-Davis PC Benchmarks CD-ROM contains WinBenchr 96 ,
     and Winstoner 96.  You can also get a copy of the Ziff-
     Davis Macintosh Benchmark CD-ROM, which contains
     MacBenchr 3.0 (a Mac OS system benchmark program). To get
     a benchmark CD-ROM, mail or fax the Benchmark Request
     form at the back of this manual to ZDBOp.

                     End of chapter








Index



                                Workgroups, 29
           _A_                  starting program on Windows
Applications                     95, 29
 running in background, 7       starting ServerBench, 36
                                Windows 95, 6
           _B_                  Windows 95 shortcut, 30
Background applications         Windows for Workgroups, 6
 affecting results, 7          Client configuration file, 30
Benchmarks                      creating, 30
 downloading, 54                default value, 32
BWCC.DLL                       CLIENT.CFG file, 30
 used with controller           client configuration file, 9
  interface, 25                 creating, 30
                                default file, 27, 30
           _C_                  installed on client, 30
CD-ROM                          naming scheme, 29
 finding ServerBench files, 7  CLIENT.EXE
 installing client files, 28    client executable, 30
 installing controller files,  Command line
  24                            client, 32
 installing server files, 12   Command line options (server)
Client                          option -F, 36
 choosing for mix, 32           option -S, 36
 client configuration file, 30 Controller
 CLIENT.CFG, 9                  default directory C
 command line, 32                \SB30\NW41, 24
 creating configuration file,   error messages, 46
  30                            installation directory, 24
 default directory              installed files, 25
  C\SB30\OS2WS, 29              installing the ServerBench
 default ServerBench values,     files, 23
  32                            manuals, 25
 error messages, 44             NW41CO.EXE executable, 8
 group number, 28               requirements, 6
 group number requirements, 31  running SETUP.EXE, 23
 ID number requirements, 31     setting up Excel, 6, 26
 including client               SETUP.EXE, 8
  configuration file, 29        starting on Windows for
 installation directory, 29      Workgroups, 25
 installed files, 30            starting program on Windows
 installing the ServerBench      95, 25
  files, 28                     starting ServerBench, 35
 modifying Windows for          test suites directory, 26
  Workgroups command line, 33   Windows 95 shortcut, 25
 modifying command lineon
  Windows 95, 33                          _D_
 name, 27, 29                  Data files
 name requirements, 31          used with disk tests, 13, 15
 requirements, 6               Directories
 OS2WSCL.EXE executable, 8       C\SB30\OS2WS on client, 29
 running SETUP.EXE, 28           C\SB30\ OS2WS on controller,
 starting on Windows for           24
                                client installation, 29
  controller installation, 24   CLIENT.CFG, 9, 30
 disk test data files, 12       CLIENT.EXE, 30
 DOCS on controller, 25         data, 13, 15
 for disk test data files, 15   default CLIENT.CFG, 27
 RESULTS, 38                    GENERAL.HLP, 25
 RESULTS on controller, 25      HOSTS, 21
 \SB30 on server, 12            MAKEBAT.EXE utility, 8
 server installation, 12, 13    NW41CL.EXE, 8
 SUITES on controller, 26       NW41CO.EXE, 8
Disk test                       NW41SR.EXE, 8, 12, 13
 directory for data files, 12,  PORT.HLP, 25
  15                            RESULTS.XLM, 25
 Disk Test File Initial Size    SBC30A.EXE, 25
  Parameter, 15                 SBC30B.EXE, 25
 temporary data files, 13, 15   SETUP.EXE, 8, 9
Diskettes                       SVB_PROC.DAT, 13
 installing client files, 28    SVB_SEED.DAT, 13, 30
 installing controller files,   SVR.EXE, 13
  24                            SVR.txt, 14
 installing server file, 13     SVRBENCH.XLA, 25
DOCS subdirectory
 controller subdirectories, 25            _G_
                               GENERAL.HLP
           _E_                  generic help file, 25
Errors                         Group number
 client error messages, 44      client, 28
 contacting ZDBOp, 53           requirements, 31
 controller error messages, 46
 controller format, 40                    _H_
 Problem Report form, 61       Help file
 reporting on different         GENERAL.HLP, 25
  machines, 40                  PORT.HLP, 25
 server, 41                    HOSTS file
 server executing error         TCP/IP stack uses, 21
  messages, 44                            _I_
 server file error messages,   ID number
  42                            requirements, 31
 server format, 41              used in mixes, 32
 server kernel error messages, Installation directory
  42                            client, 29
 server network error           controller, 24
  messages, 41                  server, 12
 server settings error          verifying server directory,
  messages, 43                   13
 what to check first, 39       Installation diskettes
Excel                           creating with MAKEBAT.EXE, 8
 setting up on controller, 26   installing client files, 28
                                installing controller files,
           _F_                   24
-F command line option          installing server file, 13
 (server), 36                  Installing ServerBench
Files                           installing client files from
 BWCC.DLL, 25
 C                               24
 installing client files from   installing server file, 12
  diskette, 28                 NIC cards
 installing client files from   setting up multiple cards, 21
  network drive, 28            Numbers
 installing controller files    client, 28
  from CD-ROM, 24               requirements for client, 31
 installing controller files    used in mixes, 32
  from diskette, 24            NW41CL.EXE
 installing controller files    client executable, 8
  from network drive, 24       NW41CO.EXE
 installing server file from    controller executable, 8
  CD-ROM, 12                   NW41SR.EXE
 installing server file from    deleting, 13
  diskette, 13                  executing, 13
 installing server file from    installing on the server, 12
  network drive, 12             server executable, 8, 12
 locating files, 7                        _O_
 overview, 8                   OS/2 Warp Server
 verifying client               modify configuration, 11
  installation, 30              thread model, 3
 verifying controller          OS2WSCL.EXE
  installation, 25              client executable, 8
 verifying server              OS2WSCO.EXE
  installation, 13              controller executable, 8
IP addresses, 17               OS2WSS.EXE
 setting up multiple NIC        deleting, 13
  cards, 21                     executing, 13
           _L_                  installing on the server, 12
License Agreement, 35           server executable, 8, 12
           _M_                            _P_
MacBench                       PCTCP.INI file
 Ziff-Davis benchmark, 54       increasing TCP window size,
MAKEBAT.EXE utility              40
 creating installation         Ping utility, 15, 20
  diskettes, 8                 PORT.HLP
Mixes                           ServerBench on OS/2 help
 selecting clients to run, 32    file, 25
           _N_                 Problem
Names                           reporting, 53
 client, 27, 29                 what to check first, 39
 requirements for client, 31   Problem Report form, 61
Network                        Protocols
 checking with ping utility,    using TCP/IP, 17
  15, 20                                  _R_
Network directory              Requirements
 containing ServerBench files,  complete list, 5
  7                            Results
Network drive                   benefits of test network, 7
 installing client files, 28    effect of background
 installing controller files,    activity, 7
  saving, 38                    files on diskettes you
 stored in RESULTS directory,    create, 8
  25                            files on network directory, 7
 viewing, 37                    getting installation files, 7
RESULTS directory, 38           installation overview, 8
 controller subdirectory, 25    installing client files from
RESULTS.XLM                      CD-ROM, 28
 Excel macro, 25                installing client files from
           _S_                   diskette, 28
-S command line option          installing client files from
 (server), 36                    network drive, 28
SBC30A.EXE                      installing controller files
 controller executable, 25       from CD-ROM, 24
SBC30B.EXE                      installing controller files
 controller file, 25             from diskette, 24
Screen saver programs           installing controller files
 affecting results, 7            from network drive, 24
Server                          installing server file from
 checking with ping utility,     CD-ROM, 12
  15, 20                        installing server file from
 create ServerBench directory,   diskette, 13
  12                            installing server file from
 default name, 32                network drive, 12
 deleting NW41SR.EXE, 13        installing the client files,
 errors, 41                      28
 executing error messages, 44   installing the controller
 executing NW41SR.EXE, 13        files, 23
 file error messages, 42        installing the server files,
 installed files, 13             12
 installing the ServerBench     License Agreement, 35
  files, 12                     manuals on controller, 25
 kernel error messages, 42      Problem Report form, 61
 modify configuration, 11       requesting, 54
 network error messages, 41     requirements, 5
 NW41SR.EXE executable, 8, 12   server requirements, 5
 option  -F, 36                 starting on client, 36
 option  -S, 36                 starting on clients, 36
 requirements, 5                starting on controller, 35
 settings error messages, 43    starting on server, 36
 starting ServerBench, 36       test network, 7
 using multiple NICs, 21        test suites directory, 26
ServerBench                     verifying client
 basic system setup, 6           installation, 30
 choosing clients for mix, 32   verifying controller
 client numbers, 32              installation, 25
 client requirements, 6         verifying server
 controller requirements, 6      installation, 13
 default values for clients,    viewing results, 37
  32                           Service threads, 3
 definition, 1                 SETUP.EXE
 effect of background           for the client, 9
  applications, 7               for the controller, 8
 files on CD-ROM, 7             running on client, 28
                                running on controller, 23
Standard test suites                      _T_
 in SUITES directory, 26       TCP/IP
Starting ServerBench            HOSTS file, 21
 client, 36                     setting up, 17
 clients, 36                   Technical support
 controller, 35                 contacting, 53
 server, 36                     Problem Report form, 61
SUITES subdirectory             what to check first, 39
 controller subdirectories, 26 Test network, 7
SVB_PROC.DAT, 13               Test suites, 37
SVB_SEED.DAT, 13                in SUITES directory, 26
 client file, 30                selecting clients to run, 32
SVR.EXE executable, 13          viewing results, 37
SVR.txt, 14                    Thread model, 3
SVRBENCH.XLA                   Threads
 Excel macro, 25                service threads, 3
                                          _W_
                               WinBench
                                Ziff-Davis benchmark, 54
                               Windows 95
                                modifying client command
                                 line, 33
                                on client, 6
                                shortcut to client program,
                                 30
                                shortcut to controller
                                 program, 25
                               Windows for Workgroups
                                client icon, 29
                                controller icon, 25
                                modifying client command
                                 line, 33
                                on client, 6
                               Winsock
                                with TCP/IP, 17
                               Winstone
                                Ziff-Davis benchmark, 54
                               World Wide Web page, 53
                                zdbopwebmaster@ zd.com, 53

                                          _Z_
                               ZD Net
                                installing client files, 28
                                installing controller files,
                                 24
                               ZD Net/CompuServe Edition, 53
                               ZD Net/World Wide Web Edition,
                                53
                               ZDBENCH
                                ZDBOp forum, 53
ZDBOp
 CompuServe forum, 53
 contacting, 53
 contacting via ZD Net, 53
 contacting via
  [e-mail], 54
 forum GO ZDBENCH, 53
 Macintosh Benchmark CD-ROM,
  54
 mailing address, 54
 PC Benchmarks CD-ROM, 54
 World Wide Web page, 53
Ziff-Davis Benchmarks
 program group, 25, 29
Ziff-Davis Server Benchmarks CD-
 ROM, 7
 installing client files, 28
 installing controller files,
  24
 installing server file, 12
 requesting, 54

   Problem Report Form for ServerBench on OS/2 Warp Server
Information about you:
Name:
_________________________________________________________________
___________
Address:
_________________________________________________________________
_________
Company:
_________________________________________________________________
________
Phone or Fax: _____________________________E-Mail
Address_____________________________
Describe your ServerBench setup:
Please send us the filled-out results Tables 4 and 5 (the server
and client disclosure tables). We need to know at a minimum the
operating system and version number, the network operating system
and version number, the network protocol and version number, and
other information in those results tables for each machine. (If
you don't have up-to-date Tables 4 and 5, you can enter that
information here.)
Server___________________________________________________________
_________________
Controller:______________________________________________________
___________________
Client:__________________________________________________________
___________________
Details of the problem:
Which test suite were you running? (If you were running a test
suite you created or a modified standard test suite, send us a
copy of the test suite.)
_______________________________________________
_________________________________________________________________
_________________
Please write any server error messages you received here:
__________________________________

_________________________________________________________________
________________
_________________________________________________________________
_________________
Please write any controller error messages you received here and
the stage the test suite was at here:
_________________________________________________________________
_________________
_________________________________________________________________
_________________
Please write any client error messages you received and the stage
the client was in here:___________
_________________________________________________________________
_________________
_________________________________________________________________
_________________
Can you reproduce the problem? ______ Other comments:
__________________________________
_________________________________________________________________
_________________
Please send this form to:
Fax number:           [phone]
or Mail:              Ziff-Davis Benchmark Operation
       1001 Aviation Parkway, Suite 400
       Morrisville, NC 27560
       Attention: ServerBench Technical Support



                   Benchmark Request Form

Please check the boxes of the products you want:
___              Ziff-Davis PC Benchmarks CD-ROM
  Contains the Winstone and WinBench benchmarks for desktop PCs.
___              Ziff-Davis Server Benchmarks CD-ROM
  Contains NetBench for file servers with DOS, Windows for
  Workgroups, and Mac OS system clients and
  ServerBench for client/servers for the server platforms Windows NT
  Server 3.51 using Digital  Alpha,
  MIPS, PowerPC, and x86-compatible processors, SCO UnixWare, SCO
  OpenServer Release 5,
  OS/2 Warp Server,  NetWare 4.1, and NetWare 4.1 SMP.
___              Ziff-Davis Macintosh Benchmark CD-ROM
  Contains MacBench  for Mac OS systems and Power Macintosh.
Please send these products to:
Name:
______________________________________________________________
Company:
___________________________________________________________
Address:
____________________________________________________________
City: ______________________________ State: _______________ Zip:
_________
Country:
_____________________________________________________________
Telephone: ___________________________ FAX:
__________________________
We answer requests in the order we receive them. We ship all
benchmarks via 3rd-class U.S. Please allow 4-6 weeks for
delivery. For faster shipment, provide your Federal Express
account information below:
Your Federal Express account number:
____________________________________
Check one:    ___ priority overnight   ___ standard overnight
Please return this form:
Fax to:               [phone]
or Mail to:           Ziff-Davis Benchmark Operation
       1001 Aviation Parkway, Suite 400
       Morrisville, NC 27560