1 1984-01-07  run_benchmark
 2 
 3 Syntax as a command:  run_benchmark CONTROL_DIR_PATH
 4 
 5 
 6 Function: runs a benchmark specified by the control file of a
 7 specified benchmark control directory, leaving the results in the
 8 directory.
 9 
10 
11 Arguments:
12 CONTROL_DIR_PATH
13    The pathname of a benchmark control directory.  The .benchmark
14    suffix is assumed.
15 
16 
17 Control arguments:
18 -trace
19    Traces the internal operation of the benchmark subsystem on the
20    user terminal.
21 -no_trace
22    Prevents tracing of the internal operation of the benchmark
23    subsystem on the user terminal.  This is the default.
24 
25 
26 Access required:  sma to the benchmark control directory.
27 
28 
29 Notes: The run_benchmark command initiates the benchmark and then
30 returns to command level.  The benchmark runs in the background.  When
31 the benchmark is complete, a message is printed on the user terminal.
32 
33 While the benchmark is in operation, the benchmark_status command can
34 be used to see the state of the stream(s) that make up the benchmark.
35 The stop_benchmark command can be used to terminate the benchmark
36 prematurely.
37 
38 The benchmark system is not recursive.  Only one benchmark may be run
39 in a process at a time.
40 
41 
42 The benchmark system maintains audit files for each of the streams in
43 the benchmark.  They are named as follows:
44 
45      NAME.date_time.audit
46 
47 where NAME is the name of the stream from the benchmark control file,
48 and date_time is the time when the benchmark was started.  These audit
49 files contain all the traffic over the stream.  The display_audit_file
50 command can be used to display the contents of these audit files.