SPSS® 12.0 Command Syntax Reference

4 Universals
subcommand (MISSING) is not specified. If a default is not followed by **, it is in effect
when the subcommand (or keyword) is specified by itself.
Figure 1 Syntax diagram
Independent samples:
Keywords (in all upper case)
T-TEST GROUPS=varname ({1,2** }) /VARIABLES=varlist
{value }
{value,value}
User specification (in lower case)
Default (in bold)
[/MISSING={ANALYSIS**} [INCLUDE]]
{LISTWISE }
Alternatives (in aligned { })
[/FORMAT={LABELS**}]
{NOLABELS}
Optional specification (in [ ])
Paired samples:
T-TEST PAIRS=varlist [WITH varlist [(PAIRED)]] [/varlist ...]
Repeatable elements (with ...)
[/MISSING={ANALYSIS**} [INCLUDE]]
{LISTWISE }
Parentheses (cannot be omitted)
[/FORMAT={LABELS**}]
{NOLABELS}
**Default if the subcommand is omitted.
• Parentheses, apostrophes, and quotation marks are required where indicated.
• Elements enclosed in square brackets ([ ]) are optional. Wherever brackets would confuse
the format, they are omitted. The command description explains which specifications are
required and which are optional.
• Braces ({ }) indicate a choice between elements. You can specify any one of the elements
enclosed within the aligned braces.
• Ellipses indicate that you can repeat an element in the specification. The specification
T-TEST PAIRS=varlist [WITH varlist [(PAIRED)]] [/varlist ...]
means that you can specify multiple variable lists with optional WITH variables and the
keyword PAIRED in parentheses.
• Most abbreviations are obvious; for example, varname stands for variable name and varlist
stands for a variable list.
• The command terminator is not shown in the syntax diagram.
Command Specification
Note
Subgrouping (in italics)
The following rules apply to all commands:
• Commands begin with a keyword that is the name of the command and often have
additional specifications, such as subcommands and user specifications. Refer to the
discussion of each command to see which subcommands and additional specifications are
required.
• Commands and any command specifications can be entered in upper and lower case.
Commands, subcommands, keywords, and variable names are translated to upper case