Professional Documents
Culture Documents
Readme
Readme
0 for Windows
Installation
Instructions for installing SPSS 16 for Windows, including the minimum
hardware and software requirements, are located on the CD-ROM in the
Installation Documents directory.
Information and Limitations
New features. For a list of new features in the latest SPSS for Windows
release, please visit
http://www.spss.com/spss/whats_new.htm
For a list of new features in SPSS, see the What's New in SPSS 16.0?
topic in the online help or the cover letter that was included with your
system.
Saving Stata and SAS files with multi-byte variable names. When saving
data files in Stata or SAS format, SPSS variable names that contain
multi-byte characters (e.g., Japanese or Chinese characters) are
converted to variables names of the general form Vnnn, where nnn is an
integer value. an integer value.
Dimensions Data Sources. When reading Dimensions data sources (Open
Dimensions Data on the File menu or GET DATA /TYPE=OLEDB), non-English
data may not be read correctly. To use non-English Dimensions data
sources in SPSS, save the data in SPSS format in the source application.
Dimensions
Dimensions
Dimensions
use a DMOM
There are known problems using SAS files saved in SPSS with the SAS
Viewer and SAS JMP 5 - these applications have a different mechanism for
reading files which isnt the same or as stable as the one used in SAS.
* Filename limitations for data files saved in SAS formats. The
following excerpt is from the SAS JMP 5 README: "Double-byte characters
should not be used in filenames when writing SAS files [from within
JMP]. This is a limitation of the SAS local data provider that is to be
corrected in version 9 of SAS". This holds true for SAS files saved in
SPSS.
* SAS formats and string length limitations. If you use SPSS to open SAS
data file types, you may not be able to get string values longer than
255 bytes. If your data contain values longer than 255 bytes, SPSS will
get only the first 255 bytes.
* Text Wizard data caching. The Text Wizard provides an optional setting
that automatically caches the data that it imports. By default caching
is on and the wizard creates a copy of the entire dataset. If you turn
caching off, SPSS does not have access to the entire data file -- the
original data source is re-read as needed -- and the total number of
cases is unknown. When the total number of cases is unknown, Go to Case,
Copy, and Paste do not work as expected in the Data Editor. You can
correct the problem by using the File menu to Cache Data.
* Using syntax to read data with ODBC. If you use syntax to read data
from a database with ODBC, we recommend caching your data. Caching your
data ensures that the data are in the same order each time that SPSS
needs to make a data pass. It also ensures that your analysis isn't
affected by updates to the database that occur while the syntax is being
processed. To cache the data, add a CACHE command to the syntax
immediately after your GET DATA command.
* SQL Server ODBC Driver. If you are using the SPSS OEM 5.2 SQL Server
Wire Protocol, you should modify the driver setup to ensure proper
handling of quoted field and table names in SQL statements generated by
the Database Wizard and Export to Database Wizard or specified in the
GET DATA and SAVE TRANSLATE commands. In the Advanced tab of the driver
setup, select (check) "Enable Quoted Identifiers". In local analysis
mode, you can modify the driver setup using the Windows ODBC Data Source
Administrator, which you can access from within SPSS via the "Add ODBC
data source" button in the Database Wizard or Export to Database Wizard.
For database access in distributed analysis mode (using SPSS Server),
contact your database administrator.
Procedures
* Linear Mixed Models. In the Random dialog box if the Include Intercept
checkbox is checked but no factors or covariates are specified as random
effects, the Next button will not become available. Therefore, in order
to generate a RANDOM subcommand with no effect(s) other than an
intercept, that subcommand must be the last one specified in the Random
dialog box. If there are multiple subcommands specified, the last of
which contains only the intercept, that specification will not be
generated unless Continue is clicked while remaining at that last
specification, unless that specification also includes a subject
combination
Other
* Customers who have licensed the PES Adaptor and are upgrading from
SPSS 14 may have problems storing and retrieving Complex Samples plan
files. If problems occur you should redefine MIME-type mappings for
Complex Samples plan files. Open the Predictive Enterprise Administrator
(http://<pes server>/config/mimeManager) and delete any existing
definitions for .csplan and .csaplan files. Then redefine the mappings
for the two file types using a single dash (-) instead of a double dash
(--) in the MIME type definition.
* Temporary Folder Location
The temporary folder location specified on the File Locations tab of the
Options dialog does not change the location of temporary data files
created by SPSS in SPSS 16.0. The location of temporary data files can
be controlled by an environment variable setting specified by the
operating system.
On Windows, SPSS checks the following environment variables in order to
determine where to put temporary files:
SPSSTMPDIR
SPSSTEMPDIR
TMPDIR
TEMP
If none of these is defined, SPSS uses c:
* Syntax files can be saved in Unicode or in the local code page (local
encoding). In most cases, when you open a file in the syntax window,
SPSS automatically determines the correct encoding. Sometimes it will
be wrong. If you see three funny characters at the start of the file,
close it and reopen specifying Unicode. If the contents look scrambled,
try a different encoding setting. If it still looks wrong, your SPSS
locale may be different from the way the file was saved. Use an
appropriate SET LOCALE command to resolve this.
* Double byte characters aren't properly displayed in SPSS-generated PDF
files.
* If you use the Browse button in the Menu Editor to select a syntax or
script file for a custom menu item, the value displayed in the Filename
field will be enclosed in quotes. You should remove these quotes,
otherwise the file will not be found when you use the custom menu item.
For syntax files, this problem manifests as an alert of the general form
"Cannot start ['filename']." For script files, you will see this message
in the Viewer window: "No language is configured to execute this script.
Cannot run the script."
* Citrix and Sax BASIC error. When you run SPSS as a published Citrix
application, you may encounter a Sax BASIC error when you attempt to run
a procedure. The problem can be corrected by editing the location of the
global procedures file on the SPSS Options Scripts tab.
Resources
SPSS for Windows Product Information - <http://www.spss.com/spss/>
SPSS Technical Support - <http://www.spss.com/tech/>
Legal Notices
Portions of the Software are licensed under the Apache License, Version
2.0 (the ""License""); you may not use applicable files except in
compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Keyoti (c) Copyright 2002, all rights reserved
Copyright (C) 2001 by First Peer, Inc. All rights reserved.
Copyright (C) 2001 by Eric Kidd. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
This product includes ACME software: Copyright 2000 by Jef Poskanzer
<jef@mail.acme.com>. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
Copyright (c) 1999, 2006 Tanuki Software, Inc.
Permission is hereby granted, free of charge, to any person
obtaining a copy of the Java Service Wrapper and associated
documentation files (the ""Software""), to deal in the Software
without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sub-license,
and/or sell copies of the Software, and to permit persons to
whom the Software is furnished to do so, subject to the
following conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED ""AS IS"", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
Portions of the Software have been derived from source code
developed by Silver Egg Technology under the following license:
BEGIN Silver Egg Techology License ----------------------------------Copyright (c) 2001 Silver Egg Technology
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the ""Software""), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sub-license, and/or
sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following
conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED ""AS IS"", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*