IBM SPSS Statistics Core System User Guide
IBM SPSS Statistics Core System User Guide
IBM SPSS Statistics Core System User Guide
User's Guide
IBM
Note
Before using this information and the product it supports, read the information in “Notices” on page
267.
Product Information
This edition applies to version 27, release 0, modification 0 of IBM® SPSS® Statistics and to all subsequent releases and
modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation .
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
Contents
Chapter 1. Overview.............................................................................................. 1
Windows....................................................................................................................................................... 1
Designated window versus active window............................................................................................ 1
Variable names and variable labels in dialog box lists............................................................................... 1
Data type, measurement level, and variable list icons............................................................................... 2
Auto-Recovery..............................................................................................................................................2
Restore points.........................................................................................................................................2
Finding out more.......................................................................................................................................... 3
iii
Opening Data Files from a Remote Server................................................................................................ 43
File Access in Local and Distributed Analysis Mode................................................................................. 43
Availability of Procedures in Distributed Analysis Mode.......................................................................... 44
Absolute versus Relative Path Specifications...........................................................................................44
iv
Setting measurement level for variables with unknown measurement level..........................................66
Multiple Response Sets............................................................................................................................. 67
Defining Multiple Response Sets......................................................................................................... 67
Copy Data Properties................................................................................................................................. 68
Copying Data Properties.......................................................................................................................68
Identifying Duplicate Cases.......................................................................................................................71
Visual Binning.............................................................................................................................................72
To Bin Variables....................................................................................................................................73
Binning Variables..................................................................................................................................73
Automatically Generating Binned Categories..................................................................................... 74
Copying Binned Categories.................................................................................................................. 75
User-Missing Values in Visual Binning.................................................................................................76
v
Select cases............................................................................................................................................. 103
Select cases: If................................................................................................................................... 104
Select cases: Random sample...........................................................................................................104
Select cases: Range........................................................................................................................... 104
Weight cases............................................................................................................................................104
Restructuring Data...................................................................................................................................105
To Restructure Data........................................................................................................................... 105
Restructure Data Wizard: Select Type...............................................................................................105
Restructure Data Wizard (Variables to Cases): Number of Variable Groups....................................108
Restructure Data Wizard (Variables to Cases): Select Variables...................................................... 108
Restructure Data Wizard (Variables to Cases): Create Index Variables...........................................109
Restructure Data Wizard (Variables to Cases): Create One Index Variable..................................... 110
Restructure Data Wizard (Variables to Cases): Create Multiple Index Variables.............................111
Restructure Data Wizard (Variables to Cases): Options................................................................... 111
Restructure Data Wizard (Cases to Variables): Select Variables...................................................... 111
Restructure Data Wizard (Cases to Variables): Sort Data................................................................. 112
Restructure Data Wizard (Cases to Variables): Options....................................................................112
Restructure Data Wizard: Finish........................................................................................................ 113
vi
Grouping rows or columns ................................................................................................................ 130
Ungrouping rows or columns............................................................................................................. 130
Rotating row or column labels........................................................................................................... 130
Sorting rows....................................................................................................................................... 130
Inserting rows and columns.............................................................................................................. 131
Controlling display of variable and value labels................................................................................131
Changing the output language...........................................................................................................131
Navigating large tables...................................................................................................................... 132
Undoing changes................................................................................................................................132
Working with layers................................................................................................................................. 132
Creating and displaying layers...........................................................................................................132
Go to layer category........................................................................................................................... 133
Showing and hiding items....................................................................................................................... 133
Hiding rows and columns in a table...................................................................................................133
Showing hidden rows and columns in a table................................................................................... 133
Hiding and showing dimension labels............................................................................................... 133
Hiding and showing table titles......................................................................................................... 133
TableLooks...............................................................................................................................................133
To apply a TableLook......................................................................................................................... 134
To edit or create a TableLook............................................................................................................ 134
Table properties...................................................................................................................................... 134
To change pivot table properties....................................................................................................... 134
Table properties: general...................................................................................................................134
Table properties: notes......................................................................................................................135
Table properties: cell formats........................................................................................................... 135
Table properties: borders.................................................................................................................. 136
Table properties: printing.................................................................................................................. 136
Cell properties......................................................................................................................................... 137
Font and background......................................................................................................................... 137
Format value.......................................................................................................................................137
Alignment and margins...................................................................................................................... 137
Footnotes and captions........................................................................................................................... 137
Adding footnotes and captions..........................................................................................................137
To hide or show a caption.................................................................................................................. 137
To hide or show a footnote in a table................................................................................................ 138
Footnote marker.................................................................................................................................138
Renumbering footnotes..................................................................................................................... 138
Editing footnotes in legacy tables......................................................................................................138
Data cell widths....................................................................................................................................... 139
Changing column width........................................................................................................................... 139
Displaying hidden borders in a pivot table..............................................................................................139
Selecting rows, columns, and cells in a pivot table................................................................................ 139
Printing pivot tables.................................................................................................................................140
Controlling table breaks for wide and long tables............................................................................ 140
Creating a chart from a pivot table..........................................................................................................141
Legacy tables........................................................................................................................................... 141
vii
Chapter 13. Automated Output Modification.......................................................149
Style Output: Select ................................................................................................................................ 149
Style Output............................................................................................................................................. 150
Style Output: Labels and Text............................................................................................................152
Style Output: Indexing....................................................................................................................... 152
Style Output: TableLooks...................................................................................................................152
Style Output: Size...............................................................................................................................152
Table Style............................................................................................................................................... 152
Table Style: Condition........................................................................................................................ 153
Table Style: Format............................................................................................................................ 154
viii
Chapter 18. Options...........................................................................................179
Options.....................................................................................................................................................179
General options....................................................................................................................................... 179
Language options.....................................................................................................................................181
Viewer options......................................................................................................................................... 182
Data Options............................................................................................................................................ 182
Changing the default variable view....................................................................................................184
Currency options......................................................................................................................................184
To create custom currency formats.................................................................................................. 184
Output options......................................................................................................................................... 184
Chart options........................................................................................................................................... 185
Data Element Colors.......................................................................................................................... 185
Data Element Lines............................................................................................................................ 186
Data Element Markers........................................................................................................................186
Data Element Fills.............................................................................................................................. 187
Pivot Tables options................................................................................................................................ 187
File Locations options..............................................................................................................................188
Script options...........................................................................................................................................189
Multiple imputations options.................................................................................................................. 190
Syntax editor options...............................................................................................................................190
Privacy options.........................................................................................................................................191
ix
Chapter 21. Production jobs...............................................................................235
Syntax files...............................................................................................................................................236
Output...................................................................................................................................................... 236
HTML options .....................................................................................................................................237
PowerPoint options ........................................................................................................................... 237
PDF options ....................................................................................................................................... 237
Text options .......................................................................................................................................237
Production jobs with OUTPUT commands........................................................................................ 238
Runtime values........................................................................................................................................ 238
Run options.............................................................................................................................................. 239
Server login.............................................................................................................................................. 239
Adding and Editing Server Login Settings..........................................................................................239
User prompts........................................................................................................................................... 239
Background job status.............................................................................................................................240
Running production jobs from a command line......................................................................................240
Converting Production Facility files.........................................................................................................241
Chapter 25. Encrypting data files, output documents, and syntax files................ 265
Notices..............................................................................................................267
Trademarks..............................................................................................................................................268
Index................................................................................................................ 269
x
Chapter 1. Overview
Windows
There are a number of different types of windows in IBM SPSS Statistics:
Data Editor. The Data Editor displays the contents of the data file. You can create new data files or modify
existing data files with the Data Editor. If you have more than one data file open, there is a separate Data
Editor window for each data file.
Viewer. All statistical results, tables, and charts are displayed in the Viewer. You can edit the output and
save it for later use. A Viewer window opens automatically the first time you run a procedure that
generates output.
Pivot Table Editor. Output that is displayed in pivot tables can be modified in many ways with the Pivot
Table Editor. You can edit text, swap data in rows and columns, add color, create multidimensional
tables, and selectively hide and show results.
Chart Editor. You can modify high-resolution charts and plots in chart windows. You can change the
colors, select different type fonts or sizes, switch the horizontal and vertical axes, rotate 3-D scatterplots,
and even change the chart type.
Text Output Editor. Text output that is not displayed in pivot tables can be modified with the Text Output
Editor. You can edit the output and change font characteristics (type, style, color, size).
Syntax Editor. You can paste your dialog box choices into a syntax window, where your selections appear
in the form of command syntax. You can then edit the command syntax to use special features that are
not available through dialog boxes. You can save these commands in a file for use in subsequent sessions.
Ordinal
Nominal
• For more information on measurement level, see “Variable measurement level” on page 47.
• For more information on numeric, string, date, and time data types, see “Variable type” on page 47.
Auto-Recovery
The Auto-Recovery dialog displays in instances when there is unsaved data in the active session and IBM
SPSS Statistics exits unexpectedly (the dialog displays after relaunching SPSS Statistics). The dialog
provides options for restoring data from previous sessions that quit unexpectedly and for deleting saved
session data.
Note: Saved session data will remain in a backed-up state until you either restore or delete the data. The
Document Recovery dialog will continue to display each time you launch SPSS Statistics until all saved
sessions are either restored or deleted.
Refer to the Automatic Recovery section in the “General options” on page 179 dialog for information on
the available automatic recovery settings.
Restore points
Restore points save data from active sessions that either quit unexpectedly (automatic recovery) or that
you explicitly save. Each restore point is an SPSS Statistics session snapshot. Each restore point contains
Data Editor, syntax, and output file information that was active at the time the session either quit
Restore Point... dialog. Select a restore point and click the delete icon .
Chapter 1. Overview 3
4 IBM SPSS Statistics 27 Core System User's Guide
Chapter 2. Getting help
Context-sensitive help
In many places in the user interface, you can get context-sensitive help.
• Help buttons in dialogs take you directly to the help topic for that dialog.
• Right-click on terms in an activated pivot table in the Viewer and choose What's This? from the pop-up
menu to display definitions of the terms.
• In a command syntax window, position the cursor anywhere within a syntax block for a command and
press F1 on the keyboard. The help for that command is displayed
Other resources
Answers to many common problems can be found at https://www.ibm.com/products/spss-statistics/
support.
If you're a student using a student, academic or grad pack version of any IBM SPSS software product,
please see our special online Solutions for Education pages for students. If you're a student using a
university-supplied copy of the IBM SPSS software, please contact the IBM SPSS product coordinator at
your university.
The IBM SPSS Statistics community has resources for all levels of users and application developers.
Download utilities, graphics examples, new statistical modules, and articles. Visit the IBM SPSS Statistics
community at https://www.ibm.com/community/spss-statistics.
Documentation in PDF format for statistical algorithms and command syntax is available at https://
www.ibm.com/support/pages/ibm-spss-statistics-27-documentation.
6 IBM SPSS Statistics 27 Core System User's Guide
Chapter 3. Data files
Data files come in a wide variety of formats, and this software is designed to handle many of them,
including:
• Excel spreadsheets
• Database tables from many database sources, including Oracle, SQLServer, DB2, and others
• Tab-delimited, CSV, and other types of simple text files
• SAS data files
• Stata data files
Text Wizard
The Text Wizard can read text data files formatted in a variety of ways:
• Tab-delimited files
• Space-delimited files
• Comma-delimited files
• Fixed-field format files
For delimited files, you can also specify other characters as delimiters between values, and you can
specify multiple delimiters.
Encoding
The encoding of a file affects the way character data are read. Unicode data files typically contain a byte
order mark that identifies the character encoding. Some applications create Unicode files without a byte
order mark, and code page data files do not contain any encoding identifier.
• Unicode (UTF-8). Reads the file as Unicode UTF-8.
• Unicode (UTF-16). Reads the file as Unicode UTF-16 in the endianness of the operating system.
• Unicode (UTF-16BE). Reads the file as Unicode UTF-16, big endian.
• Unicode (UTF-16LE). Reads the file as Unicode UTF-16, little endian.
• Local Encoding. Reads the file in current locale code page character encoding.
If a file contains a Unicode byte order mark, it is read in that Unicode encoding, regardless of the encoding
you select. If a file does not contain a Unicode byte order mark, by default the encoding is assumed to be
the current locale code page character encoding, unless you select one of the Unicode encodings.
To change the current locale for data files in a different code page character encoding, select
Edit>Options from the menus, and change the locale on the Language tab.
Formatting options
Formatting options for reading variables include:
Automatic
The format is determined based on an evaluation of all the data values.
Numeric
Valid values include numbers, a leading plus or minus sign, and a decimal indicator.
Connection Pooling
If you access the same database source multiple times in the same session or job, you can improve
performance with connection pooling.
1. In the last step of the wizard, paste the command syntax into a syntax window.
2. At the end of the quoted CONNECT string, add Pooling=true.
Aggregating Data
If you are in distributed mode, connected to a remote server (available with IBM SPSS Statistics Server),
you can aggregate the data before reading it into IBM SPSS Statistics.
You can also aggregate data after reading it into IBM SPSS Statistics, but preaggregating may save time
for large data sources.
1. To create aggregated data, select one or more break variables that define how cases are grouped.
2. Select one or more aggregated variables.
3. Select an aggregate function for each aggregate variable.
4. Optionally, create a variable that contains the number of cases in each break group.
Note: If you use IBM SPSS Statistics random sampling, aggregation is not available.
Defining Variables
Variable names and labels. The complete database field (column) name is used as the variable label.
Unless you modify the variable name, the Database Wizard assigns variable names to each column from
the database in one of two ways:
• If the name of the database field forms a valid, unique variable name, the name is used as the variable
name.
• If the name of the database field does not form a valid, unique variable name, a new, unique name is
automatically generated.
Click any cell to edit the variable name.
Converting strings to numeric values. Select the Recode to Numeric box for a string variable if you want
to automatically convert it to a numeric variable. String values are converted to consecutive integer values
based on alphabetical order of the original values. The original values are retained as value labels for the
new variables.
Width for variable-width string fields. This option controls the width of variable-width string values. By
default, the width is 255 bytes, and only the first 255 bytes (typically 255 characters in single-byte
languages) will be read. The width can be up to 32,767 bytes. Although you probably don't want to
Sorting Cases
If you are in distributed mode, connected to a remote server (available with IBM SPSS Statistics Server),
you can sort the data before reading it into IBM SPSS Statistics.
You can also sort data after reading it into IBM SPSS Statistics, but presorting may save time for large
data sources.
Results
The Results step displays the SQL Select statement for your query.
• You can edit the SQL Select statement before you run the query, but if you click the Back button to
make changes in previous steps, the changes to the Select statement will be lost.
• To save the query for future use, use the Save query to file section.
• To paste complete GET DATA syntax into a syntax window, select Paste it into the syntax editor for
further modification. Copying and pasting the Select statement from the Results window will not paste
the necessary command syntax.
Note: The pasted syntax contains a blank space before the closing quote on each line of SQL that is
generated by the wizard. These blanks are not superfluous. When the command is processed, all lines of
the SQL statement are merged together in a very literal fashion. Without the space, there would be no
space between the last character on one line and first character on the next line.
Cognos connections
The Cognos Connections dialog specifies the IBM Cognos Business Intelligence server URL and any
required additional credentials.
Cognos server URL. The URL of the IBM Cognos Business Intelligence server. This is the value of the
"external dispatcher URI" environment property of IBM Cognos Configuration on the server. Contact your
system administrator for more information
Mode. Select Set Credentials if you need to log in with a specific namespace, username and password
(for example, as an administrator). Select Use Anonymous connection to log in with no user credentials,
in which case you do not fill in the other fields. Select Stored Credentials to use the login information
from a stored credential. To use a stored credential, you must be connected to the IBM SPSS
Collaboration and Deployment Services Repository that contains the credential. After you are connected
to the repository, click Browse to see the list of available credentials.
Namespace ID. The security authentication provider used to log on to the server. The authentication
provider is used to define and maintain users, groups, and roles, and to control the authentication
process.
User name. Enter the user name with which to log on to the server.
Password. Enter the password associated with the specified user name.
Save as Default. Saves these settings as your default, to avoid having to re-enter them each time.
Cognos location
The Specify Location dialog box enables you to select a package from which to import data, or a package
or folder from which to import reports. It displays the public folders that are available to you. If you select
Data in the main dialog, the list will display folders containing data packages. If you select Report in the
main dialog, the list will display folders containing list reports. Select the location you want by navigating
through the folder structure.
File information
A data file contains much more than raw data. It also contains any variable definition information,
including:
• Variable names
• Variable formats
• Descriptive variable and value labels
This information is stored in the dictionary portion of the data file. The Data Editor provides one way to
view the variable definition information. You can also display complete dictionary information for the
active dataset or any other data file.
To Display Data File Information
1. From the menus in the Data Editor window choose:
File > Display Data File Information
2. For the currently open data file, choose Working File.
3. For other data files, choose External File, and then select the data file.
The data file information is displayed in the Viewer.
Options
Depending on the file type, additional options are available.
Encoding
Available for SAS files and text data formats: tab-delimited, comma-delimited, and fixed ASCII text.
Write variable names to file
Available for Excel, tab-delimited, comma-delimited, 1-2-3, and SYLK. For Excel 97 and later
versions, you can write either variable names or labels. For variables without defined variable labels,
the variable name is used.
Sheet name
For Excel 2007 and later versions, you can specify a sheet name. You can also append a sheet to an
existing file.
Save value labels to a .sas file
SAS 6 and later versions.
For information on exporting data to database tables, see “Exporting to a Database” on page 29.
Options
• For all versions of Excel, you can include variable names as the first row of the Excel file.
• For Excel 97 and later versions, you can write either variable names or labels. For variables without
defined variable labels, the variable name is used.
• For Excel 2007 and later versions, you can specify a sheet name. You can also append a sheet to an
existing file.
Variable types
The following table shows the variable type matching between the original data in IBM SPSS Statistics
and the exported data in Excel.
Table 2. How Excel data formats map to IBM SPSS Statistics variable types and formats
IBM SPSS Statistics Variable Type Excel Data Format
Numeric 0.00; #,##0.00; ...
Comma 0.00; #,##0.00; ...
Dollar $#,##0_); ...
Date d-mmm-yyyy
Time hh:mm:ss
String General
Variable types
The following table shows the variable type matching between the original data in IBM SPSS Statistics
and the exported data in SAS.
Table 3. How SAS variable types and formats map to IBM SPSS Statistics types and formats
IBM SPSS Statistics Variable SAS Variable Type SAS Data Format
Type
Numeric Numeric 12
Comma Numeric 12
Dot Numeric 12
Scientific Notation Numeric 12
Date Numeric (Date) for example,
MMDDYY10, ...
Date (Time) Numeric Time18
Dollar Numeric 12
Custom Currency Numeric 12
String Character $8
Table 4. How Stata variable type and format map to IBM SPSS Statistics type and format
IBM SPSS Statistics Variable Stata Variable Type Stata Data Format
Type
Numeric Numeric g
Comma Numeric g
Dot Numeric g
Scientific Notation Numeric g
Date*, Datetime Numeric D_m_Y
Time, DTime Numeric g (number of seconds)
Wkday Numeric g (1–7)
Month Numeric g (1–12)
Dollar Numeric g
Custom Currency Numeric g
String String s
Exporting to a Database
You can use the Export to Database Wizard to:
• Replace values in existing database table fields (columns) or add new fields to a table.
• Append new records (rows) to a database table.
• Completely replace a database table or create a new table.
To export data to a database:
1. From the menus in the Data Editor window for the dataset that contains the data you want to export,
choose:
File > Export > Database
2. Select the database source.
3. Follow the instructions in the export wizard to export the data.
Creating Database Fields from IBM SPSS Statistics Variables
When creating new fields (adding fields to an existing database table, creating a new table, replacing a
table), you can specify field names, data type, and width (where applicable).
Field name. The default field names are the same as the IBM SPSS Statistics variable names. You can
change the field names to any names allowed by the database format. For example, many databases
allow characters in field names that aren't allowed in variable names, including spaces. Therefore, a
variable name like CallWaiting could be changed to the field name Call Waiting.
Type. The export wizard makes initial data type assignments based on the standard ODBC data types or
data types allowed by the selected database format that most closely matches the defined IBM SPSS
Statistics data format--but databases can make type distinctions that have no direct equivalent in IBM
SPSS Statistics, and vice versa. For example, most numeric values in IBM SPSS Statistics are stored as
User-Missing Values
There are two options for the treatment of user-missing values when data from variables are exported to
database fields:
• Export as valid values. User-missing values are treated as regular, valid, nonmissing values.
• Export numeric user-missing as nulls and export string user-missing values as blank spaces.
Numeric user-missing values are treated the same as system-missing values. String user-missing
values are converted to blank spaces (strings cannot be system-missing).
Selecting a Table
When modifying or replacing a table in the database, you need to select the table to modify or replace.
This panel in the Export to Database Wizard displays a list of tables and views in the selected database.
By default, the list displays only standard database tables. You can control the type of items that are
displayed in the list:
• Tables. Standard database tables.
• Views. Views are virtual or dynamic "tables" defined by queries. These can include joins of multiple
tables and/or fields derived from calculations based on the values of other fields. You can append
records or replace values of existing fields in views, but the fields that you can modify may be restricted,
depending on how the view is structured. For example, you cannot modify a derived field, add fields to a
view, or replace a view.
• Synonyms. A synonym is an alias for a table or view, typically defined in a query.
• System tables. System tables define database properties. In some cases, standard database tables
may be classified as system tables and will be displayed only if you select this option. Access to real
system tables is often restricted to database administrators.
Summary
• Dataset. The IBM SPSS Statistics session name for the dataset that is used to export data. This
information is primarily useful if you have multiple open data sources. A data source opened with
command syntax has a dataset name only if one is explicitly assigned.
• Table. The name of the table to be modified or created.
• Cases to Export. Either all cases are exported or cases that are selected by a previously defined filter
condition are exported.
• Action. Indicates how the database is modified (for example, create a new table, add fields or records
to an existing table).
• User-Missing Values. User-missing values can be exported as valid values or treated the same as
system-missing for numeric variables and converted to blank spaces for string variables. This setting is
controlled in the panel in which you select the variables to export.
Bulk Loading
Bulk load. Submits data to the database in batches instead of one record at a time. This action can make
the operation much faster, particularly for large data files.
• Batch size. Specifies the number records to submit in each batch.
• Batch commit. Commits records to the database in the specified batch size.
• ODBC binding. Uses the ODBC binding method to commit records in the specified batch size. This
option is only available if the database supports ODBC binding. This option is not available on macOS.
– Row-wise binding. Row-wise binding typically improves speed compared to the use of
parameterized inserts that insert data on a record-by-record basis.
– Column-wise binding. Column-wise binding improves performance by binding each database
column to an array of n values.
Comparing datasets
Compare Datasets compares the active dataset to another dataset in the current session or an external
file in IBM SPSS Statistics format.
To compare datasets
1. Open a data file and make sure it is the active dataset. (You can make a dataset the active dataset by
clicking on the Data Editor window for that dataset.)
2. From the menus choose:
Data > Compare Datasets
3. Select the open dataset or IBM SPSS Statistics data file that you want to compare to the active
dataset.
4. Select one or more fields (variables) that you want to compare.
Optionally, you can:
• Match cases (records) based on one or more case ID values.
• Compare data dictionary properties (field and value labels, user-missing values, measurement level,
etc).
• Create a flag field in the active dataset that identifies mismatched cases.
• Create new datasets that contain only matched cases or only mismatched cases.
Distributed analysis mode allows you to use a computer other than your local (or desktop) computer for
memory-intensive work. Because remote servers that are used for distributed analysis are typically more
powerful and faster than your local computer, distributed analysis mode can significantly reduce
computer processing time. Distributed analysis with a remote server can be useful if your work involves:
• Large data files, particularly data read from database sources.
• Memory-intensive tasks. Any task that takes a long time in local analysis mode may be a good candidate
for distributed analysis.
Distributed analysis affects only data-related tasks, such as reading data, transforming data, computing
new variables, and calculating statistics. Distributed analysis has no effect on tasks related to editing
output, such as manipulating pivot tables or modifying charts.
Note: Distributed analysis is available only if you have both a local version and access to a licensed server
version of the software that is installed on a remote server.
Server Login
The Server Login dialog box allows you to select the computer that processes commands and runs
procedures. You can select your local computer or a remote server.
You can add, modify, or delete remote servers in the list. Remote servers usually require a user ID and
password, and a domain name may also be necessary. If you are licensed to use the Statistics Adapter
and your site is running IBM SPSS Collaboration and Deployment Services you may be able to connect to
a remote server using single sign-on. Single sign-on allows users to connect to a remote server without
explicitly providing a user ID and password. The necessary authentication is performed with the user's
existing credentials on the current machine--obtained, for example, from Windows Active Directory.
Contact your system administrator for information about available servers, a user ID and password,
domain names, and other connection information, including whether single sign-on is supported at your
site.
You can select a default server and save the user ID, domain name, and password that are associated
with any server. You are automatically connected to the default server when you start a new session.
Important: You can connect to a server that is not at the same release level as the client. The server can
be one or two releases newer or older compared to the client. However, it is not recommended to
maintain this configuration for an extended time. If the server is newer than the client, the server may
create output that cannot be read by the client. If the client is newer than the server, syntax submitted by
the client may not be recognized by the server. Therefore, you should talk to your administrator about
connecting to a server that is at the same release level as the client.
If you are licensed to use the Statistics Adapter and your site is running IBM SPSS Collaboration and
Deployment Services 3.5 or later, you can click Search... to view a list of servers that are available on your
network. If you are not logged on to a IBM SPSS Collaboration and Deployment Services Repository, you
will be prompted to enter connection information before you can view the list of servers.
GET FILE='/bin/sales.sav'.
INSERT FILE='/bin/salesjob.sps'.
The Data Editor provides a convenient, spreadsheet-like method for creating and editing data files. The
Data Editor window opens automatically when you start a session.
The Data Editor provides two views of your data:
• Data View. This view displays the actual data values or defined value labels.
• Variable View. This view displays variable definition information, including defined variable and value
labels, data type (for example, string, date, or numeric), measurement level (nominal, ordinal, or scale),
and user-defined missing values.
In both views, you can add, change, and delete information that is contained in the data file.
Data View
Many of the features of Data View are similar to the features that are found in spreadsheet applications.
There are, however, several important distinctions:
• Rows are cases. Each row represents a case or an observation. For example, each individual respondent
to a questionnaire is a case.
• Columns are variables. Each column represents a variable or characteristic that is being measured. For
example, each item on a questionnaire is a variable.
• Cells contain values. Each cell contains a single value of a variable for a case. The cell is where the case
and the variable intersect. Cells contain only data values. Unlike spreadsheet programs, cells in the
Data Editor cannot contain formulas.
• The data file is rectangular. The dimensions of the data file are determined by the number of cases and
variables. You can enter data in any cell. If you enter data in a cell outside the boundaries of the defined
data file, the data rectangle is extended to include any rows and/or columns between that cell and the
file boundaries. There are no "empty" cells within the boundaries of the data file. For numeric variables,
blank cells are converted to the system-missing value. For string variables, a blank is considered a valid
value.
Variable View
Variable View contains descriptions of the attributes of each variable in the data file. In Variable View:
• Rows are variables.
• Columns are variable attributes.
You can add or delete variables and modify attributes of variables, including the following attributes:
• Variable name
• Data type
• Number of digits or characters
• Number of decimal places
• Descriptive variable and value labels
• User-defined missing values
• Column width
• Measurement level
All of these attributes are saved when you save the data file.
In addition to defining variable properties in Variable View, there are two other methods for defining
variable properties:
• The Copy Data Properties Wizard provides the ability to use an external IBM SPSS Statistics data file or
another dataset that is available in the current session as a template for defining file and variable
properties in the active dataset. You can also use variables in the active dataset as templates for other
variables in the active dataset. Copy Data Properties is available on the Data menu in the Data Editor
window.
• Define Variable Properties (also available on the Data menu in the Data Editor window) scans your data
and lists all unique data values for any selected variables, identifies unlabeled values, and provides an
auto-label feature. This method is particularly useful for categorical variables that use numeric codes to
represent categories--for example, 0 = Male, 1 = Female.
Variable names
The following rules apply to variable names:
• Each variable name must be unique; duplication is not allowed.
• Variable names can be up to 64 bytes long, and the first character must be a letter or one of the
characters @, #, or $. Subsequent characters can be any combination of letters, numbers,
nonpunctuation characters, and a period (.). In code page mode, sixty-four bytes typically means 64
characters in single-byte languages (for example, English, French, German, Spanish, Italian, Hebrew,
Russian, Greek, Arabic, and Thai) and 32 characters in double-byte languages (for example, Japanese,
Chinese, and Korean). Many string characters that only take one byte in code page mode take two or
more bytes in Unicode mode. For example, é is one byte in code page format but is two bytes in Unicode
format; so résumé is six bytes in a code page file and eight bytes in Unicode mode.
Note: Letters include any nonpunctuation characters used in writing ordinary words in the languages
supported in the platform's character set.
• Variable names cannot contain spaces.
• A # character in the first position of a variable name defines a scratch variable. You can only create
scratch variables with command syntax. You cannot specify a # as the first character of a variable in
dialogs that create new variables.
• A $ sign in the first position indicates that the variable is a system variable. The $ sign is not allowed as
the initial character of a user-defined variable.
• The period, the underscore, and the characters $, #, and @ can be used within variable names. For
example, A._$@#1 is a valid variable name.
• Variable names cannot begin or end with a period. Names that begin with a period are invalid; names
the end with a period may be interpreted as a command terminator. You cannot create variables that
begin or end with a period in dialogs that create new variables.
• Variable names ending in underscores should be avoided, since such names may conflict with names of
variables automatically created by commands and procedures.
• Reserved keywords cannot be used as variable names. Reserved keywords are ALL, AND, BY, EQ, GE,
GT, LE, LT, NE, NOT, OR, TO, and WITH.
• Variable names can be defined with any mixture of uppercase and lowercase characters, and case is
preserved for display purposes.
• When long variable names need to wrap onto multiple lines in output, lines are broken at underscores,
periods, and points where content changes from lower case to upper case.
Variable type
Variable Type specifies the data type for each variable. By default, all new variables are assumed to be
numeric. You can use Variable Type to change the data type. The contents of the Variable Type dialog box
depend on the selected data type. For some data types, there are text boxes for width and number of
decimals; for other data types, you can simply select a format from a scrollable list of examples.
The available data types are as follows:
Variable labels
You can assign descriptive variable labels up to 256 characters (128 characters in double-byte
languages). Variable labels can contain spaces and reserved characters that are not allowed in variable
names.
Value labels
You can assign descriptive value labels for each value of a variable. This process is particularly useful if
your data file uses numeric codes to represent non-numeric categories (for example, codes of 1 and 2 for
male and female).
Missing values
Missing Values defines specified data values as user-missing. For example, you might want to distinguish
between data that are missing because a respondent refused to answer and data that are missing
because the question didn't apply to that respondent. Data values that are specified as user-missing are
flagged for special treatment and are excluded from most calculations.
Column width
You can specify a number of characters for the column width. Column widths can also be changed in Data
View by clicking and dragging the column borders.
• Column width for proportional fonts is based on average character width. Depending on the characters
used in the value, more or fewer characters may be displayed in the specified width.
• Column width affect only the display of values in the Data Editor. Changing the column width does not
change the defined width of a variable.
Variable alignment
Alignment controls the display of data values and/or value labels in Data View. The default alignment is
right for numeric variables and left for string variables. This setting affects only the display in Data View.
Spell checking
variable and value labels
To check the spelling of variable labels and value labels:
1. Select the Variable View tab in the Data Editor window.
Entering data
In Data View, you can enter data directly in the Data Editor. You can enter data in any order. You can enter
data by case or by variable, for selected areas or for individual cells.
• The active cell is highlighted.
• The variable name and row number of the active cell are displayed in the top left corner of the Data
Editor.
• When you select a cell and enter a data value, the value is displayed in the cell editor at the top of the
Data Editor.
• Data values are not recorded until you press Enter or select another cell.
• To enter anything other than simple numeric data, you must define the variable type first.
If you enter a value in an empty column, the Data Editor automatically creates a new variable and assigns
a variable name.
Editing data
With the Data Editor, you can modify data values in Data View in many ways. You can:
• Change data values
• Cut, copy, and paste data values
• Add and delete cases
• Add and delete variables
• Change the order of variables
You can also use the Window menu to insert and remove pane splitters. To insert splitters:
1. In Data View, from the menus choose:
Window > Split
Splitters are inserted above and to the left of the selected cell.
• If the top left cell is selected, splitters are inserted to divide the current view approximately in half, both
horizontally and vertically.
• If any cell other than the top cell in the first column is selected, a horizontal pane splitter is inserted
above the selected cell.
• If any cell other than the first cell in the top row is selected, a vertical pane splitter is inserted to the left
of the selected cell.
Starting with version 14.0, multiple data sources can be open at the same time, making it easier to:
• Switch back and forth between data sources.
• Compare the contents of different data sources.
• Copy and paste data between data sources.
• Create multiple subsets of cases and/or variables for analysis.
• Merge multiple data sources from various data formats (for example, spreadsheet, database, text data)
without saving each data source first.
Once you've opened a data file or entered data in the Data Editor, you can start creating reports, charts,
and analyses without any additional preliminary work. However, there are some additional data
preparation features that you may find useful, including the ability to:
• Assign variable properties that describe the data and determine how certain values should be treated.
• Identify cases that may contain duplicate information and exclude those cases from analyses or delete
them from the data file.
• Create new variables with a few distinct categories that represent ranges of values from variables with a
large number of possible values.
Variable properties
Data entered in the Data Editor in Data View or read from an external file format (such as an Excel
spreadsheet or a text data file) lack certain variable properties that you may find very useful, including:
• Definition of descriptive value labels for numeric codes (for example, 0 = Male and 1 = Female).
• Identification of missing values codes (for example, 99 = Not applicable).
• Assignment of measurement level (nominal, ordinal, or scale).
All of these variable properties (and others) can be assigned in Variable View in the Data Editor. There are
also several utilities that can assist you in this process:
• Define Variable Properties can help you define descriptive value labels and missing values. This is
particularly useful for categorical data with numeric codes used for category values. See the topic
“Defining Variable Properties” on page 63 for more information.
• Set Measurement Level for Unknown identifies variables (fields) that do not have a defined
measurement level and provides the ability to set the measurement level for those variables. This is
important for procedures in which measurement level can affect the results or determines which
features are available. See the topic “Setting measurement level for variables with unknown
measurement level” on page 66 for more information.
• Copy Data Properties provides the ability to use an existing IBM SPSS Statistics data file as a template
for file and variable properties in the current data file. This is particularly useful if you frequently use
external-format data files that contain similar content (such as monthly reports in Excel format). See
the topic “Copying Data Properties” on page 68 for more information.
Results
The last step in the Copy Data Properties Wizard provides information on the number of variables for
which variable properties will be copied from the source data file, the number of new variables that will
be created, and the number of dataset (file) properties that will be copied.
You can also choose to paste the generated command syntax into a syntax window and save the syntax
for later use.
Missing values
For numeric variables, the system-missing value is treated like any other value—cases with the system-
missing value for an identifier variable are treated as having matching values for that variable. For string
variables, cases with no value for an identifier variable are treated as having matching values for that
variable.
Filtered cases
Filter conditions are ignored. Filtered cases are included in the evaluation of duplicate cases. If you want
to exclude cases, define selection rules with Data > Select Cases and select Delete unselected cases.
Visual Binning
Visual Binning is designed to assist you in the process of creating new variables based on grouping
contiguous values of existing variables into a limited number of distinct categories. You can use Visual
Binning to:
• Create categorical variables from continuous scale variables. For example, you could use a scale
income variable to create a new categorical variable that contains income ranges.
• Collapse a large number of ordinal categories into a smaller set of categories. For example, you could
collapse a rating scale of nine down to three categories representing low, medium, and high.
In the first step, you:
1. Select the numeric scale and/or ordinal variables for which you want to create new categorical
(binned) variables.
Optionally, you can limit the number of cases to scan. For data files with a large number of cases, limiting
the number of cases scanned can save time, but you should avoid this if possible because it will affect the
distribution of values used in subsequent calculations in Visual Binning.
Note: String variables and nominal numeric variables are not displayed in the source variable list. Visual
Binning requires numeric variables, measured on either a scale or ordinal level, since it assumes that the
data values represent some logical order that can be used to group values in a meaningful fashion. You
To Bin Variables
1. From the menus in the Data Editor window choose:
Transform > Visual Binning...
2. Select the numeric scale and/or ordinal variables for which you want to create new categorical
(binned) variables.
3. Select a variable in the Scanned Variable List.
4. Enter a name for the new binned variable. Variable names must be unique and must follow variable
naming rules. See the topic “Variable names” on page 46 for more information.
5. Define the binning criteria for the new variable. See the topic “Binning Variables” on page 73 for more
information.
6. Click OK.
Binning Variables
The Visual Binning main dialog box provides the following information for the scanned variables:
Scanned Variable List. Displays the variables you selected in the initial dialog box. You can sort the list
by measurement level (scale or ordinal) or by variable label or name by clicking on the column headings.
Cases Scanned. Indicates the number of cases scanned. All scanned cases without user-missing or
system-missing values for the selected variable are used to generate the distribution of values used in
calculations in Visual Binning, including the histogram displayed in the main dialog box and cutpoints
based on percentiles or standard deviation units.
Missing Values. Indicates the number of scanned cases with user-missing or system-missing values.
Missing values are not included in any of the binned categories. See the topic “User-Missing Values in
Visual Binning” on page 76 for more information.
Current Variable. The name and variable label (if any) for the currently selected variable that will be used
as the basis for the new, binned variable.
Binned Variable. Name and optional variable label for the new, binned variable.
• Name. You must enter a name for the new variable. Variable names must be unique and must follow
variable naming rules. See the topic “Variable names” on page 46 for more information.
• Label. You can enter a descriptive variable label up to 255 characters long. The default variable label is
the variable label (if any) or variable name of the source variable with (Binned) appended to the end of
the label.
Minimum and Maximum. Minimum and maximum values for the currently selected variable, based on the
scanned cases and not including values defined as user-missing.
Nonmissing Values. The histogram displays the distribution of nonmissing values for the currently
selected variable, based on the scanned cases.
• After you define bins for the new variable, vertical lines on the histogram are displayed to indicate the
cutpoints that define bins.
• You can click and drag the cutpoint lines to different locations on the histogram, changing the bin
ranges.
• You can remove bins by dragging cutpoint lines off the histogram.
Note: The histogram (displaying nonmissing values), the minimum, and the maximum are based on the
scanned values. If you do not include all cases in the scan, the true distribution may not be accurately
reflected, particularly if the data file has been sorted by the selected variable. If you scan zero cases, no
information about the distribution of values is available.
Data Transformations
In an ideal situation, your raw data are perfectly suitable for the type of analysis you want to perform, and
any relationships between variables are either conveniently linear or neatly orthogonal. Unfortunately,
this is rarely the case. Preliminary analysis may reveal inconvenient coding schemes or coding errors, or
data transformations may be required in order to expose the true relationship between variables.
You can perform data transformations ranging from simple tasks, such as collapsing categories for
analysis, to more advanced tasks, such as creating new variables based on complex equations and
conditional statements.
Computing Variables
Use the Compute dialog box to compute values for a variable based on numeric transformations of other
variables.
• You can compute values for numeric or string (alphanumeric) variables.
• You can create new variables or replace the values of existing variables. For new variables, you can also
specify the variable type and label.
• You can compute values selectively for subsets of data based on logical conditions.
• You can use a large variety of built-in functions, including arithmetic functions, statistical functions,
distribution functions, and string functions.
To Compute Variables
1. From the menus choose:
Transform > Compute Variable...
2. Type the name of a single target variable. It can be an existing variable or a new variable to be added
to the active dataset.
3. To build an expression, either paste components into the Expression field or type directly in the
Expression field.
• You can paste functions or commonly used system variables by selecting a group from the Function
group list and double-clicking the function or variable in the Functions and Special Variables list (or
select the function or variable and click the arrow adjacent to the Function group list). Fill in any
parameters indicated by question marks (only applies to functions). The function group labeled All
provides a listing of all available functions and system variables. A brief description of the currently
selected function or variable is displayed in a reserved area in the dialog box.
• String constants must be enclosed in quotation marks or apostrophes.
• If values contain decimals, a period (.) must be used as the decimal indicator.
• For new string variables, you must also select Type & Label to specify the data type.
Functions
Many types of functions are supported, including:
• Arithmetic functions
• Statistical functions
• String functions
• Date and time functions
• Distribution functions
• Random variable functions
• Missing value functions
• Scoring functions
For more information and a detailed description of each function, type functions on the Index tab of the
Help system.
Shift Values
Shift Values creates new variables that contain the values of existing variables from preceding or
subsequent cases.
Name. Name for the new variable. This must be a name that does not already exist in the active dataset.
Get value from earlier case (lag). Get the value from a previous case in the active dataset. For example,
with the default number of cases value of 1, each case for the new variable has the value of the original
variable from the case that immediately precedes it.
Get value from following case (lead). Get the value from a subsequent case in the active dataset. For
example, with the default number of cases value of 1, each case for the new variable has the value of the
original variable from the next case.
Recoding Values
You can modify data values by recoding them. This is particularly useful for collapsing or combining
categories. You can recode the values within existing variables, or you can create new variables based on
the recoded values of existing variables.
Automatic Recode
The Automatic Recode dialog box allows you to convert string and numeric values into consecutive
integers. When category codes are not sequential, the resulting empty cells reduce performance and
increase memory requirements for many procedures. Additionally, some procedures cannot use string
variables, and some require consecutive integer values for factor levels.
• The new variable(s) created by Automatic Recode retain any defined variable and value labels from the
old variable. For any values without a defined value label, the original value is used as the label for the
recoded value. A table displays the old and new values and value labels.
• String values are recoded in alphabetical order, with uppercase letters preceding their lowercase
counterparts.
Rank Cases
The Rank Cases dialog box allows you to create new variables containing ranks, normal and Savage
scores, and percentile values for numeric variables.
New variable names and descriptive variable labels are automatically generated, based on the original
variable name and the selected measure(s). A summary table lists the original variables, the new
variables, and the variable labels. (Note: The automatically generated new variable names are limited to a
maximum length of 8 bytes.)
Optionally, you can:
• Rank cases in ascending or descending order.
• Organize rankings into subgroups by selecting one or more grouping variables for the By list. Ranks are
computed within each group. Groups are defined by the combination of values of the grouping variables.
For example, if you select gender and minority as grouping variables, ranks are computed for each
combination of gender and minority.
To Rank Cases
1. From the menus choose:
Transform > Rank Cases...
2. Select one or more variables to rank. You can rank only numeric variables.
Optionally, you can rank cases in ascending or descending order and organize ranks into subgroups.
Define Dates
The Define Dates dialog box allows you to generate date variables that can be used to establish the
periodicity of a time series and to label output from time series analysis.
Cases Are. Defines the time interval used to generate dates.
• Not dated removes any previously defined date variables. Any variables with the following names are
deleted: year_, quarter_, month_, week_, day_, hour_, minute_, second_, and date_.
• Custom indicates the presence of custom date variables created with command syntax (for example, a
four-day workweek). This item merely reflects the current state of the active dataset. Selecting it from
the list has no effect.
First Case Is. Defines the starting date value, which is assigned to the first case. Sequential values, based
on the time interval, are assigned to subsequent cases.
Periodicity at higher level. Indicates the repetitive cyclical variation, such as the number of months in a
year or the number of days in a week. The value displayed indicates the maximum value you can enter.
For hours, minutes, and seconds the maximum is the displayed value minus one.
A new numeric variable is created for each component that is used to define the date. The new variable
names end with an underscore. A descriptive string variable, date_, is also created from the components.
For example, if you selected Weeks, days, hours, four new variables are created: week_, day_, hour_,
and date_.
If date variables have already been defined, they are replaced when you define new date variables that
will have the same names as the existing date variables.
To Define Dates for Time Series Data
1. From the menus choose:
Data > Define Dates...
2. Select a time interval from the Cases Are list.
3. Enter the value(s) that define the starting date for First Case Is, which determines the date assigned to
the first case.
Sort cases
This dialog box sorts cases (rows) of the active dataset based on the values of one or more sorting
variables. You can sort cases in ascending or descending order.
• If you select multiple sort variables, cases are sorted by each variable within categories of the
preceding variable on the Sort list. For example, if you select gender as the first sorting variable and
minority as the second sorting variable, cases will be sorted by minority classification within each
gender category.
• The sort sequence is based on the locale-defined order (and is not necessarily the same as the
numerical order of the character codes). The default locale is the operating system locale. You can
control the locale with the Language setting on the General tab of the Options dialog box (Edit menu).
To Sort Cases
1. From the menus choose:
Data > Sort Cases...
2. Select one or more sorting variables.
Optionally, you can do the following:
Index the saved file. Indexing table lookup files can improve performance when merging data files
with STAR JOIN.
Save the sorted file. You can save the sorted file, with the option of saving it as encrypted. Encryption
allows you to protect confidential information stored in the file. Once encrypted, the file can only be
opened by providing the password assigned to the file.
To save the sorted file with encryption:
3. Select Save file with sorted data and click File.
4. Select Encrypt file with password in the Save Sorted Data As dialog box.
5. Click Save.
6. In the Encrypt File dialog box, provide a password and re-enter it in the Confirm password text box.
Passwords are limited to 10 characters and are case-sensitive.
Warning: Passwords cannot be recovered if they are lost. If the password is lost the file cannot be
opened.
Creating strong passwords
• Use eight or more characters.
• Include numbers, symbols and even punctuation in your password.
• Avoid sequences of numbers or characters, such as "123" and "abc", and avoid repetition, such as
"111aaa".
• Do not create passwords that use personal information such as birthdays or nicknames.
• Periodically change the password.
Note: Storing encrypted files to an IBM SPSS Collaboration and Deployment Services Repository is not
supported.
Note: Encrypted data files and output documents cannot be opened in versions of IBM SPSS Statistics
prior to version 21. Encrypted syntax files cannot be opened in versions prior to version 22.
Sort variables
You can sort the variables in the active dataset based on the values of any of the variable attributes (e.g.,
variable name, data type, measurement level), including custom variable attributes.
• Values can be sorted in ascending or descending order.
• You can save the original (pre-sorted) variable order in a custom variable attribute.
• Sorting by values of custom variable attributes is limited to custom variable attributes that are currently
visible in Variable View.
For more information on custom variable attributes, see “Custom Variable Attributes” on page 51.
To Sort Variables
In Variable View of the Data Editor:
1. Right-click the attribute column heading and from the pop-up menu choose Sort Ascending or Sort
Descending.
or
2. From the menus in Variable View or Data View, choose:
Data > Sort Variables
3. Select the attribute you want to use to sort variables.
4. Select the sort order (ascending or descending).
• The list of variable attributes matches the attribute column names displayed in Variable View of the
Data Editor.
• You can save the original (pre-sorted) variable order in a custom variable attribute. For each variable,
the value of the attribute is an integer value indicating its position prior to sorting; so by sorting
variables based on the value of that custom attribute you can restore the original variable order.
Transpose
Transpose creates a new data file in which the rows and columns in the original data file are transposed
so that cases (rows) become variables and variables (columns) become cases. Transpose automatically
creates new variable names and displays a list of the new variable names.
Add Cases
Add Cases merges the active dataset with a second dataset or external IBM SPSS Statistics data file that
contains the same variables (columns) but different cases (rows). For example, you might record the
same information for customers in two different sales regions and maintain the data for each region in
separate files. The second dataset can be an external IBM SPSS Statistics data file or a dataset available
in the current session.
Unpaired Variables. Variables to be excluded from the new, merged data file. Variables from the active
dataset are identified with an asterisk (*). Variables from the other dataset are identified with a plus sign
(+). By default, this list contains:
• Variables from either data file that do not match a variable name in the other file. You can create pairs
from unpaired variables and include them in the new, merged file.
• Variables defined as numeric data in one file and string data in the other file. Numeric variables cannot
be merged with string variables.
• String variables of unequal width. The defined width of a string variable must be the same in both data
files.
Variables in New Active Dataset. Variables to be included in the new, merged data file. By default, all of
the variables that match both the name and the data type (numeric or string) are included on the list.
• You can remove variables from the list if you do not want them to be included in the merged file.
• Any unpaired variables included in the merged file will contain missing data for cases from the file that
does not contain that variable.
Indicate case source as variable. Indicates the source data file for each case. This variable has a value of
0 for cases from the active dataset and a value of 1 for cases from the external data file.
1. Open at least one of the data files that you want to merge. If you have multiple datasets open, make
one of the datasets that you want to merge the active dataset. The cases from this file will appear first
in the new, merged data file.
Add Variables
Add Variables merges the active data file with another open data file or external IBM SPSS Statistics data
file that contains the same cases (rows) but different variables (columns). For example, you might want to
merge a data file that contains pre-test results with one that contains post-test results.
Variables tab
Use the Variables tab to add, remove, and rename variables to include in the merged file.
• Variables from the active data file are identified with an asterisk (*).
• Variables from the other data file are identified with a plus sign (+).
Excluded Variables
Variables to exclude from the new, merged data file.
• When the One-to-one merge based on file order setting is selected on the Merge Method tab, all
variables in the second dataset whose names are the same as names in active dataset are excluded.
• When the One-to-one merge based on key values or One-to-many merge based on key values
setting is selected on the Merge Method tab, all duplicate names variables in the second dataset
(that are a different basic type (string/numeric) than the same variable names in the active dataset)
are excluded.
Included Variables
Variables to include in the new, merged data file. If you want to include an excluded variable with a
duplicate name in the merged data file, use Rename to change the name.
• When the One-to-one merge based on file order setting is selected on the Merge Method tab, all
variables in the active dataset and all uniquely named variables in the second dataset are included.
• When the One-to-one merge based on key values or One-to-many merge based on key values
setting is selected on the Merge Method tab, all uniquely named variables in both datasets are
included. Variables in the active dataset, with duplicate names in second dataset that are a different
basic type (string/numeric) in the second dataset, are also included.
Key Variables
For key value merges, cases are merged based on key variable values.
• The default list assignment is determined by the selected Merge Method. Variables are never
automatically assigned to the Key Variables list.
– When the One-to-one merge based on file order setting is selected on the Merge Method tab,
no variables are included, the Move control is disabled, and manually dragging and dropping
variables has no effect.
– When the One-to-one merge based on key values or One-to-many merge based on key values
setting is selected on the Merge Method tab, all variables with same name and same basic type
(string/numeric) in both datasets are included.
• Each key variable must have the same name and same basic data type (string or numeric) in both
files.
Aggregate Data
Aggregate Data aggregates groups of cases in the active dataset into single cases and creates a new,
aggregated file or creates new variables in the active dataset that contain aggregated data. Cases are
aggregated based on the value of zero or more break (grouping) variables. If no break variables are
specified, then the entire dataset is a single break group.
• If you create a new, aggregated data file, the new data file contains one case for each group defined by
the break variables. For example, if there is one break variable with two values, the new data file will
contain only two cases. If no break variable is specified, the new data file will contain one case.
• If you add aggregate variables to the active dataset, the data file itself is not aggregated. Each case with
the same value(s) of the break variable(s) receives the same values for the new aggregate variables. For
example, if gender is the only break variable, all males would receive the same value for a new
aggregate variable that represents average age. If no break variable is specified, all cases would receive
the same value for a new aggregate variable that represents average age.
Break Variable(s). Cases are grouped together based on the values of the break variables. Each unique
combination of break variable values defines a group. When creating a new, aggregated data file, all break
variables are saved in the new file with their existing names and dictionary information. The break
variable, if specified, can be either numeric or string.
Aggregated Variables. Source variables are used with aggregate functions to create new aggregate
variables. The aggregate variable name is followed by an optional variable label, the name of the
aggregate function, and the source variable name in parentheses.
You can override the default aggregate variable names with new variable names, provide descriptive
variable labels, and change the functions used to compute the aggregated data values. You can also
create a variable that contains the number of cases in each break group.
To Aggregate a Data File
1. From the menus choose:
Data > Aggregate...
2. Optionally select break variables that define how cases are grouped to create aggregated data. If no
break variables are specified, then the entire dataset is a single break group.
3. Select one or more aggregate variables.
4. Select an aggregate function for each aggregate variable.
Split file
Split File splits the data file into separate groups for analysis based on the values of one or more grouping
variables. If you select multiple grouping variables, cases are grouped by each variable within categories
of the preceding variable on the Groups Based On list. For example, if you select gender as the first
grouping variable and minority as the second grouping variable, cases will be grouped by minority
classification within each gender category.
• You can specify up to eight grouping variables.
• Each eight bytes of a long string variable (string variables longer than eight bytes) counts as a variable
toward the limit of eight grouping variables.
Select cases
Select Cases provides several methods for selecting a subgroup of cases based on criteria that include
variables and complex expressions. You can also select a random sample of cases. The criteria used to
define a subgroup can include:
• Variable values and ranges
• Date and time ranges
• Case (row) numbers
• Arithmetic expressions
• Logical expressions
• Functions
All cases. Turns case filtering off and uses all cases.
If condition is satisfied. Use a conditional expression to select cases. If the result of the conditional
expression is true, the case is selected. If the result is false or missing, the case is not selected.
Random sample of cases. Selects a random sample based on an approximate percentage or an exact
number of cases.
Based on time or case range. Selects cases based on a range of case numbers or a range of dates/times.
Use filter variable. Use the selected numeric variable from the data file as the filter variable. Cases with
any value other than 0 or missing for the filter variable are selected.
Output
This section controls the treatment of unselected cases. You can choose one of the following alternatives
for the treatment of unselected cases:
• Filter out unselected cases. Unselected cases are not included in the analysis but remain in the
dataset. You can use the unselected cases later in the session if you turn filtering off. If you select a
random sample or if you select cases based on a conditional expression, this generates a variable
named filter_$ with a value of 1 for selected cases and a value of 0 for unselected cases.
• Copy selected cases to a new dataset. Selected cases are copied to a new dataset, leaving the original
dataset unaffected. Unselected cases are not included in the new dataset and are left in their original
state in the original dataset.
• Delete unselected cases. Unselected cases are deleted from the dataset. Deleted cases can be
recovered only by exiting from the file without saving any changes and then reopening the file. The
deletion of cases is permanent if you save the changes to the data file.
Select cases: If
This dialog box allows you to select subsets of cases using conditional expressions. A conditional
expression returns a value of true, false, or missing for each case.
• If the result of a conditional expression is true, the case is included in the selected subset.
• If the result of a conditional expression is false or missing, the case is not included in the selected
subset.
• Most conditional expressions use one or more of the six relational operators (<, >, <=, >=, =, and ~=) on
the calculator pad.
• Conditional expressions can include variable names, constants, arithmetic operators, numeric (and
other) functions, logical variables, and relational operators.
Weight cases
Weight Cases gives cases different weights (by simulated replication) for statistical analysis.
• The values of the weighting variable should indicate the number of observations represented by single
cases in your data file.
• Cases with zero, negative, or missing values for the weighting variable are excluded from analysis.
• Fractional values are valid and some procedures, such as Frequencies, Crosstabs, and Custom Tables,
will use fractional weight values. However, most procedures treat the weighting variable as a replication
Restructuring Data
Use the Restructure Data Wizard to restructure your data for the procedure that you want to use. The
wizard replaces the current file with a new, restructured file. The wizard can:
• Restructure selected variables into cases
• Restructure selected cases into variables
• Transpose all data
To Restructure Data
1. From the menus choose:
Data > Restructure...
2. Select the type of restructuring that you want to do.
3. Select the data to restructure.
Optionally, you can:
• Create identification variables, which allow you to trace a value in the new file back to a value in the
original file
• Sort the data prior to restructuring
• Define options for the new file
• Paste the command syntax into a syntax window
In this example, the first two rows are a case group because they are related. They contain data for the
same factor level. In IBM SPSS Statistics data analysis, the factor is often referred to as a grouping
variable when the data are structured this way.
• Groups of columns. Does the current file have variables and conditions recorded in the same column?
For example:
In this example, the two columns are a variable group because they are related. They contain data for
the same variable--var_1 for factor level 1 and var_2 for factor level 2. In IBM SPSS Statistics data
analysis, the factor is often referred to as a repeated measure when the data are structured this way.
How should the data be arranged in the new file? This is usually determined by the procedure that you
want to use to analyze your data.
• Procedures that require groups of cases. Your data must be structured in case groups to do analyses
that require a grouping variable. Examples are univariate, multivariate, and variance components with
General Linear Model, Mixed Models, and OLAP Cubes and independent samples with T Test or
Table 12. Test scores recorded in separate columns for each factor
score_a score_b
1014 864
684 636
810 638
You want to do an independent-samples t test. You have a column group consisting of score_a and
score_b, but you don't have the grouping variable that the procedure requires. Select Restructure
selected variables into cases in the Restructure Data Wizard, restructure one variable group into a new
variable named score, and create an index named group. The new data file is shown in the following
figure.
When you run the independent-samples t test, you can now use group as the grouping variable.
You want to do a paired-samples t test. Your data structure is case groups, but you don't have the
repeated measures for the paired variables that the procedure requires. Select Restructure selected
When you run the paired-samples t test, you can now use bef and aft as the variable pair.
We'll restructure the variable group into a single variable, width, and create a single numeric index. The
new data are shown in the following table.
Index starts with 1 and increments for each variable in the group. It restarts each time a new row is
encountered in the original file. We can now use index in procedures that require a grouping variable.
We'll restructure the variable group into a single variable, width, and create two indices. The new data are
shown in the following table.
Creating an indicator variable results in one new variable for each unique value of product. The
restructured data are:
In this example, the restructured data could be used to get frequency counts of the products that
customers buy.
Viewer
Results are displayed in the Viewer. You can use the Viewer to:
• Browse results
• Show or hide selected tables and charts
• Change the display order of results by moving selected items
• Move items between the Viewer and other applications
The Viewer is divided into two panes:
• The left pane contains an outline view of the contents.
• The right pane contains statistical tables, charts, and text output.
You can click an item in the outline to go directly to the corresponding table or chart. You can click and
drag the right border of the outline pane to change the width of the outline pane.
Viewer outline
The outline pane provides a table of contents of the Viewer document. You can use the outline pane to
navigate through your results and control the display. Most actions in the outline pane have a
corresponding effect on the contents pane.
• Selecting an item in the outline pane displays the corresponding item in the contents pane.
• Moving an item in the outline pane moves the corresponding item in the contents pane.
• Collapsing the outline view hides the results from all items in the collapsed levels.
Controlling the outline display. To control the outline display, you can:
• Expand and collapse the outline view
• Change the outline level for selected items
• Change the size of items in the outline display
• Change the font that is used in the outline display
Copy special
When copying and pasting large amounts of output, particularly very large pivot tables, you can improve
the speed of the operation by using Edit > Copy Special to limit the number of formats copied to the
clipboard.
You can also save the selected formats as the default set of formats to copy to the clipboard. This setting
persists across sessions.
Interactive output
Interactive output objects contain multiple, related output objects. The selection in one object can
change what is displayed or highlighted in the other object. For example, selecting a row in a table might
highlight an area in a map or display a chart for a different category.
Interactive output objects do not support editing features, such as changing text, colors, fonts, or table
borders. The individual objects can be copied from the interactive object to the Viewer. Tables copied
from interactive output can be edited in the pivot table editor.
Print settings
File>Print Settings controls how interactive objects are printed.
• Print visible view only. Prints only the view that is currently displayed. This option is the default
setting.
• Print all views. Prints all views contained in the interactive output.
• The selected option also determines the default action for exporting the output object.
Export output
Export Output saves Viewer output in HTML, text, Word/RTF, Excel, PowerPoint (requires PowerPoint 97
or later), and PDF formats. Charts can also be exported in a number of different graphics formats.
Note: Export to PowerPoint is available only on Windows operating systems and is not available in the
Student Version.
To export output
1. Make the Viewer the active window (click anywhere in the window).
2. From the menus choose:
HTML options
HTML export requires a browser that is compatible with HTML 5. The following options are available for
exporting output in HTML format:
Layers in pivot tables. By default, inclusion or exclusion of pivot table layers is controlled by the table
properties for each pivot table. You can override this setting and include all layers or exclude all but the
currently visible layer. See the topic “Table properties: printing” on page 136 for more information.
Export layered tables as interactive. Layered tables are displayed as they appear in the Viewer, and you
can interactively change the displayed layer in the browser. If this option is not selected, each table layer
is displayed as a separate table.
Tables as HTML. This controls style information included for exported pivot tables.
• Export with styles and fixed column width. All pivot table style information (font styles, background
colors, etc.) and column widths are preserved.
• Export without styles. Pivot tables are converted to default HTML tables. No style attributes are
preserved. Column width is determined automatically.
Word/RTF options
The following options are available for exporting output in Word format:
Layers in pivot tables. By default, inclusion or exclusion of pivot table layers is controlled by the table
properties for each pivot table. You can override this setting and include all layers or exclude all but the
currently visible layer. See the topic “Table properties: printing” on page 136 for more information.
Wide Pivot Tables. Controls the treatment of tables that are too wide for the defined document width. By
default, the table is wrapped to fit. The table is divided into sections, and row labels are repeated for each
section of the table. Alternatively, you can shrink wide tables or make no changes to wide tables and
allow them to extend beyond the defined document width.
Preserve break points. If you have defined break points, these settings will be preserved in the Word
tables.
Include footnotes and captions. Controls the inclusion or exclusion of all pivot table footnotes and
captions.
Views of Models. By default, inclusion or exclusion of model views is controlled by the model properties
for each model. You can override this setting and include all views or exclude all but the currently visible
view. See the topic “Model properties” on page 144 for more information. (Note: all model views,
including tables, are exported as graphics.)
Page Setup for Export. This opens a dialog where you can define the page size and margins for the
exported document. The document width used to determine wrapping and shrinking behavior is the page
width minus the left and right margins.
To set Word export options
1. Select Word/RTF as the export format.
2. Click Change Options.
Excel options
The following options are available for exporting output in Excel format:
Create a worksheet or workbook or modify an existing worksheet. By default, a new workbook is
created. If a file with the specified name already exists, it will be overwritten. If you select the option to
create a worksheet, if a worksheet with the specified name already exists in the specified file, it will be
overwritten. If you select the option to modify an existing worksheet, you must also specify the worksheet
name. (This is optional for creating a worksheet.) Worksheet names cannot exceed 31 characters and
cannot contain forward or back slashes, square brackets, question marks, or asterisks.
When exporting to Excel 97-2004, if you modify an existing worksheet, charts, model views, and tree
diagrams are not included in the exported output.
Location in worksheet. Controls the location within the worksheet for the exported output. By default,
exported output will be added after the last column that has any content, starting in the first row, without
PowerPoint options
The following options are available for PowerPoint:
Layers in pivot tables. By default, inclusion or exclusion of pivot table layers is controlled by the table
properties for each pivot table. You can override this setting and include all layers or exclude all but the
currently visible layer. See the topic “Table properties: printing” on page 136 for more information.
Wide Pivot Tables. Controls the treatment of tables that are too wide for the defined document width. By
default, the table is wrapped to fit. The table is divided into sections, and row labels are repeated for each
section of the table. Alternatively, you can shrink wide tables or make no changes to wide tables and
allow them to extend beyond the defined document width.
Include footnotes and captions. Controls the inclusion or exclusion of all pivot table footnotes and
captions.
Use Viewer outline entries as slide titles. Includes a title on each slide that is created by the export.
Each slide contains a single item that is exported from the Viewer. The title is formed from the outline
entry for the item in the outline pane of the Viewer.
Views of Models. By default, inclusion or exclusion of model views is controlled by the model properties
for each model. You can override this setting and include all views or exclude all but the currently visible
view. See the topic “Model properties” on page 144 for more information. (Note: all model views,
including tables, are exported as graphics.)
Page Setup for Export. This opens a dialog where you can define the page size and margins for the
exported document. The document width used to determine wrapping and shrinking behavior is the page
width minus the left and right margins.
To set PowerPoint export options
1. Select PowerPoint as the export format.
2. Click Change Options.
Note: Export to PowerPoint is available only on Windows operating systems.
PDF options
The following options are available for PDF:
Embed bookmarks. This option includes bookmarks in the PDF document that correspond to the Viewer
outline entries. Like the Viewer outline pane, bookmarks can make it much easier to navigate documents
with a large number of output objects.
Text options
The following options are available for text export:
Pivot Table Format. Pivot tables can be exported in tab-separated or space-separated format. For space-
separated format, you can also control:
• Column Width. Autofit does not wrap any column contents, and each column is as wide as the widest
label or value in that column. Custom sets a maximum column width that is applied to all columns in
the table, and values that exceed that width wrap onto the next line in that column.
• Row/Column Border Character. Controls the characters used to create row and column borders. To
suppress display of row and column borders, enter blank spaces for the values.
Layers in pivot tables. By default, inclusion or exclusion of pivot table layers is controlled by the table
properties for each pivot table. You can override this setting and include all layers or exclude all but the
currently visible layer. See the topic “Table properties: printing” on page 136 for more information.
Include footnotes and captions. Controls the inclusion or exclusion of all pivot table footnotes and
captions.
Views of Models. By default, inclusion or exclusion of model views is controlled by the model properties
for each model. You can override this setting and include all views or exclude all but the currently visible
view. See the topic “Model properties” on page 144 for more information. (Note: all model views,
including tables, are exported as graphics.)
To set text export options
1. Select Text as the export format.
2. Click Change Options.
Print Preview
Print Preview shows you what will print on each page for Viewer documents. It is a good idea to check
Print Preview before actually printing a Viewer document, because Print Preview shows you items that
may not be visible by looking at the contents pane of the Viewer, including:
• Page breaks
• Hidden layers of pivot tables
• Breaks in wide tables
• Headers and footers that are printed on each page
If any output is currently selected in the Viewer, the preview displays only the selected output. To view a
preview for all output, make sure nothing is selected in the Viewer.
To change printed chart size, page numbering, and space between printed Items
1. Make the Viewer the active window (click anywhere in the window).
2. From the menus choose:
File > Page Attributes...
3. Click the Options tab.
4. Change the settings and click OK.
Saving output
The contents of the Viewer can be saved to the following formats:
• Viewer files (*.spv). The format that is used to display files in the Viewer window.
To save results in other formats (for example, text, Word, Excel), use Export on the File menu.
Pivot tables
Many results are presented in tables that can be pivoted interactively. That is, you can rearrange the rows,
columns, and layers.
Note: If you require tables that are compatible with IBM SPSS Statistics releases prior to 20, then it is
recommended to render them as legacy tables. See the topic “Legacy tables” on page 141 for more
information.
Pivoting a table
1. Activate the pivot table.
2. From the menus choose:
Pivot > Pivoting Trays
A table has three dimensions: rows, columns, and layers. A dimension can contain multiple elements (or
none at all). You can change the organization of the table by moving elements between or within
dimensions. To move an element, just drag and drop it where you want it.
Sorting rows
To sort the rows of a pivot table:
1. Activate the table.
2. Select any cell in the column you want to use to sort on. To sort just a selected group of rows, select
two or more contiguous cells in the column you want to use to sort on.
3. From the menus, choose:
Edit > Sort rows
4. Select Ascending or Descending from the submenu.
• If the row dimension contains groups, sorting affects only the group that contains the selection.
• You cannot sort across group boundaries.
• You cannot sort tables with more than one item in the row dimension.
Note: This feature is not available in legacy tables.
Undoing changes
You can undo the most recent change or all changes to an activated pivot table. Both actions apply only to
changes made since the most recent activation of the table.
To undo the most recent change:
1. From the menus, choose:
Edit > Undo
To undo all changes:
2. From the menus, choose:
Edit > Restore
Note: Edit > Restore is not available for legacy tables.
Go to layer category
Go to Layer Category allows you to change layers in a pivot table. This dialog box is particularly useful
when there are many layers or the selected layer has many categories.
TableLooks
A TableLook is a set of properties that define the appearance of a table. You can select a previously
defined TableLook or create your own TableLook.
• Before or after a TableLook is applied, you can change cell formats for individual cells or groups of cells
by using cell properties. The edited cell formats remain intact, even when you apply a new TableLook.
• Optionally, you can reset all cells to the cell formats that are defined by the current TableLook. This
option resets any cells that were edited. If As Displayed is selected in the TableLook Files list, any
edited cells are reset to the current table properties.
• Only table properties that are defined in the Table Properties dialog are saved in TableLooks.
TableLooks do not include individual cell modifications.
To apply a TableLook
1. Activate a pivot table.
2. From the menus, choose:
Format > TableLooks...
3. Select a TableLook from the list of files. To select a file from another directory, click Browse.
4. Click OK to apply the TableLook to the selected pivot table.
Table properties
Table Properties allows you to set general properties of a table, set cell styles for various parts of a table,
and save a set of those properties as a TableLook. You can:
• Control general properties, such as hiding empty rows or columns and adjusting printing properties.
• Control the format and position of footnote markers.
• Determine specific formats for cells in the data area, for row and column labels, and for other areas of
the table.
• Control the width and color of the lines that form the borders of each area of the table.
Cell properties
Cell properties are applied to a selected cell. You can change the font, value format, alignment, margins,
and colors. Cell properties override table properties; therefore, if you change table properties, you do not
change any individually applied cell properties.
To change cell properties:
1. Activate a table and select the cell(s) in the table.
2. From the Format menu or the pop-up menu choose Cell Properties.
Format value
The Format Value tab controls value formats for the selected cells. You can select formats for numbers,
dates, time, or currencies, and you can adjust the number of decimal digits that are displayed.
Note: The list of Currency formats contains Dollar format (numbers with a leading dollar sign) and five
custom currency formats. By default, all custom currency formats are set to the default number format,
which contains no currency or other custom symbols. Use Edit>Options>Currency to define custom
currency formats.
Footnote marker
Footnote Marker changes the characters that can be used to mark a footnote. By default, standard
footnote markers are sequential letters or numbers, depending on the table properties settings. You can
also assign a special marker. Special markers are not affected when you renumber footnotes or switch
between numbers and letters for standard markers. The display of numbers or letters for standard
markers and the subscript or superscript position of footnote markers are controlled by the Footnotes tab
of the Table Properties dialog.
Note: For changing footnote markers in legacy tables, see “Editing footnotes in legacy tables” on page
138.
To change footnote markers:
1. Select a footnote.
2. From the Format menu, choose Footnote Marker.
Special markers are limited to 2 characters. Footnotes with special markers precede footnotes with
sequential letters or numbers in the footnote area of the table; so changing to a special marker can
reorder the footnote list.
Renumbering footnotes
When you have pivoted a table by switching rows, columns, and layers, the footnotes may be out of order.
To renumber the footnotes:
1. From the Format menu choose Renumber Footnotes.
Legacy tables
You can choose to render tables as legacy tables (referred to as full-featured tables in release 19) which
are then fully compatible with IBM SPSS Statistics releases prior to 20. Legacy tables may render slowly
and are only recommended if compatibility with releases prior to 20 is required. For information on how
to create legacy tables, see “Pivot Tables options” on page 187.
Some results are presented as models, which appear in the output Viewer as a special type of
visualization. The visualization displayed in the output Viewer is not the only view of the model that is
available. A single model contains many different views. You can activate the model in the Model Viewer
and interact with the model directly to display the available model views. You can also choose to print and
export all the views in the model.
Model properties
Depending on your Model Viewer, choose:
File > Properties
or
File > Print View
Each model has associated properties that let you specify which views are printed from the output
Viewer. By default, only the view that is visible in the output Viewer is printed. This is always a main view,
and only one main view. You can also specify that all available model views are printed. These include all
the main views and all the auxiliary views (except for auxiliary views based on selection in the main view;
these are not printed). Note that you can also print individual model views within the Model Viewer itself.
See the topic “Printing a model” on page 144 for more information.
Printing a model
Printing from the Model Viewer
You can print a single model view within the Model Viewer itself.
1. Activate the model in the Model Viewer. See the topic “Interacting with a model” on page 143 for more
information.
2. From the menus choose View > Edit Mode, if available.
3. On the General toolbar palette in the main or auxiliary view (depending on which one you want to
print), click the print icon. (If this palette is not displayed, choose Palettes>General from the View
menu.)
Note: If your Model Viewer does not support a print icon, then choose File > Print.
Printing from the output Viewer
When you print from the output Viewer, the number of views that are printed for a specific model depend
on the model's properties. The model can be set to print only the displayed view or all of the available
model views. See the topic “Model properties” on page 144 for more information.
Exporting a model
By default, when you export models from the output Viewer, inclusion or exclusion of model views is
controlled by the model properties for each model. For more information about model properties, see
“Model properties” on page 144 . On export, you can override this setting and include all model views or
only the currently visible model view. In the Export Output dialog box, click Change Options... in the
Document group. For more information about exporting and this dialog box, see “Export output” on page
120 . Note that all model views, including tables, are exported as graphics. Also note that auxiliary views
based on selections in the main view are never exported.
Ensemble Viewer
Predictor Importance
Typically, you will want to focus your modeling efforts on the predictor fields that matter most and
consider dropping or ignoring those that matter least. The predictor importance chart helps you do this by
indicating the relative importance of each predictor in estimating the model. Since the values are relative,
the sum of the values for all predictors on the display is 1.0. Predictor importance does not relate to
model accuracy. It just relates to the importance of each predictor in making a prediction, not whether or
not the prediction is accurate.
Predictor importance is not available for all ensemble models. The predictor set may vary across
component models, but importance can be computed for predictors used in at least one component
model.
Predictor Frequency
The predictor set can vary across component models due to the choice of modeling method or predictor
selection. The Predictor Frequency plot is a dot plot that shows the distribution of predictors across
component models in the ensemble. Each dot represents one or more component models containing the
predictor. Predictors are plotted on the y-axis, and are sorted in descending order of frequency; thus the
topmost predictor is the one that is used in the greatest number of component models and the
bottommost one is the one that was used in the fewest. The top 10 predictors are shown.
Predictors that appear most frequently are typically the most important. This plot is not useful for
methods in which the predictor set cannot vary across component models.
Automated output modification applies formatting and other changes to the contents of the active Viewer
window. Changes that can be applied include:
• All or selected viewer objects
• Selected types of output objects (for example, charts, logs, pivot tables)
• Pivot table content based on conditional expressions
• Outline (navigation) pane content
The types of changes you can make include:
• Delete objects
• Index objects (add a sequential numbering scheme)
• Change the visible property of objects
• Change the outline label text
• Transpose rows and columns in pivot tables
• Change the selected layer of pivot tables
• Change the formatting of selected areas or specific cells in a pivot table based on conditional
expressions (for example, make all significance values less than 0.05 bold)
To specify automated output modification:
1. From the menus, choose:Utilities > Style Output
2. Select one or more objects in the Viewer.
3. Select the options you want in the Select dialog. (You can also select objects before you open the
dialog.)
4. Select the output changes you want in the Style Output dialog.
Style Output
The Style Output dialog specifies the changes you want to make to the selected output objects in the
Viewer.
Create a Backup of the Output. Changes made by the automated output modification process cannot be
undone. To preserve the original Viewer document, create a backup copy.
Object Properties
You specify the changes that you want to make to each selection from the Selections and Properties
section in the Object Properties section. The available properties are determined by the selected row in
the Selections and Properties section.
Command. The name of the procedure if the selection refers to a single procedure. The selection can
include multiple instances of the same procedure.
Type. The type of object.
Subtype. If the selection refers to a single table type, the table subtype name is displayed.
Outline Label. The label in the outline pane that is associated with the selection. You can replace the
label text or add information to the label. For more information, see the topic Style Output: Labels and
Text.
Table Style
The Table Style dialog specifies conditions for automatically changing properties of pivot tables based on
specific conditions. For example, you can make all significance values less than 0.05 bold and red. The
The powerful command language allows you to save and automate many common tasks. It also provides
some functionality not found in the menus and dialog boxes.
Most commands are accessible from the menus and dialog boxes. However, some commands and options
are available only by using the command language. The command language also allows you to save your
jobs in a syntax file so that you can repeat your analysis at a later date or run it in an automated job with
the a production job.
A syntax file is simply a text file that contains commands. While it is possible to open a syntax window
and type in commands, it is often easier if you let the software help you build your syntax file using one of
the following methods:
• Pasting command syntax from dialog boxes
• Copying syntax from the output log
• Copying syntax from the journal file
Detailed command syntax reference information is available in two forms: integrated into the overall Help
system and as a separate PDF file, called the Command Syntax Reference, also available from the Help
menu. Context-sensitive Help for the current command in a syntax window is available by pressing the F1
key.
Syntax Rules
When you run commands from a command syntax window during a session, you are running commands in
interactive mode.
The following rules apply to command specifications in interactive mode:
• Each command must start on a new line. Commands can begin in any column of a command line and
continue for as many lines as needed. The exception is the END DATA command, which must begin in
the first column of the first line after the end of data.
• Each command should end with a period as a command terminator. It is best to omit the terminator on
BEGIN DATA, however, so that inline data are treated as one continuous specification.
• The command terminator must be the last nonblank character in a command.
• In the absence of a period as the command terminator, a blank line is interpreted as a command
terminator.
Note: For compatibility with other modes of command execution (including command files run with
INSERT or INCLUDE commands in an interactive session), each line of command syntax should not
exceed 256 characters.
• Most subcommands are separated by slashes (/). The slash before the first subcommand on a
command is usually optional.
• Variable names must be spelled out fully.
• Text included within apostrophes or quotation marks must be contained on a single line.
• A period (.) must be used to indicate decimals, regardless of your regional or locale settings.
• Variable names ending in a period can cause errors in commands created by the dialog boxes. You
cannot create such variable names in the dialog boxes, and you should generally avoid them.
Command syntax is case insensitive, and three- or four-letter abbreviations can be used for many
command specifications. You can use as many lines as you want to specify a single command. You can
add space or break lines at almost any point where a single blank is allowed, such as around slashes,
parentheses, arithmetic operators, or between variable names. For example,
FREQUENCIES
VARIABLES=JOBCAT GENDER
/PERCENTILES=25 50 75
/BARCHART.
and
Terminology
Commands. The basic unit of syntax is the command. Each command begins with the command name,
which consists of one, two, or three words--for example, DESCRIPTIVES, SORT CASES, or ADD VALUE
LABELS.
Auto-Completion
The Syntax Editor provides assistance in the form of auto-completion of commands, subcommands,
keywords, and keyword values. By default, you are prompted with a context-sensitive list of available
terms as you type. Pressing Enter or Tab will insert the currently highlighted item in the list at the position
of the cursor. You can display the list on demand by pressing Ctrl+Spacebar and you can close the list by
pressing the Esc key.
The Auto Complete menu item on the Tools menu toggles the automatic display of the auto-complete list
on or off. You can also enable or disable automatic display of the list from the Syntax Editor tab in the
Options dialog box. Toggling the Auto Complete menu item overrides the setting on the Options dialog but
does not persist across sessions.
Note: The auto-completion list will close if a space is entered. For commands consisting of multiple
words--such as ADD FILES--select the command before entering any spaces.
Color Coding
The Syntax Editor color codes recognized elements of command syntax, such as commands and
subcommands, as well as various syntactical errors like unmatched quotes or parentheses. Unrecognized
text is not color coded.
Commands. By default, recognized commands are colored blue and in bold text. If, however, there is a
recognized syntactical error within the command--such as a missing parenthesis--the command name is
colored red and in bold text by default.
Note: Abbreviations of command names--such as FREQ for FREQUENCIES--are not colored, but such
abbreviations are valid.
Subcommands. Recognized subcommands are colored green by default. If, however, the subcommand is
missing a required equals sign or an invalid equals sign follows it, the subcommand name is colored red
by default.
Keywords. Recognized keywords are colored maroon by default. If, however, the keyword is missing a
required equals sign or an invalid equals sign follows it, the keyword is colored red by default.
Keyword values. Recognized keyword values are colored orange by default. User-specified values of
keywords such as integers, real numbers, and quoted strings are not color coded.
Comments. Text within a comment is colored gray by default.
Quotes. Quotes and text within quotes are colored black by default.
Syntactical Errors. Text associated with the following syntactical errors is colored red by default.
Breakpoints
Breakpoints allow you to stop execution of command syntax at specified points within the syntax window
and continue execution when ready.
• Breakpoints are set at the level of a command and stop execution prior to running the command.
• Breakpoints cannot occur within LOOP-END LOOP, DO IF-END IF, DO REPEAT-END REPEAT, INPUT
PROGRAM-END INPUT PROGRAM, and MATRIX-END MATRIX blocks. They can, however, be set at the
beginning of such blocks and will stop execution prior to running the block.
• Breakpoints cannot be set on lines containing non-IBM SPSS Statistics command syntax, such as occur
within BEGIN PROGRAM-END PROGRAM, BEGIN DATA-END DATA, and BEGIN GPL-END GPL blocks.
• Breakpoints are not saved with the command syntax file and are not included in copied text.
• By default, breakpoints are honored during execution. You can toggle whether breakpoints are honored
or not from Tools > Honor Breakpoints.
To Insert a Breakpoint
1. Click anywhere in the gutter to the left of the command text.
or
2. Position the cursor within the command.
3. From the menus choose:
Tools > Toggle Breakpoint
The breakpoint is represented as a red circle in the gutter to the left of the command text and on the
same line as the command name.
Clearing Breakpoints
To clear a single breakpoint:
1. Click the icon representing the breakpoint in the gutter to the left of the command text.
or
2. Position the cursor within the command.
3. From the menus choose:
Bookmarks
Bookmarks allow you to quickly navigate to specified positions in a command syntax file. You can have up
to 9 bookmarks in a given file. Bookmarks are saved with the file, but are not included when copying text.
To Insert a Bookmark
1. Position the cursor on the line where you want to insert the bookmark.
2. From the menus choose:
Tools > Toggle Bookmark
The new bookmark is assigned the next available number, from 1 to 9. It is represented as a square
enclosing the assigned number and displayed in the gutter to the left of the command text.
Clearing Bookmarks
To clear a single bookmark:
1. Position the cursor on the line containing the bookmark.
2. From the menus choose:
Tools > Toggle Bookmark
To clear all bookmarks:
1. From the menus choose:
Tools > Clear All Bookmarks
Renaming a Bookmark
You can associate a name with a bookmark. This is in addition to the number (1-9) assigned to the
bookmark when it was created.
1. From the menus choose:
Tools > Rename Bookmark
2. Enter a name for the bookmark and click OK.
The specified name replaces any existing name for the bookmark.
Navigating with Bookmarks
To navigate to the next or previous bookmark:
1. From the menus choose:
Tools > Next Bookmark
or
Tools > Previous Bookmark
To navigate to a specific bookmark:
1. From the menus choose:
Tools > Go To Bookmark
2. Select the bookmark.
Formatting Syntax
You can indent or outdent selected lines of syntax and you can automatically indent selections so that the
syntax is formatted in a manner similar to syntax pasted from a dialog box.
• The default indent is four spaces and applies to indenting selected lines of syntax as well as to
automatic indentation. You can change the indent size from the Syntax Editor tab in the Options dialog
box.
• Note that using the Tab key in the Syntax Editor does not insert a tab character. It inserts a space.
To indent text
1. Select the text or position the cursor on a single line that you want to indent.
2. From the menus choose:
Tools > Indent Syntax > Indent
You can also indent a selection or line by pressing the Tab key.
To outdent text
1. Select the text or position the cursor on a single line that you want to outdent.
2. From the menus choose:
Tools > Indent Syntax > Outdent
To automatically indent text
1. Select the text.
2. From the menus choose:
Tools > Indent Syntax > Auto Indent
When you automatically indent text, any existing indentation is removed and replaced with the
automatically generated indents. Note that automatically indenting code within a BEGIN PROGRAM block
may break the code if it depends on specific indentation to function, such as Python code containing
loops and conditional blocks.
Syntax formatted with the auto-indent feature may not run in batch mode. For example, auto-indenting an
INPUT PROGRAM-END INPUT PROGRAM, LOOP-END LOOP, DO IF-END IF or DO REPEAT-END
REPEAT block will cause the syntax to fail in batch mode because commands in the block will be indented
* Encoding: en_US.windows-1252.
COMPUTE lagvar=LAG(var1).
COMPUTE var1=var1*2.
and
COMPUTE lagvar=LAG(var1).
EXECUTE.
COMPUTE var1=var1*2.
yield very different results for the value of lagvar, since the former uses the transformed value of var1
while the latter uses the original value.
* Encoding: en_US.windows-1252.
COMPUTE lagvar=LAG(var1).
COMPUTE var1=var1*2.
and
COMPUTE lagvar=LAG(var1).
EXECUTE.
COMPUTE var1=var1*2.
yield very different results for the value of lagvar, since the former uses the transformed value of var1
while the latter uses the original value.
High-resolution charts and plots are created by the procedures on the Graphs menu and by many of the
procedures on the Analyze menu. This chapter provides an overview of the chart facility.
Building Charts
The Chart Builder allows you to build charts from predefined gallery charts or from the individual parts
(for example, axes and bars). You build a chart by dragging and dropping the gallery charts or basic
elements onto the canvas, which is the large area to the right of the Variables list in the Chart Builder
dialog box.
As you are building the chart, the canvas displays a preview of the chart. Although the preview uses
defined variable labels and measurement levels, it does not display your actual data. Instead, it uses
randomly generated data to provide a rough sketch of how the chart will look.
Using the gallery is the preferred method for new users. For information about using the gallery, see
“Building a Chart from the Gallery” on page 167.
How to Start the Chart Builder
1. From the menus choose:
Graphs > Chart Builder
Editing Charts
The Chart Editor provides a powerful, easy-to-use environment where you can customize your charts and
explore your data. The Chart Editor features:
• Simple, intuitive user interface. You can quickly select and edit parts of the chart using menus and
toolbars. You can also enter text directly on a chart.
• Wide range of formatting and statistical options. You can choose from a full range of styles and
statistical options.
• Powerful exploratory tools. You can explore your data in various ways, such as by labeling, reordering,
and rotating it. You can change chart types and the roles of variables in the chart. You can also add
distribution curves and fit, interpolation, and reference lines.
• Flexible templates for consistent look and behavior. You can create customized templates and use
them to easily create charts with the look and options that you want. For example, if you always want a
specific orientation for axis labels, you can specify the orientation in a template and apply the template
to other charts.
How to View the Chart Editor
1. Double-click a chart in the Viewer.
The process of applying a predictive model to a set of data is referred to as scoring the data. IBM SPSS
Statistics has procedures for building predictive models such as regression, clustering, tree, and neural
network models. Once a model has been built, the model specifications can be saved in a file that
contains all of the information necessary to reconstruct the model. You can then use that model file to
generate predictive scores in other datasets. Note: Some procedures produce a model XML file, and some
procedures produce a compressed file archive (.zip file).
Example. The direct marketing division of a company uses results from a test mailing to assign propensity
scores to the rest of their contact database, using various demographic characteristics to identify
contacts most likely to respond and make a purchase.
Scoring is treated as a transformation of the data. The model is expressed internally as a set of numeric
transformations to be applied to a given set of fields (variables)--the predictors specified in the model--in
order to obtain a predicted result. In this sense, the process of scoring data with a given model is
inherently the same as applying any function, such as a square root function, to a set of data.
The scoring process consists of two basic steps:
1. Build the model and save the model file. You build the model using a dataset for which the outcome of
interest (often referred to as the target) is known. For example, if you want to build a model that will
predict who is likely to respond to a direct mail campaign, you need to start with a dataset that already
contains information on who responded and who did not respond. For example, this might be the
results of a test mailing to a small group of customers or information on responses to a similar
campaign in the past.
Note: For some model types there is no target outcome of interest. Clustering models, for example, do
not have a target, and some nearest neighbor models do not have a target.
2. Apply that model to a different dataset (for which the outcome of interest is not known) to obtain
predicted outcomes.
Scoring Wizard
You can use the Scoring Wizard to apply a model created with one dataset to another dataset and
generate scores, such as the predicted value and/or predicted probability of an outcome of interest.
To score a dataset with a predictive model
1. Open the dataset that you want to score.
2. Open the Scoring Wizard. From the menus choose:
Utilities > Scoring Wizard.
3. Select a model XML file or compressed file archive (.zip fle). Use the Browse button to navigate to a
different location to select a model file.
4. Match fields in the active dataset to fields used in the model. See the topic “ Matching model fields to
dataset fields” on page 172 for more information.
5. Select the scoring functions you want to use. See the topic “ Selecting scoring functions” on page 173
for more information.
Select a Scoring Model. The model file can be an XML file or a compressed file archive (.zip file) that
contains model PMML. The list only displays files with a .zip or .xml extension; the file extensions are not
displayed in the list. You can use any model file created by IBM SPSS Statistics. You can also use some
model files created by other applications, such as IBM SPSS Modeler, but some model files created by
other applications cannot be read by IBM SPSS Statistics, including any models that have multiple target
fields (variables).
Model Details. This area displays basic information about the selected model, such as model type, target
(if any), and predictors used to build the model. Since the model file has to be read to obtain this
information, there may be a delay before this information is displayed for the selected model. If the XML
file or .zip file is not recognized as a model that IBM SPSS Statistics can read, a message indicating that
the file cannot be read is displayed.
Utilities
This chapter describes the functions found on the Utilities menu and the ability to reorder target variable
lists.
• For information on the Scoring Wizard, see Chapter 16, “Scoring data with predictive models,” on page
171.
• For information on merging model and transformation XML files, see “Merging model and
transformation XML files” on page 174.
Variable information
The Variables dialog box displays variable definition information for the currently selected variable,
including:
• Variable label
• Data format
• User-missing values
• Value labels
• Measurement level
Visible. The Visible column in the variable list indicates if the variable is currently visible in the Data
Editor and in dialog box variable lists.
Go To. Goes to the selected variable in the Data Editor window.
Paste. Pastes the selected variables into the designated syntax window at the cursor location.
To modify variable definitions, use the Variable view in the Data Editor.
There are two ways to open the Variables dialog box.
• From the menus, choose Utilities > Variables....
• Right-click a variable name in the Data Editor and select Variable Information... from the context
menu.
Options
Options control a wide variety of settings:
• Session journal, which keeps a record of all commands run in every session
• Display order for variables in dialog box source lists
• Items that are displayed and hidden in new output results
• TableLook for new pivot tables
• Custom currency formats
Options control various settings.
General options
Variable Lists
These settings control the display of variables in dialog box lists. You can display variable names or
variable labels. Names or labels can be displayed in alphabetical or file order or grouped by measurement
level. Display order affects only source variable lists. Target variable lists always reflect the order in which
variables were selected.
Roles
Some dialogs support the ability to pre-select variables for analysis based on defined roles. See the topic
“Roles” on page 50 for more information.
Use predefined roles
By default, pre-select variables based on defined roles.
Use custom assignments
By default, do not use roles to pre-select variables.
You can also switch between predefined roles and custom assignment within the dialogs that support this
functionality. The setting here controls only the initial default behavior in effect for each dataset.
Windows
Look and feel
Controls the basic appearance of windows and dialog boxes. If you notice any display issues after
changing the look and feel, try shutting down and restarting the application.
Open syntax window at startup
Syntax windows are text file windows used to enter, edit, and run commands. If you frequently work
with command syntax, select this option to automatically open a syntax window at the beginning of
each session. This is useful primarily for experienced users who prefer to work with command syntax
instead of dialog boxes.
Open only one dataset at a time
Closes the currently open data source each time you open a different data source using the menus
and dialog boxes. By default, every time you use the menus and dialog boxes to open a new data
source, that data source opens in a new Data Editor window, and any other data sources open in other
Data Editor windows remain open and available during the session until explicitly closed.
When you select this option, it takes effect immediately but does not close any datasets that were
open at the time the setting was changed. This setting has no effect on data sources opened using
command syntax, which relies on DATASET commands to control multiple datasets. See the topic
Chapter 6, “Working with Multiple Data Sources,” on page 61 for more information.
Display native macOS file dialogs
When selected, file selection dialogs in the macOS version of SPSS Statistics are presented in native
macOS format. Historically, file selection dialogs have been heavily customized to accommodate
specific SPSS Statistics file features. This settings allows you to default file selection dialogs to native
macOS format.
Note: This feature is available only in macOS environments.
Language options
Language
Output language. Controls the language that is used in the output. Does not apply to simple text output.
The list of available languages depends on the currently installed language files. (Note: This setting does
not affect the user interface language.) Depending on the language, you might also need to use Unicode
character encoding for characters to render properly.
Note: Custom scripts that rely on language-specific text strings in the output might not run correctly when
you change the output language. For more information, see the topic “Script options” on page 189.
User Interface. This setting controls the language that is used in menus, dialogs, and other user interface
features. (Note: This setting does not affect the output language.)
Viewer options
Viewer output display options affect only new output that is produced after you change the settings.
Output that is already displayed in the Viewer is not affected by changes in these settings.
Initial Output State
Controls which items are automatically displayed or hidden each time that you run a procedure and
how items are initially aligned. You can control the display of the following items: log, warnings, notes,
titles, pivot tables, charts, tree diagrams, and text output. You can also turn the display of commands
in the log on or off. You can copy command syntax from the log and save it in a syntax file.
Note: All output items are displayed left-aligned in the Viewer. Only the alignment of printed output is
affected by the justification settings. Centered and right-aligned items are identified by a small
symbol.
Title
Controls the font style, size, and color for new output titles. The font Size list provides a set of
predefined sizes, but you can manually enter other, supported size values.
Page Title
Controls the font style, size, and color for new page titles and page titles that are generated by TITLE
and SUBTITLE command syntax or created by New Page Title on the Insert menu. The font Size list
provides a set of predefined sizes, but you can manually enter other, supported size values.
Text Output
Font that is used for text output. Text output is designed for use with a monospaced (fixed-pitch) font.
If you select a proportional font, tabular output does not align properly. The font Size list provides a
set of predefined sizes, but you can manually enter other, supported size values.
Default Page Setup
Controls the default options for orientation and margins for printing.
Data Options
Transformation and Merge Options. Each time the program executes a command, it reads the data file.
Some data transformations (such as Compute and Recode) and file transformations (such as Add
Variables and Add Cases) do not require a separate pass of the data, and execution of these commands
can be delayed until the program reads the data to execute another command, such as a statistical or
charting procedure.
• For large data files, where reading the data can take some time, you may want to select Calculate
values before used to delay execution and save processing time. When this option is selected, the
results of transformations you make using dialog boxes such as Compute Variable will not appear
immediately in the Data Editor; new variables created by transformations will be displayed without any
data values; and data values in the Data Editor cannot be changed while there are pending
transformations. Any command that reads the data, such as a statistical or charting procedure, will
execute the pending transformations and update the data displayed in the Data Editor. Alternatively,
you can use Run Pending Transforms on the Transform menu.
• With the default setting of Calculate values immediately, when you paste command syntax from
dialogs, an EXECUTE command is pasted after each transformation command. See the topic “Multiple
Execute Commands” on page 164 for more information.
Currency options
You can create up to five custom currency display formats that can include special prefix and suffix
characters and special treatment for negative values.
The five custom currency format names are CCA, CCB, CCC, CCD, and CCE. You cannot change the format
names or add new ones. To modify a custom currency format, select the format name from the source list
and make the changes that you want.
Prefixes, suffixes, and decimal indicators defined for custom currency formats are for display purposes
only. You cannot enter values in the Data Editor using custom currency characters.
Output options
Output options control the default setting for a number of output options.
Outline labeling. Controls display of variable names, variable labels, data values, and value labels in the
outline pane of the Viewer.
Pivot table labeling. Controls display of variable names, variable labels, data values, and value labels in
pivot tables.
Descriptive variable and value labels (Variable view in the Data Editor, Label and Values columns) often
make it easier to interpret your results. However, long labels can be awkward in some tables. Changing
labeling options here only affects the default display for new output.
One click descriptives. Controls options for descriptive statistics generated for selected variables in the
Data Editor. See the topic “Obtaining Descriptive Statistics for Selected Variables” on page 58 for more
information.
• Suppress tables with many categories. For variables with more than the specified number of unique
values, frequency tables will not be displayed.
Chart options
Chart Template
New charts can use either the settings selected here or the settings from a chart template file.
Available chart templates are provided in the drop-down list. The Samples section updates to reflect
the style of the selected chart template.
When User specified is selected from the drop-down list, click Browse to select a chart template file.
To create a chart template file, create a chart with the attributes that you want and save it as a
template (choose Save Chart Template from the File menu).
Current Settings
Available settings include:
Font
Font used for all text in new charts.
Style Cycle Preference
The initial assignment of colors and patterns for new charts. Cycle through colors only uses only
colors to differentiate chart elements and does not use patterns. Cycle through patterns only
uses only line styles, marker symbols, or fill patterns to differentiate chart elements and does not
use color.
Frame
Controls the display of inner and outer frames on new charts.
Grid Lines
Controls the display of scale and category axis grid lines on new charts.
Style Cycles
Customizes the colors, line styles, marker symbols, and fill patterns for new charts. You can change
the order of the colors and patterns that are used when a new chart is created.
Chart Aspect Ratio
The width-to-height ratio of the outer frame of new charts. You can specify a width-to-height ratio
from 0.1 to 10.0. Values less than 1 make charts that are taller than they are wide. Values greater
than 1 make charts that are wider than they are tall. A value of 1 produces a square chart. Once a
chart is created, its aspect ratio cannot be changed.
Sample Settings
The available settings provide options for displaying sample charts as either bar charts or
scatterplots.
TableLook
Select a TableLook from the list of files and click OK or Apply. You can use one of the TableLooks
provided with IBM SPSS Statistics, or you can create your own in the Pivot Table Editor (choose
TableLooks from the Format menu).
Browse
Allows you to select a TableLook from another directory.
Set TableLook Directory
Allows you to change the default TableLook directory. Use Browse to navigate to the directory you
want to use, select a TableLook in that directory, and then select Set TableLook Directory.
Note: TableLooks created in earlier versions of IBM SPSS Statistics cannot be used in version 16.0 or
later.
Column Widths
These options control the automatic adjustment of column widths in pivot tables.
Adjust for labels only
Adjusts column width to the width of the column label. This produces more compact tables, but data
values wider than the label may be truncated.
Adjust for labels and data for all tables
Adjusts column width to whichever is larger: the column label or the largest data value. This produces
wider tables, but it ensures that all values will be displayed.
Table Comment
You can automatically include comments for each table.
• Comment text is displayed in a tooltip when you hover over a table in the Viewer.
• Screen readers read the comment text when the table has focus.
Sample
The Sample section provides a visual representation of the selected TableLook.
Display "<.001" when significance value is less than .001 (the observed value is observed)
When this setting is selected, small significance values are presented as "<.001" in table output.
Session Journal
You can use the session journal to automatically record commands run in a session. This includes
commands entered and run in syntax windows and commands generated by dialog box choices. You can
edit the journal file and use the commands again in other sessions. You can turn journaling off and on,
Temporary folder
This specifies the location of temporary files created during a session. In distributed mode (available with
the server version), this does not affect the location of temporary data files. In distributed mode, the
location of temporary data files is controlled by the environment variable SPSSTMPDIR, which can be set
only on the computer running the server version of the software. If you need to change the location of the
temporary directory, contact your system administrator.
Python 3 Location
These settings specify the installation of Python 3.8, which is used by the IBM SPSS Statistics -
Integration Plug-in for Python when you are running Python from SPSS Statistics. By default, the Python
distribution 3.8 that is installed with SPSS Statistics (as part of IBM SPSS Statistics - Essentials for
Python) is used. The distribution is in the Python3 directory under the directory where SPSS Statistics is
installed. To use a different installation of Python on your computer, specify the path to the root directory
of that installation of Python. The setting takes effect in the current session unless Python was already
started by running a Python program, a Python script, or an extension command that is implemented in
Python. In that case, the setting will be in effect in the next session. This setting is only available in local
analysis mode. In distributed analysis mode (requires IBM SPSS Statistics Server), the Python location on
the remote server is set from the IBM SPSS Statistics Administration Console. Contact your system
administrator for assistance.
Script options
Use the Scripts tab to specify the default script language and any autoscripts you want to use. You can
use scripts to automate many functions, including customizing pivot tables.
Note: Legacy Sax Basic users must manually convert any custom autoscripts. The autoscripts installed
with pre-16.0 versions are available as a set of separate script files located in the Samples subdirectory of
the directory where IBM SPSS Statistics is installed. By default, no output items are associated with
autoscripts. You must manually associate all autoscripts with the output items, as described below. For
information on converting legacy autoscripts, see “Compatibility with Versions Prior to 16.0” on page 259.
Default script language
The default script language determines the script editor that is launched when new scripts are
created. It also specifies the default language whose executable will be used to run autoscripts. The
available scripting languages depend on your platform. For Windows, the available scripting
languages are Basic, which is installed with the Core system, and the Python programming language.
For all other platforms, scripting is available with the Python programming language. You can choose
Python 3 as the default script language for the Python programming.
Privacy options
The Privacy tab provides options for:
Allow SPSS Statistics to share your information with IBM
When enabled, SPSS Statistics shares your usage and performance data with IBM.
The setting helps improve SPSS Statistics. All collected data is transmitted securely.
Disable SPSS Statistics from retrieving Welcome dialog content updates
When enabled, SPSS Statistics will not automatically retrieve Welcome dialog content updates. The
updates may include features enhancement information, and other product specific information.
Disable SPSS Statistics from sending error reports to IBM
When enabled, SPSS Statistics does not automatically send error reports to IBM.
Menu Editor
You can use the Menu Editor to customize your menus. With the Menu Editor you can:
• Add menu items that run customized scripts.
• Add menu items that run command syntax files.
• Add menu items that launch other applications and automatically send data to other applications.
You can send data to other applications in the following formats: IBM SPSS Statistics, Excel, Lotus 1-2-3,
tab-delimited, and dBASE IV.
To Add Items to Menus
1. From the menus choose:
View > Menu Editor...
2. In the Menu Editor dialog box, double-click the menu (or click the plus sign icon) to which you want to
add a new item.
3. Select the menu item above which you want the new item to appear.
4. Click Insert Item to insert a new menu item.
5. Enter the text for the new item. On Windows operating systems, an ampersand (&) before a letter
specifies that letter should be used as the underlined mnemonic key.
6. Select the file type for the new item (script file, command syntax file, or external application).
7. Click Browse to select a file to attach to the menu item.
You can also add entirely new menus and separators between menu items. Optionally, you can
automatically send the contents of the Data Editor to another application when you select that application
on the menu.
Customizing Toolbars
You can customize toolbars and create new toolbars. Toolbars can contain any of the available tools,
including tools for all menu actions. They can also contain custom tools that launch other applications,
run command syntax files, or run script files.
Show Toolbars
Use Show Toolbars to show or hide toolbars, customize toolbars, and create new toolbars. Toolbars can
contain any of the available tools, including tools for all menu actions. They can also contain custom tools
that launch other applications, run command syntax files, or run script files.
To Customize Toolbars
1. From the menus choose:
View > Toolbars > Customize
2. Select the toolbar you want to customize and click Edit, or click New to create a new toolbar.
3. For new toolbars, enter a name for the toolbar, select the windows in which you want the toolbar to
appear, and click Edit.
4. Select an item in the Categories list to display available tools in that category.
5. Drag and drop the tools you want onto the toolbar displayed in the dialog box.
6. To remove a tool from the toolbar, drag it anywhere off the toolbar displayed in the dialog box.
To create a custom tool to open a file, to run a command syntax file, or to run a script:
7. Click New Tool in the Edit Toolbar dialog box.
8. Enter a descriptive label for the tool.
9. Select the action you want for the tool (open a file, run a command syntax file, or run a script).
10. Click Browse to select a file or application to associate with the tool.
New tools are displayed in the User-Defined category, which also contains user-defined menu items.
Toolbar Properties
Use Toolbar Properties to select the window types in which you want the selected toolbar to appear. This
dialog box is also used for creating names for new toolbars.
To Set Toolbar Properties
1. From the menus choose:
View > Toolbars > Customize
2. For existing toolbars, click Edit, and then click Properties in the Edit Toolbar dialog box.
3. For new toolbars, click New Tool.
4. Select the window types in which you want the toolbar to appear. For new toolbars, also enter a
toolbar name.
Edit Toolbar
Use the Edit Toolbar dialog box to customize existing toolbars and create new toolbars. Toolbars can
contain any of the available tools, including tools for all menu actions. They can also contain custom tools
that launch other applications, run command syntax files, or run script files.
To Change Toolbar Images
1. Select the tool for which you want to change the image on the toolbar display.
2. Click Change Image.
3. Select the image file that you want to use for the tool. The following image formats are supported:
BMP, PNG, GIF, JPG.
• Images should be square. Images that are not square are clipped to a square area.
• Images are automatically scaled to fit. For optimal display, use 16x16 pixel images for small toolbar
images or 32x32 pixel images for large toolbar images.
Extensions are custom components that extend the capabilities of IBM SPSS Statistics. Extensions are
packaged in extension bundles (.spe files) and are installed to IBM SPSS Statistics. Extensions can be
created by any user and shared with other users by sharing the associated extension bundle.
The following utilities are provided for working with extensions:
• The “Extension Hub” on page 195, which is accessed from Extensions > Extension Hub, is an interface
for searching for, downloading, and installing extensions from the IBM SPSS Predictive Analytics
collection on GitHub. From the Extension Hub dialog, you can also view details of the extensions that
are installed on your computer, get updates for installed extensions, and remove extensions.
• You can install an extension bundle that is stored on your local computer from Extensions > Install
Local Extension Bundle.
• You can use the Custom Dialog Builder for Extensions to create an extension that includes a user
interface, which is referred to as a custom dialog. Custom dialogs generate SPSS Statistics command
syntax that carries out the tasks that are associated with the extension. You design the generated
syntax as part of designing the custom dialog.
• You can use the Create Extension Bundle and Edit Extension Bundle dialogs for cases where you can't
use the Custom Dialog Builder for Extensions. For more information, see the topic “Creating and editing
extension bundles” on page 233.
Extension Hub
From the Extension Hub dialog, you can do the following tasks:
• Explore extensions that are available from the IBM SPSS Predictive Analytics collection on GitHub. You
can select extensions to install now or you can download selected extensions and install them later.
• Get updated versions of extensions that are already installed on your computer.
• View details about the extensions that are already installed on your computer.
• Remove extensions that are installed on your computer.
To download or remove extensions:
1. From the menus, choose: Extensions > Extension Hub
2. Select the extensions that you want to download or remove and click OK. All selections that are made
on the Explore and Installed tabs are processed when you click OK.
By default, the extensions that are selected for download are downloaded and installed on your
computer. From the Settings tab, you can choose to download the selected extensions to a specified
location without installing them. You can then install them later by choosing Extensions > Install Local
Extension Bundle. For Windows and Mac, you can install an extension by double-clicking the extension
bundle file.
Important:
• Extensions are always installed, or downloaded, to your local computer. If you work in distributed
analysis mode, then see the topic “Installing local extension bundles” on page 197 for further details.
• For Windows 7 and later, installing an updated version of an existing extension bundle might require
running IBM SPSS Statistics with administrator privileges. You can start IBM SPSS Statistics with
administrator privileges by right-clicking the icon for IBM SPSS Statistics and choosing Run as
administrator. In particular, if you receive an error message that states that one or more extension
bundles could not be installed, then try running with administrator privileges.
Note: The license that you agree to when you install an extension can be viewed at any later time by
clicking More info... for the extension on the Installed tab.
Explore tab
The Explore tab displays all of the extensions that are available from the IBM SPSS Predictive Analytics
collection on GitHub (https://ibmpredictiveanalytics.github.io/). From the Explore tab, you can select new
extensions to download and install, and you can select updates for extensions that are already installed
on your computer. The Explore tab requires an internet connection.
• For each extension, the number of the latest version and the associated date of that version are
displayed. A brief summary of the extension is also provided. For extensions that are already installed
on your computer, the installed version number is also displayed.
• You can view detailed information about an extension by clicking More info. When an update is
available, More info displays information about the update.
• You can view the prerequisites for running an extension, such as whether the IBM SPSS Statistics -
Integration Plug-in for R is required, by clicking Prerequisites. When an update is available,
Prerequisites displays information about the update.
Refine by
You can refine the set of extensions that are displayed. You can refine by general categories of
extensions, the language in which the extension is implemented, the type of organization that provided
the extension, or the state of the extension. For each group, such as Category, you can select multiple
items by which to refine the displayed list of extensions. You can also refine by search terms. Searches
are not case-sensitive, and the asterisk (*) is treated as any other character and does not indicate a
wildcard search.
• To refine the displayed list of extensions, click Apply. Pressing the enter key when the cursor is in the
Search box has the same effect as clicking Apply.
• To reset the list to display all available extensions, delete any text in the Search box, deselect all items,
and click Apply.
Installed tab
The Installed tab displays all of the extensions that are installed on your computer. From the Installed
tab, you can select updates for installed extensions that are available from the IBM SPSS Predictive
Analytics collection on GitHub and you can remove extensions. To get updates for installed extensions,
you must have an internet connection.
• For each extension, the installed version number is displayed. When an internet connection is available,
the number of the latest version and the associated date of that version are displayed. A brief summary
of the extension is also provided.
• You can view detailed information about an extension by clicking More info. When an update is
available, More info displays information about the update.
• You can view the prerequisites for running an extension, such as whether the IBM SPSS Statistics -
Integration Plug-in for R is required, by clicking Prerequisites. When an update is available,
Prerequisites displays information about the update.
Refine by
You can refine the set of extensions that are displayed. You can refine by general categories of
extensions, the language in which the extension is implemented, the type of organization that provided
the extension, or the state of the extension. For each group, such as Category, you can select multiple
items by which to refine the displayed list of extensions. You can also refine by search terms. Searches
are not case-sensitive, and the asterisk (*) is treated as any other character and does not indicate a
wildcard search.
• To refine the displayed list of extensions, click Apply. Pressing the enter key when the cursor is in the
Search box has the same effect as clicking Apply.
• To reset the list to display all available extensions, delete any text in the Search box, deselect all items,
and click Apply.
Settings
The Settings tab specifies whether extensions that are selected for download are downloaded and then
installed or downloaded but not installed. This setting applies to new extensions and updates to existing
extensions. You might choose to download extensions without installing them if you are downloading
extensions to distribute to other users within your organization. You might also choose to download, but
not install, extensions if you don't have the prerequisites for running the extensions but plan to get the
prerequisites.
If you choose to download extensions without installing them, you can install them later by choosing
Extensions > Install Local Extension Bundle. For Windows and Mac, you can install an extension by
double-clicking the extension bundle file.
Extension Details
The Extension Details dialog box displays the information that was provided by the author of the
extension. In addition to required information, such as Summary, and Version, the author might have
included URLs to locations of relevance, such as the author's home page. If the extension was
downloaded from the Extension Hub, then it includes a license that can be viewed by clicking View
license.
Components. The Components group lists the custom dialogs, if any, and the names of any extension
commands that are included in the extension. Extension commands can be run from the syntax editor in
the same manner as built-in IBM SPSS Statistics commands. Help for an extension command might be
available by positioning the cursor within the command (in a syntax window) and pressing the F1 key.
Help might also be available by running CommandName /HELP in the syntax editor.
Note: Installing an extension that contains a custom dialog might require a restart of IBM SPSS Statistics
to see the entry for the dialog in the Components table.
Dependencies. The Dependencies group lists add-ons that are required to run the components included
in the extension.
• Integration Plug-Ins for Python and R. The components for an extension may require the Integration
Plug-in for Python, or the Integration Plug-in for R, or both. The Integration Plug-in for Java™ is installed
with the Core system and does not require separate installation.
• R packages. Lists any R packages that are required by the extension. During installation of the
extension, the installer attempts to download and install the necessary packages on your machine. If
this process fails, you will be alerted and you will then need to manually install the packages. See the
topic “Required R packages” on page 199 for more information.
• Python modules. Lists any Python modules that are required by the extension. Any such modules may
be available from the IBM SPSS Predictive Analytics community at https://www.ibm.com/community/
spss-statistics . Copy the modules to a location specified for extension commands as shown in the
output from the SHOW EXTPATHS command. Alternatively, you can copy the modules to a location on
the Python search path, such as the Python site-packages directory.
• Extensions. Lists the names of any extensions that are required by the current extension. Any such
extensions might be available for download from the Extension Hub.
Windows 7
1. Select User Accounts.
2. Select Change my environment variables.
3. Click New, enter the name of the environment variable (for instance, SPSS_EXTENSIONS_PATH) in the
Variable name field and enter the path or paths in the Variable value field.
Windows 10
1. Enter envrionment variable in the Windows search field and click the Edit the system
environment variables result that is provided. The System Properties dialog opens to the Advanced
tab, which provides the Environment Variables... control.
2. Click Environment Variables... to open the Environment Variables dialog.
3. In the User variables for <username> section, click New, enter the name of the environment variable
(for instance, SPSS_EXTENSIONS_PATH) in the Variable name field and enter the path or paths in the
Variable value field.
Important: For users of Windows 7 and later versions of Windows, installing an updated version of an
existing extension bundle might require running IBM SPSS Statistics with administrator privileges. You
can start IBM SPSS Statistics with administrator privileges by right-clicking the icon for IBM SPSS
Statistics and choosing Run as administrator. In particular, if you receive an error message that states
that one or more extension bundles could not be installed, then try running with administrator privileges.
Required R packages
The extension installer attempts to download and install any R packages that are required by the
extension and not found on your computer. If you do not have internet access, you will need to obtain the
necessary packages from someone who does. If installation of the packages fails, you will be alerted with
the list of required packages. You can also view the list from the Extension Details dialog box, once the
extension is installed. See the topic “Extension Details” on page 197 for more information. Packages can
be downloaded from http://www.r-project.org/ and then installed from within R. For details, see the R
Installation and Administration guide, distributed with R.
Note: For UNIX (including Linux) users, packages are downloaded in source form and then compiled. This
requires that you have the appropriate tools installed on your machine. See the R Installation and
Administration guide for details. In particular, Debian users should install the r-base-dev package from
apt-get install r-base-dev.
Permissions
By default, required R packages are installed to the library folder under the location where R is
installed (for example, C:\Program Files\R\R-3.6.x\library on Windows). If you do not have write
permission to this location or would like to store R packages--installed for extensions--elsewhere, you
can specify one or more alternate locations by defining the SPSS_RPACKAGES_PATH environment
variable. When present, the paths specified in SPSS_RPACKAGES_PATH are added to the R library search
path and take precedence over the default location. R packages will be installed to the first writable
location. For multiple locations, separate each with a semicolon on Windows and a colon on Linux and
Mac. The specified locations must exist on the target machine. After setting SPSS_RPACKAGES_PATH,
you will need to restart IBM SPSS Statistics for the changes to take effect. For information on how to set
an environment variable on Windows, see “Installation locations for extensions” on page 198.
-statssrv. Specifies that you are running the utility on a IBM SPSS Statistics Server. You should also install
the same extension bundles on client machines that connect to the server.
-download no|yes. Specifies whether the utility has permission to access the internet in order to
download any R packages required by the specified extension bundles. The default is no. If you keep the
default or do not have internet access then you will need to manually install any required R packages. See
the topic “Required R packages” on page 199 for more information.
–source <folder> | <filename>... Specifies the extension bundles to install. You can specify the path to a
folder containing extension bundles or you can specify a list of filenames of extension bundles. If you
specify a folder, all extension bundles (files of type .spe) found in the folder will be installed. Separate
multiple filenames with one or more spaces. Enclose paths with double-quotes if they contain spaces.
Note: When running installextbundles.sh on IBM SPSS Statistics Server for UNIX, the Bash shell
must be present on the server machine.
Canvas
The canvas is the area of the Custom Dialog Builder where you design the layout of your dialog.
Properties Pane
The properties pane is the area of the Custom Dialog Builder where you specify properties of the controls
that make up the dialog as well as properties of the dialog itself, such as the menu location.
Tools Palette
The tools palette provides the set of controls that can be included in a custom dialog. You can show or
hide the Tools Palette by choosing Tools Palette from the View menu.
Syntax Template
The Syntax Template specifies the command syntax that is generated by the custom dialog. You can
move the Syntax Template pane to a separate window by clicking Move to New Window. To move a
separate Syntax Template window back into the Custom Dialog Builder, click Restore to Main Window.
Compatibility Mode
1. Double-click the menu (or click the plus sign icon) to which you want to add the item for the new
dialog.
If you want to create custom menus or submenus, use the Menu Editor. For more information, see the
topic “Menu Editor” on page 193, and also see the associated note in the Note section.
2. Select the menu item above which you want the item for the new dialog to appear. After the item is
added, you can use the Move Up and Move Down buttons to reposition it.
3. Enter a title for the menu item. Titles within a particular menu or submenu must be unique.
4. Click Add.
Options
• Add a separator above or below the new menu item.
• Specify the path to an image that appears next to the menu item for the custom dialog. The supported
image types are gif and png. The image cannot be larger than 16 x 16 pixels.
Note:
• The Menu Location dialog box displays menus for all add-on modules. Be sure to add the menu item for
your custom dialog to a menu that is available to you or other users of your dialog.
• If you add your dialog to a menu that was created from the Menu Editor (View>Menu Editor), then
users of your dialog must manually create the same menu from their Menu Editor. Otherwise, the dialog
is added to their Extensions menu.
FREQUENCIES VARIABLES=%%target_list%%
/FORMAT = NOTABLE
/BARCHART.
• %%target_list%% is the value of the Identifier property for the target list control. At run time it will be
replaced by the current value of the Syntax property of the control.
• Defining the Syntax property of the target list control to be %%ThisValue%% specifies that at run time,
the current value of the property will be the value of the control, which is the set of variables in the
target list.
FREQUENCIES VARIABLES=%%target_list%%
/FORMAT = NOTABLE
%%stats_group%%
/BARCHART.
• %%target_list%% is the value of the Identifier property for the target list control and %
%stats_group%% is the value of the Identifier property for the item group control.
The following definitions illustrate one way to specify the Syntax properties of the item group and the
check boxes that are contained within it to generate the correct result. The Syntax property of the target
list would be set to %%ThisValue%%, as described in the previous example.
Syntax property of item group: /STATISTICS %%ThisValue%%
Checked Syntax property of mean check box: MEAN
Checked Syntax property of stddev check box: STDDEV
Checked Syntax property of min check box: MINIMUM
Checked Syntax property of max check box: MAXIMUM
At run time, %%stats_group%% will be replaced by the current value of the Syntax property for the item
group control. Specifically, %%ThisValue%% will be replaced by a blank-separated list of the values of the
Checked or Unchecked Syntax property of each check box, depending on its state--checked or
unchecked. Since we only specified values for the Checked Syntax property, only checked boxes will
contribute to %%ThisValue%%. For example, if the user checks the mean and standard deviation boxes,
the run time value of the Syntax property for the item group will be /STATISTICS MEAN STDDEV.
If no boxes are checked, then the Syntax property for the item group control will be empty, and the
generated command syntax will not contain any reference to %%stats_group%%. This might or might not
be desirable. For example, even with no boxes checked you might still want to generate the STATISTICS
subcommand. This can be accomplished by referencing the identifiers for the check boxes directly in the
syntax template, as in:
FREQUENCIES VARIABLES=%%target_list%%
/FORMAT = NOTABLE
/STATISTICS %%stats_mean%% %%stats_stddev%% %%stats_min%% %%stats_max%%
/BARCHART.
Control types
The tools palette provides the controls that can be added to a custom dialog.
• Source List: A list of source variables from the active dataset. See the topic “Source List” on page 206
for more information.
• Target List: A target for variables transferred from the source list. See the topic “Target List” on page
207 for more information.
• Field Chooser: A list of all the fields from the active dataset. See the topic “Field Chooser” on page 208
for more information.
• Dataset Selector: A list of the datasets that are currently open. See the topic “Dataset Selector” on
page 209 for more information.
• Check Box: A single check box. See the topic “Check Box” on page 210 for more information.
• Combo Box: A combo box for creating drop-down lists. See the topic “Combo Box” on page 210 for
more information.
• List Box: A list box for creating single selection or multiple selection lists. See the topic “List Box” on
page 212 for more information.
• Text control: A text box that accepts arbitrary text as input. See the topic “Text control” on page 213
for more information.
• Number control: A text box that is restricted to numeric values as input. See the topic “Number
Control” on page 214 for more information.
• Date control: A spinner control for specifying date/time values, which include dates, times, and
datetimes. See the topic “Date control” on page 215 for more information.
• Secured Text: A text box that masks user entry with asterisks. See the topic “Secured Text” on page
216 for more information.
• Static Text control: A control for displaying static text. See the topic “Static Text Control” on page 217
for more information.
• Color Picker: A control for specifying a color and generating the associated RGB value. See the topic
“Color Picker” on page 217 for more information.
• Table control: A table with a fixed number of columns and a variable number of rows that are added at
run time. See the topic “Table Control” on page 218 for more information.
• Item Group: A container for grouping a set of controls, such as a set of check boxes. See the topic
“Item Group” on page 220 for more information.
• Radio Group: A group of radio buttons. See the topic “Radio Group” on page 220 for more information.
• Check Box Group: A container for a set of controls that are enabled or disabled as a group, by a single
check box. See the topic “Check Box Group” on page 221 for more information.
• File Browser: A control for browsing the file system to open or save a file. See the topic “File Browser”
on page 222 for more information.
• Tab: A single tab. See the topic “Tab” on page 223 for more information.
• Sub-dialog Button: A button for launching a sub-dialog. See the topic “Sub-dialog button” on page 223
for more information.
Source List
The Source Variable List control displays the list of variables from the active dataset that are available to
the end user of the dialog. You can display all variables from the active dataset (the default) or you can
filter the list based on type and measurement level--for instance, numeric variables that have a
measurement level of scale. Use of a Source List control implies the use of one or more Target List
controls. The Source List control has the following properties:
Target List
The Target List control provides a target for variables that are transferred from the source list. Use of the
Target List control assumes the presence of a Source List control. You can specify that only a single
variable can be transferred to the control or that multiple variables can be transferred to it, and you can
constrain which types of variables can be transferred to the control--for instance, only numeric variables
with a measurement level of nominal or ordinal. The Target List control has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
ToolTip. Optional ToolTip text that appears when the user hovers over the control. The specified text only
appears when hovering over the title area of the control. Hovering over one of the listed variables will
display the variable name and label.
Target list type. Specifies whether multiple variables or only a single variable can be transferred to the
control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key]. The
Mnemonic Key property is not supported on Mac.
Separator Type. Specifies the delimiter between the selected fields in the generated syntax. The allowed
separators are a blank, a comma, and a plus sign (+). You can also enter an arbitrary single character to
be used as the separator.
Minimum Fields. The minimum number of fields that must be specified for the control, if any.
Maximum Fields. The maximum number of fields that can be specified for the control, if any.
Required for execution. Specifies whether a value is required in this control in order for execution to
proceed. If True is specified, the OK and Paste buttons will be disabled until a value is specified for this
control. If False is specified, the absence of a value in this control has no effect on the state of the OK and
Paste buttons. The default is True.
Variable Filter. Allows you to constrain the types of variables that can be transferred to the control. You
can constrain by variable type and measurement level, and you can specify whether multiple response
sets can be transferred to the control. Click the ellipsis (...) button to open the Filter dialog. You can also
Field Chooser
The Field Chooser control displays the list of fields that are available to the end user of the dialog. You can
filter the list based on type and measurement level--for instance, numeric fields that have a measurement
level of scale. You can also specify any other Field Chooser or Target List control as the source of fields for
the current Field Chooser. The Field Chooser control has the following properties:
Identifier. The unique identifier for the control.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
Title Position. Specifies the position of the title relative to the control. Values are Top and Left where Top
is the default. This property only applies when the chooser type is set to select a single field.
ToolTip. Optional ToolTip text that appears when the user hovers over the control. The specified text only
appears when hovering over the title area of the control. Hovering over one of the listed fields displays the
field name and label.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key].
Chooser Type. Specifies whether the Field Chooser in the custom dialog can be used to select a single
field or multiple fields from the field list.
Separator Type. Specifies the delimiter between the selected fields in the generated syntax. The allowed
separators are a blank, a comma, and a plus sign (+). You can also enter an arbitrary single character to
be used as the separator.
Minimum Fields. The minimum number of fields that must be specified for the control, if any.
Maximum Fields. The maximum number of fields that can be specified for the control, if any.
Required for Execution. Specifies whether a value is required in this control in order for execution to
proceed. If True is specified, the OK and Paste buttons will be disabled until a value is specified for this
control. If False is specified, the absence of a value in this control has no effect on the state of the OK and
Paste buttons.
Variable Filter. Allows you to filter the set of fields that are displayed in the control. You can filter on field
type and measurement level, and you can specify that multiple response sets are included in the field list.
Click the ellipsis (...) button to open the Filter dialog. You can also open the Filter dialog by double-
clicking the Field Chooser control on the canvas. See the topic “Filtering Variable Lists” on page 209 for
more information.
Field Source. Specifies that another Field Chooser or Target List control is the source of fields for the
current Field Chooser. When the Field Source property is not set, the source of fields is the current data
source as determined by the Data Source property of the dialog. Click the ellipsis (...) button to open the
dialog box and specify the field source.
Dataset Selector
The Dataset Selector control displays a list of the datasets that are currently open. You can use the
Dataset Selector control to capture the name of a selected dataset. You can also use it with the Data
Source property of the dialog to set the data source that is used by Source List and Field Chooser
controls.
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key]. The
Mnemonic Key property is not supported on Mac.
Required for execution. Specifies whether a value is required in this control in order for execution to
proceed. If True is specified, the OK and Paste buttons will be disabled until a value is specified for this
control. If False is specified, the absence of a value in this control has no effect on the state of the OK and
Paste buttons. The default is False.
Syntax. Specifies the command syntax that is generated by this control at run time and can be inserted in
the syntax template.
• You can specify any valid command syntax. For multi-line syntax or long syntax, click the ellipsis (...)
button and enter your syntax in the Syntax Property dialog.
• The value %%ThisValue%% specifies the run time value of the control, which is the name of the
selected dataset. This is the default.
Enabling Rule. Specifies a rule that determines when the current control is enabled. Click the ellipsis (...)
button to open the dialog box and specify the rule. The Enabling Rule property is visible only when other
controls that can be used to specify an enabling rule exist on the canvas.
Check Box
The Check Box control is a simple check box that can generate different command syntax for the checked
versus the unchecked state. The Check Box control has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key]. The
Mnemonic Key property is not supported on Mac.
Default Value. The default state of the check box--checked or unchecked.
Checked/Unchecked Syntax. Specifies the command syntax that is generated when the control is
checked and when it is unchecked. To include the command syntax in the syntax template, use the value
of the Identifier property. The generated syntax, whether from the Checked Syntax or Unchecked Syntax
property, will be inserted at the specified position(s) of the identifier. For example, if the identifier is
checkbox1, then at run time, instances of %%checkbox1%% in the syntax template will be replaced by the
value of the Checked Syntax property when the box is checked and the Unchecked Syntax property when
the box is unchecked.
• You can specify any valid command syntax. For multi-line syntax or long syntax, click the ellipsis (...)
button and enter your syntax in the Syntax Property dialog.
Enabling Rule. Specifies a rule that determines when the current control is enabled. Click the ellipsis (...)
button to open the dialog box and specify the rule. The Enabling Rule property is visible only when other
controls that can be used to specify an enabling rule exist on the canvas.
Combo Box
The Combo Box control allows you to create a drop-down list that can generate command syntax specific
to the selected list item. It is limited to single selection. The Combo Box control has the following
properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
Title Position. Specifies the position of the title relative to the control. Values are Top and Left where Top
is the default.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
List Items. Click the ellipsis (...) button to open the List Item Properties dialog box, which allows you to
specify the list items of the control. You can also open the List Item Properties dialog by double-clicking
the Combo Box control on the canvas.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key].The
Mnemonic Key property is not supported on Mac.
Editable. Specifies whether the Combo Box control is editable. When the control is editable, a custom
value can be entered at run time.
Syntax. Specifies the command syntax that is generated by this control at run time and can be inserted in
the syntax template.
Syntax
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are doubled. For example, if the Syntax property is '%%ThisValue%%' and the run time
value of the combo box is Combo box's value, then the generated syntax is 'Combo box''s
value'.
Python
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are escaped with the backslash character (\). For example, if the Syntax property is '%
%ThisValue%%' and the run time value of the combo box is Combo box's value, then the
generated syntax is 'Combo box\'s value'. Note that quote handling is not done when %
%ThisValue%% is enclosed in triple quotation marks.
R
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are escaped with the backslash character (\). For example, if the Syntax property is '%
%ThisValue%%' and the run time value of the combo box is Combo box's value, then the
generated syntax is 'Combo box\'s value'.
None
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are retained with no modification.
Enabling Rule. Specifies a rule that determines when the current control is enabled. Click the ellipsis (...)
button to open the dialog box and specify the rule. The Enabling Rule property is visible only when other
controls that can be used to specify an enabling rule exist on the canvas.
List Box
The List Box control allows you to display a list of items that support single or multiple selection and
generate command syntax specific to the selected item(s). The List Box control has the following
properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
List Items. Click the ellipsis (...) button to open the List Item Properties dialog box, which allows you to
specify the list items of the control. You can also open the List Item Properties dialog by double-clicking
the List Box control on the canvas.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key].The
Mnemonic Key property is not supported on Mac.
List Box Type. Specifies whether the list box supports single selection only or multiple selection. You can
also specify that items are displayed as a list of check boxes.
Separator Type. Specifies the delimiter between the selected list items in the generated syntax. The
allowed separators are a blank, a comma, and a plus sign (+). You can also enter an arbitrary single
character to be used as the separator.
Minimum Selected. The minimum number of items that must be selected in the control, if any.
Maximum Selected. The maximum number of items that can be selected in the control, if any.
Syntax. Specifies the command syntax that is generated by this control at run time and can be inserted in
the syntax template.
• The value %%ThisValue%% specifies the run time value of the control and is the default. If the list items
are manually defined, the run time value is the value of the Syntax property for the selected list item. If
the list items are based on a target list control, the run time value is the value of the selected list item.
For multiple selection list box controls, the run time value is a list of the selected items, delimited by the
specified Separator Type (default is blank separated). See the topic “Specifying list items for combo
boxes and list boxes” on page 211 for more information.
• You can specify any valid command syntax. For multi-line syntax or long syntax, click the ellipsis (...)
button and enter your syntax in the Syntax Property dialog.
Syntax
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are doubled. For example, if the Syntax property is '%%ThisValue%%' and the selected list
item is List item's value, then the generated syntax is 'List item''s value'.
Python
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are escaped with the backslash character (\). For example, if the Syntax property is '%
%ThisValue%%' and the selected list item is List item's value, then the generated syntax is
'List item\'s value'. Note that quote handling is not done when %%ThisValue%% is
enclosed in triple quotation marks.
R
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are escaped with the backslash character (\). For example, if the Syntax property is '%
%ThisValue%%' and the selected list item is List item's value, then the generated syntax is
'List item\'s value'.
None
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are retained with no modification.
Enabling Rule. Specifies a rule that determines when the current control is enabled. Click the ellipsis (...)
button to open the dialog box and specify the rule. The Enabling Rule property is visible only when other
controls that can be used to specify an enabling rule exist on the canvas.
Text control
The Text control is a simple text box that can accept arbitrary input, and has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
Title Position. Specifies the position of the title relative to the control. Values are Top and Left where Top
is the default.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key]. The
Mnemonic Key property is not supported on Mac.
Text Content. Specifies the allowed contents. The value Any specifies that the contents are arbitrary. The
value Variable Name specifies that the text box must contain a string that adheres to rules for IBM SPSS
Statistics variable names. See the topic “Variable names” on page 46 for more information. The value
New dataset name specifies that the text box must contain a valid IBM SPSS Statistics dataset name and
cannot be the name of a currently open dataset.
Default Value. The default contents of the text box.
Width. Specifies the width of the text area of the control in characters. The allowed values are positive
integers. An empty value means that the width is automatically determined.
Required for execution. Specifies whether a value is required in this control in order for execution to
proceed. If True is specified, the OK and Paste buttons will be disabled until a value is specified for this
Syntax
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are doubled. For example, if the Syntax property is'%%ThisValue%%' and the run time
value of the text control is Text box's value, then the generated syntax is 'Text box''s
value'.
Python
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are escaped with the backslash character (\). For example, if the Syntax property is '%
%ThisValue%%' and the run time value of the text control is Text box's value, then the
generated syntax is 'Text box\'s value'. Quote handling is not done when %%ThisValue%%
is enclosed in triple quotation marks.
R
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are escaped with the backslash character (\). For example, if the Syntax property is '%
%ThisValue%%' and the run time value of the text control is Text box's value, then the
generated syntax is 'Text box\'s value'.
None
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are retained with no modification.
Enabling Rule. Specifies a rule that determines when the current control is enabled. Click the ellipsis (...)
button to open the dialog box and specify the rule. The Enabling Rule property is visible only when other
controls that can be used to specify an enabling rule exist on the canvas.
Number Control
The Number control is a text box for entering a numeric value, and has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
Title Position. Specifies the position of the title relative to the control. Values are Top and Left where Top
is the default.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key]. The
Mnemonic Key property is not supported on Mac.
Date control
The Date control is a spinner control for specifying date/time values, which include dates, times, and
datetimes. The Date control has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
Title Position. Specifies the position of the title relative to the control. Values are Top and Left where Top
is the default.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key]. The
Mnemonic Key property is not supported on Mac.
Type. Specifies whether the control is for dates, times, or datetime values.
Date
The control specifies a calendar date of the form yyyy-mm-dd. The default run time value is
specified by the Default Value property.
Time
The control specifies the time of day in the form hh:mm:ss. The default run time value is the
current time of day.
Secured Text
The Secured Text control is a text box that masks user entry with asterisks.
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
Title Position. Specifies the position of the title relative to the control. Values are Top and Left where Top
is the default.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key]. The
Mnemonic Key property is not supported on Mac.
Encrypt passed value. Specifies whether the value in the generated command syntax is encrypted. True
specifies that the value is encrypted. The default is False, which specifies that the value is not encrypted.
Encrypted values can be decrypted only by IBM SPSS Statistics commands that can process encrypted
passwords, such as the GET and SAVE commands.
Width. Specifies the width of the text area of the control in characters. The allowed values are positive
integers. An empty value means that the width is automatically determined.
Required for execution. Specifies whether a value is required in this control in order for execution to
proceed. If True is specified, the OK and Paste buttons will be disabled until a value is specified for this
control. If False is specified, the absence of a value in this control has no effect on the state of the OK and
Paste buttons. The default is False.
Syntax. Specifies the command syntax that is generated by this control at run time and can be inserted in
the syntax template.
• You can specify any valid command syntax. For multi-line syntax or long syntax, click the ellipsis (...)
button and enter your syntax in the Syntax Property dialog.
• The value %%ThisValue%% specifies the run time value of the control, which is the content of the text
box. This is the default.
• If the Syntax property includes %%ThisValue%% and the run time value of the secured text control is
empty, then the secured text control does not generate any command syntax.
Quote Handling. Specifies handling of quotation marks in the run time value of %%ThisValue%% when
the Syntax property contains %%ThisValue%% as part of a quoted string. In this context, a quoted string
is a string that is enclosed in single quotation marks or double quotation marks. Quote handling applies
Syntax
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are doubled. For example, if the Syntax property is '%%ThisValue%%' and the run time
value of the control is Secured Text's value, then the generated syntax is 'Secured
Text''s value'.
Python
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are escaped with the backslash character (\). For example, if the Syntax property is '%
%ThisValue%%' and the run time value of the control is Secured Text's value, then the
generated syntax is 'Secured Text\'s value'. Quote handling is not done when %
%ThisValue%% is enclosed in triple quotation marks.
R
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are escaped with the backslash character (\). For example, if the Syntax property is '%
%ThisValue%%' and the run time value of the control is Secured Text's value, then the
generated syntax is 'Secured Text\'s value'.
None
Quotation marks in the run time value of %%ThisValue%% that match the enclosing quotation
marks are retained with no modification.
Enabling Rule. Specifies a rule that determines when the current control is enabled. Click the ellipsis (...)
button to open the dialog box and specify the rule. The Enabling Rule property is visible only when other
controls that can be used to specify an enabling rule exist on the canvas.
Note: The Secured Text control is not available in compatibility mode.
Color Picker
The Color Picker control is a user interface for specifying a color and generating the associated RGB value.
The Color Picker control has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
Title Position. Specifies the position of the title relative to the control. Values are Top and Left where Top
is the default.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key]. The
Mnemonic Key property is not supported on Mac.
Syntax. Specifies the command syntax that is generated by this control at run time and can be inserted in
the syntax template.
Table Control
The Table control creates a table with a fixed number of columns and a variable number of rows that are
added at run time. The Table control has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key].The
Mnemonic Key property is not supported on Mac.
Reorder Buttons. Specifies whether move up and move down buttons are added to the table. These
buttons are used at run time to reorder the rows of the table.
Table Columns. Click the ellipsis (...) button to open the Table Columns dialog box, where you specify the
columns of the table.
Minimum Rows. The minimum number of rows that must be in the table.
Maximum Rows. The maximum number of rows that can be in the table.
Required for Execution. Specifies whether a value is required in this control in order for execution to
proceed. If True is specified, the OK and Paste buttons will be disabled until a value is specified for this
control. If False is specified, the absence of a value in this control has no effect on the state of the OK and
Paste buttons.
Syntax. Specifies the command syntax that is generated by this control at run time and can be inserted in
the syntax template.
• The value %%ThisValue%% specifies the run time value of the control and is the default. The run time
value is a blank-separated list of the syntax that is generated by each column in the table, starting with
the leftmost column. If the Syntax property includes %%ThisValue%% and none of the columns
generate syntax, then the table as a whole does not generate any syntax.
• You can specify any valid command syntax. For multi-line syntax or long syntax, click the ellipsis (...)
button and enter your syntax in the Syntax Property dialog.
Enabling Rule. Specifies a rule that determines when the current control is enabled. Click the ellipsis (...)
button to open the dialog box and specify the rule. The Enabling Rule property is visible only when other
controls that can be used to specify an enabling rule exist on the canvas.
Note: The Table control is not available in compatibility mode.
Syntax
Double quotation marks in cell values are doubled. For example, if the cell value is This
"quoted" value then the generated syntax is "This ""quoted"" value".
Python
Double quotation marks in cell values are escaped with the backslash character (\). For example,
if the cell value is This "quoted" value then the generated syntax is "This \"quoted\"
value".
R
Double quotation marks in cell values are escaped with the backslash character (\). For example,
if the cell value is This "quoted" value then the generated syntax is "This \"quoted\"
value".
None
Double quotation marks in cell values are retained with no modification.
Width(chars). Specifies the width of the column in characters. The allowed values are positive integers.
Syntax. Specifies the command syntax that is generated by this column at run time. The generated
syntax for the table as a whole is a blank-separated list of the syntax that is generated by each column in
the table, starting with the leftmost column.
• You can specify any valid command syntax. For multi-line syntax or long syntax, click the ellipsis (...)
button and enter your syntax in the Syntax Property dialog.
• The value %%ThisValue%% specifies the run time value of the column, which is a list of the values in the
column, delimited by the specified separator.
• If the Syntax property for the column includes %%ThisValue%% and the run time value of the column is
empty, then the column does not generate any syntax.
Note: You can add a row for a new Table column in the blank line at the bottom of the existing list in the
Table Columns dialog. Entering any of the properties other than the identifier generates a unique
identifier, which you can keep or modify. You can delete a Table column by clicking the identifier cell for
the Table column and pressing delete.
Link to Control
You can link a Table control to a Field Chooser control. When a Table control is linked to a Field Chooser,
there is a row in the table for each field in the Field Chooser. Rows are added to the table by adding fields
to the Field Chooser. Rows are deleted from the table by removing fields from the Field Chooser. A linked
Table control can be used, for example, to specify properties of fields that are selected in a Field Chooser.
Item Group
The Item Group control is a container for other controls, allowing you to group and control the syntax
generated from multiple controls. For example, you have a set of check boxes that specify optional
settings for a subcommand, but only want to generate the syntax for the subcommand if at least one box
is checked. This is accomplished by using an Item Group control as a container for the check box controls.
The following types of controls can be contained in an Item Group: field chooser, dataset selector, check
box, combo box, list box, text control, number control, date control, secured text, static text, color picker,
table control, radio group, and file browser. The Item Group control has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title for the group. For multi-line titles or long titles, click the ellipsis (...) button and
enter your title in the Title Property dialog.
Syntax. Specifies the command syntax that is generated by this control at run time and can be inserted in
the syntax template.
• You can specify any valid command syntax. For multi-line syntax or long syntax, click the ellipsis (...)
button and enter your syntax in the Syntax Property dialog.
• You can include identifiers for any controls contained in the item group. At run time the identifiers are
replaced with the syntax generated by the controls.
• The value %%ThisValue%% generates a blank-separated list of the syntax generated by each control in
the item group, in the order in which they appear in the group (top to bottom). This is the default. If the
Syntax property includes %%ThisValue%% and no syntax is generated by any of the controls in the item
group, then the item group as a whole does not generate any command syntax.
Enabling Rule. Specifies a rule that determines when the current control is enabled. Click the ellipsis (...)
button to open the dialog box and specify the rule. The Enabling Rule property is visible only when other
controls that can be used to specify an enabling rule exist on the canvas.
Radio Group
The Radio Group control is a container for a set of radio buttons, each of which can contain a set of nested
controls. The Radio Group control has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title for the group. For multi-line titles or long titles, click the ellipsis (...) button and
enter your title in the Title Property dialog.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Radio Buttons. Click the ellipsis (...) button to open the Radio Group Properties dialog box, which allows
you to specify the properties of the radio buttons as well as to add or remove buttons from the group. The
ability to nest controls under a given radio button is a property of the radio button and is set in the Radio
Group Properties dialog box. Note that you can also open the Radio Group Properties dialog by double-
clicking the Radio Group control on the canvas.
Syntax. Specifies the command syntax that is generated by this control at run time and can be inserted in
the syntax template.
• You can specify any valid command syntax. For multi-line syntax or long syntax, click the ellipsis (...)
button and enter your syntax in the Syntax Property dialog.
File Browser
The File Browser control consists of a text box for a file path and a browse button that opens a standard
IBM SPSS Statistics dialog to open or save a file. The File Browser control has the following properties:
Identifier. The unique identifier for the control. This is the identifier to use when referencing the control
in the syntax template.
Title. An optional title that appears with the control. For multi-line titles or long titles, click the ellipsis (...)
button and enter your title in the Title Property dialog.
Title Position. Specifies the position of the title relative to the control. Values are Top and Left where Top
is the default.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Mnemonic Key. An optional character in the title to use as a keyboard shortcut to the control. The
character appears underlined in the title. The shortcut is activated by pressing Alt+[mnemonic key]. The
Mnemonic Key property is not supported on Mac.
File System Operation. Specifies whether the dialog launched by the browse button is appropriate for
opening files or for saving files. A value of Open indicates that the browse dialog validates the existence of
the specified file. A value of Save indicates that the browse dialog does not validate the existence of the
specified file.
Browser Type. Specifies whether the browse dialog is used to select a file (Locate File) or to select a
folder (Locate Folder).
File Filter. Click the ellipsis (...) button to open the File Filter dialog box, which allows you to specify the
available file types for the open or save dialog. By default, all file types are allowed. Note that you can also
open the File Filter dialog by double-clicking the File Browser control on the canvas.
File System Type. In distributed analysis mode, this specifies whether the open or save dialog browses
the file system on which IBM SPSS Statistics Server is running or the file system of your local computer.
Select Server to browse the file system of the server or Client to browse the file system of your local
computer. The property has no effect in local analysis mode.
Tab
The Tab control adds a tab to the dialog. Any of the other controls can be added to the new tab. The Tab
control has the following properties:
Identifier. The unique identifier for the control.
Title. The title of the tab.
Position. Specifies the position of the tab on the dialog, relative to the other tabs on the dialog.
Enabling Rule. Specifies a rule that determines when the current control is enabled. Click the ellipsis (...)
button to open the dialog box and specify the rule. The Enabling Rule property is visible only when other
controls that can be used to specify an enabling rule exist on the canvas.
Note: The Tab control is not available in compatibility mode.
Sub-dialog button
The Sub-dialog Button control specifies a button for launching a sub-dialog and provides access to the
Dialog Builder for the sub-dialog. The Sub-dialog Button has the following properties:
Identifier. The unique identifier for the control.
Title. The text that is displayed in the button.
ToolTip. Optional ToolTip text that appears when the user hovers over the control.
Sub-dialog. Click the ellipsis (...) button to open the Custom Dialog Builder for the sub-dialog. You can
also open the builder by double-clicking on the Sub-dialog button.
Extension Properties
The Extension Properties dialog specifies information about the current extension within the Custom
Dialog Builder for Extensions, such as the name of the extension and the files in the extension.
Note: The Extension Properties dialog does not apply in Compatibility mode.
• All custom dialogs that are created in the Custom Dialog Builder for Extensions are part of an extension.
• Fields on the Required tab of the Extension Properties dialog must be specified before you can install an
extension and the custom dialogs that are contained in it.
To specify the properties for an extension, from the menus in the Custom Dialog Builder for Extensions
choose:
Extension > Properties
General properties
Description
A more detailed description of the extension than that provided for the Summary field. For example,
you might list the major features available with the extension.
Date
An optional date for the current version of the extension. No formatting is provided.
Author
The author of the extension. You might want to include an email address.
Links
A set of URLs to associate with the extension; for example, the author's home page. The format of this
field is arbitrary so be sure to delimit multiple URLs with spaces, commas, or some other reasonable
delimiter.
Keywords
A set of keywords with which to associate the extension.
Platform
Information about any restrictions that apply to using the extension on particular operating system
platforms.
Dependencies
Maximum SPSS Statistics Version
The maximum version of IBM SPSS Statistics on which the extension can be run.
Integration Plug-in for Python required
Specifies whether the Integration Plug-in for Python is required.
• If the Python implementation code is specified to run in Python 3, then select Python 3 for the
Python Version.
• If the extension requires Python modules that are not explicitly included in the extension, then
enter the names in the Required Python Modules control. Any such modules should be contributed
to the IBM SPSS Predictive Analytics community ( https://www.ibm.com/community/spss-
statistics ). To add the first module, click anywhere in the Required Python Modules control to
highlight the entry field. Pressing Enter, with the cursor in a given row, will create a new row. You
delete a row by selecting it and pressing Delete.
The user of the extension is responsible for downloading any required Python modules and copying
them to a location that is specified for extension commands, as shown in the output from the SHOW
EXTPATHS command. Alternatively, the modules can be copied to a location on the Python search
path, such as the Python site-packages directory.
Integration Plug-in for R required
Specifies whether the Integration Plug-in for R is required.
If the extension requires any R packages from the CRAN package repository, then enter the names of
those packages in the Required R Packages control. Names are case sensitive. To add the first
package, click anywhere in the Required R Packages control to highlight the entry field. Pressing
Enter, with the cursor in a given row, will create a new row. You delete a row by selecting it and
pressing Delete. When the extension is installed, IBM SPSS Statistics will check if the required R
packages are installed and attempt to download and install any that are missing.
Required Extensions
Enter the names of any extensions that are required by the current extension. To add the first
extension, click anywhere in the Required Extensions control to highlight the entry field. Pressing
Enter, with the cursor in a particular row, creates a new row. You delete a row by selecting it and
pressing Delete. The user of the extensions is responsible for installing any required extensions.
Localization
Custom Dialogs
You can add translated versions of the properties file (specifies all strings that appear in the dialog)
for a custom dialog within the extension. To add translations for a particular dialog, select the dialog,
click Add Translations, and select the folder that contains the translated versions. All translated files
for a particular dialog must be in the same folder. For instructions on creating the translation files, see
the topic “Creating Localized Versions of Custom Dialogs” on page 231.
Translation Catalogues Folder
You can include a folder containing translation catalogues. This allows you to provide localized
messages and localized output from Python or R programs that implement an extension command
included in the extension. You can also provide localized versions of the Summary and Description
fields for the extension that are displayed when end users view the extension details from the
Extension Hub. The set of all localized files for an extension must be in a folder named lang. Browse
to the lang folder that contains the localized files and select that folder.
For information on localizing output from Python and R programs, see the topics on the Integration
Plug-in for Python and the Integration Plug-in for R, in the Help system.
To provide localized versions of the Summary and Description fields, create a file named
<extension name>_<language-identifier>.properties for each language for which a
translation is being provided. At run time, if the .properties file for the current user interface
language cannot be found, the values of the Summary and Description fields that are specified on the
Required and Optional tabs are used.
• <extension name> is the value of the Name field for the extension, with any spaces replaced by
underscore characters.
• <language-identifier> is the identifier for a particular language. Identifiers for the languages
that are supported by IBM SPSS Statistics are shown in what follows.
For example, the French translations for an extension named MYORG MYSTAT are stored in the file
MYORG_MYSTAT_fr.properties.
The .properties file must contain the following two lines, which specify the localized text for the
two fields:
• The keywords Summary and Description must be in English and the localized text must be on the
same line as the keyword, and with no line breaks.
• The file must be in ISO 8859-1 encoding. Characters that cannot be directly represented in this
encoding must be written with Unicode escapes ("\u").
The lang folder that contains the localized files must have a subfolder named <language-
identifier> that contains the localized .properties file for a particular language. For example,
the French .properties file must be in the lang/fr folder.
Language Identifiers
de. German
en. English
es. Spanish
fr. French
it. Italian
ja. Japanese
Installing an extension
Installing the extension that is open in the Custom Dialog Builder for Extensions also installs the custom
dialogs that are contained in the extension. Installing an existing extension replaces the existing version,
which includes replacing all custom dialogs in the extension that were already installed.
To install the currently open extension, from the menus in the Custom Dialog Builder for Extensions
choose:
File > Install
By default, extensions are installed to a general user-writable location for your operating system. For
more information, see the topic “Installation locations for extensions” on page 198.
Uninstalling an extension
From the menus in the Custom Dialog Builder for Extensions, choose:
File > Uninstall
Production jobs run IBM SPSS Statistics in an automated fashion. The program runs unattended and ends
after the last command runs. You can also schedule the production job to run automatically at scheduled
times. Production jobs are useful if you often run the same set of time-consuming analyses, such as
weekly reports.
You can run production jobs in two different ways:
Interactively. The program runs unattended in a separate session on either your local computer or a
remote server. Your local computer must remain on (and connected to the remote server, if applicable)
until the job is complete.
In the background on a server. The program runs in a separate session on a remote server. Your local
computer does not have to remain on and does not have to remain connected to the remote server. You
can disconnect and retrieve the results later.
Note: Running a production job on a remote server requires access to a server that is running IBM SPSS
Statistics Server.
Default encoding
By default, IBM SPSS Statistics runs in Unicode mode. You can run production jobs in Unicode mode or
the current locale encoding. The encoding affects how data and syntax files are read. For more
information, see the topic “General options” on page 179.
• Unicode (UTF-8). The production job runs in Unicode mode. By default, text data files and command
syntax files are read as Unicode UTF-8. You can specify a code page encoding for text data files with the
ENCODING subcommand on the GET DATA command. You can specify a code page encoding for syntax
files with the ENCODING subcommand on the INCLUDE or INSERT command.
– Local encoding for syntax files. If a syntax file does not contain a UTF-8 byte order mark, read
syntax files as the current locale encoding. This setting overrides any ENCODING specification on
INCLUDE or INSERT. It also ignores any code page identifier in the file.
• Local encoding. The production job runs in the current locale encoding. Unless a different encoding is
explicitly specified on a command that reads text data (for example, GET DATA), text data files are read
in the current locale encoding. Syntax file with a Unicode UTF-8 byte order mark are read as Unicode
UTF-8. All other syntax files are read in the current locale encoding.
Syntax files
Production jobs use command syntax files to tell IBM SPSS Statistics what to do. A command syntax file
is a simple text file containing command syntax. You can use the syntax editor or any text editor to create
the file. You can also generate command syntax by pasting dialog box selections into a syntax window.
See the topic Chapter 14, “Working with Command Syntax,” on page 155 for more information.
If you include multiple command syntax files, the files are concatenated together in the order they appear
in the list and run as a single job.
Syntax format. Controls the form of the syntax rules used for the job.
• Interactive. Each command must end with a period. Periods can appear anywhere within the
command, and commands can continue on multiple lines, but a period as the last nonblank character
on a line is interpreted as the end of the command. Continuation lines and new commands can start
anywhere on a new line. These are the "interactive" rules in effect when you select and run commands
in a syntax window.
• Batch. Each command must start at the beginning of a new line (no blank spaces before the start of the
command), and continuation lines must be indented at least one space. If you want to indent new
commands, you can use a plus sign, dash, or period as the first character at the start of the line and then
indent the actual command. The period at the end of the command is optional. This setting is
compatible with the syntax rules for command files included with the INCLUDE command.
Note: Do not use the Batch option if your syntax files contain GGRAPH command syntax that includes
GPL statements. GPL statements will only run under interactive rules.
Error Processing. Controls the treatment of error conditions in the job.
• Continue processing after errors. Errors in the job do not automatically stop command processing. The
commands in the production job files are treated as part of the normal command stream, and command
processing continues in the normal fashion.
• Stop processing immediately. Command processing stops when the first error in a production job file
is encountered. This is compatible with the behavior of command files included with the INCLUDE
command.
Output
These options control the name, location, and format of the production job results. The following format
options are available:
• Viewer file (.spv). Results are saved in IBM SPSS Statistics Viewer format in the specified file location.
You can store to disk or to an IBM SPSS Collaboration and Deployment Services Repository. Storing to
an IBM SPSS Collaboration and Deployment Services Repository requires the Statistics Adapter.
• Word/RTF. Pivot tables are exported as Word tables with all formatting attributes intact (for example,
cell borders, font styles, and background colors). Text output is exported as formatted RTF. Charts, tree
diagrams, and model views are included in PNG format. Note that Microsoft Word might not display
extremely wide tables properly.
• Excel. Pivot table rows, columns, and cells are exported as Excel rows, columns, and cells, with all
formatting attributes intact (for example, cell borders, font styles, and background colors). Text output
is exported with all font attributes intact. Each line in the text output is a row in the Excel file, with the
entire contents of the line in a single cell. Charts, tree diagrams, and model views are included in PNG
format. Output can be exported as Excel 97-2004 or Excel 2007 and higher.
• HTML. Pivot tables are exported as HTML tables. Text output is exported as preformatted HTML. Charts,
tree diagrams, and model views are embedded in the document in the selected graphic format. A
browser compatible with HTML 5 is required for viewing output that is exported in HTML format.
HTML options
Table options
No table options are available for HTML format. All pivot tables are converted to HTML tables.
Image options
The available image types are: JPEG, PNG, and BMP. You can also scale the image size from 1% to
200%.
PowerPoint options
Table Options. You can use the Viewer outline entries as slide titles. Each slide contains a single output
item. The title is formed from the outline entry for the item in the outline pane of the Viewer.
Image Options. You can scale the image size from 1% to 200%. (All images are exported to PowerPoint
in TIFF format.)
Note: PowerPoint format is only available on Windows operating systems and requires PowerPoint 97 or
later.
PDF options
Embed bookmarks. This option includes bookmarks in the PDF document that correspond to the Viewer
outline entries. Like the Viewer outline pane, bookmarks can make it much easier to navigate documents
with a large number of output objects.
Embed fonts. Embedding fonts ensures that the PDF document will look the same on all computers.
Otherwise, if some fonts used in the document are not available on the computer being used to view (or
print) the PDF document, font substitution may yield suboptimal results.
Text options
Table Options. Pivot tables can be exported in tab-separated or space-separated format. For space-
separated format, you can also control:
• Column Width. Autofit does not wrap any column contents, and each column is as wide as the widest
label or value in that column. Custom sets a maximum column width that is applied to all columns in
the table, and values that exceed that width wrap onto the next line in that column.
• Row/Column Border Character. Controls the characters used to create row and column borders. To
suppress display of row and column borders, enter blank spaces for the values.
Image Options. The available image types are: EPS, JPEG, TIFF, PNG, and BMP. On Windows operating
systems, EMF (enhanced metafile) format is also available. You can also scale the image size from 1% to
200%.
Runtime values
Runtime values defined in a production job file and used in a command syntax file simplify tasks such as
running the same analysis for different data files or running the same set of commands for different sets
of variables. For example, you could define the runtime value @datafile to prompt you for a data file name
each time you run a production job that uses the string @datafile in place of a file name in the command
syntax file.
• Runtime value substitution uses the macro facility (DEFINE-!ENDDEFINE) to create string substitution
values.
• Runtime values in command syntax files are ignored if they are enclosed in quotation marks. If the
runtime value needs to be quoted, select Quote Value. If the runtime value is only part of a quoted
string, you can include the runtime value in a macro with the !UNQUOTE and !EVAL parameters.
Symbol. The string in the command syntax file that triggers the production job to prompt the user for a
value. The symbol name must begin with an @ sign and must conform to variable naming rules. See the
topic “Variable names” on page 46 for more information.
Default Value. The value that the production job supplies by default if you don't enter a different value.
This value is displayed when the production job prompts you for information. You can replace or modify
the value at runtime. If you don't provide a default value, don't use the silent keyword when running the
production job with command line switches, unless you also use the -symbol switch to specify runtime
values. See the topic “Running production jobs from a command line” on page 240 for more information.
User Prompt. The descriptive label that is displayed when the production job prompts you to enter
information. For example, you could use the phrase "What data file do you want to use?" to identify a field
that requires a data filename.
Quote Value. Encloses the default value or the value entered by the user in quotes. For example, file
specifications should be enclosed in quotes.
DEFINE !LabelSub()
VARIABLE LABELS Var1
!QUOTE(!concat(!UNQUOTE('First part of label - '), !UNQUOTE(!EVAL(@replace)), !UNQUOTE(' -
rest of label'))).
Run options
You can run production jobs in two different ways:
Interactively. The program runs unattended in a separate session on either your local computer or a
remote server. Your local computer must remain on (and connected to the remote server, if applicable)
until the job is complete.
In the background on a server. The program runs in a separate session on a remote server. Your local
computer does not have to remain on and does not have to remain connected to the remote server. You
can disconnect and retrieve the results later.
Note: Running a production job on a remote server requires access to a server that is running IBM SPSS
Statistics Server.
Statistics server. If you select to run the production job in the background on a remote server, you must
specify the server on which it will run. Click Select Server to specify the server. This applies only to jobs
run in the background on a remote server, not jobs run interactively on a remote server.
Server login
Use the Server login dialog to add and modify remote servers and to select the server to use to run the
current production job. Remote servers usually require a user ID and password, and a domain name may
also be necessary. Contact your system administrator for information about available servers, a user ID
and password, domain names, and other connection information.
If your site is running IBM SPSS Collaboration and Deployment Services 3.5 or later, you can click
Search... to view a list of servers that are available on your network. If you are not logged on to a IBM
SPSS Collaboration and Deployment Services Repository, you will be prompted to enter connection
information before you can view the list of servers.
User prompts
A production job prompts you for values whenever you run a production job that contains defined runtime
symbols. You can replace or modify the default values that are displayed. Those values are then
substituted for the runtime symbols in all command syntax files associated with the production job.
MacOS:
Depending on how you invoke the production job, you may need to include directory paths for the
application's executable file (located in the directory in which the application is installed) and/or the
production job file.
Note: You cannot run command line production jobs while the IBM SPSS Statistics Subscription
application is running.
You can run production jobs from a command line with the following switches:
-production [prompt|silent]. Start the application in production mode. The prompt and silent
keywords specify whether to display the dialog box that prompts for runtime values if they are specified in
the job. The prompt keyword is the default and shows the dialog box. The silent keyword suppresses the
dialog box. If you use the silent keyword, you can define the runtime symbols with the -symbol
switch. Otherwise, the default value is used. The -switchserver and -singleseat switches are
ignored when using the -production switch.
-symbol <values>. List of symbol-value pairs used in the production job. Each symbol name starts with
@. Values that contain spaces should be enclosed in quotes. Rules for including quotes or apostrophes in
string literals may vary across operating systems, but enclosing a string that includes single quotes or
apostrophes in double quotes usually works (for example, “'a quoted value'”). The symbols must be
defined in the production job using the Runtime Values tab. See the topic “Runtime values” on page 238
for more information.
-background. Run the production job in the background on a remote server. Your local computer does
not have to remain on and does not have to remain connected to the remote server. You can disconnect
and retrieve the results later. You must also include the -production switch and specify the server
using the -server switch.
Example
Windows:
MacOS:
• This example assumes that you are running the command line from the installation directory, so no path
is required for the IBM SPSS Statistics Subscription executable file. The default installation path is as
follows:
Windows: $InstalledPath$
MacOS: $InstalledPath$/IBMSPSSStatistics.app/Contents/MacOS/
• The directory path for the location of the production job uses the Windows back slash convention. On
Macintosh and Linux, use forward slashes. The forward slashes in the quoted data file specification will
work on all operating systems since this quoted string is inserted into the command syntax file and
forward slashes are acceptable in commands that include file specifications (for example, GET FILE,
GET DATA, SAVE) on all operating systems.
• The silent keyword suppresses any user prompts in the production job, and the --symbol switch
inserts the quoted data file name and location wherever the runtime symbol @sex male appears in the
command syntax files included in the production job.
[installpath]\prodconvert [filepath]\filename.spp
where [installpath] is the location of the folder in which IBM SPSS Statistics is installed and [filepath] is
the folder t the original production job file is located. A new file with the same name but with the
extension .spj is created in the same folder as the original file. (Note: If the path contains spaces, enclose
each path and file specification in double quotes. On Macintosh operating systems, use forward slashes
instead of back slashes.)
Limitations
• WMF and EMF chart formats are not supported. PNG format is used in place of these formats.
• The export options Output Document (No Charts), Charts Only, and Nothing are not supported. All
output objects supported by the selected format are included.
• Remote server settings are ignored. To specify remote server settings for distributed analysis, you need
to run the production job from a command line, using command line switches to specify the server
settings. See the topic “Running production jobs from a command line” on page 240 for more
information.
• Publish to Web settings are ignored.
The Output Management System (OMS) provides the ability to automatically write selected categories of
output to different output files in different formats. Formats include: Word, Excel, PDF, IBM SPSS
Statistics data file format (.sav), Viewer file format (.spv), XML, HTML, and text. See the topic “OMS
options” on page 246 for more information.
To use the Output Management System Control Panel
1. From the menus choose:
Utilities > OMS Control Panel...
You can use the control panel to start and stop the routing of output to various destinations.
• Each OMS request remains active until explicitly ended or until the end of the session.
• A destination file that is specified on an OMS request is unavailable to other procedures and other
applications until the OMS request is ended.
• While an OMS request is active, the specified destination files are stored in memory (RAM), so active
OMS requests that write a large amount of output to external files may consume a large amount of
memory.
• Multiple OMS requests are independent of each other. The same output can be routed to different
locations in different formats, based on the specifications in different OMS requests.
• The order of the output objects in any particular destination is the order in which they were created,
which is determined by the order and operation of the procedures that generate the output.
Limitations
• For Output XML format, the specification for the Headings output type has no effect. If any output from
a procedure is included, the procedure title output is included.
• If the OMS specification results in nothing other than Headings objects or a Notes tables being included
for a procedure, then nothing is included for that procedure.
Adding new OMS requests
1. Select the output types (tables, charts, etc.) that you want to include. See the topic “Output object
types” on page 244 for more information.
2. Select the commands to include. If you want to include all output, select all items in the list. See the
topic “Command identifiers and table subtypes” on page 245 for more information.
3. For commands that produce pivot table output, select the specific table types to include.
The list displays only the tables that are available in the selected commands; any table type that is
available in one or more of the selected commands is displayed in the list. If no commands are
selected, all table types are displayed. See the topic “Command identifiers and table subtypes” on
page 245 for more information.
4. To select tables based on text labels instead of subtypes, click Labels. See the topic “Labels” on page
245 for more information.
5. Click Options to specify the output format (for example, IBM SPSS Statistics data file, XML, or HTML).
By default, Output XML format is used. See the topic “OMS options” on page 246 for more information.
6. Specify an output destination:
• File. All selected output is routed to a single file.
• Based on object names. Output is routed to multiple destination files based on object names. A
separate file is created for each output object, with a filename based on either table subtype names
or table labels. Enter the destination folder name.
• New dataset. For IBM SPSS Statistics data file format output, you can route the output to a dataset.
The dataset is available for subsequent use in the same session but is not saved unless you explicitly
save it as a file prior to the end of the session. This option is available only for IBM SPSS Statistics
data file format output. Dataset names must conform to variable-naming rules. See the topic
“Variable names” on page 46 for more information.
7. Optionally:
• Exclude the selected output from the Viewer. If you select Exclude from Viewer, the output types in
the OMS request will not be displayed in the Viewer window. If multiple active OMS requests include
the same output types, the display of those output types in the Viewer is determined by the most recent
OMS request that contains those output types. See the topic “Excluding output display from the viewer”
on page 248 for more information.
• Assign an ID string to the request. All requests are automatically assigned an ID value, and you can
override the system default ID string with a descriptive ID, which can be useful if you have multiple
active requests that you want to identify easily. ID values that you assign cannot start with a dollar sign
($).
Tips for selecting multiple items in a list
The following tips are for selecting multiple items in a list:
• Press Ctrl+A to select all items in a list.
• Use Shift+click to select multiple contiguous items.
• Use Ctrl+click to select multiple noncontiguous items.
To end and delete OMS requests
Active and new OMS requests are displayed in the Requests list, with the most recent request at the top.
You can change the widths of the information columns by clicking and dragging the borders, and you can
scroll the list horizontally to see more information about a particular request.
An asterisk (*) after the word Active in the Status column indicates an OMS request that was created with
command syntax that includes features that are not available in the Control Panel.
To end a specific, active OMS request:
1. In the Requests list, click any cell in the row for the request.
2. Click End.
To end all active OMS requests:
1. Click End All.
To delete a new request (a request that has been added but is not yet active):
1. In the Requests list, click any cell in the row for the request.
2. Click Delete.
Note: Active OMS requests are not ended until you click OK.
Labels
As an alternative to table subtype names, you can select tables based on the text that is displayed in the
outline pane of the Viewer. You can also select other object types based on their labels. Labels are useful
for differentiating between multiple tables of the same type in which the outline text reflects some
attribute of the particular output object, such as the variable names or labels. There are, however, a
number of factors that can affect the label text:
• If split-file processing is on, split-file group identification may be appended to the label.
• Labels that include information about variables or values are affected by your current output label
options settings (Edit menu, Options, Output Labels tab).
• Labels are affected by the current output language setting (Edit menu, Options, General tab).
To specify labels to use to identify output objects
1. In the Output Management System Control Panel, select one or more output types and then select one
or more commands.
2. Click Labels.
OMS options
You can use the OMS Options dialog box to:
• Specify the output format.
• Specify the image format (for HTML and Output XML output formats).
• Specify what table dimension elements should go into the row dimension.
• Include a variable that identifies the sequential table number that is the source for each case (for IBM
SPSS Statistics data file format).
Format
Excel
Excel 97-2004 and Excel 2007 and higher formats. Pivot table rows, columns, and cells are exported
as Excel rows, columns, and cells, with all formatting attributes intact -- for example, cell borders,
font styles, and background colors. Text output is exported with all font attributes intact. Each line in
the text output is a row in the Excel file, with the entire contents of the line contained in a single cell.
Charts, tree diagrams, and model views are included in PNG format.
HTML
Output objects that would be pivot tables in the Viewer are converted to HTML tables. Text output
objects are tagged <PRE> in the HTML. Charts, tree diagrams, and model views are embedded in the
document in the selected format.
Output XML
XML that conforms to the spss-output schema.
PDF
Output is exported as it would appear in Print Preview, with all formatting attributes intact. The PDF
file includes bookmarks that correspond to the entries in the Viewer outline pane.
IBM SPSS Statistics Data File
This format is a binary file format. All output object types other than tables are excluded. Each column
of a table becomes a variable in the data file. To use a data file that is created with OMS in the same
session, you must end the active OMS request before you can open the data file.See the topic
“Routing output to IBM SPSS Statistics data files” on page 249 for more information.
Text
Space-separated text. Output is written as text, with tabular output aligned with spaces for fixed-
pitch fonts. Charts, tree diagrams, and model views are excluded.
Tabbed Text
Tab-delimited text. For output that is displayed as pivot tables in the Viewer, tabs delimit table
column elements. Text block lines are written as is; no attempt is made to divide them with tabs at
useful places. Charts, tree diagrams, and model views are excluded.
Graphics Images
For HTML and Output XML formats, you can include charts, tree diagrams, and model views as image files.
A separate image file is created for each chart and/or tree.
• For HTML document format, standard <IMG SRC='filename'> tags are included in the HTML
document for each image file.
• For Output XML document format, the XML file contains a chart element with an ImageFile attribute
of the general form <chart imageFile="filepath/filename"/> for each image file.
• Image files are saved in a separate subdirectory (folder). The subdirectory name is the name of the
destination file, without any extension and with _files appended to the end. For example, if the
destination file is julydata.htm, the images subdirectory will be named julydata_files.
Format
The available image formats are PNG, JPG, and BMP.
Size
You can scale the image size from 10% to 200%.
Include Imagemaps
For HTML document format, this option creates image map ToolTips that display information for some
chart elements, such as the value of the selected point on a line chart or bar on a bar chart.
Table Pivots
For pivot table output, you can specify the dimension element(s) that should appear in the columns. All
other dimension elements appear in the rows. For IBM SPSS Statistics data file format, table columns
become variables, and rows become cases.
• If you specify multiple dimension elements for the columns, they are nested in the columns in the order
in which they are listed. For IBM SPSS Statistics data file format, variable names are constructed by
nested column elements. See the topic “Variable names in OMS-generated data files” on page 249 for
more information.
• If a table doesn't contain any of the listed dimension elements, all dimension elements for that table
will appear in the rows.
• Table pivots that are specified here have no effect on tables that are displayed in the Viewer.
Each dimension of a table--row, column, layer--may contain zero or more elements. For example, a
simple two-dimensional crosstabulation contains a single row dimension element and a single column
dimension element, each of which contains one of the variables that are used in the table. You can use
either positional arguments or dimension element "names" to specify the dimension elements that you
want to put into the column dimension.
All dimensions in rows
Creates a single row for each table. For IBM SPSS Statistics format data files, this means each table is
a single case, and all the table elements are variables.
List of positions
The general form of a positional argument is a letter indicating the default position of the element--C
for column, R for row, or L for layer--followed by a positive integer indicating the default position
within that dimension. For example, R1 would indicate the outermost row dimension element.
• To specify multiple elements from multiple dimensions, separate each dimension with a space—for
example, R1 C2.
Viewing all dimension elements and their labels for a pivot table
1. Activate (double-click) the table in the Viewer.
2. From the menus choose:
View > Show All
or
3. If the pivoting trays aren't displayed, from the menus choose:
Pivot > Pivoting Trays
The element labels are dispalyed in the pivoting trays.
Logging
You can record OMS activity in a log in XML or text format.
• The log tracks all new OMS requests for the session but does not include OMS requests that were
already active before you requested a log.
• The current log file ends if you specify a new log file or if you deselect (clear) Log OMS activity.
How to specify OMS logging
To specify OMS logging:
1. Click Logging in the Output Management System Control Panel.
• OMS command and subType attribute values are not affected by output language or display settings for
variable names/labels or values/value labels.
• XML is case sensitive. A subType attribute value of "frequencies" is not the same as a subType
attribute value of "Frequencies."
• All information that is displayed in a table is contained in attribute values in OXML. At the individual cell
level, OXML consists of “empty” elements that contain attributes but no “content” other than the
content that is contained in attribute values.
• Table structure in OXML is represented row by row; elements that represent columns are nested within
the rows, and individual cells are nested within the column elements:
<pivotTable...>
<dimension axis='row'...>
<dimension axis='column'...>
<category...>
<cell text=’...' number='...' decimals='...'/>
</category>
<category...>
<cell text='...' number='...' decimals='...'/>
</category>
</dimension>
</dimension>
...
</pivotTable>
The preceding example is a simplified representation of the structure that shows the descendant/
ancestor relationships of these elements. However, the example does not necessarily show the parent/
child relationships, because there are typically intervening nested element levels.
The following example shows a simple frequency table and the complete output XML representation of
that table.
As you may notice, a simple, small table produces a substantial amount of XML. That's partly because the
XML contains some information that is not readily apparent in the original table, some information that
might not even be available in the original table, and a certain amount of redundancy.
• The table contents as they are (or would be) displayed in a pivot table in the Viewer are contained in
text attributes. An example is as follows:
• For a numeric variable, there would be a number attribute instead of a string attribute. The label
attribute is present only if the variable or values have defined labels.
• The <cell> elements that contain cell values for numbers will contain the text attribute and one or
more additional attribute values. An example is as follows:
The number attribute is the actual, unrounded numeric value, and the decimals attribute indicates the
number of decimal positions that are displayed in the table.
• Because columns are nested within rows, the category element that identifies each column is repeated
for each row. For example, because the statistics are displayed in the columns, the element <category
text="Frequency"> appears three times in the XML: once for the male row, once for the female row,
and once for the total row.
OMS identifiers
The OMS Identifiers dialog box is designed to assist you in writing OMS command syntax. You can use this
dialog box to paste selected command and subtype identifiers into a command syntax window.
To use the oms identifiers dialog box
1. From the menus choose:
Utilities > OMS Identifiers...
2. Select one or more command or subtype identifiers. (Use Ctrl+click to select multiple identifiers in
each list.)
3. Click Paste Commands and/or Paste Subtypes.
• The list of available subtypes is based on the currently selected command(s). If multiple commands are
selected, the list of available subtypes is the union of all subtypes that are available for any of the
selected commands. If no commands are selected, all subtypes are listed.
• The identifiers are pasted into the designated command syntax window at the current cursor location. If
there are no open command syntax windows, a new syntax window is automatically opened.
• Each command and/or subtype identifier is enclosed in quotation marks when pasted, because OMS
command syntax requires these quotation marks.
• Identifier lists for the COMMANDS and SUBTYPES keywords must be enclosed in brackets, as in:
Autoscripts
Autoscripts are scripts that run automatically when triggered by the creation of specific pieces of output
from selected procedures. For example, you can use an autoscript to automatically remove the upper
diagonal and highlight correlation coefficients below a certain significance whenever a Correlations table
is produced by the Bivariate Correlations procedure.
Autoscripts can be specific to a given procedure and output type or apply to specific output types from
different procedures. For example, you might have an autoscript that formats the ANOVA tables produced
by One-Way ANOVA as well as ANOVA tables produced by other statistical procedures. On the other hand,
Frequencies produces both a frequency table and a table of statistics, and you might choose to have a
different autoscript for each.
Each output type for a given procedure can only be associated with a single autoscript. You can, however,
create a base autoscript that is applied to all new Viewer items prior to the application of any autoscripts
for specific output types. See the topic “Script options” on page 189 for more information.
The Scripts tab in the Options dialog box (accessed from the Edit menu) displays the autoscripts that have
been configured on your system and allows you to set up new autoscripts or modify the settings for
existing ones. Optionally, you can create and configure autoscripts for output items directly from the
Viewer.
Events that Trigger Autoscripts
The following events can trigger autoscripts:
• Creation of a pivot table
• Creation of a Notes object
• Creation of a Warnings object
You can also use a script to trigger an autoscript indirectly. For example, you could write a script that
invokes the Correlations procedure, which in turn triggers an autoscript registered to the resulting
Correlations table.
Creating Autoscripts
You can create an autoscript by starting with the output object that you want to serve as the trigger--for
instance, a frequency table.
1. In the Viewer, select the object that will trigger the autoscript.
2. From the menus choose:
Utilities > Create/Edit AutoScript…
If the selected object does not have an associated autoscript, an Open dialog prompts you for the
location and name of a new script.
3. Browse to the location where the new script will be stored, enter a file name and click Open. The
editor for the default script language opens. You can change the default script language from the
Scripts tab on the Options dialog. See the topic “Script options” on page 189 for more information.
4. Type the code.
For help with converting custom Sax Basic autoscripts used in pre-16.0 versions, see “Compatibility with
Versions Prior to 16.0” on page 259.
Note: By default, the executable associated with the default script language will be used to run the
autoscript. You can change the executable from the Scripts tab in the Options dialog.
If the selected object is already associated with an autoscript, the script is opened in the script editor
associated with the language in which the script is written.
Scripting in Basic
Scripting in Basic is available on Windows only and is installed with the Core system. Extensive online
help for scripting in Basic is available from the IBM SPSS Statistics Basic Script Editor. The editor can be
accessed from File>New>Script when the default script language (set from the Scripts tab on the Options
dialog) is set to Basic (the system default on Windows). It is also accessed from File>Open>Script, by
choosing Basic (wwd;sbs) in the Files of type list.
Note: For Windows 7 and higher, accessing the online help for Basic scripting requires the Windows Help
program (WinHlp32.exe), which may not be present on your system. If you cannot view the online help,
then contact Microsoft for instructions on how to obtain the Windows Help program (WinHlp32.exe).
Sub Descriptives_Table_DescriptiveStatistics_Create _
(objPivotTable As Object,objOutputDoc As Object,lngIndex As Long)
'Autoscript
'Trigger Event: DescriptiveStatistics Table Creation after running
' Descriptives procedure.
'Purpose: Swaps the Rows and Columns in the currently active pivot table.
'Assumptions: Selected Pivot Table is already activated.
'Effects: Swaps the Rows and Columns in the output
'Inputs: Pivot Table, OutputDoc, Item Index
End Sub
Sub Main
'Purpose: Swaps the Rows and Columns in the currently active pivot table.
'Effects: Swaps the Rows and Columns in the output
• Notice that nothing in the converted script indicates which object the script is to be applied to. The
association between an output item and an autoscript is set from the Scripts tab of the Options dialog
and maintained across sessions.
• scriptContext.GetOutputItem gets the output item (an ISpssItem object) that triggered the
autoscript.
• The object returned by scriptContext.GetOutputItem is not activated. If your script requires an
activated object, you'll need to activate it, as done in this example with the ActivateTable method.
When you're finished with any table manipulations, call the Deactivate method.
For version 16.0, there is no distinction between scripts that are run as autoscripts and scripts that aren't
run as autoscripts. Any script, appropriately coded, can be used in either context. See the topic “The
scriptContext Object” on page 261 for more information.
Note: To trigger a script from the application creation event, see “Startup Scripts” on page 261.
Script Editor
For version 16.0 and above the script editor for Basic no longer supports the following pre-16.0 features:
• The Script, Analyze, Graph, Utilities, and Add-Ons menus.
• The ability to paste command syntax into a script window.
The IBM SPSS Statistics Basic Script Editor is a standalone application that is launched from within IBM
SPSS Statistics via File>New>Script, File>Open>Script, or Utilities>Create/Edit AutoScript (from a Viewer
window). It allows you to run scripts against the instance of IBM SPSS Statistics from which it was
launched. Once opened, the editor will remain open after exiting IBM SPSS Statistics, but scripts that use
IBM SPSS Statistics objects will no longer run.
File Types
To connect to a running instance of the IBM SPSS Statistics client from an external COM client, use:
If more than one client is running, GetObject will connect to the most recently launched one.
Note: For post-16.0 versions, the identifier is still Application16.
Sub Main
If scriptContext Is Nothing Then
MsgBox "I'm not an autoscript"
Else
MsgBox "I'm an autoscript"
End If
End Sub
• When a script is not run as an autoscript, the scriptContext object will have a value of Nothing.
• Given the If-Else logic in this example, you would include your autoscript-specific code in the Else
clause. Any code that is not to be run in the context of an autoscript would be included in the If clause.
Of course you can also include code that is to be run in either context.
Getting Values Required by Autoscripts
The scriptContext object provides access to values required by an autoscript, such as the output item
that triggered the current autoscript.
• The scriptContext.GetOutputItem method returns the output item (an ISpssItem object) that
triggered the current autoscript.
• The scriptContext.GetOutputDoc method returns the output document (an ISpssOutputDoc
object) associated with the current autoscript.
• The scriptContext.GetOutputItemIndex method returns the index, in the associated output
document, of the output item that triggered the current autoscript.
Note: The object returned by scriptContext.GetOutputItem is not activated. If your script requires
an activated object, you'll need to activate it--for instance, with the ActivateTable method. When
you're finished with any manipulations, call the Deactivate method.
Startup Scripts
You can create a script that runs at the start of each session and a separate script that runs each time you
switch servers. For Windows you can have versions of these scripts in both Python and Basic. For all other
platforms the scripts can only be in Python.
• The startup script must be named StartClient_.py for Python or StartClient_.wwd for Basic.
#StartServer_.py
import SpssClient
SpssClient.StartClient()
SpssClient.RunSyntax(r""" HOST COMMAND=['net use y: \\myserver\data']. """)
SpssClient.StopClient()
The SpssClient.RunSyntax method is used to run a HOST command that calls the Windows net use
command to perform the mapping. When the StartServer_ script runs, IBM SPSS Statistics is in
distributed mode so the HOST command runs on the IBM SPSS Statistics Server machine.
If you have command syntax files that contain TABLES syntax that you want to convert to CTABLES
syntax and/or IGRAPH syntax that you want to convert to GGRAPH syntax, a simple utility program is
provided to help you get started with the conversion process. There are, however, significant functionality
differences between TABLES and CTABLES and between IGRAPH and GGRAPH. It is likely that you will
find that the utility program cannot convert some of your TABLES and IGRAPH syntax jobs or may
generate CTABLES and GGRAPH syntax that produces tables and graphs that do not closely resemble the
originals produced by the TABLES and IGRAPH commands. For most tables, you can edit the converted
syntax to produce a table closely resembling the original.
The utility program is designed to:
• Create a new syntax file from an existing syntax file. The original syntax file is not altered.
• Convert only TABLES and IGRAPH commands in the syntax file. Other commands in the file are not
altered.
• Retain the original TABLES and IGRAPH syntax in commented form.
• Identify the beginning and end of each conversion block with comments.
• Identify TABLES and IGRAPH syntax commands that could not be converted.
• Convert command syntax files that follow either interactive or production mode syntax rules.
This utility cannot convert commands that contain errors. The following other limitations also apply.
TABLES Limitations
The utility program may convert TABLES commands incorrectly under some circumstances, including
TABLES commands that contain:
• Parenthesized variable names with the initial letters "sta" or "lab" in the TABLES subcommand if the
variable is parenthesized by itself—for example, var1 by (statvar) by (labvar). These will be
interpreted as the (STATISTICS) and (LABELS) keywords.
• SORT subcommands that use the abbreviations A or D to indicate ascending or descending sort order.
These will be interpreted as variable names.
The utility program cannot convert TABLES commands that contain:
• Syntax errors.
• OBSERVATION subcommands that refer to a range of variables using the TO keyword (for example,
var01 TO var05).
• String literals broken into segments separated by plus signs (for example, TITLE "My" + "Title").
• Macro calls that, in the absence of macro expansion, would be invalid TABLES syntax. Since the
converter does not expand the macro calls, it treats them as if they were simply part of the standard
TABLES syntax.
The utility program will not convert TABLES commands contained in macros. All macros are unaffected by
the conversion process.
IGRAPH Limitations
IGRAPH changed significantly in release 16. Because of these changes, some subcommands and
keywords in IGRAPH syntax created before that release may not be honored. See the IGRAPH section in
the Command Syntax Reference for the complete revision history.
The conversion utility program may generate additional syntax that it stores in the INLINETEMPLATE
keyword within the GGRAPH syntax. This keyword is created only by the conversion program. Its syntax is
not intended to be user-editable.
Using the Conversion Utility Program
The conversion utility program, SyntaxConverter.exe, can be found in the installation directory. It is
designed to run from a command prompt. The general form of the command is:
You can protect confidential information stored in a data file, an output document, or a syntax file by
encrypting the file with a password. Once encrypted, the file can only be opened by providing the
password. The option to encrypt a file is provided on the Save As dialogs for data files, output documents,
and syntax files. You can also encrypt a data file when sorting it and saving the sorted file.
• Passwords cannot be recovered if they are lost. If the password is lost the file cannot be opened.
• Passwords are limited to 10 characters and are case-sensitive.
Creating strong passwords
• Use eight or more characters.
• Include numbers, symbols and even punctuation in your password.
• Avoid sequences of numbers or characters, such as "123" and "abc", and avoid repetition, such as
"111aaa".
• Do not create passwords that use personal information such as birthdays or nicknames.
• Periodically change the password.
Modifying encrypted files
• If you open an encrypted file, make modifications to it and choose File > Save, the modified file will be
saved with the same password.
• You can change the password on an encrypted file by opening the file, repeating the steps for
encrypting it, and specifying a different password in the Encrypt File dialog box.
• You can save an unencrypted version of an encrypted data file or output document by opening the file,
choosing File > Save As and deselecting Encrypt file with password in the associated Save As dialog
box. For an encrypted syntax file, select Syntax from the Save as type drop-down list to save an
unencrypted version of the file.
Note: Encrypted data files and output documents cannot be opened in versions of IBM SPSS Statistics
prior to version 21. Encrypted syntax files cannot be opened in versions prior to version 22.
266 IBM SPSS Statistics 27 Core System User's Guide
Notices
This information was developed for products and services offered in the US. This material might be
available from IBM in other languages. However, you may be required to own a copy of the product or
product version in that language in order to access it.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that only
that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not grant you any license to these patents. You can send
license inquiries, in writing, to:
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at
"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or
trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon,
Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or
its subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.
A cases (continued)
finding in Data Editor 57
Access (Microsoft) 15 inserting new cases 56
active file restructuring into variables 105
caching 39 selecting subsets 103, 104
creating a temporary active file 39 sorting 95
virtual active file 39 weighting 104
active window 1 categorical data
adding group labels 130 converting interval data to discrete categories 72
aggregating data cell properties 137
aggregate functions 102 cells in pivot tables
variable names and labels 102 formats 135
algorithms 5 hiding 133
alignment selecting 139
in Data Editor 50 showing 133
output 116, 182 widths 139
alternating row colors centered moving average function 91
pivot tables 135 centering output 116, 182
aspect ratio 185 character encoding 181
attributes Chart Builder
custom variable attributes 51 gallery 167
automated output modification 149, 150, 152–154 Chart Editor
automated production 235 properties 168
automatic output modification 149 chart options 185
automatic recovery 2 charts
Automatic Recovery 179 aspect ratio 185
autoscripts creating from pivot tables 141
associating with viewer objects 256 exporting 120
Basic 261 hiding 115
creating 256 missing values 169
trigger events 255 overview 167
size 169
templates 169, 185
B wrapping panels 169
background color 137 Cognos
banding 72 exporting to Cognos TM1 35
bi-directional text 181 reading Cognos Business Intelligence data 19
binning 72 reading Cognos TM1 data 21
Blom estimates 84 collapsing categories 72
BMP files color coding
exporting charts 120, 125 syntax editor 159
bookmarks colors in pivot tables
syntax editor 161 borders 136
borders column width
displaying hidden borders 139 controlling default width 187
break variables controlling maximum width 134
in Aggregate Data 101 controlling width for wrapped text 134
breakpoints in Data Editor 50
syntax editor 160 pivot tables 139
columns
changing width in pivot tables 139
C selecting in pivot tables 139
COMMA format 47, 48
caching
comma-delimited files 10
active file 39
command identifiers 245
captions 137
command language 155
cases
command line switches
finding duplicates 71
Index 269
command line switches (continued) Custom Dialog Builder (continued)
Production jobs 240 file browser 222
command syntax file type filter 223
accessing Command Syntax Reference 5 filtering variable lists 209
adding to menus 193 help file 202
journal file 164, 165 installing compatible custom dialogs 229
output log 156 installing extensions containing dialogs 228
pasting 156 item group control 220
Production jobs rules 235 layout rules 203
running 163 list box 212
running with toolbar buttons 194 list box list items 211
syntax rules 155 localizing dialogs and help files 231
command syntax editor menu location 202
auto-completion 159 modifying compatible custom dialogs 229
bookmarks 157, 161 modifying dialogs in installed extensions 228
breakpoints 157, 160, 163 number control 214
color coding 159 opening compatible custom dialog package files 229
command spans 157 opening extensions containing dialogs 228
commenting or uncommenting text 162 preview 205
formatting syntax 162 radio group 220
indenting syntax 162 radio group buttons 221
line numbers 157 saving compatible custom dialogs 229
multiple views/panes 157 saving extensions containing dialogs 228
options 190 secured text 216
command syntax files 163, 164 source list 206
comparing datasets 37 static text control 217
compatible custom dialog 200 sub-dialog button 223
computing variables sub-dialog properties 224
computing new string variables 78 syntax template 204
conditional transformations 77 tab 223
continuation text table control 218
for pivot tables 136 table control columns 218
controlling number of rows to display 134 target list 207
copy special 119 text control 213
copying and pasting output into other applications 119 Custom Dialog Builder for Extensions 200
counting occurrences 79 custom tables
Crosstabs converting TABLES command syntax to CTABLES 263
fractional weights 104 custom variable attributes 51
CSV format
reading data 10
saving data 23
D
CTABLES data dictionary
converting TABLES command syntax to CTABLES 263 applying from another file 68
cumulative sum function 91 Data Editor
currency formats 184 alignment 50
custom attributes 51 changing data type 57
custom currency formats 47, 184 column width 50
Custom Dialog Builder data value restrictions 55
check box 210 Data View 45
check box group 221 defining variables 46
color picker 217 descriptive statistics 58
combo box 210 descriptive statistics options 184
combo box list items 211 display options 59
compatible custom dialog package (spd) files 229 editing data 55, 56
converting to enhanced dialogs 229 entering data 54
custom dialogs for extension commands 231 entering non-numeric data 54
data source 202 entering numeric data 54
dataset selector 209 filtered cases 58
date control 215 inserting new cases 56
dialog properties 202 inserting new variables 56
enabling rules 224 moving variables 57
extension bundle files 228 multiple open data files 61, 179
field chooser 208 multiple views/panes 59
field source 209 printing 59
Index 271
ensemble viewer (continued) file transformations (continued)
predictor frequency 146 transposing variables and cases 96
predictor importance 146 weighting cases 104
entering data files
non-numeric 54 adding a text file to the Viewer 117
numeric 54 opening 7
using value labels 55 filtered cases
environment variables in Data Editor 58
SPSSTMPDIR 188 find and replace
EPS files Viewer documents 118
exporting charts 120, 125 fixed format 10
Excel files fonts
adding menu item to send data to Excel 193 in Data Editor 59
opening 7 in the outline pane 117
reading 8 footers 126
saving 23 footnotes
saving value labels instead of values 23 charts 169
Excel format markers 135
exporting output 120, 122, 246 renumbering 138
excluding output from Viewer with OMS 248 freefield format 10
EXECUTE (command) functions
pasted from dialog boxes 164, 165 missing value treatment 78
export data 23
exporting
models 144
G
exporting charts GET DATA
automated production 235 versus DATA LIST command 39
exporting data versus GET CAPTURE command 39
adding menu items to export data 193 GGRAPH
exporting output converting IGRAPH to GGRAPH 263
Excel format 120, 122, 246 grid lines
HTML 121 pivot tables 139
HTML format 120 group labels 130
OMS 243 grouping rows or columns 130
PDF format 120, 123, 246 grouping variables
PowerPoint format 120 creating 105
text format 246
Word format 120, 122, 246
extension bundles H
batch installation 199
headers 126
creating extension bundles 233
Help windows 5
installing extension bundles 197
hiding
installing on Statistics Server 199
captions 137
extension commands
dimension labels 133
custom dialogs 231
footnotes 138
extensions
procedure results 115
extension details 197
rows and columns 133
finding and installing new extensions 196
titles 133
installing updates to extensions 196
toolbars 193
removing extensions 196
hiding (excluding) output from the Viewer with OMS 248
viewing installed extensions 196
hiding variables
Data Editor 176
F dialog lists 176
HTML
fast pivot tables 187 exporting output 120, 121
file information 22
file locations
controlling default file locations 188 I
file transformations
IBM SPSS Data Collection data
aggregating data 101
saving 34
merging data files 97, 98
IBM SPSS Statistics data file format
restructuring data 105
routing output to a data file 246, 249
sorting cases 95
icons
split-file processing 102
Index 273
OMS (continued) P
using XSLT with OXML 252
variable names in SAV files 249 page numbering 127
Word format 246 page setup
XML 246, 250 chart size 127
online Help 5 headers and footers 126
opening pane splitter
restore points 2 Data Editor 59
opening files syntax editor 157
controlling default file locations 188 pasting output into other applications 119
data files 7 PDF
dBASE files 7, 9 exporting output 120, 123
Excel files 7 PDF format
Lotus 1-2-3 files 7 exporting output 246
spreadsheet files 7 performance
Stata files 9 caching data 39
SYSTAT files 7 pivot tables
tab-delimited files 7 alignment 137
text data files 10 alternating row colors 135
options background color 137
charts 185 borders 136
currency 184 captions 137
data 182 cell formats 135
descriptive statistics in Data Editor 184 cell properties 137
general 179 cell widths 139
language 181 changing display order 129
output labels 184 changing the look 133
pivot table look 187 continuation text 136
scripts 189 controlling number of rows to display 135
syntax editor 190 controlling table breaks 140
temporary directory 188 creating charts from tables 141
two-digit years 182 default column width adjustment 187
Variable View 184 default look for new tables 187
Viewer 182 deleting group labels 130
ordinal displaying hidden borders 139
measurement level 47, 65 editing 129
outer join 16 exporting as HTML 120
outline fast pivot tables 187
changing levels 117 fonts 137
collapsing 116 footnote properties 135
expanding 116 footnotes 137–139
in Viewer 116 general properties 134
output grid lines 139
alignment 116, 182 grouping rows or columns 130
centering 116, 182 hiding 115
changing output language 131 inserting group labels 130
closing output items 118 inserting rows and columns 131
copying 115 language 131
deleting 115, 116 layers 132
encrypting 127 legacy tables 141
exporting 120 manipulating 129
hiding 115 margins 137
interactive 120 moving rows and columns 129
modifying 149, 150, 152–154 pasting as tables 119
moving 115 pasting into other applications 119
pasting into other applications 119 pivoting 129
saving 127 printing large tables 140
showing 115 printing layers 126
Viewer 115 properties 134
Output Management System (OMS) 243, 252 render tables faster 187
output object types rotating labels 130
in OMS 244 scaling to fit page 134, 136
OXML 252 selecting rows and columns 139
showing and hiding cells 133
Index 275
Savage scores 84 servers
saving adding 41, 239
restore points 2 editing 41, 239
saving charts logging in 41
BMP files 120, 125 names 41, 239
EMF files 120 port numbers 41, 239
EPS files 120, 125 session journal 188
JPEG files 120, 125 Shift Values 79
metafiles 120 showing
PICT files 120 captions 137
PNG files 125 dimension labels 133
PostScript files 125 footnotes 138
TIFF files 125 results 115
saving files rows or columns 133
controlling default file locations 188 titles 133
data files 23 toolbars 193
database file queries 19 sizes
IBM SPSS Statistics data files 23 in outline 117
saving output smoothing function 91
Excel format 120, 122 sorting
HTML 120, 121 pivot table rows 130
HTML format 120 variables 96
PDF format 120, 123 sorting cases 95
PowerPoint format 120, 123 sorting variables 96
text format 120, 124 space-delimited data 10
Word format 120, 122 speed
scale caching data 39
measurement level 47, 65 spelling
scale variables dictionary 182
binning to create categorical variables 72 split-file processing 102
scaling split-model viewer 147
pivot tables 134, 136 splitting tables
scientific notation controlling table breaks 140
suppressing in output 179 spp files
scoring converting to spj files 241
matching dataset fields to model fields 172 spreadsheet files
merging model and transformation XML files 174 reading 9
missing values 172 SPSSTMPDIR environment variable 188
models supported for export and scoring 171 Stata files
scoring functions 173 opening 7, 9
scripts reading 7
adding to menus 193 saving 23
autoscripts 255 string format 47
Basic 259 string variables
creating 255 breaking up long strings in earlier releases 23
default language 189, 255 computing new string variables 78
editing 255 entering data 54
languages 255 missing values 49
Python 257 recoding into consecutive integers 82
running 255 style output 150
running with toolbar buttons 194 subsets of cases
startup scripts 261 random sample 104
search and replace selecting 103, 104
Viewer documents 118 subtitles
seasonal difference function 91 charts 169
select cases 103 subtypes
selecting cases vs. labels 245
based on selection criteria 104 syntax
date range 104 accessing Command Syntax Reference 5
random sample 104 journal file 164, 165
range of cases 104 output log 156
time range 104 pasting 156
selection methods Production jobs rules 235
selecting rows and columns in pivot tables 139 running 163
Index 277
variable names (continued) wrapping
wrapping long variable names in output 46 controlling column width for wrapped text 134
variable pairs variable and value labels 49
creating 105
variable sets
defining 176
X
using 176 XML
Variable View OXML output from OMS 252
customizing 52, 53, 184 routing output to XML 246
variables saving output as XML 243
defining 46 table structure in OXML 250
defining variable sets 176 XSLT
definition information 175 using with OXML 252
display order in dialog boxes 179
finding in Data Editor 57
inserting new variables 56 Y
moving 57
years
recoding 80–82
two-digit values 182
renaming for merged data files 98
restructuring into cases 105
sorting 96 Z
vertical label text 130
Viewer z scores
changing outline font 117 in Rank Cases 84
changing outline levels 117
changing outline sizes 117
collapsing outline 116
deleting output 116
display options 182
displaying data values 184
displaying value labels 184
displaying variable labels 184
displaying variable names 184
excluding output types with OMS 248
expanding outline 116
find and replace information 118
hiding results 115
moving output 115
outline 116
outline pane 115
results pane 115
saving document 127
search and replace information 118
space between output items 127
virtual active file 39
Visual Bander 72
W
weighted data
and restructured data files 113
weighting cases
fractional weights in Crosstabs 104
wide tables
pasting into Microsoft Word 119
window splitter
Data Editor 59
syntax editor 157
windows
active window 1
designated window 1
Word format
exporting output 120, 122, 246
wide tables 120