Release Notes - IBM SPSS Modeler 17.0

Content

For a list of new features in the latest SPSS Modeler release, see the topic “New Features in IBM SPSS Modeler 17.0” in the online help or Knowledge Center.

System requirements and installation

For information regarding requirements and installation, see: http://www.ibm.com/software/analytics/spss/products/modeler/requirements.html.

Unable to start the installer from the automatically started launch pad.

If auto start is turned on, the launch pad will start automatically when the DVD is inserted into a Windows machine. In some cases users will not be able to start the installer by clicking the launch buttons on the automatically started launch pad screen. If this happens close the running launch pad, browse to the DVD content, right click on Launchpad64.exe and select "Run as administrator". After the launch pad has started click on the desired launch buttons on the launch pad screen and the installer will start as normal.

Windows - run as administrator

If you are installing on a Windows Server 2008, Windows Server 2012, Windows Vista, Windows 7, or Windows 8 operating system, you must use "Run as Administrator" by first right-clicking on the executable.

IBM Cognos TM1

IBM Cognos TM1 10.2 Fix Pack 1, or later, is required before Modeler can import and export Cognos TM1 data.

Ubuntu 14 on Linux

On Linux, there can be issues with installing Modeler Server on Ubuntu 14. For an explanation of the workaround please see the following: https://flexeracommunity.force.com/customer/articles/en_US/PROBLEM/Malformed-uxxxx-Encoding-Error-Generated-when-Launching-Installer

Single sign-on for data sources

You can connect to databases from IBM SPSS Modeler using single sign-on. If you want to create a database connection using single sign-on, you must first use your ODBC management software to properly configure a data source and single sign-on token. Then when connecting to a database in IBM SPSS Modeler, IBM SPSS Modeler will use that same single sign-on token and the user will not be prompted to log on to the data source.

However, if the data source was not configured properly for single sign-on, IBM SPSS Modeler will prompt the user to log on to the data source. The user will still be able to access the data source after providing valid credentials.

For complete details about configuring ODBC data sources on your system with single sign-on enabled, see your database vendor documentation. Following is an example of the general steps that may be involved:

1. Configure your database so it can support Kerberos single sign-on.
2. On the IBM SPSS Modeler Server machine, create an ODBC data source and test it. The DSN connection should not require a user ID and password.
3. Connect to IBM SPSS Modeler Server using single sign-on and begin using the ODBC data source created and validate in step 2.

Single sign-on Kerberos authentication issue

If you plan to use single sign-on for SPSS Modeler on either Windows 7 SP1 or Windows Server 2008 R2 SP1, you may be affected by a known issue. As an example, you may see an error message that resembles the following: STATUS_TRUSTED_RELATIONSHIP_FAILURE

If you are affected, see the hotfix available at http://support.microsoft.com/kb/2526946. for an explanation and solution.

Known problems

At time of publication, the following issues were known:

• Java heap space error in Modeler Server

For some tasks, when processing a large number of records, it is possible that a Java heap space error can be displayed.

If this happens, you can configure the JVM setting to increase the memory. as follows:

1. Close the stream that generated the error.
2. In the <Modeler Server installation path>\config folder, open the jvm.cfg
3. Configure the setting, the default is 256; for example: options, "-Xmx1024m"
4. Save the configuration and reopen the stream.

• datetime_now function returns null value against Teradata

When using the DataDirect Teradata driver, the SQL_COLUMN_TYPE may return a null value. The alternative is to use the native Teradata driver.

SPSS Modeler Entity Analytics

• DB2 password restrictions

When connecting to a DB2 instance, the characters that you cannot use, either on their own or in any combination, are as follows:

`

^

,

;

'

"

(

)

\

&

#

<

>

=

|

$

{

}

In addition, you also cannot use a blank space.

• AIX and Solaris

Entity Analytics does not support AIX 6.1 (or earlier), or Solaris.

• Windows 32-Bit

Entity Analytics on Win32 is not supported.

• Membership of administration groups

If you intend to run administrative tasks, for example to create or delete a repository, you will need to run as administrator. For more information, see: http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0007134.html

Windows - Add your account to the DB2ADMNS group.

UNIX - Add your account to the db2iadm1 group; for example: usermod -G db2iadm1 user.

In addition you have to log out and log back in to your account, or reboot, before these changes take effect.

• Non-Latin character data not supported

Data in non-Latin characters is not supported for Entity Analytics in this release. Where the data consists of a mixture of records in Latin (i.e., Western European) and non-Latin character sets, only the entities for the Latin data will be resolved.

• Incorrect number of fields detected when running Streaming EA node

You may encounter an error of the form "Incorrect number of fields detected in the server
data model" when running the Streaming EA node. This can happen if you have edited the
repository configuration since creating the Streaming EA node. Editing the configuration in these
circumstances can have the effect of changing the number and names of the fields output from the
node. To resolve the issue, open the Streaming EA node and click the Refresh button. Doing so
causes the number and names of the output fields to be recalculated.

• Repositories not removed when Entity Analytics is uninstalled

Before uninstalling Entity Analytics, note that any repositories that were created are not removed when Entity Analytics is uninstalled. These repositories will be available if Entity Analytics is later reinstalled.

To delete a repository, follow the instructions in the "Entity Analytics tasks" section of the Entity Analytics User Guide. Use the procedure "Deleting an entity repository" or "Deleting a repository when unable to connect to it" as appropriate.

Note that the delete_repository.bat or delete_repository.sh scripts are located in the "<modeler_install_dir>/ext/bin/pasw.entityanalytics" directory.

Also note that DB2 is not uninstalled when you uninstall EA. For details on how to uninstall DB2 see: http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/c0059726.html

• Upgrading an Entity Analytics repository created in Modeler 16 to Modeler 17

After you install Modeler 17 Premium, but before you first use Entity Analytics, take the following actions to complete the upgrade:

• Backup the DB2 database that includes the EA repository that is to be upgraded, and upgrade the repository
• Move the g2_config.xml instance from the Modeler 16 version of to the Modeler 17 version.
• Move the folder for each repository that is to be upgraded from the Modeler 16 location to the Modeler 17 location.
• Modify the g2.ini file.

These steps are explained in the following topics.

NOTE: After you upgrade your DB2 database to be usable in Modeler 17, it will no longer be usable in Modeler 16

Backup the DB2 database that includes the EA repository, and upgrade the repository
1. Open the IBM DB2 Command Window – as an Administrator
2. Backup your existing databases
Type the following commands, substituting your database name for {DB}, your user name for {USER}, and your password for {PASSWORD}. In addition, replace {C:\} with the path where you want the backup to be located.
1. db2 CONNECT TO {DB} USER {USER} USING {PASSWORD}
2. db2 QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS
3. db2 CONNECT RESET
4. db2 BACKUP DATABASE {DB} USER {USER} USING {PASSWORD} TO {C:\} WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 COMPRESS WITHOUT PROMPTING
5. db2 CONNECT TO {DB} USER {USER} USING {PASSWORD}
6. db2 UNQUIESCE DATABASE
7. db2 CONNECT RESET
3. Upgrade the Entity Analytics Repository
1. db2 connect to {DB} user {USER} using {PASSWORD}
2. cd C:/Program Files/ibm/SPSS/Modeler/17/ext/bin/pasw.entityanalytics/templates
3. db2 -tvf Upgrade16to17.sql
4. Exit the command window
1. Type exit




Moving the g2_config.xml instance for the repository being upgraded
The file g2_config.xml is used by the EA components to locate the EA web service for a named repository.

1. Edit the Modeler 16 version of g2_config.xml. The default locations are:


Windows: C:\ProgramData\IBM\SPSS\Modeler\16\EA\g2_config.xml

UNIX: <modeler16-install-directory>/ext/bin/pasw.entityanalytics/EA/g2_config.xml


2. Find and remove the instance for the repository being upgraded

For example, if upgrading a repository called AAA, remove the following:

<instance external="false" g2host="localhost" g2port="1321" host="9.30.214.79"


name="AAA"
path="C:\ProgramData\IBM\SPSS\Modeler\16\EA\repositories\AAA\g2.ini"
port="1320"/>

3. Edit the Modeler 17 version of g2_config.xml. The default locations are:

Windows: C:\ProgramData\IBM\SPSS\Modeler\17\EA\g2_config.xml

UNIX: <modeler17-install-directory>/ext/bin/pasw.entityanalytics/EA/g2_config.xml


4. Add the instance removed in Step 2 and update its path by changing 16 to 17

For example:

<g2instances>


.
.
<instance external="false" g2host="localhost" g2port="1321" host="9.30.214.79"
name="AAA"
path="C:\ProgramData\IBM\SPSS\Modeler\17\EA\repositories\AAA\g2.ini"
port="1320"/></g2instances></config>


Move the folder for the repository from Modeler 16 location to Modeler 17 location

For example: If upgrading a repository called AAA, move the folder named AAA and all of its contents. The default locations are:

Windows:

From: C:\ProgramData\IBM\SPSS\Modeler\16\EA\repositories
To: C:\ProgramData\IBM\SPSS\Modeler\17\EA\repositories

UNIX:
From: <modeler16-install-directory>/ext/bin/pasw.entityanalytics/EA/repositories
To: <modeler17-install-directory>/ext/bin/pasw.entityanalytics/EA/repositories


Modifying g2.ini

For example, if upgrading a repository called AAA, the default locations of the files to edit would be:

Windows: C:\ProgramData\IBM\SPSS\Modeler\17\EA\repositories\AAA\g2.ini

UNIX: <modeler17-install-directory>/ext/bin/pasw.entityanalytics/EA/repositories/AAA/g2.ini

1. Change paths from 16 to 17 in the SUPPORTPATH entry found in the [ER] section

2. Move the SUPPORTPATH entry from the [GNR] section to the [PIPELINE] section

3. Remove the entire [GNR] section

4. Change paths from 16 to 17 in the SUPPORTPATH entry that is now in the [PIPELINE] section

5. Append the following XLIT_RULEs to the SUPPORTPATH entry now in the [PIPELINE] section. For example:


SUPPORTPATH=C:\Program Files\IBM\SPSS\Modeler\17\ext\bin\pasw.entityanalytics\data
XLIT_RULE1=arabicTransRule.ibm
XLIT_RULE2=chineseTransRule.ibm
XLIT_RULE3=cyrillicTransRule.ibm
XLIT_RULE4=greekTransRule.ibm
XLIT_RULE5=hindiTransRule.ibm
XLIT_RULE6=japaneseTransRule.ibm
XLIT_RULE7=koreanTransRule.ibm
XLIT_RULE8=chineseONTransRule.ibm
XLIT_RULE9=cyrillicONTransRule.ibm
XLIT_RULE10=hindiONTransRule.ibm
XLIT_RULE11=japaneseONTransRule.ibm
XLIT_RULE12=koreanONTransRule.ibm
XLIT_RULE13=anyTransRule.ibm

Database import and export

• SQL Server support with the Data Access Pack driver.

The ODBC configuration for SQL Server must have the "Enable Quoted Identifiers" ODBC connection attribute set to “Yes” (the default for this driver is "No"). On UNIX this attribute is configured in the system information file (odbc.ini) using the "QuotedId" option.

• In Database Caching with IBM DB2.

When attempting to cache a node in a stream which reads data from a DB2 database, you may see the error message “A default table space could not be found with a pagesize of at least 4096 that authorization ID TEST is authorized to use”. To configure DB2 to enable in-database caching to work properly in SPSS Modeler, the database administrator should create a "user temporary" tablespace and grant access to this tablespace to the relevant DB2 accounts. We recommend using a pagesize of 32768 in the new tablespace, as this will increase the limit on the number of fields that can be successfully cached.

• Database errors with IBM DB2 for z/OS.

When running streams against DB2 for z/OS, you may experience database errors if the timeout for idle database connections is enabled and set too low. In DB2 for z/OS version 8, the default has changed from no timeout to 2 minutes. The solution is to increase the value of the DB2 system parameter IDLE THREAD TIMEOUT (IDTHTOIN), or reset the value to 0.

• Scoring some models with confidences enabled using generated SQL returns a database error message on DB2 z/OS.

Scoring a subset of algorithms, with confidences enabled, using generated SQL can return an error on execution. The issue is specific to DB2 for z/OS; to fix this, use the Modeler Server Scoring Adapter for DB2 on z/OS.

• Database bulk loaders.

In order to use the bulk loading feature of the Database export node, you need to install Python on the same machine as SPSS Modeler (or if using SPSS Modeler Server, on the same machine as the server). The "python_exe_path" parameter must be set in the options.cfg file. You can install Python from the SPSS Modeler Client, SPSS Modeler Server or SPSS Modeler Solution Publisher product DVDs.

• Some aggregation results can differ between SQL pushback and native modes with Oracle.

When running a stream containing an Aggregate node, the values returned for 1st and 3rd Quartiles when pushing back SQL to an Oracle database may differ from those returned in native mode.

Modeling nodes

• Record ID field.

Passing a non-numeric Record ID field into a modeling algorithm may cause a stream to execute slowly. The Record ID field is not a requirement for modeling, so we recommend filtering out the field.

• Logistic Regression.

Binomial Logistic Regression does not allow strings longer than 8 characters. You can avoid this problem by encoding strings, for example by using the Anonymize node, before passing them to the algorithm.

If temporary disk space is low, Binomial Logistic Regression can fail to build, and reports an error. When building from a large data set (10GB or more), the same amount of free disk space is needed. You can use the environment variable SPSSTMPDIR to set the location of the temporary directory.

• Cox regression.

On scoring a Cox regression model, an error is reported if empty strings in categorical variables are used as input to model building. Avoid using empty strings as input.

Model nuggets

• Settings information.

For some models, Settings information may not be displayed in the information sidebar of the model nugget if split fields are used. Settings information can be accessed from the modeling node as follows. For auto modeling nodes, open the modeling node and choose Expert tab > click the Model parameters column > Specify > Expert tab of Algorithm settings dialog box. For single modeling nodes, open the modeling node and choose Build Options tab > Ensembles.

Excel export node

• Memory required increases with number of rows when exporting to Excel 2003.

Exporting a large number of records (tens of thousands) to an Excel 2003 (.xls) file can fail with the message "Insufficient memory for JVM - please increase in jvm.cfg". However, increasing the value of the Java heap size may not cure the problem. Try exporting fewer records at a time. The problem does not occur when exporting to Excel 2007/2010 (.xlsx) format.

SPSS Modeler Server on UNIX

• Insufficient virtual memory in multithreaded AIX environments.

In a multithreaded AIX environment, it is possible for workloads that formerly completed successfully to fail with insufficient memory owing to a change to the startup scripts for SPSS Modeler Server, SPSS Modeler Solution Publisher and SPSS Modeler Solution Publisher Runtime Library. To avoid this problem, remove the following line from the startup script:

MALLOCOPTIONS=multiheap

• Profile command script error in Solaris environments.

In some Solaris environments you may see the following error when attempting to create or manage profile command scripts:

unknown operator "=="

If this happens, the workaround is to edit the file: scripts/profiles/jython.sh file and change the first line to replace: /bin/sh with: /usr/bin/bash (or an equivalent reference to the bash shell).

Integration with IBM SPSS Collaboration and Deployment Services

• Storing SPSS Modeler streams in SPSS Collaboration and Deployment Services.

No unlock checkbox is available when storing streams in the Collaboration and Deployment Services repository. Unlock is the default when storing streams. To lock or unlock an object, choose Tools->Repository->Explore, navigate to the object, and right-click on its name to display the context menu.

• Incomplete output for Gains graph from Evaluation node.

In Deployment Manager, on running a job containing a stream with an Evaluation node set to produce a Gains graph, the graph output may be incomplete if the system is running under Oracle Weblogic 11g using the Oracle JRockit JRE. To avoid this problem, use the IBM JRE.

Integration with IBM SPSS Statistics

• Generating non-English output.

When generating output in languages other than English, it is advisable to specify the language in the Syntax.

• The 'Launch application' option of a Statistics Export node does not open the data set when working in distributed mode.

When running Modeler and Statistics together in Server mode, writing the data out and launching a Statistics session does not automatically open a Statistics client showing the data set read into the active data set. The workaround is to manually open the data file in Statistics client once it is launched.

Multi-byte data

• Inserting multibyte data into Teradata from SPSS Modeler Server.

To insert multibyte data into a Teradata database from SPSS Modeler Server, use the following configuration:

1. Run the server in Unicode.

2. Set the Teradata user default character set to UNICODE using tdadmin.

3. Configure CharacterSet=UTF8 (UNIX DSN), or set the Session Character Set to UTF-8 (Windows DSN).

4. Ensure that there are only ASCII characters in the column names.

• String Collation.

In this release, string sorting and comparison use the ICU 4.8.1 collation service for the system locale. Japanese collation does not distinguish half-width from full-width Katakana.

Accessibility

• Graphs.

The screen reader is not able to read graphs, so these are not accessible to visually-impaired users.

TM1 data import

Not all data is imported from TM1 to Modeler if the dimension before the measure dimension only has one element.

Modeler Administration Console

If you use the Modeler Administration Console with Modeler Server in Windows, you need to add a "log" directory under the Modeler Server installation path. The default installation path is: C:\Program Files\IBM\SPSS\ModelerServer\17.

SPSS Modeler Text Analytics

• Cancelling an extraction can take a long time when working with very large data sets.

Multiple Interactive Workbench sessions can cause sluggish behavior. Text Analytics and Modeler share a common Java run-time engine when an interactive workbench session is launched. Depending on the number of Interactive Workbench sessions you invoke during a Modeler session - even if opening and closing the same session - system memory may cause the application to become sluggish. This effect may be especially pronounced if you are working with large data or have a machine with less than the recommended RAM setting of 4GB. If you notice your machine is slow to respond, it is recommended that you save all your work, shut down Modeler and re-launch the application. Running Text Analytics on a machine with less than the recommended memory - particularly when working with large data sets or for prolonged periods of time - may cause Java to run out of memory and shut down. It is strongly suggested you upgrade to the recommended memory setting or larger (or use Text Analytics Server) if you work with large data.

• Scoring on rules is different in Text Analytics depending on whether you load a text analysis package (TAP) from Text Analytics directly or whether you load a TAP from Text Analytics for Surveys

Use TAPs made within Text Analytics as the ones made in Text Analytics for Surveys may be created using a different version of the linguistic resources.

• Linux on x64 - openMP support requires the customer to install a separate package.

Linux Red Hat x64 support.
For Red Hat Linux, openMP support requires the package "libgomp-4.4.4-13.el5", which is available from the RedHat website: https://rhn.redhat.com/network/software/search.pxt

Linux SuSe x64 support.

For SuSe11, openMP support requires the package "libgomp43 4.3.3_20081022", which is available from the SuSe website: http://www.suse.com/LinuxPackages/packageRouter.jsp?product=server&version=11&service_pack=&architecture=i386&package_name=index_group.

The package is for the GNU compiler collection OpenMP runtime library, and is available from the section titled: "Development/Libraries/Parallel".

• Client memory exhausted after many repeated Interactive Workbench extractions.

Modeler Client can run out of memory after multiple Text Analytics Interactive Workbench sessions have been run without restarting the application. Monitor the memory usage in the status line and, if running low, close and re-open Modeler Client.

• Text Analytics Japanese Adapter - Prerequisite.

The Text Analytics Japanese Adapter installer requires the presence of Modeler Adapter. Please ensure the Modeler Adapter is installed on your machine before you install the Text Analytics Japanese Adapter.

• Sentiment secondary analyzer not working on Windows 32-bit.
  If performing the following tasks, you may receive errors on Windows 32-bit.
  
  1. Generate a concept model directly with the Sentiment secondary analyzer selected.
  2. Connect the newly created Concept model and Preview it.
  3. Build an Interactive Model, with TLA and Sentiment secondary analyzer enabled.
  4. Run a TLA node with Sentiment secondary analyzer enabled.
  
  To resolve, we recommend changing the JVM settings -Xmx320m and -Xms64bit in the file <Modeler_Install_Dir>\config\jvm.cfg.

Related information

Technical Support is available to maintenance customers. Customers may contact Technical Support for assistance in using IBM Corp. products or for installation help for one of the supported hardware environments. To reach Technical Support, see the IBM Corp. web site at http://www.ibm.com/support. We recommend that you check the support site for updates.

© Copyright IBM Corporation 1994, 2015.