MTS Multipurpose Elite Test - Manual (Page 87)

FileType= Block-Arbitrary
Date= Fri May 12 07:55:44 2010
Description= this is a sample test profile
ActionList= <DO 1 on>, <DO 1 off>, counter1, “counter 2”
Channels= 1
Header Data Syntax
Comments Suggestions Keyword
This required entry must be first. Block-Arbitrary or Phase FileType=
This optional entry can be in any form. Last modified date and time Date=
This optional entry can be in any form
(quotation marks are not needed) on one line. User-defined description of the
file Description=
This optional entry applies if you have actions
or counters associated with your profile. See Action and Counter Syntax
on page 87.
ActionList=
This required entry must be followed by
channel and channel data definitions for each
channel in the profile. Number of channels in profile Channels=
6.2.11.5.0 Action and Counter Syntax
Observe the following syntax requirements when adding actions or counters to a profile file.
• Actions and counters are defined by the keyword Action. This attribute may be a constant value or a
column of values.
• If the Action column is the last column in the file, the action value may be left blank. If the Action column
is not the last column, you must specify the empty string (“ ”) as a placeholder (any other string will be
interpreted as a unique counter name).
• If the string contains embedded spaces, then counter names must be enclosed in double quotation marks
(“ ”). If the name is one word, the quotation marks are not necessary.
• Action names must be delimited by a left angle bracket (<) and a right angle bracket (>). The Profile
process will use these delimiters to distinguish between event actions and counters. If the delimiters are
missing, these strings will be interpreted as new counters. If the delimiters are used for a counter, the
process will interpret the name as an event action. Neither of these syntax errors will generate an error,
but they may cause unexpected results.
• The keyword ActionList= must be in the file header if any actions are defined. It must include all event
action names defined in the file; counter names are optional. The names must be separated by a comma.
This list cannot exceed 256 characters without containing a space. MTS recommends separating items
in the list with a comma (required) and a space.
Example with counters and actions
FileType= Block-Arbitrary
Date= Wed_Jul 05 15:11:32
Multipurpose Elite Test Design Guide 87
6.0 Creating Advanced Tests