Usage Note 38058: How to enable the Score Code Export node in SAS® Enterprise Miner(tm) 6.1_M2 and 6.1_M3
If SAS® Scoring Accelerator for Teradata is licensed, then SAS Enterprise Miner automatically displays the Score Code Export node on the list of tools.
Starting in SAS Enterprise Miner 6.1_M2, the Score Code Export node is now available in SAS Enterprise Miner even without a SAS Scoring Accelerator for Teradata license. However, the node does not appear on the list of tools automatically. Choose one of these two options to display the node on the list of tools.
The two options below must be applied if you are running SAS Enterprise Miner 6.1_M2 or SAS Enterprise Miner 6.1_M3. To find out whether you are using this version, from within the SAS Enterprise Miner Client, go to Help ► About. The About screen displays the exact version that is installed. For another way to determine which version of SAS and SAS Enterprise Miner you are running, see this SAS Note: 35968 "Using the ViewRegistry Report and other methods to determine the SAS® 9.2 and SAS® 9.3 software releases and hot fixes that are installed".
- Option Number One:
Add this statement to your SAS Enterprise Miner Project Start Code.
%let EM_SCOREEXPORT=Y;
Note: This line can also be added to your AUTOEXEC.SAS file
or your APPSERVER_AUTOEXEC.SAS file. Adding the line to an
AUTOEXEC.SAS file makes the statement available without having to edit the
Project Start Code on a project by project basis.
- Option Number Two:
Edit the CODEEXPORT.XML file. This file is found in your
Configuration directory. A default example location is:
SAS\Config\Lev1\AnalyticsPlatform\apps\EnterpriseMiner\conf\components.
You can either remove the required section so that it looks like this:
Or, you can comment out the "Required" section like this:
In order for the change to have effect, after editing the file, restart the SAS®
Analytics Platform server. Then, restart your SAS Enterprise Miner client.
Operating System and Release Information
SAS System | SAS Enterprise Miner | Windows 7 Professional x64 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Windows 7 Professional 32 bit | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Windows 7 Home Premium x64 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Microsoft® Windows® for x64 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Microsoft Windows XP 64-bit Edition | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Windows 7 Home Premium 32 bit | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Windows 7 Enterprise x64 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Windows 7 Enterprise 32 bit | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Microsoft Windows XP Professional | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Microsoft Windows Server 2008 for x64 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Microsoft Windows Server 2008 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Microsoft Windows Server 2003 for x64 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Solaris for x64 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Linux for x64 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Linux | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
HP-UX IPF | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
64-bit Enabled Solaris | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
64-bit Enabled HP-UX | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
64-bit Enabled AIX | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Windows 7 Ultimate x64 | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
Windows 7 Ultimate 32 bit | 6.1_M2 | 7.1 | 9.2 TS2M2 | 9.3 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Date Modified: | 2013-01-18 09:03:52 |
Date Created: | 2009-12-07 11:35:50 |