1 1984-01-07  cv_benchmark_control
  2 
  3 Syntax as a command:  cv_benchmark_control CONTROL_SOURCE_PATH
  4 
  5 
  6 Function: constructs the control file for a benchmark directory from
  7 an ASCII source.
  8 
  9 
 10 Arguments:
 11 CONTROL_SOURCE_PATH
 12    The pathname of an ASCII file describing a benchmark directory.  If
 13    the .bcontrol suffix is not given, it is assumed.
 14 
 15 
 16 Notes:
 17 
 18 A benchmark control file specifies a set of streams to be run as a
 19 benchmark.  Each stream is assigned a name.  The control file
 20 specifies the script to be run for each stream, and the attach
 21 description of the communications channel over which the script will
 22 be transmitted.
 23 
 24 This command creates a segment named "_benchmark_control_" in the
 25 current working directory, which should be a benchmark directory (a
 26 directory with the .benchmark suffix).  All scripts specified in the
 27 control file are assumed to be present in the control directory.
 28 
 29 
 30 See the cv_benchmark_script command for more information on scripts.
 31 See benchmark.gi.info for general information on the benchmark
 32 subsystem.
 33 
 34 
 35 Examples:
 36 
 37 Channel:  sty.ulogin*;
 38 Attach_options:  "-destination "" xascii_crt bmrk""";
 39 
 40 Stream:  fred;
 41  script:  fred_s_script;
 42 end;
 43 
 44 Stream:  george;
 45  script:  george_s_script;
 46 end;
 47 
 48 End;
 49 
 50 
 51 Control segment syntax:
 52 
 53 A control file is made up of two kinds of statements: default
 54 statements and stream specification groups.  Default statements
 55 specify default values for following stream specification groups.
 56 
 57 
 58 Stream specifications:
 59 
 60 A stream specification group begin with a Stream statement.  The
 61 syntax of a Stream statement is:
 62 
 63    Stream:  <name>;
 64 
 65 This begins the specification of a stream named <name>.  From the
 66 Stream statement until the end statement come the specifications of
 67 the stream.  These are chosen from the following:
 68 
 69    script:  <script_name>;
 70 Specifies that the script <script_name>.bmark is to be used for this
 71 stream.
 72 
 73 
 74   channel:  <quoted-channel-name>;
 75 Specifies, in conjunction with the attach description, the name of the
 76 communications channel to be used for this stream.  This statement is
 77 optional.
 78 
 79  attach_options:  <quoted-attach-options>;
 80 Specifies, in conjunction with the attach description, additional
 81 options for the attachment of the channel.
 82 
 83 
 84  attach_description:  <quoted-attach-description>;
 85 Specifies the attach description of the communications channel.  The
 86 attach description is assumed to be an ioa_ control string, and the
 87 channel and attach_options are substituted in in that order.  The
 88 default attach_description (unless changed by an Attach_description
 89 statement) is "tty_ ^a ^a -no_block." The channel is substituted for
 90 the first ^a, and the options for the second.
 91 
 92  end;
 93 specifies the end of a stream specification group.
 94 
 95 
 96 Default statements:
 97 
 98 Default statements specify default for following stream
 99 specifications.  There is one default statement for each stream
100 specification.  Default statements have the same syntax as their
101 corresponding stream statements, but their keywords are capitalized.
102 For example, the Script statement is the default statement for the
103 script stream specification.
104 
105 The default attach_description is "tty_ ^a ^a -no_block".  The default
106 script, channel, and attach options are null.