Examples

Using the Keyword type

The Keyword type is used to specify a parameter that takes a single value. As an example, consider an OPTIONS subcommand with a parameter for controlling missing values, and represented in the syntax diagram as:

/OPTIONS MISSING={PAIRWISE}
                 {LISTWISE}

The specification of MISSING is best handled with a Keyword type parameter. The XML syntax specification for the OPTIONS subcommand is:

<Subcommand Name="OPTIONS">
   <Parameter Name="MISSING" ParameterType="Keyword">
      <EnumValue Name="PAIRWISE"/>
      <EnumValue Name="LISTWISE"/>
   </Parameter>
</Subcommand>

An example of command syntax containing the OPTIONS subcommand is:

/OPTIONS MISSING=LISTWISE

The Keyword type always requires the parameter name, followed by an equals sign, followed by a single value.

Using the KeywordList type

The KeywordList type is used to specify a parameter that can take on multiple values. As an example, consider an OPTIONS subcommand with a parameter for specifying one or more file types from a fixed set, and represented in the syntax diagram as:

/OPTIONS FILETYPES=[SAV SAS STATA]

The specification of FILETYPES is best handled with a KeywordList type parameter. The XML syntax specification for the OPTIONS subcommand is:

<Subcommand Name="OPTIONS">
   <Parameter Name="FILETYPES" ParameterType="KeywordList">
      <EnumValue Name="SAV"/>
      <EnumValue Name="SAS"/>
      <EnumValue Name="STATA"/>
   </Parameter>
</Subcommand>

An example of command syntax containing the OPTIONS subcommand is:

/OPTIONS FILETYPES=SAV SAS

The KeywordList type always requires the parameter name, followed by an equals sign, followed by one or more values.

Using the LeadingToken Type

The LeadingToken type is used to specify a parameter that has a name but no associated value. As an example, consider a PLOT subcommand for specifying types of plots to include in output, and represented in the syntax diagram as:

/PLOT OBSERVED FORECAST FIT

The specification of PLOT is best handled with a set of LeadingToken type parameters. The XML syntax specification for the PLOT subcommand is:

<Subcommand Name="PLOT">
   <Parameter Name="OBSERVED" ParameterType="LeadingToken"/>
   <Parameter Name="FORECAST" ParameterType="LeadingToken"/>
   <Parameter Name="FIT" ParameterType="LeadingToken"/>
</Subcommand>

An example of command syntax containing the PLOT subcommand is:

/PLOT OBSERVED FIT

Using the TokenList Type

The TokenList type is used to specify a parameter that can take on multiple values. It is similar to the KeywordList type but TokenList values are not bound by the rules required of KeywordList values. As an example, consider a MODEL subcommand with a parameter for specifying model interaction effects, and represented in the syntax diagram as:

/MODEL EFFECTS=effect-list

The specification of the effects list is handled with a TokenList type parameter. The XML syntax specification for the MODEL subcommand is:

<Subcommand Name="MODEL">
   <Parameter Name="EFFECTS" ParameterType="TokenList"/>
</Subcommand>

An example of command syntax containing the MODEL subcommand is:

/MODEL EFFECTS=A*B C(D)