Providing software solutions since 1976


SAS Data Integration Studio Release 3.4

Hot Fix Downloads

 
34DATABLDR01 was replaced by 34DATABLDR10

34DATABLDR02 was replaced by 34DATABLDR10

34DATABLDR03 was replaced by 34DATABLDR10

34DATABLDR04 was replaced by 34DATABLDR10

34DATABLDR05 was replaced by 34DATABLDR10

34DATABLDR07 was replaced by 34DATABLDR10

34DATABLDR08 was replaced by 34DATABLDR10

34DATABLDR09 was replaced by 34DATABLDR10

34DATABLDR10
Issue(s) Addressed :Introduced:
SN-018287Macro variable names defined in a generated transformation revert backto default when job is deployed34DATABLDR01
SN-018280ALERT - Extract and SQL Join transformations might generate invalid code when column labels contain single or double quotes34DATABLDR01
SN-018285ALERT - Duplicate column names across lookup tables might result in incorrect lookup results34DATABLDR01
SN-018282ALERT - The Update SAS ETL/Data Integration Studio Prototypes tool incorrectly generates "Objects are still checked out..." dialog34DATABLDR01
SN-018275ALERT - Code might be generated in incorrect order, resulting in errors during program execution34DATABLDR01
SN-018284ALERT - New libraries and tables get created when existing objects should have been referenced during a Paste or Import process34DATABLDR01
SN-018526ALERT - Lookup transformation code fails with ERROR: The name "columnname"n is not a valid SAS name34DATABLDR02
SN-018531Solutions Repository - ERROR: Failed to create metric table34DATABLDR02
SN-018942SASŪ Data Integration Studio SAP jobs can be corrupted by the Export/Import or Copy/Paste operations34DATABLDR03
SN-018873Source-to-target mappings can be corrupted in the new SQL Jointransformation34DATABLDR03
SN-018858ALERT - Batch execution problems result when the Lookup transformation generates code with line lengths greater than 256 characters34DATABLDR03
SN-018874The "Update SAS Data Integration Studio Metadata" tool in SASŪ Management Console does not automatically register all occurrences of custom trees on a metadata server34DATABLDR03
SN-018970An SQL Join transformation cannot be deleted from an existing jobdefinition34DATABLDR03
SN-018957ALERT - The Loader transformation's "Update/Insert" technique in SASŪ Data Integration Studio 3.4 might load nonmapped target-table columns with incorrect data34DATABLDR03
SN-018341SASŪ Splitter target objects do not establish correct linkage when used as direct input to a Lookup transformation34DATABLDR04
SN-019644ALERT - The ITMS repository becomes corrupted when you delete a job while theProperties sheet of an aggregation table is open34DATABLDR04
SN-019641A Java exception error occurs when you delete multiple tables in SASŪ Data Integration Studio 3.4 using the Delete w/Contents menu item34DATABLDR04
SN-019466An error occurs on the SQL Join when you use the import/export or the copy/paste functions in SASŪ Data Integration Studio34DATABLDR04
SN-019461Job modifications cause mapping expressions in SQL Join transformationsto disappear34DATABLDR04
SN-019645SASŪ Data Integration Studio 3.4 jobs with an SQL join transformation might become corrupted if you insert additional transformations into the flow34DATABLDR04
SN-020145Incorrect behavior during partial promotion export and missing contentunder the BI Manager plug-in 1.434DATABLDR05
SN-021026ALERT - SASŪ Data Integration Studio job code generates in the wrong order34DATABLDR05
SN-020256ALERT - Objects do not appear in the tree when you attempt to import a packageinto the Foundation repository34DATABLDR05
SN-020485SASŪ generates a "com.sas.workspace.WsAppServerLibraryException: Libname XXXXXXXX is not assigned" error when you attempt to launch View Data on a target34DATABLDR05
SN-020741ALERT - The target table is generated with incorrect data when multiple lookuptables and the target table contain a column with the same name34DATABLDR05
SN-020740ALERT - The target table is generated with incorrect data when lookup tablecolumn names match source table column names34DATABLDR05
SN-020255ALERT - A failure might occur when you use the Import Wizard to perform animport operation34DATABLDR05
SN-031008Hot fixes 913SMC04 and 14JPS02 provide the capability to add job flows using partial promotion34DATABLDR05
SN-020525A checked out job containing an SQL join transformation with ORDERBY/GROUP BY column(s) loses the mappings for those columns34DATABLDR05
SN-020573Job flow gets broken into multiple pieces when you remove a transformation directly above a SASŪ splitter34DATABLDR05
SN-020036Batch execution problems result when the Lookup transformation generatesRETAIN and IF statements with line lengths greater than 256 characters34DATABLDR05
SN-020489Process Designer does not respond as expected when you manage multipleconnections between two transformations34DATABLDR05
SN-020483Load Technique settings in the SASŪ Scalable Performance Data Server Loader transformation do not get surfaced correctly when the locale is set to any value other34DATABLDR05
SN-020708The Lookup transformation generates a syntax error if the named literalquoting is disabled in the last lookup table34DATABLDR05
SN-020576ALERT - Jobs that contain SCD Type 2 Loader transformations can fail when youattempt to execute them simultaneously34DATABLDR05
SN-020285The Update Table Metadata process terminates prematurely and generates a Java exception34DATABLDR05
SN-020431User-written code is not exported in an .SPK file34DATABLDR05
SN-020455Note and document objects are duplicated in the target repository duringa partial-promotion import34DATABLDR05
SN-020531SCD Type 2 Loader does not maintain NOT NULL attribute for temporaryDBMS tables to match the columns of the table34DATABLDR05
SN-020526Swapping inputs to a join may result in invalid syntax34DATABLDR05
SN-020754Work tables become detached from a job flow when two or more Lookuptransformations are directly connected34DATABLDR05
SN-020709An attempt to drag an input table that is already input to an existingSQL Join transformation into the empty input template of another SQLJoin fails34DATABLDR05
SN-030548Mappings and expressions are lost in job definitions when tables or external files are imported via partial promotion34DATABLDR07
SN-030515ALERT - Job and information map objects associated with tables that are not unique by name, but reside in different libraries, might import incorrectly34DATABLDR07
SN-030535SAS returns an error when importing metadata package files34DATABLDR07
SN-030512Data Quality schemes located on a classic mainframe file system do not surface in the Apply Lookup Standardization transformation34DATABLDR07
SN-030513Data Quality options cannot be set correctly when you reference a mainframe workspace server34DATABLDR07
SN-031833The Data Library Manager might unintentionally and incorrectly update concatenated library paths34DATABLDR08
SN-032156The Data Location button is missing from the Process tab within the Properties window of the Loop transformation34DATABLDR08
SN-031941A metadata write error prevents you from saving a SASŪ Data Integration Studio job after you delete a SAS Splitter transformation34DATABLDR08
SN-032154SQL Join generates invalid code when formats or functions used within expressions match column names in source or target tables34DATABLDR08
SN-032145SASŪ Data Integration Studio might return an error when you generate code or submit a job that contains a Lookup transformation34DATABLDR08
SN-032203Send Email status handling might not function in SASŪ Financial Management jobs that are created in SASŪ Data Integration Studio34DATABLDR08
SN-032544The Lookup transformation exception table might contain incorrect lookup table name values34DATABLDR08
SN-032230The Data Validation transformation lookup table and column definitions are lost during SASŪ metadata import34DATABLDR08
SN-032150A job that is checked out might generate incorrect code for a transformation that is also checked out34DATABLDR08
SN-032227ALERT - All options and parameters for all objects in a repository are lost after deleting a file object34DATABLDR08
SN-032226The Data Library Manager might unintentionally and incorrectly update concatenated library paths34DATABLDR08
SN-032170Expanding a folder or library within the SASŪ Data Integration Studio tree views can become inhibitively slow as the number of objects increases34DATABLDR08
SN-032186The Export and Import feature in SASŪ Data Integration Studio or SASŪ Management Console might change the order of columns in some objects34DATABLDR08
SN-032183SASŪ Data Integration Studio Loader does not re-create non-key constraints that are dropped before the load34DATABLDR08
SN-032181SASŪ Data Integration Studio jobs with deeply nested code can produce syntax errors due to incorrect line wrapping34DATABLDR08
SN-032159Input tables shown in Process Designer for the SQL Join transformation are missing from the Designer tab in that transformation's Properties window34DATABLDR08
SN-032224SASŪ Data Integration Studio generates an error when importing jobs with SAP data transforms 34DATABLDR08
SN-032201A SASŪ Data Integration Studio job might generate different code for deployment than for viewing or submission from the user interface34DATABLDR08
SN-031929Multiple issues can come up when you perform scheduling from within SASŪ Data Integration Studio34DATABLDR09
SN-032585Partial promotion import fails with string index out of range error34DATABLDR09
SN-034410Column names that contain special characters are not handled correctly during Update Table Metadata processing34DATABLDR10
SN-034418SASŪ Data Integration Studio appears to stop responding when deleting a Table Loader transformation34DATABLDR10
SN-034298Apply Lookup Standardization code fails with errors when run on certain operating systems34DATABLDR10
SN-034414SAS® program file content gets deleted when you copy or promote a job with multiple references to the same SAS program file34DATABLDR10
 
WindowsReleased: Jan 2009
Install Instructions: 34DATABLDR10wn.txt
Download: 34DATABLDR10 for Windows   (file size: 32.7M)
Top ^

 
12MITIBRIDGE01
Issue(s) Addressed :Introduced:
SN-019949Exporting metadata with a SASŪ Metadata Bridge from SASŪ Management Console might cause an error 12MITIBRIDGE01
 
WindowsReleased: Aug 2007
Install Instructions: 12MITIBRIDGE01wn.txt
Download: 12MITIBRIDGE01 for Windows   (file size: 19.3M)

 
913SMC01 was replaced by 913SMC02

913SMC02
Issue(s) Addressed :Introduced:
SN-017858Unable to select a SAS Data Integration Studio Custom group folder destination for a new library in the New Library wizard 913SMC01
SN-017875SAS Data Integration Studio 3.4 Custom tree displays only the BIP tree and BI folders 913SMC01
SN-017874BI Manager Plug-in does not sort a column correctly 913SMC01
 
WindowsReleased: Mar 2007
Install Instructions: 913SMC02wn.txt
Download: 913SMC02 for Windows   (file size: 27.6M)
ATTENTION (1): This hot fix should be applied to any client machine running SAS Management Console for SAS 9.1.3 Service Pack 4, with Implementation-Version=9.1.20050622.20001. Do not apply this hot fix to any other Implementation-Version of SAS Management Console.
ATTENTION (2): Additional requirements are SAS Foundation Services (BI Manager) 1.4. To determine the version of BI Manager Installed on your system, go into the SAS Management Console and click on the root node of the BI Manager and select 'About' for Implementation Version 1.4.0.0.20060626.74052.
 
HPUX 64bitReleased: Mar 2007
Install Instructions: 913SMC02h6.txt
Download: 913SMC02 for HPUX 64bit   (file size: 65.6M)
ATTENTION (1): This hot fix should be applied to any client machine running SAS Management Console for SAS 9.1.3 Service Pack 4, with Implementation-Version=9.1.20050622.20001. Do not apply this hot fix to any other Implementation-Version of SAS Management Console.
ATTENTION (2): Additional requirements are SAS Foundation Services (BI Manager) 1.4. To determine the version of BI Manager Installed on your system, go into the SAS Management Console and click on the root node of the BI Manager and select 'About' for Implementation Version 1.4.0.0.20060626.74052.
 
Solaris 64bitReleased: Mar 2007
Install Instructions: 913SMC02s6.txt
Download: 913SMC02 for Solaris 64bit   (file size: 37.9M)
ATTENTION (1): This hot fix should be applied to any client machine running SAS Management Console for SAS 9.1.3 Service Pack 4, with Implementation-Version=9.1.20050622.20001. Do not apply this hot fix to any other Implementation-Version of SAS Management Console.
ATTENTION (2): Additional requirements are SAS Foundation Services (BI Manager) 1.4. To determine the version of BI Manager Installed on your system, go into the SAS Management Console and click on the root node of the BI Manager and select 'About' for Implementation Version 1.4.0.0.20060626.74052.
 
AIX 64bitReleased: Mar 2007
Install Instructions: 913SMC02r6.txt
Download: 913SMC02 for AIX 64bit   (file size: 42.4M)
ATTENTION (1): This hot fix should be applied to any client machine running SAS Management Console for SAS 9.1.3 Service Pack 4, with Implementation-Version=9.1.20050622.20001. Do not apply this hot fix to any other Implementation-Version of SAS Management Console.
ATTENTION (2): Additional requirements are SAS Foundation Services (BI Manager) 1.4. To determine the version of BI Manager Installed on your system, go into the SAS Management Console and click on the root node of the BI Manager and select 'About' for Implementation Version 1.4.0.0.20060626.74052.
 
LinuxReleased: Mar 2007
Install Instructions: 913SMC02lx.txt
Download: 913SMC02 for Linux   (file size: 36.3M)
ATTENTION (1): This hot fix should be applied to any client machine running SAS Management Console for SAS 9.1.3 Service Pack 4, with Implementation-Version=9.1.20050622.20001. Do not apply this hot fix to any other Implementation-Version of SAS Management Console.
ATTENTION (2): Additional requirements are SAS Foundation Services (BI Manager) 1.4. To determine the version of BI Manager Installed on your system, go into the SAS Management Console and click on the root node of the BI Manager and select 'About' for Implementation Version 1.4.0.0.20060626.74052.
 
HPUX for ItaniumReleased: Mar 2007
Install Instructions: 913SMC02hx.txt
Download: 913SMC02 for HPUX for Itanium   (file size: 90.0M)
ATTENTION (1): This hot fix should be applied to any client machine running SAS Management Console for SAS 9.1.3 Service Pack 4, with Implementation-Version=9.1.20050622.20001. Do not apply this hot fix to any other Implementation-Version of SAS Management Console.
ATTENTION (2): Additional requirements are SAS Foundation Services (BI Manager) 1.4. To determine the version of BI Manager Installed on your system, go into the SAS Management Console and click on the root node of the BI Manager and select 'About' for Implementation Version 1.4.0.0.20060626.74052.
Top ^

 
913SMC04 was replaced by 913SMC08

913SMC05 was replaced by 913SMC08

913SMC06 was replaced by 913SMC08

913SMC08
Issue(s) Addressed :Introduced:
SN-031008Hot fixes 913SMC04 and 14JPS02 provide the capability to add job flows using partial promotion913SMC04
SN-013777The "ERROR: There is an illegal character in the entity name" message can appear when you attempt to update metadata that contains special characters913SMC04
SN-018534Importing tables in SAS Management Console stops working after applying913SMC01 hot fix913SMC04
SN-019308SAS Grid Manager offering does not ship with a license for Integration Technologies913SMC04
SN-020145Incorrect behavior during partial promotion export and missing contentunder the BI Manager plug-in 1.4913SMC04
SN-020080ALERT - The Define Repository Dependencies dialog in the SASŪ Management Console and SASŪ Data Integration Studio contains a translation error913SMC04
SN-020251Dependencies for jobs in a flow cannot be selected or changed913SMC04
SN-017365Scheduled Reports window does not update status when a scheduled reporthas run913SMC05
SN-030908When hot fix 913SM04 is applied to a Japanese version of SASŪ Management Console, the language is converted to English for the scheduler plug-in913SMC05
SN-030903When a flow is deleted within SASŪ Management Console, it remains visible in SAS Management Console and Platform LSF still runs the job913SMC05
SN-030905Adding exceptions to a job flow's advanced properties might corrupt the job properties and cause the job not to execute913SMC05
SN-030909When a job is deleted from outside of a flow, the flow metadata can become corrupt913SMC05
SN-032226The Data Library Manager might unintentionally and incorrectly update concatenated library paths913SMC06
SN-031833The Data Library Manager might unintentionally and incorrectly update concatenated library paths913SMC06
SN-033003Trigger times for flow schedules are based on the client machine rather than the server after you apply hot fix 913SMC06913SMC07
SN-033552Flows that are launched by Java applications in the UNIX environment can leave XML files behind in the local drive’s root directory913SMC07
SN-033550An error might occur if you try to delete deployment directories under the Schedule Manager plug-in in SASŪ Management Console913SMC07
SN-033409The RunAs job property that is defined on the Advanced Properties tab in the Schedule Manager is not honored913SMC07
SN-035907Man-in-the-middle/downgrade attacks could cause credentials to improperly encrypt during the initial login from a SAS client913SMC08
 
WindowsReleased: May 2009
Install Instructions: 913SMC08wn.txt
Download: 913SMC08 for Windows   (file size: 30.2M)
ATTENTION (1): You must download this hotfix, 913SMC08, and 14JPS02 respectively for this hotfix to be fully functional.
ATTENTION (2): This hot fix should be applied to any client machine running SAS Management Console with the following, Implementation-Version=9.1.20060726.1008. You can determine the SMC level from the About SAS Management Console Dialog under Product Release Information.
 
HPUX 64bitReleased: May 2009
Install Instructions: 913SMC08h6.txt
Download: 913SMC08 for HPUX 64bit   (file size: 68.1M)
ATTENTION (1): You must download this hotfix, 913SMC08, and 14JPS02 respectively for this hotfix to be fully functional.
ATTENTION (2): This hot fix should be applied to any client machine running SAS Management Console with the following, Implementation-Version=9.1.20060726.1008. You can determine the SMC level from the About SAS Management Console Dialog under Product Release Information.
 
Solaris 64bitReleased: May 2009
Install Instructions: 913SMC08s6.txt
Download: 913SMC08 for Solaris 64bit   (file size: 40.5M)
ATTENTION (1): You must download this hotfix, 913SMC08, and 14JPS02 respectively for this hotfix to be fully functional.
ATTENTION (2): This hot fix should be applied to any client machine running SAS Management Console with the following, Implementation-Version=9.1.20060726.1008. You can determine the SMC level from the About SAS Management Console Dialog under Product Release Information.
 
AIX 64bitReleased: May 2009
Install Instructions: 913SMC08r6.txt
Download: 913SMC08 for AIX 64bit   (file size: 44.9M)
ATTENTION (1): You must download this hotfix, 913SMC08, and 14JPS02 respectively for this hotfix to be fully functional.
ATTENTION (2): This hot fix should be applied to any client machine running SAS Management Console with the following, Implementation-Version=9.1.20060726.1008. You can determine the SMC level from the About SAS Management Console Dialog under Product Release Information.
 
LinuxReleased: May 2009
Install Instructions: 913SMC08lx.txt
Download: 913SMC08 for Linux   (file size: 38.8M)
ATTENTION (1): You must download this hotfix, 913SMC08, and 14JPS02 respectively for this hotfix to be fully functional.
ATTENTION (2): This hot fix should be applied to any client machine running SAS Management Console with the following, Implementation-Version=9.1.20060726.1008. You can determine the SMC level from the About SAS Management Console Dialog under Product Release Information.
 
HPUX for ItaniumReleased: May 2009
Install Instructions: 913SMC08hx.txt
Download: 913SMC08 for HPUX for Itanium   (file size: 92.5M)
ATTENTION (1): You must download this hotfix, 913SMC08, and 14JPS02 respectively for this hotfix to be fully functional.
ATTENTION (2): This hot fix should be applied to any client machine running SAS Management Console with the following, Implementation-Version=9.1.20060726.1008. You can determine the SMC level from the About SAS Management Console Dialog under Product Release Information.
Top ^

 
E9BA20 was replaced by E9BC59

E9BA54 was replaced by E9BC59

E9BB74 was replaced by E9BC59

E9BC03 was replaced by E9BC59


E9BC59
Issue(s) Addressed :Introduced:
SN-017857Exception may occur while exporting a block of objects from the Data Intgration Studio Custom tree E9BA20
SN-017860ALERT - Parameter definitions associated with all Stored Process may be inadvertently deleted if a Stored Process that contains parameters is re-imported into the Foundation repository via BI Manager E9BA20
SN-017852ALERT - External Table objects may get inadvertently deleted from metadata when importing or exporting metadata multiple times E9BA20
SN-017855ALERT - Server code does not support exporting and importing from a Project repository E9BA20
SN-017761ALERT - Jobs that are duplicated within a Project repository may lose their connection to Target objects E9BA20
SN-017743Login to SAS web application fails when using an email address as the userid with LDAP authentication E9BA20
SN-017854ALERT - Incorrect behavior may occur when all items are not selected within a package when performing a metadata import in Data Integration Studio or BI Manager E9BA20
SN-017767Export and Import Wizards require Metadata Server fixes E9BA20
SN-018452Unauthorized access to metadata server content E9BA54
SN-030465ALERT - Adding new records to a metadata repository after performing a metadata restore adds multiple metadata objects with the same internal Id valueE9BB74
SN-031345Metadata objects stored in a custom repository are not returned by client applications or metadata query results when they should beE9BC03
SN-033984Poor performance occurs in client applications when the metadata environment contains a large number of repositoriesE9BC59
SN-034096Content is added to a parent repository, even when you do not have Check In Metadata permissionsE9BC59
 
OS/390Released: Dec 2008
Install Instructions: E9BC59os.txt
Download: E9BC59 for OS/390   (file size: 1.3M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
 
WindowsReleased: Dec 2008
Install Instructions: E9BC59wn.txt
Download: E9BC59 for Windows   (file size: 2.4M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
 
Windows for IPF
(64bit)
Released: Dec 2008
Install Instructions: E9BC59w6.txt
Download: E9BC59 for Windows for IPF (64bit)   (file size: 3.3M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
 
HPUX 64bitReleased: Dec 2008
Install Instructions: E9BC59h6.txt
Download: E9BC59 for HPUX 64bit   (file size: 2.0M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
 
Solaris 64bitReleased: Dec 2008
Install Instructions: E9BC59s6.txt
Download: E9BC59 for Solaris 64bit   (file size: 2.4M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
 
AIX 64bitReleased: Dec 2008
Install Instructions: E9BC59r6.txt
Download: E9BC59 for AIX 64bit   (file size: 1.7M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
 
LinuxReleased: Dec 2008
Install Instructions: E9BC59lx.txt
Download: E9BC59 for Linux   (file size: 1.5M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
 
HPUX for ItaniumReleased: Dec 2008
Install Instructions: E9BC59hx.txt
Download: E9BC59 for HPUX for Itanium   (file size: 3.4M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
 
Linux for ItaniumReleased: Dec 2008
Install Instructions: E9BC59li.txt
Download: E9BC59 for Linux for Itanium   (file size: 2.9M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
 
Solaris for x64Released: Dec 2008
Install Instructions: E9BC59sx.txt
Download: E9BC59 forSolaris for x64   (file size: 1.3M)
ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running.
Top ^



E9IH01
Issue(s) Addressed :Introduced:
SN-017764ALERT - Processing halted and Error dialog box displayed when reading IBM WebSphere MQ queue E9IH01
 
OS/390Released: Jun 2006
Install Instructions: E9IH01os.txt
Download: E9IH01 for OS/390   (file size: 121K)
ATTENTION: This hot fix should be applied to all locations where the SAS Workspace Server and Stored Process Server is running.
 
WindowsReleased: Jun 2006
Install Instructions: E9IH01wn.txt
Download: E9IH01 for Windows   (file size: 1.7M)
ATTENTION: This hot fix should be applied to all locations where the SAS Workspace Server and Stored Process Server is running.
 
HPUX 64bitReleased: Jun 2006
Install Instructions: E9IH01h6.txt
Download: E9IH01 for HPUX 64bit   (file size: 100K)
ATTENTION: This hot fix should be applied to all locations where the SAS Workspace Server and Stored Process Server is running.
 
Solaris 64bitReleased: Jun 2006
Install Instructions: E9IH01s6.txt
Download: E9IH01 for Solaris 64bit   (file size: 115K)
ATTENTION: This hot fix should be applied to all locations where the SAS Workspace Server and Stored Process Server is running.
 
AIX 64bitReleased: Jun 2006
Install Instructions: E9IH01r6.txt
Download: E0BA20 for AIX 64bit   (file size: 90K)
ATTENTION: This hot fix should be applied to all locations where the SAS Workspace Server and Stored Process Server is running.
 
Compaq Tru64 UNIXReleased: Jun 2006
Install Instructions: E9IH01ap.txt
Download: E0BA20 for Compaq Tru64 UNIX   (file size: 120K)
ATTENTION: This hot fix should be applied to all locations where the SAS Workspace Server and Stored Process Server is running.
 
LinuxReleased: Jun 2006
Install Instructions: E9IH01lx.txt
Download: E9IH01 for Linux   (file size: 80K)
ATTENTION: This hot fix should be applied to all locations where the SAS Workspace Server and Stored Process Server is running.
 
OpenVMS AlphaReleased: Jun 2006
Install Instructions: E9IH01av.txt
Download: E9IH01 for OpenVMS Alpha   (file size: 111K)
ATTENTION: This hot fix should be applied to all locations where the SAS Workspace Server and Stored Process Server is running.

 
Top ^




PLEASE CAREFULLY READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING MATERIALS FROM THIS SITE. BY DOWNLOADING ANY MATERIALS FROM THIS SITE, YOU ARE AGREEING TO THESE TERMS.
You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). This Code is designed to either correct an error in the Software or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.

Copyright © 2014 SAS Institute Inc. All Rights Reserved.