34DATABLDR10 |
Issue(s) Addressed : | Introduced: |
SN-018287 | Macro variable names defined in a generated transformation revert backto default when job is deployed | 34DATABLDR01 |
SN-018280 | ALERT - Extract and SQL Join transformations might generate invalid code when column labels contain single or double quotes | 34DATABLDR01 |
SN-018285 | ALERT - Duplicate column names across lookup tables might result in incorrect lookup results | 34DATABLDR01 |
SN-018282 | ALERT - The Update SAS ETL/Data Integration Studio Prototypes tool incorrectly generates "Objects are still checked out..." dialog | 34DATABLDR01 |
SN-018275 | ALERT - Code might be generated in incorrect order, resulting in errors during program execution | 34DATABLDR01 |
SN-018284 | ALERT - New libraries and tables get created when existing objects should have been referenced during a Paste or Import process | 34DATABLDR01 |
SN-018526 | ALERT - Lookup transformation code fails with ERROR: The name "columnname"n is not a valid SAS name | 34DATABLDR02 |
SN-018531 | Solutions Repository - ERROR: Failed to create metric table | 34DATABLDR02 |
SN-018942 | SASŪ Data Integration Studio SAP jobs can be corrupted by the Export/Import or Copy/Paste operations | 34DATABLDR03 |
SN-018873 | Source-to-target mappings can be corrupted in the new SQL Jointransformation | 34DATABLDR03 |
SN-018858 | ALERT - Batch execution problems result when the Lookup transformation generates code with line lengths greater than 256 characters | 34DATABLDR03 |
SN-018874 | The "Update SAS Data Integration Studio Metadata" tool in SASŪ Management Console does not automatically register all occurrences of custom trees on a metadata server | 34DATABLDR03 |
SN-018970 | An SQL Join transformation cannot be deleted from an existing jobdefinition | 34DATABLDR03 |
SN-018957 | ALERT - The Loader transformation's "Update/Insert" technique in SASŪ Data Integration Studio 3.4 might load nonmapped target-table columns with incorrect data | 34DATABLDR03 |
SN-018341 | SASŪ Splitter target objects do not establish correct linkage when used as direct input to a Lookup transformation | 34DATABLDR04 |
SN-019644 | ALERT - The ITMS repository becomes corrupted when you delete a job while theProperties sheet of an aggregation table is open | 34DATABLDR04 |
SN-019641 | A Java exception error occurs when you delete multiple tables in SASŪ Data Integration Studio 3.4 using the Delete w/Contents menu item | 34DATABLDR04 |
SN-019466 | An error occurs on the SQL Join when you use the import/export or the copy/paste functions in SASŪ Data Integration Studio | 34DATABLDR04 |
SN-019461 | Job modifications cause mapping expressions in SQL Join transformationsto disappear | 34DATABLDR04 |
SN-019645 | SASŪ Data Integration Studio 3.4 jobs with an SQL join transformation might become corrupted if you insert additional transformations into the flow | 34DATABLDR04 |
SN-020145 | Incorrect behavior during partial promotion export and missing contentunder the BI Manager plug-in 1.4 | 34DATABLDR05 |
SN-021026 | ALERT - SASŪ Data Integration Studio job code generates in the wrong order | 34DATABLDR05 |
SN-020256 | ALERT - Objects do not appear in the tree when you attempt to import a packageinto the Foundation repository | 34DATABLDR05 |
SN-020485 | SASŪ generates a "com.sas.workspace.WsAppServerLibraryException: Libname XXXXXXXX is not assigned" error when you attempt to launch View Data on a target | 34DATABLDR05 |
SN-020741 | ALERT - The target table is generated with incorrect data when multiple lookuptables and the target table contain a column with the same name | 34DATABLDR05 |
SN-020740 | ALERT - The target table is generated with incorrect data when lookup tablecolumn names match source table column names | 34DATABLDR05 |
SN-020255 | ALERT - A failure might occur when you use the Import Wizard to perform animport operation | 34DATABLDR05 |
SN-031008 | Hot fixes 913SMC04 and 14JPS02 provide the capability to add job flows using partial promotion | 34DATABLDR05 |
SN-020525 | A checked out job containing an SQL join transformation with ORDERBY/GROUP BY column(s) loses the mappings for those columns | 34DATABLDR05 |
SN-020573 | Job flow gets broken into multiple pieces when you remove a transformation directly above a SASŪ splitter | 34DATABLDR05 |
SN-020036 | Batch execution problems result when the Lookup transformation generatesRETAIN and IF statements with line lengths greater than 256 characters | 34DATABLDR05 |
SN-020489 | Process Designer does not respond as expected when you manage multipleconnections between two transformations | 34DATABLDR05 |
SN-020483 | Load Technique settings in the SASŪ Scalable Performance Data Server Loader transformation do not get surfaced correctly when the locale is set to any value other | 34DATABLDR05 |
SN-020708 | The Lookup transformation generates a syntax error if the named literalquoting is disabled in the last lookup table | 34DATABLDR05 |
SN-020576 | ALERT - Jobs that contain SCD Type 2 Loader transformations can fail when youattempt to execute them simultaneously | 34DATABLDR05 |
SN-020285 | The Update Table Metadata process terminates prematurely and generates a Java exception | 34DATABLDR05 |
SN-020431 | User-written code is not exported in an .SPK file | 34DATABLDR05 |
SN-020455 | Note and document objects are duplicated in the target repository duringa partial-promotion import | 34DATABLDR05 |
SN-020531 | SCD Type 2 Loader does not maintain NOT NULL attribute for temporaryDBMS tables to match the columns of the table | 34DATABLDR05 |
SN-020526 | Swapping inputs to a join may result in invalid syntax | 34DATABLDR05 |
SN-020754 | Work tables become detached from a job flow when two or more Lookuptransformations are directly connected | 34DATABLDR05 |
SN-020709 | An attempt to drag an input table that is already input to an existingSQL Join transformation into the empty input template of another SQLJoin fails | 34DATABLDR05 |
SN-030548 | Mappings and expressions are lost in job definitions when tables or external files are imported via partial promotion | 34DATABLDR07 |
SN-030515 | ALERT - Job and information map objects associated with tables that are not unique by name, but reside in different libraries, might import incorrectly | 34DATABLDR07 |
SN-030535 | SAS returns an error when importing metadata package files | 34DATABLDR07 |
SN-030512 | Data Quality schemes located on a classic mainframe file system do not surface in the Apply Lookup Standardization transformation | 34DATABLDR07 |
SN-030513 | Data Quality options cannot be set correctly when you reference a mainframe workspace server | 34DATABLDR07 |
SN-031833 | The Data Library Manager might unintentionally and incorrectly update concatenated library paths | 34DATABLDR08 |
SN-032156 | The Data Location button is missing from the Process tab within the Properties window of the Loop transformation | 34DATABLDR08 |
SN-031941 | A metadata write error prevents you from saving a SASŪ Data Integration Studio job after you delete a SAS Splitter transformation | 34DATABLDR08 |
SN-032154 | SQL Join generates invalid code when formats or functions used within expressions match column names in source or target tables | 34DATABLDR08 |
SN-032145 | SASŪ Data Integration Studio might return an error when you generate code or submit a job that contains a Lookup transformation | 34DATABLDR08 |
SN-032203 | Send Email status handling might not function in SASŪ Financial Management jobs that are created in SASŪ Data Integration Studio | 34DATABLDR08 |
SN-032544 | The Lookup transformation exception table might contain incorrect lookup table name values | 34DATABLDR08 |
SN-032230 | The Data Validation transformation lookup table and column definitions are lost during SASŪ metadata import | 34DATABLDR08 |
SN-032150 | A job that is checked out might generate incorrect code for a transformation that is also checked out | 34DATABLDR08 |
SN-032227 | ALERT - All options and parameters for all objects in a repository are lost after deleting a file object | 34DATABLDR08 |
SN-032226 | The Data Library Manager might unintentionally and incorrectly update concatenated library paths | 34DATABLDR08 |
SN-032170 | Expanding a folder or library within the SASŪ Data Integration Studio tree views can become inhibitively slow as the number of objects increases | 34DATABLDR08 |
SN-032186 | The Export and Import feature in SASŪ Data Integration Studio or SASŪ Management Console might change the order of columns in some objects | 34DATABLDR08 |
SN-032183 | SASŪ Data Integration Studio Loader does not re-create non-key constraints that are dropped before the load | 34DATABLDR08 |
SN-032181 | SASŪ Data Integration Studio jobs with deeply nested code can produce syntax errors due to incorrect line wrapping | 34DATABLDR08 |
SN-032159 | Input tables shown in Process Designer for the SQL Join transformation are missing from the Designer tab in that transformation's Properties window | 34DATABLDR08 |
SN-032224 | SASŪ Data Integration Studio generates an error when importing jobs with SAP data transforms | 34DATABLDR08 |
SN-032201 | A SASŪ Data Integration Studio job might generate different code for deployment than for viewing or submission from the user interface | 34DATABLDR08 |
SN-031929 | Multiple issues can come up when you perform scheduling from within SASŪ Data Integration Studio | 34DATABLDR09 |
SN-032585 | Partial promotion import fails with string index out of range error | 34DATABLDR09 |
SN-034410 | Column names that contain special characters are not handled correctly during Update Table Metadata processing | 34DATABLDR10 |
SN-034418 | SASŪ Data Integration Studio appears to stop responding when deleting a Table Loader transformation | 34DATABLDR10 |
SN-034298 | Apply Lookup Standardization code fails with errors when run on certain operating systems | 34DATABLDR10 |
SN-034414 | SAS® program file content gets deleted when you copy or promote a job with multiple references to the same SAS program file | 34DATABLDR10 |
|
Windows | Released: Jan 2009 |
Install Instructions: 34DATABLDR10wn.txt |
Download: 34DATABLDR10 for Windows   (file size: 32.7M) |
913SMC02 |
Issue(s) Addressed : | Introduced: |
SN-017858 | Unable to select a SAS Data Integration Studio Custom group folder destination for a new library in the New Library wizard | 913SMC01 |
SN-017875 | SAS Data Integration Studio 3.4 Custom tree displays only the BIP tree and BI folders | 913SMC01 |
SN-017874 | BI Manager Plug-in does not sort a column correctly | 913SMC01 |
|
Windows | Released: 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 64bit | Released: 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 64bit | Released: 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 64bit | Released: 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.
|
|
Linux | Released: 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 Itanium | Released: 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.
|
913SMC08 |
Issue(s) Addressed : | Introduced: |
SN-031008 | Hot fixes 913SMC04 and 14JPS02 provide the capability to add job flows using partial promotion | 913SMC04 |
SN-013777 | The "ERROR: There is an illegal character in the entity name" message can appear when you attempt to update metadata that contains special characters | 913SMC04 |
SN-018534 | Importing tables in SAS Management Console stops working after applying913SMC01 hot fix | 913SMC04 |
SN-019308 | SAS Grid Manager offering does not ship with a license for Integration Technologies | 913SMC04 |
SN-020145 | Incorrect behavior during partial promotion export and missing contentunder the BI Manager plug-in 1.4 | 913SMC04 |
SN-020080 | ALERT - The Define Repository Dependencies dialog in the SASŪ Management Console and SASŪ Data Integration Studio contains a translation error | 913SMC04 |
SN-020251 | Dependencies for jobs in a flow cannot be selected or changed | 913SMC04 |
SN-017365 | Scheduled Reports window does not update status when a scheduled reporthas run | 913SMC05 |
SN-030908 | When hot fix 913SM04 is applied to a Japanese version of SASŪ Management Console, the language is converted to English for the scheduler plug-in | 913SMC05 |
SN-030903 | When a flow is deleted within SASŪ Management Console, it remains visible in SAS Management Console and Platform LSF still runs the job | 913SMC05 |
SN-030905 | Adding exceptions to a job flow's advanced properties might corrupt the job properties and cause the job not to execute | 913SMC05 |
SN-030909 | When a job is deleted from outside of a flow, the flow metadata can become corrupt | 913SMC05 |
SN-032226 | The Data Library Manager might unintentionally and incorrectly update concatenated library paths | 913SMC06 |
SN-031833 | The Data Library Manager might unintentionally and incorrectly update concatenated library paths | 913SMC06 |
SN-033003 | Trigger times for flow schedules are based on the client machine rather than the server after you apply hot fix 913SMC06 | 913SMC07 |
SN-033552 | Flows that are launched by Java applications in the UNIX environment can leave XML files behind in the local driveâs root directory | 913SMC07 |
SN-033550 | An error might occur if you try to delete deployment directories under the Schedule Manager plug-in in SASŪ Management Console | 913SMC07 |
SN-033409 | The RunAs job property that is defined on the Advanced Properties tab in the Schedule Manager is not honored | 913SMC07 |
SN-035907 | Man-in-the-middle/downgrade attacks could cause credentials to improperly encrypt during the initial login from a SAS client | 913SMC08 |
|
Windows | Released: 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 64bit | Released: 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 64bit | Released: 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 64bit | Released: 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.
|
|
Linux | Released: 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 Itanium | Released: 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.
|
E9BC59 |
Issue(s) Addressed : | Introduced: |
SN-017857 | Exception may occur while exporting a block of objects from the Data Intgration Studio Custom tree | E9BA20 |
SN-017860 | ALERT - 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-017852 | ALERT - External Table objects may get inadvertently deleted from metadata when importing or exporting metadata multiple times | E9BA20 |
SN-017855 | ALERT - Server code does not support exporting and importing from a Project repository | E9BA20 |
SN-017761 | ALERT - Jobs that are duplicated within a Project repository may lose their connection to Target objects | E9BA20 |
SN-017743 | Login to SAS web application fails when using an email address as the userid with LDAP authentication | E9BA20 |
SN-017854 | ALERT - 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-017767 | Export and Import Wizards require Metadata Server fixes | E9BA20 |
SN-018452 | Unauthorized access to metadata server content | E9BA54 |
SN-030465 | ALERT - Adding new records to a metadata repository after performing a metadata restore adds multiple metadata objects with the same internal Id value | E9BB74 |
SN-031345 | Metadata objects stored in a custom repository are not returned by client applications or metadata query results when they should be | E9BC03 |
SN-033984 | Poor performance occurs in client applications when the metadata environment contains a large number of repositories | E9BC59 |
SN-034096 | Content is added to a parent repository, even when you do not have Check In Metadata permissions | E9BC59 |
|
OS/390 | Released: 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. |
|
Windows | Released: 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 64bit | Released: 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 64bit | Released: 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 64bit | Released: 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. |
|
Linux | Released: 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 Itanium | Released: 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 Itanium | Released: 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 x64 | Released: 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. |
E9IH01 |
Issue(s) Addressed : | Introduced: |
SN-017764 | ALERT - Processing halted and Error dialog box displayed when reading IBM WebSphere MQ queue | E9IH01 |
|
OS/390 | Released: 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. |
|
Windows | Released: 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 64bit | Released: 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 64bit | Released: 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 64bit | Released: 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 UNIX | Released: 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. |
|
Linux | Released: 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 Alpha | Released: 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. |