SPSS 27 - 1 Win Sys Req
SPSS 27 - 1 Win Sys Req
SPSS 27 - 1 Win Sys Req
Product
IBM SPSS Statistics 27.0.1.0
IBM SPSS Statistics 27.0.1.0
Detailed System Requirements
Operating Systems
The Operating sysytems section specifies the operating systems that IBM SPSS Component support
Statistics 27.0.1.0 supports, organized by operating system familiy.
Full
Operating system families
Partial
Windows
None
Windows
Summary
Operating system OperatingHardware Bitness Product Components Notes?
system minimum
minimum
Windows Notes
1. If Statistics Desktop or Statistics Developer is installed on a supported Windows Server operating system, it
must use a Concurrent License.
2. If Statistics Desktop or Statistics Developer is installed on a supported Windows Server operating system, it
must use a Concurrent License.
Hardware
Windows
Other Desktop Minimum free disk space: Linux: 1.5 gigabyte (GB) for installation. • Windows
Hardware • IBM SPSS Because the installer extracts files before installing, the same Server 2012 R2
Statistics Client amount of temporary disk space is also needed for the installer. If Datacenter Edition
you do not have enough space in /tmp or the installing userâ##s x86-64
Server home directory, use the IATEMPDIR environment variable to
• IBM SPSS specify a different temporary location for the extracted installer • Windows
Statistics files. You can remove this folder after installation. Additional free Server 2012 R2
Server disk space is required to run the program (for temporary files). Essentials Edition
The amount of space needed for temporary files depends on x86-64
the number of users, the expected size of the .sav file, and the
procedure. You can use the following formula to estimate the • Windows Server
space needed: <number of users> * <.sav file size> * <factor 2012 R2 Standard
for procedures>, where <factor for procedures> can range from Edition x86-64
1 to 2.5. For example, for procedures like K-Means Cluster
Analysis (QUICK CLUSTER), Classification Tree (TREE), and
• Windows Server
2016 Datacenter
Two-Step Cluster Analysis (TWOSTEP CLUSTER), the <factor
Edition x86-64
for procedures> is closer to 1 than 2.5. If sorting is involved, it is
2.5. So, if you have four users, the expected .sav file size is 100 • Windows Server
MB, and sorting is involved, you should allow 1 GB (4 Ã# 100 MB 2016 Essentials
Ã# 2.5) of storage for temporary files. Edition x86-64
• Windows Server
2016 Standard
Edition x86-64
• Windows Server
2019 Datacenter
Edition x86-64
• Windows Server
2019 Essentials
Edition x86-64
• Windows Server
2019 Standard
Edition x86-64
Glossary
Bitness Compatibility of the product with the bit version support that is provided by an
operating system. Different parts of a product might run on the same operating
system but support different application bitness. For example, one part of the
product might run only in 32-bit mode, whereas another might support 64-bit
tolerate mode.
31: The product or part of the product runs as a 31-bit application in a 31-bit
operating environment.
32: The product or part of the product runs as a 32-bit application in a 32-bit
operating environment.
64-tolerate: The product or part of the product runs as a 32-bit application in a
64-bit operating environment.
64-exploit: The product or part of the product runs natively as a 64-bit application
in a 64-bit operating environment.
Co-installed Additional products that are included in the product package and installed when
the product is installed.
Deployment unit Deployment Structure identifies pieces of a product that can be independently
deployed onto one or more machines in a distributed infrastructure.
• The top level of the deployment structure consists of one or more deployment
units. There are four possible deployment units that a product might support:
Desktop, Server, Agent or client, Mobile.
Desktop deployment unit: Part of the deployment structure intended for use
by a single user, typically installed on the user desktops. Examples of desktop
deployment units include development tools, administrative tools, stand-alone
business applications.
Server deployment unit: Part of the deployment structure that can provide
services to multiple clients, providing the server in a client-server architecture.
Examples of server deployment units include application servers, management
servers, database servers and server-based business applications.
Agent or client deployment unit: Part of the deployment structure that allows
remote connection between software. Examples of agent of client deployment
units include agents in management system that are installed in the same tier
as the managed resources, a remote application, or database clients that are
installed with the software accessing the remote services.
Mobile deployment unit: Part of the deployment structure intended for use by
a single user, typically installed on a mobile device. An example of a mobile
deployment unit is a mobile application.
Hypervisor A virtual machine in which a product can run on a guest operating system.
Limited operating By default, the supported guest operating systems for a product and a hypervisor
system support are the operating systems that are supported by both the product and the
hypervisor. If a product restricts support to a subset of these operating systems,
this restriction will be indicated by specifying that there is Limited Operating
System Support.
Operating system The minimum operating system maintenance level that is required to run on the
minimum product.
Prerequisite The minimum maintenance level that is required for the prerequisite to work with
minimum the product.
Product minimum The minimum maintenance level that is required for the product to run on the
operating system, on an hypervisor, or work with a prerequisite product or
supported software.
Supported software The minimum maintenance level that is required for the supported software to
minimum work with the product.
Long Term Support A Long Term Support Release is a recommended product level for which support,
Release including defect and security updates, will be provided over a specified period of
time.
Continuous Delivery A Continuous Delivery Product delivers new function to clients more frequently.
Product
Continuous Delivery A Continuous Delivery Product delivers new function to clients more frequently.
Product - Long Term Since frequent releases may not be suitable for all client environments, Long
Support Release Term Support Releases provide a package that will be supported for a longer
period of time.
Disclaimers
This report is subject to the Terms of Use (https://www.ibm.com/legal/us/en/) and the following
disclaimers:
The information contained in this report is provided for informational purposes only. While efforts were made to
verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without
warranty of any kind, express or implied, including but not limited to the implied warranties of merchantability,
non-infringement, and fitness for a particular purpose. In addition, this information is based on IBM’s current
product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for
any direct, indirect, incidental, consequential, special or other damages arising out of the use of, or otherwise
related to, this report or any other materials. Nothing contained in this publication is intended to, nor shall have
the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the
terms and conditions of the applicable license agreement governing the use of IBM software.
References in this report to IBM products, programs, or services do not imply that they will be available in all
countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may
change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended
to be a commitment to future product or feature availability in any way. The underlying database used to support
these reports is refreshed on a weekly basis. Discrepancies found between reports generated using this web tool
and other IBM documentation sources may or may not be attributed to different publish and refresh cycles for
this tool and other sources. Nothing contained in this report is intended to, nor shall have the effect of, stating
or implying that any activities undertaken by you will result in any specific sales, revenue growth, savings or
other results. You assume sole responsibility for any results you obtain or decisions you make as a result of this
report.
Notwithstanding the Terms of Use (https://www.ibm.com/legal/us/en/), users of this site are permitted to copy
and save the reports generated from this tool for such users own internal business purpose. No other use shall
be permitted.