Users
Admin Group. When a user connects to the IBM® SPSS® Statistics Administration Console, the server software checks if the user is a member of the administrator group. The administrator group corresponds to a system account group on the machine on which the server software is installed. Any member of the administrator group has adminstrative-level rights to the server software. This means that a member of this group can use the IBM SPSS Statistics Administration Console to configure the server. You can specify any system account group to be the administrator group. However, if the server software cannot find the group, it will revert to the default group, which is the administrator group for the computer on which the server software is installed (for example, the Administrators group on an English Windows system).
Client Data Access. When end users connect to the server software and open a data file, they are able to see the actual data in the file. Always displaying the data in the client application can negatively affect performance and increase network traffic. Therefore, you may choose to prevent the data from displaying in the client application. The client will still display the data dictionary, allowing the end user to check which variables appear in the data. The client data access setting is a global setting for all users and can be overridden by the user profile or group setting. See the topic IBM SPSS Statistics Server User Profiles and Groups for more information.
Sort. When end users connect to the server software and run a sort procedure, the server software uses the specified sort engine. The engine must be installed and configured on the server software computer. For more information about using a third-party sort engine, see Chapter 4 of the IBM SPSS Statistics Server Administrator's Guide.
Umask. You can adjust the umask that is used when users connect to the server software running on a UNIX machine. This three-digit octal number is a global setting for all users and can be overridden by the user profile or group setting. See the topic IBM SPSS Statistics Server User Profiles and Groups for more information. Note that this setting is not available when the server software is running under Windows.
Maximum Threads. You can specify a limit to the number of threads that the server software can use. You may do this to limit the system resources available for multithreaded procedures. The maximum threads setting is a global setting for all users and can be overridden by the user profile or group setting. See the topic IBM SPSS Statistics Server User Profiles and Groups for more information.
Cache Compression. When end users explicitly issue a
CACHE command or run a procedure that creates scratch files automatically, the
server software can compress the scratch (temporary) files using zlib. You should turn cache
compression on if your users typically read large data files. A compressed scratch file reduces the
amount of disk I/O compared to an uncompressed scratch file but requires more processing by the
server software. To minimize the effect of the extra CPU time on job elapsed time, compression and
decompression are performed using separate threads. That means that one or more processors can be
handling these chores while others are executing commands. Because the extra overhead is greater
when writing a file compared to reading it, let your users know that they should use a higher value
for SET CACHE. Doing so will reduce the frequency of writing scratch files and
increase the number of times each scratch file is read. The cache compression setting determines the
default behavior for cache compression. You can also set the compression override setting to allow
users to override this default. The cache compression setting is a global setting for all users and
can be overridden by the user profile or group setting. See the topic IBM SPSS Statistics Server User Profiles and Groups for more information.
Compression Override. You can specify whether end users can override the
cache compression setting with SET ZCOMPRESSION syntax. The compression override
setting is a global setting for all users and can be overridden by the user profile or group
setting. See the topic IBM SPSS Statistics Server User Profiles and Groups for more information.
Maximum JVM Memory. When end users connect to the server software, memory is allocated for the Java virtual machine (JVM) on the server computer. Memory is allocated for each user. You can change the amount of allocated memory by specifying a number in megabytes (MB). You may need to this if users have jobs that require a large amount of memory, for example when exporting very large custom tables. The JVM memory setting is a global setting for all users and can be overridden by the user profile or group setting. See the topic IBM SPSS Statistics Server User Profiles and Groups for more information.
Compiled Transformations. When a syntax job includes transformation
commands, the server software converts the transformations to bytecode when the syntax job is run.
This bytecode is then "interpreted" while running the syntax job. The server software can compile
the transformations to machine code to improve performance when there are many cases in the data and
several transformations in the syntax job. If Compiled Transformations is set
to Yes and a user issues the SET CMPTRANS=YES command, the
server software will:
- Convert the transformations to bytecode as usual.
- Convert the bytecode to C++ code.
- Compile the C++ code to machine code.
- Execute the machine code.
Compiler Path. The full path to the C++ compiler that is used for compiling transformations. You must use MinGW, which is a Windows port of the GNU Compiler Collection (GCC). Be sure to include the executable name in the path specification, for example C:\MinGW\bin\g++.exe.
Restrict Database Access. You can restrict database access to specific database sources. To restrict sources to a specific list of DSNs, set this to Yes and identify the permitted sources with the Permitted Database Sources setting. If this is set to No, end users can access any database that is configured on the server.
Permitted Database Sources. If Restrict Database Access is set to Yes, specify the DSNs to which users have access. Use semicolons to delimit DSNs (for example, Fraud - Analytic;Fraud - Operational).