What's New? (ARCHIVE)

 

LATEST HOT FIX RELEASES

Hot Fix Releases for the Week of: January 16, 2012

E9BD61 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017873	ALERT - Extra WHERE clause may get added to query passed to databases	E9BA31
SN-017888	Segmentation Violation error issued when using PROC SQL and SAS/ACCESS® with a LENGTH= option larger than 32	E9BA31
SN-018108	Segmentation violation when executing multiple queries against a PROC SQL view containing a LIBNAME statement	E9BA44
SN-018176	ALERT - Import of table through Information Map Library Engine deletes physical table	E9BA48
SN-020479	Batch jobs might end with a return code of 4 with no warning in the SAS® log	E9BA53
SN-018487	Compress() function returns incorrect results when used on PROC SQL INSERT statement after applying SAS® 9.1.3 Service Pack 4	E9BA53
SN-016074	"WARNING: At least one nonessential grouping column reference has been removed from a GROUP BY's reference list"	E9BA53
SN-019170	Errors issued when integer references for column is used in a PROC SQL GROUP BY statement	E9BA83
SN-019372	Performance is poor in the SQL procedure when you use the COUNT(Distinct xxxx) function	E9BB04
SN-019527	Specifying the NOIPASSTHRU option in PROC SQL does not disable implicit passthru	E9BB04
SN-016547	Correlated subqueries using column aliases may not be passed to your dbms when using SAS/ACCESS LIBNAME statement	E9BB10
SN-019930	Using more than 36 tables in a UNION operation within an SQL procedure generates an error message	E9BB26
SN-020130	Aliases columns or aliased tables in the SQL procedure blocks Implicit Pass-Through	E9BB29
SN-030428	Aliased constant values become missing in outer joins and unions	E9BB29
SN-020162	Using functions without parameters in WHERE clauses can block Implicit Pass-Through	E9BB29
SN-020126	SAS/ACCESS® software now provides full support of the INNER JOIN syntax	E9BB29
SN-020116	SAS/ACCESS® software fails to use table aliases correctly when you use in-line SELECT statements	E9BB29
SN-020123	Incorrect SQL text is generated when inner and left joins are used	E9BB29
SN-020125	Using implicit pass-through might cause an incorrect table reference assignment	E9BB29
SN-020129	An incorrect Implicit Pass-Through query is generated when you use a combination of inner and outer Joins	E9BB29
SN-020122	Performance issues occur because SQL code is not passed to the database	E9BB29
SN-030390	Improvements are now available in relational database optimization via the SQL procedure	E9BB70
SN-019655	Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio	E9BB70
SN-020635	Incorrect textualization of SQL Implicit Pass-Through queries occurs when you combine multiple inner joins with one or more outer joins	E9BB70
SN-032085	Incorrect SQL optimization may produce incorrect results	E9BB76
SN-030942	The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHAR	E9BB76
SN-030923	Aliased summary functions in Base SAS® software are not passed to databases	E9BB76
SN-030893	Using an ORDER BY clause in the SQL procedure causes performance problems	E9BB76
SN-031102	A segmentation-violation error might occur after you apply Hot Fix E9BA83 and you access Oracle	E9BB76
SN-031191	Support is now available for the PROC SQL CREATE TABLE statement for the SAS® Scalable Performance Data Server®	E9BB93
SN-031122	SQLPLAN internal errors might occur when you select columns from an SQL view	E9BB93
SN-031121	Implicit Pass-Through errors occur when accessing Oracle tables	E9BB93
SN-031291	Errors occur in SAS® Scalable Performance Data Server® for numeric columns that are defined with the MISSING statement when it is used in WHERE processing	E9BB99
SN-031211	Errors occur in the SQL procedure's Implicit Pass-Through facility after you apply hot fixes E9BB72, E9BB76, and E9BB80	E9BB99
SN-031249	SQLPLAN errors occur when you reference a calculated column on an SQL WHERE clause	E9BB99
SN-031905	Enhancements to the Implicit SQL Pass-Through facility enable more of a query to be passed to a database	E9BC11
SN-031863	ALERT - Using the EQT operator in the SQL procedure incorrectly classifies rows with missing values as a match	E9BC11
SN-031564	Performance problems occur when you use the CASE expression with DBMS tables	E9BC11
SN-031825	After applying hot fixes E9BB98 and E9BB99, column aliases are passed to the SQL GROUP BY clause in place of the corresponding real column names	E9BC11
SN-033763	Using the CALCULATED keyword in a WHERE clause in a PROC SQL inner join generates a cartesian product	E9BC25
SN-033649	Calculations that involve DBMS datetime values can return incorrect results	E9BC25
SN-033073	Using the CALCULATED keyword in a WHERE clause generates a Carteisan product	E9BC25
SN-032636	A Read-access violation might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99	E9BC25
SN-032537	ALERT - Incorrect query results might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99 or you run SAS® 9.2	E9BC25
SN-032925	An error occurs when you use the IDXNAME= and the WHERE= data set options in an SQL procedure query	E9BC32
SN-032472	Concatenating libraries can result in Read-access violations in the SQL procedure	E9BC32
SN-032545	An SQLPLAN error might occur after you apply hot fixes E9BB98 and E9BB99	E9BC32
SN-032406	Outer joins that contain a WHERE clause with the STRIP() and PUT() functions cause abnormal endings	E9BC32
SN-035779	The LENGTH= column modifier is handled incorrectly when you use PROC SQL to create character columns in SAS® Scalable Performance Data Server® tables	E9BC32
SN-034012	Column aliases are not passed correctly to GROUP BY or ORDER BY clauses in the SAS® Scalable Performance Data Server®	E9BC32
SN-032542	An error message incorrectly appears when you use the IDXNAME= and the WHERE= option data set options together in an SQL procedure	E9BC32
SN-011210	Incorrect results occur when you use a WHERE= option with indexed tables in the SQL procedure	E9BC46
SN-034564	The COUNT() or N() functions return incorrect results when used in a query containing a WHERE clause or a WHERE= data set option	E9BC46
SN-035011	A Read-access violation occurs in the SQL procedure when the WHERE= data set option is placed in an ORDER BY clause	E9BC46
SN-033094	ALERT - Incorrect results might be generated when you use the LIBNAME statement to join multiple Oracle tables	E9BC46
SN-033648	ALERT - The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2	E9BC62
SN-034993	An error occurs when you run an SQL query with the ORACLE LIBNAME engine	E9BC62
SN-034975	Segmentation violations might occur after you apply Hot Fix E9BC46 in queries that reference DBMS tables	E9BC62
SN-034391	An SQLPLAN error might occur when you use a calculated field to subset a table	E9BC62
SN-036280	ALERT - The SQL procedure generates incorrect results when you copy a SAS® data set from one platform to another platform	E9BC94
SN-033084	An SQLPLAN internal error might occur when reference a variable from an in-line view that created the variable from a constant	E9BC94
SN-034678	An SQLPLAN error occurs when you submit a query with a CALCULATED column reference in a CASE expression that contains a GROUP BY clause	E9BC94
SN-036177	Incorrect results might occur when you run a PROC SQL join with an additional WHERE clause against Teradata tables	E9BC94
SN-036202	SQLPLAN internal errors might occur when you reference calculated columns in an SQL procedure	E9BC94
SN-036748	The MULTI_DATASRC_OPT= option is ignored when multiple WHERE clause predicates are used in an SQL join operation	E9BD08
SN-034153	Option DBIDIRECTEXEC prevents SAS® Enterprise Guide from opening tables created by PROC SQL	E9BD13
SN-034234	Incorrect results might occur if you use the LIBNAME statement option IP=YES with an SQL procedure that contains data calculations in a WHERE clause	E9BD13
SN-037611*	Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment	E9BD13
SN-040951	Arithemetic performed on DATA and TIME data types is not passed to the underlying DBMS in SAS/ACCESS® 9.1.3 software	E9BD20
SN-038458	SQLPLAN internal errors might occur when you reference a view in a query that has variables that are defined with the the LENGTH= column modifier	E9BD20
SN-040492	Incorrect textualization of SQL Implicit Pass-Through queries occurs when you combine multiple inner joins with the UNION operator	E9BD20
SN-037846*	A segmentation violation occurs in the SAS® 9.1.3 SQL procedure after you apply hot fixes E9BD08, E9BD09, and E9BD10 in the AIX operating environment	E9BD20
SN-038519	Specifying both the DBSLICPARM= and the MULTI_DATASRC_OPT= options might generate incorrect results	E9BD26
SN-039304	SQL views of DBMS tables may not return aliased column names	E9BD26
SN-039129	Formatting a newly created, missing numeric variable might result in a "Format not found" error	E9BD32
SN-039125	An SQLPLAN error might occur when you use a new column variable in a correlated subquery	E9BD32
SN-039271	ALERT - Outer join condition may not appear on WHERE clause when performing query against Oracle	E9BD32
SN-039984	An SQL procedure view does not return any rows when it is used in DATA step or a PRINT procedure	E9BD43
SN-041785	Read Access Violation errors occur when creating a long macro variable with the PROC SQL / INTO: macro interface	E9BD43
SN-042030	Oracle PREPARE error issued when SAS table is empty and no keys are in the WHERE clause	E9BD47
SN-044069	Performance might be affected if your query joins multiple tables or views in which variables are being renamed	E9BD61
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
Released January 16, 2012 on Tru 64, Linux Released October 4, 2011 on HPUX, Solaris (64-bit), AIX, HPUX for Itanium, Linux for Itanium, Windows, Windows for IPF (64 bit), z/OS (OS/390)
ATTENTION (1): E9BD61 for Windows is also available for the following languages: German, Spanish, French, Italian, Japanese, Polish, Simplified Chinese ATTENTION (2): Customers running SAS Base SQL must also download and install SAS Base hot fixes E9BD42 and E9BD48. Download E9BD42 Download E9BD42 for SAS with Asian Language Support (DBCS) Download E9BD48 Download E9BD48 for SAS with Asian Language Support (DBCS) ATTENTION (3): OpenVMS Alpha customers should install SAS BASE hot fix E9BD32. Download E9BD32

Top ^

PREVIOUS WEEKS

Hot Fix Releases for the Week of: December 19, 2011

E9BD59 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017514*	Job submissions to grid manager increasingly slow	E9BA05
SN-017233*	Poor performance with large DATA step and many missing values	E9BA07
SN-017667*	ALERT - Segmentation Violation in task [ DATASETS ] using DELETE statement	E9BA13
SN-017653*	-SGIO option generates I/O error message when ODS or procedure output is to an existing SAS data set	E9BA15
SN-017072	Metadata server service might show starting state but never start	E9BA19
SN-010866*	Text Pad cannot store a single character value in column 1	E9BA29
SN-017847*	SUM function and statement give incorrect output on HP Itanium	E9BA38
SN-013525*	ALERT - File>Open and File>Save might cause SAS to lock up with Jaws screen reader in SAS 9.1	E9BA55
SN-018540*	SAS Display Manager keys fail when you select Tools=>Options=>Output while using the JAWS screen reader with SAS® 9.1.3 on the Windows platform	E9BA55
SN-018790*	SAS® fails when running a very large DATA step on AIX	E9BA69
SN-019040*	Double-byte text strings are truncated when using the host WMF device driver	E9BA76
SN-018929*	Font type WingDings might not work on DBCS SAS® 9.1.3 with the GPLOT procedure	E9BA76
SN-019225*	DDE stops working after hotfix E9BA55 is installed	E9BA85
SN-019224*	PROC APPEND fails with SGIO option on Windows operating systems	E9BA85
SN-019345*	Increased LRECL support for SAS® on MS Windows	E9BA95
SN-019608*	SAS® Metadata server fails to start when system restarted	E9BB05
SN-019640*	HTML output is incorrect when ODS output is appended to an HTML file created by a DATA Step	E9BB14
SN-020233*	Increasing timeout value on UNIX may improve performance	E9BB32
SN-020274	Grid sign-on fails to honor the TCPPORTFIRST and the TCPPORTLAST options	E9BB36
SN-020438*	Unix cleanwork utility does not remove UTILLOC directories	E9BB45
SN-019386	SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]"	E9BB58
SN-020817	Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routine	E9BB58
SN-020870*	SIGNON attempts to SAS® Grid Manager might fail	E9BB58
SN-020646*	Moving the cursor off of a selected Radio Box item before releasing the mouse can incorrectly show updated selection	E9BB75
SN-021112*	A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server	E9BB75
SN-031368*	Poor performance with complex merges on AIX	E9BB95
SN-031098*	ALERT - A SAS® server might become unresponsive on highly loaded systems	E9BB95
SN-031719	Some components from version 6 of SAS/AF® software might cause a read-access violation with repeated use	E9BC09
SN-031795	Dragging the cursor to an unselected item within the Radio Box control can unexpectedly update the internal value for the unselected item	E9BC09
SN-031400	Resetting system time backwards causes negative "real time" value in STIMER output	E9BC09
SN-019028	Truncation errors might occur when using Unicode SAS with UTF-8 encoding to process 8-bit characters	E9BC18
SN-032113	The $EBCDIC format/informat generates incorrect results if ENCODING=UTF8 is set	E9BC18
SN-019330	Problems might occur when you invoke SAS® macros using Microsoft Object Linking and Embedding (OLE) automation submit method	E9BC18
SN-032096	ERROR "SAS Error Event: Error sending status, 1, to SCM. Error 6: The handle is invalid." occurs when stopping the SAS® Metadata Server	E9BC18
SN-032521	ALERT - A Multi-Processing (MP) CONNECT session might not respond in UNIX environments	E9BC18
SN-032547	Data sets written to tape in SAS® 8.2 are not readable in SAS® 9.1.3	E9BC18
SN-032945*	On HP Integrity systems, SAS® 9.1.3 SP4 installation process hangs if memory page size has been set higher than 8Kb	E9BC30
SN-032672*	DDE error "Physical file does not exist, excel|system." occurs after applying hot fix bundle E9BX03 for SAS® 9.1.3 SP4	E9BC30
SN-033403	Segmentation violation and bridge stub errors on AIX	E9BC60
SN-036130	Running large SQL queries in the AIX operating environment can generate results with missing values	E9BC60
SN-033581*	Program with a large number of ELSE statements produces incorrect results on AIX	E9BC60
SN-034651	Using a Japanese or DBCS character in a pathname may cause truncation of file name	E9BC67
SN-035477*	Invalid physical name error when a FILE statement contains certain Shift-JIS characters	E9BC83
SN-034955	The SAS® Metadata Server stops accepting new client connections and returns an error when too many files are open	E9BD12
SN-040822*	Specifying the SAS® system option OPLIST may cause a segmentation violation error in the UNIX environment	E9BD41
SN-041361	Modification datetime stamp is changed on existing version of a SAS® data set when you create a new data set with same name	E9BD44
SN-031894*	The SAS® Metadata Server might appear to hang during a period of high activity	E9BD56
SN-040494*	ALERT - A SAS/SHARE® server fails or does not respond when it is run as a Microsoft Windows service	E9BD59
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
PC:	Windows,   Windows_for_IPF_(64_bit)
ATTENTION (1): To obtain the complete fix for SN-020817 and SN-019386 you must also download and install SAS/CONNECT hot fix E9CT05. The issues described in SN-020817 and SN-019386 will not be fully fixed until both E9BD56 and E9CT05 are applied. ATTENTION (2): To obtain the complete fix for SN-021112 you must also download and install SAS/ACCESS Interface to DB2 hot fix E9D216. The issue described in SN-021112 will not be fully fixed until both E9BD56 and E9D216 are applied. This is not applicable to z/OS sites. Customers running on VMS should download E9BD44. Customers running on Unix and MVS should download E9BD56.

Top ^

Hot Fix Releases for the Week of: June 6, 2011

E9D222 for SAS/ACCESS INTERFACE TO DB2
Issue(s) Addressed:		Introduced:
SN-017707	Order by list with column numbers need spaces after each comma when DB2DECPT is set to a comma	E9D201
SN-017998	Accessing a DB2 table via a LIBNAME may result in a +239 error	E9D202
SN-019111	Calling a DB2 stored procedure may cause an infinite loop under some circumstances or it might retrieve the wrong data	E9D204
SN-020147	Accessing DB2 9 using the SAS/ACCESS® Interface to DB2 might result in an error	E9D206
SN-020869	A DB2 error might occur when you call a DB2 stored procedure running SAS/ACCESS® Interface to DB/2 on z/OS	E9D207
SN-014174	Support status for running DB2 Version 8 in the z/OS operating environment	E9D209
SN-030937	Length of DB2 error message increased	E9D211
SN-032067	An error might occur when you call a DB2 stored procedure that has an argument longer than 256 characters	E9D212
SN-013450	Additional SAS® functions might be passed to DB2	E9D213
SN-033648	ALERT - The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2	E9D215
SN-037611	Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment	E9D217
SN-037033	ALERT - Using the DBKEY= option in the SQL procedure might cause incorrect results	E9D218
SN-038580	Calling a stored procedure with a null parameter in SAS/ACCESS® Interface to DB2 might result in a -804 DB2 error	E9D219
SN-041225	Incorrect DB2 table names are created when you use the DB2LOAD or DBLOAD procedures with a DBCS edition of the third maintenance release for SAS® 9.1	E9D220
SN-042133	ALERT - Using Bulkload to insert into an already existing data set can result in incorrect data	E9D221
SN-042979	Using the DBKEY= option in the SQL procedure might cause incorrect results	E9D222
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
ATTENTION (1): Customers must also download and install SAS Base hot fixes E9BD61 and E9BD48. Download E9BD61 Download E9BD61 for SAS with Asian Language Support (DBCS) Download E9BD48 Download E9BD48 for SAS with Asian Language Support (DBCS)

Top ^

Hot Fix Releases for the Week of: May 30, 2011

E9BD56 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017514*	Job submissions to grid manager increasingly slow	E9BA05
SN-017233*	Poor performance with large DATA step and many missing values	E9BA07
SN-017667*	ALERT - Segmentation Violation in task [ DATASETS ] using DELETE statement	E9BA13
SN-017653*	-SGIO option generates I/O error message when ODS or procedure output is to an existing SAS data set	E9BA15
SN-017072	Metadata server service might show starting state but never start	E9BA19
SN-010866*	Text Pad cannot store a single character value in column 1	E9BA29
SN-017847*	SUM function and statement give incorrect output on HP Itanium	E9BA38
SN-013525*	ALERT - File>Open and File>Save might cause SAS to lock up with Jaws screen reader in SAS 9.1	E9BA55
SN-018540*	SAS Display Manager keys fail when you select Tools=>Options=>Output while using the JAWS screen reader with SAS® 9.1.3 on the Windows platform	E9BA55
SN-018790*	SAS® fails when running a very large DATA step on AIX	E9BA69
SN-019040*	Double-byte text strings are truncated when using the host WMF device driver	E9BA76
SN-018929*	Font type WingDings might not work on DBCS SAS® 9.1.3 with the GPLOT procedure	E9BA76
SN-019225*	DDE stops working after hotfix E9BA55 is installed	E9BA85
SN-019224*	PROC APPEND fails with SGIO option on Windows operating systems	E9BA85
SN-019345*	Increased LRECL support for SAS® on MS Windows	E9BA95
SN-019608*	SAS® Metadata server fails to start when system restarted	E9BB05
SN-019640*	HTML output is incorrect when ODS output is appended to an HTML file created by a DATA Step	E9BB14
SN-020233*	Increasing timeout value on UNIX may improve performance	E9BB32
SN-020274	Grid sign-on fails to honor the TCPPORTFIRST and the TCPPORTLAST options	E9BB36
SN-020438*	Unix cleanwork utility does not remove UTILLOC directories	E9BB45
SN-019386	SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]"	E9BB58
SN-020817	Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routine	E9BB58
SN-020870*	SIGNON attempts to SAS® Grid Manager might fail	E9BB58
SN-020646*	Moving the cursor off of a selected Radio Box item before releasing the mouse can incorrectly show updated selection	E9BB75
SN-021112*	A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server	E9BB75
SN-031368*	Poor performance with complex merges on AIX	E9BB95
SN-031098*	ALERT - A SAS® server might become unresponsive on highly loaded systems	E9BB95
SN-031719	Some components from version 6 of SAS/AF® software might cause a read-access violation with repeated use	E9BC09
SN-031795	Dragging the cursor to an unselected item within the Radio Box control can unexpectedly update the internal value for the unselected item	E9BC09
SN-031400	Resetting system time backwards causes negative "real time" value in STIMER output	E9BC09
SN-019028	Truncation errors might occur when using Unicode SAS with UTF-8 encoding to process 8-bit characters	E9BC18
SN-032113	The $EBCDIC format/informat generates incorrect results if ENCODING=UTF8 is set	E9BC18
SN-019330	Problems might occur when you invoke SAS® macros using Microsoft Object Linking and Embedding (OLE) automation submit method	E9BC18
SN-032096	ERROR "SAS Error Event: Error sending status, 1, to SCM. Error 6: The handle is invalid." occurs when stopping the SAS® Metadata Server	E9BC18
SN-032521	ALERT - A Multi-Processing (MP) CONNECT session might not respond in UNIX environments	E9BC18
SN-032547	Data sets written to tape in SAS® 8.2 are not readable in SAS® 9.1.3	E9BC18
SN-032945*	On HP Integrity systems, SAS® 9.1.3 SP4 installation process hangs if memory page size has been set higher than 8Kb	E9BC30
SN-032672*	DDE error "Physical file does not exist, excel|system." occurs after applying hot fix bundle E9BX03 for SAS® 9.1.3 SP4	E9BC30
SN-033403	Segmentation violation and bridge stub errors on AIX	E9BC60
SN-036130	Running large SQL queries in the AIX operating environment can generate results with missing values	E9BC60
SN-033581*	Program with a large number of ELSE statements produces incorrect results on AIX	E9BC60
SN-034651	Using a Japanese or DBCS character in a pathname may cause truncation of file name	E9BC67
SN-035477*	Invalid physical name error when a FILE statement contains certain Shift-JIS characters	E9BC83
SN-034955	The SAS® Metadata Server stops accepting new client connections and returns an error when too many files are open	E9BD12
SN-040822*	Specifying the SAS® system option OPLIST may cause a segmentation violation error in the UNIX environment	E9BD41
SN-041361	Modification datetime stamp is changed on existing version of a SAS® data set when you create a new data set with same name	E9BD44
SN-031894*	The SAS® Metadata Server might appear to hang during a period of high activity	E9BD56
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
ATTENTION (1): To obtain the complete fix for SN-020817 and SN-019386 you must also download and install SAS/CONNECT hot fix E9CT05. The issues described in SN-020817 and SN-019386 will not be fully fixed until both E9BD56 and E9CT05 are applied. ATTENTION (2): To obtain the complete fix for SN-021112 you must also download and install SAS/ACCESS Interface to DB2 hot fix E9D216. The issue described in SN-021112 will not be fully fixed until both E9BD56 and E9D216 are applied. This is not applicable to z/OS sites. Customers running on VMS should download E9BD44. Customers running on Windows should download E9BD59.

Top ^

Hot Fix Releases for the Week of: May 2, 2011

E9BD57 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017916	Japanese characters might not appear correctly in Enhanced Editor	E9BA33
SN-042626	SAS® program files are overwritten with empty files	E9BD57
Select an Available Operating System:
PC:	Windows,   Windows_for_IPF_(64_bit)

Top ^

Hot Fix Releases for the Week of: April 18, 2011

E9BD54 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017147	Output to RECFM=FB SASLIST file may contain carriage control	E9BA11
SN-017380	Client TSO session loops while processing FSBROWSE on library allocated to a SAS/SHARE® server	E9BA11
SN-019281	PROC CIMPORT fails when the transport file is a member of an uncataloged partitioned data set	E9BA41
SN-017797	"ERROR: Physical file does not exist, SYS06144.T115731.RA000.N389610T.INCL.H04" message from %INCLUDE	E9BA41
SN-018423	Control incorrectly appears to return to SAS/AF® application when sorting data on the mainframe	E9BA52
SN-013425	Autoexec may continue processing when leaving MENU entry defined to SHARE server in SAS/AF	E9BA52
SN-013720	TSO may hang when leaving SAS after running SAS/AF application with SAS/SHARE	E9BA52
SN-016476	System abend 0C4 in module SASTK	E9BA52
SN-018430	ERROR: Unable to initialize TCP/IP subsystem returns Condition Code 0	E9BA52
SN-019299	Division-by-zero processing causes severe performance degradation	E9BA75
SN-020327	Contents of a variable change when you pass the variable to the FILEEXIST function	E9BB03
SN-018637	ALTLOG and ALTLIST files may be missing if directed to HFS	E9BB03
SN-019065	DISP is ignored in LIBNAME statement when existing allocation already exists	E9BB03
SN-019522	The FILENAME function for an HFS pathSAS argument generates incorrect results	E9BB03
SN-017038	Limited support in SAS® 9.1.3 SP4 for DSNTYPE=LARGE data sets when running under z/OS Releases V1R7 and later	E9BB25
SN-019842	SAS® 9 software reads all generations of a generation data group controlled by the Storage Management Subsystem	E9BB25
SN-020035	The RELEASE procedure can damage a currently assigned SAS® data library, resulting in an I/O error or U315 abnormal ending message	E9BB34
SN-020459	Performance issues found in SAS® software memory management on the z/OS platform	E9BB44
SN-020583	Concatenation of 257 physical sequential data sets fails when you run SAS® software on z/OS	E9BB57
SN-020905	Warning messages might appear when you read a large file from a UNIX file system	E9BB67
SN-030981	MP CONNECT (multi-process CONNECT) might fail when you use the XMS Access Method in Base SAS® in the z/OS environment	E9BB90
SN-010972	An error occurs when you use the %INCLUDE statement with a fileref that begins with an underscore	E9BC06
SN-033865	Base SAS® software might enter a loop after an input/output (I/O) error or “out of spaceâ€� error occurs	E9BC53
SN-032798	The system ends abnormally with an S0C4 abend code during SAS termination	E9BC53
SN-033040	A %INCLUDE statement for an explicit path of a cataloged disk data set might fail in Base SAS® in the z/OS environment	E9BC53
SN-034459	Using the NODLTRUNCK option to process truncated libraries can result in data loss	E9BC64
SN-033892	A SAS/SHARE® server does not free a library when a client times out	E9BC70
SN-035332	The message "Libname libref is not assigned" might appear if you do not specify an engine	E9BC82
SN-035116	An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70	E9BC82
SN-035225	An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70	E9BC82
SN-036164	ERROR: "Library data set temp.dataset.name does not comply with RECFM=FS requirements or is truncated"	E9BD04
SN-037166	An abend occurs when you specify a user exit in an INFILE or FILE statement or with the ENGINE= option in the FILENAME statement	E9BD16
SN-039847	The error "...NO UNIT AVAILABLE" occurs when you allocate an existing data set	E9BD31
SN-041191	The FILEVAR= option in the INFILE or FILE statement does not work properly with the INFILE/FILE user exit	E9BD45
SN-041261	ALERT - A SAS® job that is running in a z/OS 1.12 operating environment might stop responding when an external file I/O error occurs	E9BD45
SN-041220*	Mixed-case passwords that are submitted to a SAS® server in a z/OS operating environment return a security verification failure to the client	E9BD54
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
ATTENTION: To fully implement the fix for SN-041220, you must also download and install SAS Base hot fix E9BD55. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD54 and E9BD55 are applied.

Top ^

E9BD55 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017704*	ALERT - An update to ensure proper authentication logging on to an Integration Technology Server	E9BA16
SN-032805	Trusted Peer Connections between a SAS® process in a Windows environment and a Metadata Server in a z/OS environment run as public user connections	E9BB40
SN-020384*	If your z/OS user ID begins with special characters, you cannot see pre-assigned libraries from SAS® Enterprise Guide® 4.1	E9BB40
SN-020418*	"ACCESS DENIED" authentication error is not displayed as expected when the Metadata server using a Japanese version of Windows	E9BB40
SN-031165*	IOM messages are truncated in the SAS® Metadata Server log	E9BB96
SN-034913	The SAS® Metadata Server stops responding if a long user ID or password is submitted for authentication	E9BC69
SN-034915	Submitting a blank user ID when logging in to the SAS® Metadata Server causes the server memory usage to increase suddenly	E9BC69
SN-040494	ALERT - A SAS/SHARE® server fails or does not respond when it is run as a Microsoft Windows service	E9BD37
SN-042456	You cannot access files on a SAS/SHARE® server	E9BD51
SN-041220*	Mixed-case passwords that are submitted to a SAS® server in a z/OS operating environment return a security verification failure to the client	E9BD55
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
ATTENTION(1): To fully implement the fix for SN-041220, you must also download and install SAS Base hot fix E9BD54. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD54 and E9BD55 are applied. ATTENTION(2): OpenVMS Alpha customers should install SAS BASE hot fix E9BD62.

Top ^

Hot Fix Releases for the Week of: February 14, 2011

E9BD48 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-016428	DBSLICEPARM creates incorrect syntax when DB2DECPT=,	E9BA58
SN-018162*	System abend SA03 during SAS® termination when DB2 LIBNAME engine with DEFER=YES specified	E9BA66
SN-030942	The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHAR	E9BB80
SN-031862	A U1314 abend might occur when a job sorts an SQL procedure view that references a DB2 table	E9BC14
SN-016338	Using PROC APPEND to insert rows into an Oracle table may report an error as a note	E9BC57
SN-033648	ALERT - The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2	E9BC63
SN-035895	An error occurred Executing the Workspace Job The server is disconnected message might occur if you run a job in SAS® Enterprise Guide®	E9BC90
SN-035991	A generic IOM error occurs when executing a stored process that produces graphics output	E9BC90
SN-036748	The MULTI_DATASRC_OPT= option is ignored when multiple WHERE clause predicates are used in an SQL join operation	E9BD09
SN-037611*	Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment	E9BD14
SN-035879	ALERT - Data imported from a DB2 library may be corrupt	E9BD14
SN-039997	A database error can occur when you submit an SQL query with a LIBNAME statement that uses the MULTI_DATASRC_OPT=IN_CLAUSE option	E9BD33
SN-041748	Using the LIBNAME option MULTI_DATASRC_OPT=IN_CLAUSE can result in an error	E9BD46
SN-042030	Oracle PREPARE error issued when SAS table is empty and no keys are in the WHERE clause	E9BD48
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
ATTENTION (1): To complete the installation of this hot fix, you must also download and install SAS Base hot fixes E9BD42 and E9BD61. Download E9BD42 Download E9BD42 for SAS with Asian Language Support (DBCS) Download E9BD61 Download E9BD61 for SAS with Asian Language Support (DBCS) This hot fix will NOT be fully functional without E9BD42 and E9BD61 applied. ATTENTION (2): Oracle customers running on Solaris for X64 must download and install SAS Oracle hot fix E9OC11 and SAS Base hot fix E9BB64. Download E9OC11 Download E9OC11 for SAS with Asian Language Support (DBCS) Download E9BB64 Download E9BB64 for SAS with Asian Language Support (DBCS) ATTENTION (3): Oracle customers running on all other platforms must also download and install SAS Oracle hot fix E9OC15. Download E9OC15 Download E9OC15 for SAS with Asian Language Support (DBCS) ATTENTION (4): OpenVMS Alpha customers should install SAS BASE hot fix E9BD33. Download E9BD33

Top ^

Hot Fix Releases for the Week of: February 7, 2011

E9BD50 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-031241	"ERROR: Library LIBREF is not assigned" when running the METALIB procedure	E9BA08
SN-017581	ERROR: Invalid physical name for library XXXX is displayed when using Update Table Metadata or PROC METALIB with concatenated libraries	E9BA08
SN-017580	ERROR: This Library is already assigned or cannot be reassigned	E9BA08
SN-017849	PROC METALIB fails to update an SPDS library table metadata with "Error: Invalid Option User."	E9BA30
SN-019486	"ERROR: Invalid memptr" occurs and the SAS® session becomes unresponsive when trying to access a view via a libref with the META LIBNAME engine	E9BB18
SN-020460	Joining two tables can cause your system to stop responding or can cause an access-violation problem	E9BB46
SN-031002	Database passwords are displayed in the SAS® log in clear text	E9BC24
SN-032284	A Read-access violation occurs when running PROC METALIB to update tables that originate from an Adabas database	E9BC24
SN-016116	Pre-Assigned Library fails with an unexpected error has occurred	E9BC42
SN-032376	Access violation occurs when updating metadata for a table that contains multiple indexes with long index names	E9BC66
SN-034840	Running PROC METALIB on a DB2 libray and attempting to update a table that has a foreign key relationship with another table might cause an error	E9BC75
SN-036544	ERROR: "Libname lref not available for use" occurs when assigning a library using the META engine	E9BD05
SN-038292	Libname X not available for use error when password for WebDAV library is more than nine characters	E9BD19
SN-039550	A Read access violation occurs when you use the METALIB procedure to import or register database tables into the SAS® Metadata Repository	E9BD28
SN-042180	Support for implicit pass-through facility with SAS® Scalable Performance Data Server when using the META engine on the LIBNAME statement	E9BD50
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: November 15, 2010

E9BD42 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017745	WHERE clause processing against an SQL view can cause Read Access or Segmentation Violations	E9BA28
SN-031607	Using the BY statement with the formatted ODS destinations can generate incorrect output	E9BA36
SN-017962	The first blank space in the name literal table names gets removed when you set the SYSLAST macro variable or _LAST_ system option	E9BA36
SN-017876	Creating index may cause SAS® to loop	E9BA36
SN-017981	ALERT - Incorrect output with WHERE and BY statements	E9BA36
SN-015813	Read Access Violation in Task (CONNECT) caused by long comments	E9BA50
SN-018156	Invoking an autocall macro which is stored as a SOURCE entry within a catalog may cause errors	E9BA50
SN-018305	Garbage characters in SAS log when localized DBCS SAS is used with products related to the Workspace server	E9BA50
SN-018396	Queries or WHERE clauses run against large data sets can cause SAS/SHARE® server to hang	E9BA50
SN-015882*	A DBCS character that contains the hexadecimal value for a single or double quote might be misinterpreted by the SAS® tokenizer	E9BA67
SN-019372	Performance is poor in the SQL procedure when you use the COUNT(Distinct xxxx) function	E9BB02
SN-019601	The option VALIDVARNAME=UPCASE is not working as expected	E9BB02
SN-019978	Specifying LOGPARM system option may generate INSUFFICIENT AUTHORIZATION messages	E9BB13
SN-019984	Output in the listing is truncated using the DBCS version of SAS	E9BB13
SN-019344	SAS® may ignore indexes during query on 64-Bit UNIX systems	E9BB13
SN-019578	Update Flags from PROC SQL views are propagated by SAS® procedures with OUT= option	E9BB13
SN-020208	The ACCESS=READONLY option in the CATNAME statement is not working correctly	E9BB35
SN-020562	PROC APPEND step may damage BASE data set	E9BB52
SN-021003	Using the %v or #v LOGPARM path directive might cause the workspace server to fail to start and processes to stop responding	E9BB63
SN-030428	Aliased constant values become missing in outer joins and unions	E9BB72
SN-030390	Improvements are now available in relational database optimization via the SQL procedure	E9BB72
SN-019655	Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio	E9BB72
SN-031300	Poor performance occurs when you use views that consist of inner joins from DBMS tables	E9BB98
SN-032375	Errors might occur reading XML files using the XML engine with very long strings	E9BC16
SN-033744	An incorrect buffer break occurs when calling a macro from an EXECUTE statement that specifies a parameter with an "at" sign (@) in the parameter name	E9BC51
SN-036281	PROC REPORT output generated by the CALL EXECUTE routine does not include text or variables generated by a COMPUTE block	E9BC61
SN-034018	MPRINT output generated twice when CALL EXECUTE is used within a macro	E9BC61
SN-035492	Could not find value or Record ID (RID) to do delete on index	E9BC85
SN-035117	ANYDTDTE informat incorrectly interprets invalid date value as a SAS date	E9BC86
SN-035895	An error occurred Executing the Workspace Job The server is disconnected message might occur if you run a job in SAS® Enterprise Guide®	E9BC89
SN-035991	A generic IOM error occurs when executing a stored process that produces graphics output	E9BC89
SN-034012	Column aliases are not passed correctly to GROUP BY or ORDER BY clauses in the SAS® Scalable Performance Data Server®	E9BC93
SN-036280	ALERT - The SQL procedure generates incorrect results when you copy a SAS® data set from one platform to another platform	E9BC93
SN-033084	An SQLPLAN internal error might occur when reference a variable from an in-line view that created the variable from a constant	E9BC93
SN-040951	Arithemetic performed on DATA and TIME data types is not passed to the underlying DBMS in SAS/ACCESS® 9.1.3 software	E9BC93
SN-034678	An SQLPLAN error occurs when you submit a query with a CALCULATED column reference in a CASE expression that contains a GROUP BY clause	E9BC93
SN-036177	Incorrect results might occur when you run a PROC SQL join with an additional WHERE clause against Teradata tables	E9BC93
SN-036202	SQLPLAN internal errors might occur when you reference calculated columns in an SQL procedure	E9BC93
SN-036070	Extraneous code might be added if CALL EXECUTE is used to generate many ODS HTML statements	E9BD01
SN-036592	ALERT - DELETE statement sometimes does not remove qualifying observations	E9BD10
SN-034234	Incorrect results might occur if you use the LIBNAME statement option IP=YES with an SQL procedure that contains data calculations in a WHERE clause	E9BD15
SN-038698	SAS® Enterprise Guide® becomes unresponsive and the SAS® Workspace Server log grows extremely large	E9BD22
SN-040558	Invoking nested autocall macros using des= option causes error	E9BD42
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
ATTENTION (1): To complete the installation of this hot fix, you must also download and install SAS Base hot fixes E9BD61 and E9BD48. Download E9BD61 Download E9BD61 for SAS with Asian Language Support (DBCS) Download E9BD48 Download E9BD48 for SAS with Asian Language Support (DBCS) This hot fix will NOT be fully functional without E9BD61 and E9BD48 applied. ATTENTION (2): For additional configuration instructions for improving relational database optimization, see Problem Note SN-030390 above.

Top ^

Hot Fix Releases for the Week of: September 6, 2010

E9BD39 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-019231	JAVAOBJ component object fails to free semaphores	E9BA82
SN-019812	Values are quoted when DBCS value has same hex code as delimiter character	E9BB17
SN-040559	VVALUE function causes segmentation violation in some cases in SAS® 9.1.3	E9BD39
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

E9BD40 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017915	Memory leak in transcoding routine from MBCS to MBCS	E9BA35
SN-019115	TRANWRD() function has different performance in SAS® 6, and SAS® 8 and SAS® 9.1.3	E9BA80
SN-020675	Garbage characters may result when using PROC CIMPORT to import a transport file containing double-byte character set data	E9BB51
SN-020676	PROC CIMPORT may fail or generate errors when the file contains SBCS Katakana data	E9BB51
SN-030987	Performance problems occur in DBCS SAS® software when you use the RLINK or DLM= options in the FILENAME statement	E9BB97
SN-031391	Transcoding problem occurs between SAS® Japanese encoding shift-jis and EUC	E9BC02
SN-019088	KCVT function has problem handling trailing null character	E9BC23
SN-036269	Inconsistent transcoding using the KCVT function produces incorrect results in SAS® 9.2	E9BC97
SN-040528	Slow performance of DBCS SAS® when UPCASE() function is used	E9BD40
Select an Available Operating System:
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
ATTENTION(1) : To fully implement the fix for SN-019088, you must also download and install SAS/CONNECT hot fix E9CT05. If you are running SAS with Asian Language Support, please download E9CT05 (Asian Language Support). The fix for the problem documented in this SAS Note will not be fully functional unless both E9BC97 and E9CT05 are applied. ATTENTION(2) : This hot fix is available for UNIX customers only. Customers running on PC, VMS and z/OS (OS/390) should download E9BC97. If you are running SAS with Asian Language Support, download E9BC97 (Asian Language Support).

Top ^

Hot Fix Releases for the Week of: August 16, 2010

E9BD38 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017410	SAS® OLAP Server process may crash if slicer contains infinite loop	E9BA01
SN-017408	Permission condition memory is not released when OLAP session closed	E9BA01
SN-017409	SAS® OLAP Server performance enhancements available in SAS 9.1.3 Service Pack 4	E9BA01
SN-018037	PROC OLAP DEFINE statement can allow duplicate calculated members to be created	E9BA34
SN-017931	NUNIQUE values may be incorrect depending on the setting for "Maximum number of region execution threads"	E9BA34
SN-017445	Listing active queries on SAS® OLAP Server can cause server crash	E9BA34
SN-017523	Selecting an OLAP Session in the OLAP Server monitor may cause SAS® Management Console to hang	E9BA34
SN-018020	ALERT - SAS® OLAP Server may error when empty data is passed to certain SAS® functions	E9BA34
SN-017871	ALERT - Drilldown may cause calculated member values to return from the SAS® OLAP Server as missing in Service Pack 4	E9BA34
SN-018018	Complex MDX query within a WITH expression might generate an access violation	E9BA34
SN-018030	SAS® OLAP Server might abend with an OLS_NAMESPACEDELETE traceback	E9BA34
SN-017907	ALERT - OLAP cubes with deep hierarchies may return incorrect result sets	E9BA34
SN-018089	Detailed SAS® OLAP Server logging now outputs SAS OLAP Server option settings	E9BA34
SN-018012	Threadpool options for the SAS® OLAP Server are being overwritten	E9BA34
SN-018198	TKASSERT error might be received when querying a SAS® OLAP cube on z/OS	E9BA34
SN-017449	NON EMPTY CROSSJOIN optimization in SAS® OLAP Server	E9BA47
SN-018254	MDX WHERE clause might return incorrect number of rows resulting in a performance loss	E9BA56
SN-018701	ALERT - Session and Global calculated members might be dropped when using NonEmpty Optimization	E9BA56
SN-018580	Disabling NonEmpty Crossjoin optimization does not have any effect	E9BA56
SN-018794	ALERT - DrillDownMemberTop function might cause crashes in the SAS® OLAP Server	E9BA56
SN-018702	ALERT - Global calculated members might cause crash in SAS OLAP Server with Optimization of Non Empty Crossjoins	E9BA56
SN-018795	ALERT - OLAP queries might return empty results if requesting missing values	E9BA56
SN-018796	ALERT - MDX iif functions that return null values might incorrectly return empty result sets	E9BA56
SN-019048	ALERT - Calculated measures might be dropped from the OLAP result set when using Non Empty Crossjoin Optimization	E9BA56
SN-019164	Memory degradation or access violation could occur when querying a SAS® OLAP cube with member-level security applied	E9BA84
SN-018253	DBCS drillthrough labels might not be rendered correctly	E9BA89
SN-019226	ALERT - Sorted OLAP queries might return incorrect results	E9BA89
SN-019314	Use of global MDX String functions could halt the SAS® OLAP Server	E9BA93
SN-019418	AGGREGATE MDX function might cause slow query performance when member-level security is defined to the OLAP cube	E9BA99
SN-019725	AGGREGATE functions using calculated members containing NUNIQUE measures might cause SAS® OLAP Server to crash	E9BB07
SN-019820	ALERT - NONEMPTYCROSSJOIN function might cause data loss in an OLAP Query	E9BB19
SN-020202	Incorrect totals calculated when aggregate has members in same dimension of the NUNIQUE measure being used	E9BB33
SN-020292	SAS® OLAP Server performance might be worse after applying hotfix E9BA34 or later	E9BB38
SN-020291	ALERT - SAS® OLAP Server AGGREGATE function might return incorrect results on certain calculated members	E9BB38
SN-030537	SAS MDX isEmpty function will not evaluate cells containing character data	E9BB68
SN-020146	ALERT - Total calculations might be incorrect when an NUNIQUE measure is used	E9BB68
SN-013365	Drill-through and ROLAP aggregation tables can fail if the MDX query contains a numeric member	E9BC15
SN-020028	Empty drillthrough result when format width for a column is too small	E9BC15
SN-020652	NON EMPTY CROSSJOIN optimization might drop members from result set	E9BC73
SN-035621	SAS® OLAP Server appears to hang and must be frequently restarted	E9BC88
SN-033970	NON EMPTY CROSSJOIN optimization might cause slower performance with secured data	E9BC92
SN-036393	ERROR: "An OLAP server thread has failed" occurs when a drill-through query returns no records	E9BD03
SN-038401	MDX queries using totals in SAS® Web reports are not optimized by the SAS® OLAP Server	E9BD21
SN-038374	An error related to AVL trees might be returned by OLAP queries	E9BD23
SN-038652	Performance problems might occur on SAS® OLAP Servers that are running multiple requests	E9BD24
SN-038708	"Internal server exception: access violation" and _pthread_body errors received during an OLAP query	E9BD24
SN-040398	The SAS® OLAP Server might fail on Microsoft Windows Server installations	E9BD38
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64
ATTENTION: If you are running SAS Management Console 9.1.3 Service Pack 4, with Implementation-Version=9.1.20050622.20001, you must also download and install SAS Management Console hot fix 913SMC02 to address the issue described in SN-017449. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD38 and 913SMC02 are applied. You do not need to install 913SMC02 if you have any other Implementation-Version of SAS Management Console. ATTENTION: To fully implement the fix for SN-018254, you must also download and install SAS Base hot fix E9BC49. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD38 and E9BC49 are applied.

Top ^

Hot Fix Releases for the Week of: July 19, 2010

E9BD35 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-019525	"Communication error with launch server" message when attempting to start a Workspace server or Stored Process server in SAS® 9.1.3	E9BB08
SN-036254	SAS® 9.1.3 elssrv and jproxy processes not exiting correctly on Solaris zones	E9BD02
Select an Available Operating System:
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64
ATTENTION: You should review Usage Note 32816 for additional post-processing instructions after installing this hot fix.

Top ^

E9BD36 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-036205*	Basic and extended ISO informats and formats 9.2 functionality retrofitted back to 9.1.3	E9BC95
SN-040188	CALL IS8601_CONVERT generates error messages if a null argument is passed to the routine	E9BD36
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: July 5, 2010

E9BD34 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-018463	Access Violation or 0C4 abend in module SASSFM01 when using procedures that use multi-label formats	E9BA61
SN-020189	Statistic labels in PROC TABULATE not displayed in uppercase in table output	E9BB28
SN-020444	Error in PROC TABULATE NLS versions after applying hot fix E9BB28	E9BB42
SN-020359	Variable labels that contain multi-byte character set strings do not split correctly	E9BB53
SN-030679	Page dimension "and" in PROC TABULATE not displayed in uppercase in table output	E9BB81
SN-039321	ALERT - PROC MEANS, SUMMARY, or TABULATE might report incorrect _FREQ_ values when the THREADS and NOTRAP options are specified	E9BD27
SN-040136	PROC TABULATE might give incorrect frequency statistics when only the N statistic is requested and memory is constrained	E9BD34
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: May 17, 2010

E9TE13 for SAS/ACCESS INTERFACE TO TERADATA
Issue(s) Addressed:		Introduced:
SN-018170	Teradata FASTLOAD performance problems in SAS® 9	E9TE01
SN-018429*	Running the Teradata MultiLoad utilty is now supported on z/OS	E9TE02
SN-034604	Running multiple, concurrent processes in SAS® Marketing Automation causes an error in the FastLoad utility in the SAS/ACCESS® Interface to Teradata	E9TE03
SN-019941	Running multiple, concurrent processes causes an error in the FastLoad utility when you use it with the SAS/ACCESS® Interface to Teradata	E9TE03
SN-019939	Using MULTILOAD=YES without CREATE/DROP table rights in the SAS/ACCESS® Interface to Teradata can generate an error	E9TE03
SN-020199	The same query produces different results when submitted using the Pass-Through Facility in SAS/ACCESS® Interface to Teradata and using Teradata BTEQ	E9TE04
SN-020515	An error occurs when you attempt to access a Teradata TTU 8.2 library via SAS/ACCESS® Interface to Teradata 9.1.3 Service Pack 4	E9TE04
SN-031370	LDAP authentication is not supported in SAS/ACCESS® Interface to Teradata	E9TE05
SN-032796	An incorrect error message is sometimes generated when using MODE=Teradata	E9TE06
SN-033955	Using the X versions of Teradata views to retrieve metadata causes performance degradation	E9TE07
SN-035002	An error occurs when you use the MultiLoad facility with SAS/ACCESS® 9.1.3 Interface to Teradata	E9TE08
SN-034729	Teradata's BIGINT data type is not supported in SAS/ACCESS® Interface to Teradata	E9TE08
SN-036348	An error might occur when you invoke the FastExport utility multiple times with the SAS/ACCESS® Interface to Teradata	E9TE09
SN-036369	An error might occur when you invoke the MultiLoad utility multiple times with the SAS/ACCESS® Interface to Teradata	E9TE09
SN-035616	The FastExport module fails when it is run under an object spawner	E9TE09
SN-036176	A Read-access violation occurs when you submit an explicit SQL pass-through query to Teradata	E9TE10
SN-037244	Performance decreases when you use an ORDER BY clause in the SQL procedure with the Teradata FastExport utility	E9TE11
SN-037894	A segmentation violation occurs when you use the MULTILOAD=YES option in the SAS/ACCESS® Interface to Teradata on an HP Itanium operating system	E9TE11
SN-031972	Teradata Tools and Utilities (TTU) 12 is not supported in the AIX environment	E9TE12
SN-038521	An error occurs when you use a LIBNAME statement with LDAP authentication to connect to Teradata in UNIX operating environments	E9TE12
SN-038647	An FNCLOADERROR(519) error occurs when you try to connect to the Teradata database in UNIX operating environments	E9TE12
SN-038840	Teradata Tools and Utilities (TTU) 13 is not suppported in the AIX operating environment	E9TE13
SN-038873	A UTY4015 access-module error occurs when you use the Teradata MultiLoad utility with SAS/ACCESS® Interface to Teradata	E9TE13
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium
Released May 18, 2010 on HPUX, Solaris (64-bit), Linux, HPUX for Itanium Released March 24, 2010 on AIX

Top ^

Hot Fix Releases for the Week of: May 10, 2010

E9OD08 for SAS/ACCESS INTERFACE TO ODBC
Issue(s) Addressed:		Introduced:
SN-037514	Support is now available for reading the MySQL LONGTEXT data type in SAS/ACCESS® Interface to ODBC	E9OD01
SN-018348	"Data truncated" warning issued using SAS/ACCESS® Interface to ODBC to access Informix data	E9OD01
SN-017463	Incorrect length assigned to character variables using SAS/ACCESS® Interface to ODBC and SAS 9.1.3 SP4	E9OD01
SN-018476	READBUFF setting not honored with certain SQL queries against a SAS/ACCESS® Interface to ODBC libref	E9OD02
SN-018538	"Error: DIAG[42000] [HP ODBC driver] ERROR [4118] The cursor query expression is not updatable. (-4118) when using HP ODBC driver SQL"	E9OD02
SN-018988	Netezza support for remote external tables interface for SAS/ACCESS® Interface to ODBC	E9OD03
SN-018990	Incorrect data inserted into DB2 column defined as "CHAR() FOR BIT DATA"	E9OD03
SN-018991	ALERT - Bulkloading into Microsoft SQL Server can lead to loss of precision	E9OD03
SN-019988	PROC DBLOAD fails to insert the correct number of rows when you use SAS/ACCESS® Interface to ODBC	E9OD04
SN-019994	SAS/ACCESS® Interface to ODBC has been enhanced to use the new DB2 API interface for bulk loading and importing data to DB2	E9OD04
SN-019990	A floating-point exception error can occur when you use SAS® Data Integration Studio 3.4 to update table metadata in the SAS/ACCESS® Interface to ODBC	E9OD04
SN-019995	Accessing SYBASE IQ tables with SAS/ACCESS® Interface to ODBC appears to freeze or is extremely slow	E9OD04
SN-019970	SAS/ACCESS® Interface to ODBC does not properly set the SYSDBRC and SYSDBMSG automatic macro variables when a Netezza load fails	E9OD04
SN-032370	DBLOAD procedure does not write non-English characters to Microsoft SQL Server Unicode Field	E9OD05
SN-016094	Invalid characters might display when use SAS/ACCESS® Interface to ODBC to connect a SAS Unicode server to a Unicode database	E9OD05
SN-033733	The LIBNAME statement’s QUALIFIER= option is not honored in subsequent PROC SQL SELECT statements that include the DISTINCT option and that are run against the same libref	E9OD06
SN-035182	The QUALIFIER= option is ignored when you use DISTINCT in a PROC SQL SELECT statement with a libref in SAS/ACCESS® Interface to DB2	E9OD06
SN-033148	An error message occurs when you connect to the HP Neoview database with the SAS/ACCESS® Interface to ODBC engine	E9OD06
SN-035971	An error occurs when you use SAS/ACCESS® Interface to ODBC to append data to a nonexistent DATAllegro table	E9OD07
SN-037477	An incorrect value might be inserted into an Oracle SMALLINT data type when you use SAS/ACCESS® Interface to ODBC on a Linux platform	E9OD08
Select an Available Operating System:
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium

Top ^

Hot Fix Releases for the Week of: April 26, 2010

E9OC15 for SAS/ACCESS INTERFACE TO ORACLE
Issue(s) Addressed:		Introduced:
SN-018149*	Bulkloading Oracle data on OpenVMS may load incorrect data	E9OC02
SN-014205*	SAS/ACCESS Interface to Oracle 9.2.0.5 on OpenVMS Alpha using SAS 9.1.3	E9OC02
SN-018148*	Access Violation with SAS/Access® to Oracle on OpenVMS Alpha	E9OC02
SN-018748*	ORACLE FNA support	E9OC04
SN-019772	The Oracle Database 10g client is supported on the Linux Itanium operating system through the SAS/ACCESS® Interface to Oracle	E9OC05
SN-019771	The Oracle Database 10g client is supported on the HP Itanium operating system through the SAS/ACCESS® Interface to Oracle	E9OC06
SN-020088	The SAS/ACCESS® Interface to Oracle returns incorrect byte lengths for the CHAR and VARCHAR2 columns	E9OC07
SN-020190	The Oracle bulk loader is disabled when you use the -NOXCMD command to invoke the SAS® System	E9OC07
SN-020317	The Oracle 10g client is supported on the Linux operating system through SAS/ACCESS® Interface to Oracle	E9OC08
SN-020739*	An error occurs when you allocate the SQLDAT file externally during Oracle bulk loading under z/OS	E9OC09
SN-020733	Control files and data files might still exist after you bulk load an Oracle table	E9OC09
SN-020736*	Using the Oracle Bulk Loader under z/OS to create multiple Oracle tables might cause an error	E9OC09
SN-020794	An error occurs when there is a space in the directory paths of an SQL*Loader file	E9OC09
SN-020728*	An S0C4 abnormal ending might occur during an Oracle bulk loading task on z/OS	E9OC09
SN-020726*	Externally defined .DAT files are not handled correctly by Oracle Bulk Loader under z/OS	E9OC09
SN-020712	Decreased performance might occur when you use bulk loading in SAS/ACCESS® Interface to Oracle	E9OC09
SN-020710	The BL_DEFAULT_DIR data set option enables you to overide the default path for SQL*LOADER intermediate files when bulk loading to Oracle	E9OC09
SN-020714	TIMESTAMP format does not work for all foreign languages	E9OC09
SN-020734	An error occurs when data that has any date format is loaded to Oracle in a non-English environment	E9OC09
SN-020687	Support for Oracle TIMESTAMP data types added in SAS 9.1.3	E9OC10
SN-031179	Hot Fix E9OC10 for Oracle timestamp support might cause performance degradation	E9OC11
SN-032148	The Table Loader step in a SAS® Data Integration Studio job might not stop processing properly after a constraint violation error	E9OC12
SN-019910	INSERTBUFF= should be set to 1 when Using MODIFY to update an Oracle table	E9OC12
SN-032461	An error occurs because temporary tables are not deleted when you execute SCD2 code	E9OC12
SN-036595	The BL_DELETE_FILES option deletes all file types(.ctl, .log, and .dat) that are created with the bulk loader	E9OC13
SN-035837	Trace messages do not appear for the SQL statements INSERT, UPDATE, and DELETE	E9OC13
SN-033135	"Error: Physical file does not exist" occurs when using SAS® Merchandise Data Integration with Oracle SQL*Loader	E9OC13
SN-037483*	An error occurs when you connect to Oracle from SAS® 9.1.3 with an Oracle 11g client on an Itanium machine in an HP-UX environment	E9OC14
SN-038842	An SQL query that is run against an Oracle table might return incorrect results if a WHERE clause contains the BETWEEN operator and a date operand	E9OC15
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
ATTENTION: To complete the install of this hot fix on the UNIX platforms, you must manually relink the sasora executable. See step 8 of the install instructions for more details. ATTENTION: Customers running on the Solaris for X64 platform should download and install E9OC11. DBCS customers should install the DBCS version of E9OC11. ATTENTION: To complete the installation of this hot fix, OpenVMS_Alpha customers must also download and install hot fix E9BD33. DBCS customers should install the DBCS version of E9BD33. Customers running on all other platforms should download and install hot fix E9BD48. DBCS customers should install the DBCS version of E9BD48. This hot fix will NOT be fully functional without having both E9OC15 and E9BD33 or E9BD48 applied. ATTENTION: This hot fix is intended for customers running the Oracle 9i client or above. Customers running the Oracle 8i client should either upgrade their Oracle client to 9i or above before installing this hot fix, or install E9OC09 instead.

Top ^

Hot Fix Releases for the Week of: February 8, 2010

E9NZ02 for SAS/ACCESS INTERFACE TO NETEZZA
Issue(s) Addressed:		Introduced:
SN-033362*	uploading the MATables in Netezza fails to complete	E9NZ01
SN-030556	The BULKUNLOAD= option is ONLY used as a data set option in SAS/ACCESS® Interface to Netezza	E9NZ01
SN-030464	Japanese characters do not display successfully in SAS® Enterprise Guide® when you access Netezza with SAS/ACCESS® Interface to ODBC or SAS/ACCESS® Interface to Netezza	E9NZ01
SN-035799	An error occurs when you use the Netezza engine in a LIBNAME statement to access Netezza release 4.6	E9NZ02
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium

Top ^

Hot Fix Releases for the Week of: January 4, 2010

E9TE11 for SAS/ACCESS INTERFACE TO TERADATA
Issue(s) Addressed:		Introduced:
SN-018170	Teradata FASTLOAD performance problems in SAS® 9	E9TE01
SN-018429*	Running the Teradata MultiLoad utilty is now supported on z/OS	E9TE02
SN-034604	Running multiple, concurrent processes in SAS® Marketing Automation causes an error in the FastLoad utility in the SAS/ACCESS® Interface to Teradata	E9TE03
SN-019941	Running multiple, concurrent processes causes an error in the FastLoad utility when you use it with the SAS/ACCESS® Interface to Teradata	E9TE03
SN-019939	Using MULTILOAD=YES without CREATE/DROP table rights in the SAS/ACCESS® Interface to Teradata can generate an error	E9TE03
SN-020199	The same query produces different results when submitted using the Pass-Through Facility in SAS/ACCESS® Interface to Teradata and using Teradata BTEQ	E9TE04
SN-020515	An error occurs when you attempt to access a Teradata TTU 8.2 library via SAS/ACCESS® Interface to Teradata 9.1.3 Service Pack 4	E9TE04
SN-031370	LDAP authentication is not supported in SAS/ACCESS® Interface to Teradata	E9TE05
SN-032796	An incorrect error message is sometimes generated when using MODE=Teradata	E9TE06
SN-033955	Using the X versions of Teradata views to retrieve metadata causes performance degradation	E9TE07
SN-035002	An error occurs when you use the MultiLoad facility with SAS/ACCESS® 9.1.3 Interface to Teradata	E9TE08
SN-034729	Teradata's BIGINT data type is not supported in SAS/ACCESS® Interface to Teradata	E9TE08
SN-036348	An error might occur when you invoke the FastExport utility multiple times with the SAS/ACCESS® Interface to Teradata	E9TE09
SN-036369	An error might occur when you invoke the MultiLoad utility multiple times with the SAS/ACCESS® Interface to Teradata	E9TE09
SN-035616	The FastExport module fails when it is run under an object spawner	E9TE09
SN-036176	A Read-access violation occurs when you submit an explicit SQL pass-through query to Teradata	E9TE10
SN-037244	Performance decreases when you use an ORDER BY clause in the SQL procedure with the Teradata FastExport utility	E9TE11
SN-037894	A segmentation violation occurs when you use the MULTILOAD=YES option in the SAS/ACCESS® Interface to Teradata on an HP Itanium operating system	E9TE11
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows

Top ^

Hot Fix Releases for the Week of: November 16, 2009

E9BD18 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-037898	Incorrect results might be produced when the TRANSPOSE procedure uses 2 GB or more of memory	E9BD18
Select an Available Operating System:
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: November 9, 2009

E9OR04 for SAS/OR
Issue(s) Addressed:		Introduced:
SN-036896	An incorrect optimum is produced during credit risk mitigant allocation	E9OR04
Select an Available Operating System:
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: November 2, 2009

E9NW05 for SAS/ACCESS INTERFACE TO HP NEOVIEW
Issue(s) Addressed:		Introduced:
SN-031055	An error occurs when you use SAS/ACCESS® Interface to HP Neoview and an uppercase connection user name to access the Neoview platform	E9NW01
SN-032238	Numeric data that contains decimals in an HP Neoview table are assigned a DOLLARw.d format in the SAS® System	E9NW02
SN-032718*	Bulk loading support has been added to SAS/ACCESS® Interface to HP Neoview	E9NW03
SN-032935	SAS/ACCESS® Interface to Neoview now takes advantage of the Neoview ODBC driver's 4MB Read/Write buffer	E9NW04
SN-037003	An error occurs when you use the Hewlett-Packard Neoview driver 2.3.4 with SAS® 9.1.3	E9NW05
SN-037608	User-generated queries conflict with batch programs and errors occur in SAS/ACCESS® Interface to HP Neoview	E9NW05
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
PC:	Windows
UNIX:	Solaris_(64-bit),   Linux,   HPUX_for_Itanium

Top ^

Hot Fix Releases for the Week of: October 26, 2009

E9OL06 for SAS/ACCESS INTERFACE TO OLE DB
Issue(s) Addressed:		Introduced:
SN-017331	"ERROR: Invalid Character Value for Cast Specification" with SAS/ACCESS Interface to OLE DB and SQL Server 2005	E9OL01
SN-017712	Character strings are padded with trailing blanks when you use the LIBNAME engine in SAS/ACCESS® Interface to OLE DB	E9OL01
SN-018016	Using SAS/ACCESS® Interface to OLE DB with INSERTBUFF incorrectly inserts nulls instead of data	E9OL02
SN-020253	Using SAS/ACCESS® Interface to OLE DB to connect to Informix and Oracle databases results in an incorrect data type	E9OL03
SN-020252	An error might occur when you use SAS/ACCESS® Interface to OLE DB to insert data into a table	E9OL03
SN-031361	SAS/ACCESS® Interface to OLE DB does not pass the complete SQL code to the database for inner and outer joins	E9OL04
SN-032025	Problems occur because SAS/ACCESS® Interface to ODBC and SAS/ACCESS® Interface to OLE DB deliver unique identifiers differently	E9OL05
SN-016337	SAS/ACCESS® Interface to OLE DB does not support the DBTYPE_VARIANT data type	E9OL06
Select an Available Operating System:
PC:	Windows,   Windows_for_IPF_(64_bit)
ATTENTION: Customers must also download and install SAS Base hot fixes E9BD42, E9BD61, and E9BD48. Download E9BD42 Download E9BD42 for SAS with Asian Language Support (DBCS) Download E9BD61 Download E9BD61 for SAS with Asian Language Support (DBCS) Download E9BD48 Download E9BD48 for SAS with Asian Language Support (DBCS)

Top ^

Hot Fix Releases for the Week of: October 19, 2009

E9ST11 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-037320	ERROR: Write Access Violation In Task [ STDIZE ]	E9ST11
SN-037321	Filter node gives A Problem Has Been Encountered on the Server, Write Access Violation In Task [ STDIZE ] errors	E9ST11
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: September 28, 2009

E9R305 for SAS/ACCESS INTERFACE TO R/3
Issue(s) Addressed:		Introduced:
SN-037210	Some informats fail to load when you use SAS/ACCESS® Interface to R/3 to extract SAP data	E9R305
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium

Top ^

E9GR17 for SAS/GRAPH
Issue(s) Addressed:		Introduced:
SN-017238	Plotted line(s) may be missing from a graph created with PROC GPLOT	E9GR02
SN-036987	BOX interpolation with PROC GPLOT might produce different results on UNIX versus Windows	E9GR17
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

E9ML03 for SAS/IML
Issue(s) Addressed:		Introduced:
SN-034587	ALERT - CALL EIGEN in the IML Procedure might modify the input matrix	E9ML03
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: September 14, 2009

E9BC91 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-036111	Potential memory leak in SORT module causes Workspace server to fail	E9BC91
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: August 31, 2009

E9SB09 for SAS/ACCESS INTERFACE TO SYBASE
Issue(s) Addressed:		Introduced:
SN-017567	Connection to Sybase not released when using PROC DBLOAD with the SAS/ACCESS® Interface to Sybase	E9SB01
SN-018210	Incorrect amount of data may be returned when using SAS/ACCESS® Interface to Sybase with threads	E9SB02
SN-017889	Notes, Warnings, or Errors not being issued when attempting to insert into a SYBASE table with triggers	E9SB02
SN-018400	Different column Format is given when using ORDER BY and a date literal within a SELECT statement using the Sybase engine	E9SB03
SN-018792	Text strings greater than 32767 are stored as a blank field when read into SAS® with the DBMAX_TEXT option set	E9SB04
SN-019240	Selecting a column that contains null values for autopartitioning when DBSLICEPARM=ALL might generate incorrect data	E9SB04
SN-019099	SAS/ACCESS® Interface to Sybase with the bulkcopy feature may return a warning when an actual error was issued	E9SB04
SN-019748	Incorrect results can occur when you use the DBSLICEPARM= option with SAS/ACCESS® Interface to Sybase	E9SB05
SN-033901	An error occurs in releases of Sybase that support the data types Date and Time	E9SB06
SN-033896	Performance degradation occurs when you run programs in SAS/ACCESS® Interface to Sybase after you have migrated from SAS® 8.2 to SAS® 9.1.3	E9SB06
SN-035927	ALERT - An error occurs when you append a SAS® data set to Sybase table that has a VARCHAR column with a length greater than 255	E9SB08
SN-036626	ALERT - Incorrect dates are appended to the Sybase table when you use the APPEND procedure with the SASDATEFMT= and the BULKCOPY= options	E9SB09
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX,   Solaris_(64-bit),   Tru_64,   Linux,   HPUX_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: August 24, 2009

E9BD11 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-036617	SAS® might become unresponsive if the FILEDIALOG function is called from an SCL entry on Unix platforms	E9BD11
Select an Available Operating System:
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: July 27, 2009

E9IF03 for SAS/ACCESS INTERFACE TO INFORMIX
Issue(s) Addressed:		Introduced:
SN-019818	Upgrading to SAS®9 causes SAS/ACCESS® Interface to Informix to freeze (lock up) when you try to create or drop the same table repeatedly	E9IF01
SN-033839	An error occurs in SAS/ACCESS® Interface to Informix when you run a database commit action against a non-logging Informix IDS database	E9IF02
SN-036627	Opening an Informix table in a concatenated library may cause errors	E9IF03
Select an Available Operating System:
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   HPUX_for_Itanium

Top ^

Hot Fix Releases for the Week of: July 20, 2009

E9BD07 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-030992	A memory shortage might cause a loop and SC78 abend to occur in SAS® Metadata Server in the z/OS environment	E9BB89
SN-031147	Performance issues might occur with the SAS® OLAP Server in the z/OS environment	E9BC08
SN-031661	Using the TKOPT_CPOOL3= threaded-kernel environment variable causes large amounts of memory to be used	E9BC80
SN-036446	SAS® session intermittently becomes non-responsive upon SAS termination	E9BD07
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)

Top ^

Hot Fix Releases for the Week of: July 13, 2009

E9BC98 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-020378	A segmentation violation might occur during execution of the DOWNLOAD procedure	E9BB41
SN-031087	A floating-point exception error might occur if you use the DOWNLOAD procedure to move a file that is larger than 2 GB	E9BB94
SN-013122	WZX: Invalid Conversion Map Specified	E9BC37
SN-032983	Invalid results occur when you use the DOWNLOAD procedure with the V6TRANSPORT option in SAS® 9.1.3 in the z/OS environment	E9BC37
SN-035807	Observations might be missing after you use the UPLOAD procedure to transfer data sets	E9BC52
SN-033576	SAS® Enterprise Guide® does not detect when SAS data sets are created, updated, or deleted through a grid	E9BC52
SN-036081	The UPLOAD and DOWNLOAD procedures add null values to the ends of variables when you specify a SAS® view with the DATA= data set option	E9BC98
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
Released July 17, 2009 on HPUX, Solaris (64-bit), Tru 64, HPUX for Itanium, Linux for Itanium, Windows for IPF (64 bit), z/OS (OS/390) Released June 29, 2009 on AIX, Linux, Windows
ATTENTION : If you use SAS/CONNECT, you MUST also install E9CT05. If E9CT05 is not installed, this hot fix will not be fully functional AND jobs that include PROC UPLOAD and PROC DOWNLOAD will fail. If you are running SAS with Asian Language Support, please download E9CT05 (Asian Language Support).

Top ^

E9CT05 for SAS/CONNECT
Issue(s) Addressed:		Introduced:
SN-019386	SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]"	E9CT01
SN-020817	Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routine	E9CT01
SN-031089	A floating-point exception error might occur if you use the UPLOAD procedure to move a file that is larger than 2 GB	E9CT02
SN-013122	WZX: Invalid Conversion Map Specified	E9CT03
SN-032983	Invalid results occur when you use the DOWNLOAD procedure with the V6TRANSPORT option in SAS® 9.1.3 in the z/OS environment	E9CT03
SN-031820	An error can occur when you have applied Hot Fix #E9BB97 and you remotely submit PROC UPLOAD with a WHERE clause that points to a remote DBCS machine	E9CT03
SN-034153	Option DBIDIRECTEXEC prevents SAS® Enterprise Guide from opening tables created by PROC SQL	E9CT04
SN-033576	SAS® Enterprise Guide® does not detect when SAS data sets are created, updated, or deleted through a grid	E9CT04
SN-036081	The UPLOAD and DOWNLOAD procedures add null values to the ends of variables when you specify a SAS® view with the DATA= data set option	E9CT05
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
Released July 17, 2009 on HPUX, Solaris (64-bit), Tru 64, HPUX for Itanium, Linux for Itanium, Windows for IPF (64 bit), z/OS (OS/390) Released June 29, 2009 on AIX, Linux, Windows
ATTENTION: To make this hot fix fully functional you must also download and install hot fixes E9BD56 for z/OS and Unix, E9BD59 for Windows, E9BC97 and E9BC98. If you are running SAS with Asian Language Support, please download : E9BD56 (Asian Language Support) for z/OS and Unix, E9BD59 (Asian Language Support) for Windows, E9BC97 (Asian Language Support) and E9BC98 (Asian Language Support)

Top ^

Hot Fix Releases for the Week of: July 6, 2009

E9MQ01 for SAS/ACCESS INTERFACE TO MICROSOFT SQL SERVER
Issue(s) Addressed:		Introduced:
SN-036426	The READBUFF= setting is not honored when certain types of SQL queries are made against a libref in SAS/ACCESS® Interface to Microsoft SQL Server	E9MQ01
Select an Available Operating System:
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   HPUX_for_Itanium
Released July 8, 2009 on HPUX, Solaris (64-bit), AIX Released July 6, 2009 on HPUX for Itanium

Top ^

E9PF08 for SAS/ACCESS INTERFACE TO PC FILES
Issue(s) Addressed:		Introduced:
SN-031105	Variable names truncate to 8 characters when you use the EXPORT procedure and DBMS=DTA to create a Stata file	E9PF01
SN-018769	PROC EXPORT fails for DBMS=JMP with floating point error on the Windows platform	E9PF01
SN-018768	PROC EXPORT to Stata file on Windows platform creates incorrect datatype	E9PF01
SN-018913	PROC EXPORT to JMP® creates numeric fields with 2 decimal places	E9PF01
SN-018993	Certain date formats generate error with PROC EXPORT when exporting to SPSS, STATA, and JMP files	E9PF01
SN-019383	Proc Import of SPSS v12 File Errors and Truncates Long Variable Names	E9PF02
SN-019465	Segmentation violation when importing an Excel 5.0/95 spreadsheet into SAS	E9PF02
SN-020326	The IMPORT Procedure in SAS® Enterprise Guide® does not read Excel data properly	E9PF03
SN-020325	Using the EXPORT procedure with DBMS=XLS in 9.1.3 SAS/ACCESS® Interface to PC Files under UNIX to create a Microsoft Excel file might cause problems with the Excel file	E9PF03
SN-013954*	PROC DBLOAD to create an Excel 5.0 file does not apply numeric formatting correctly	E9PF05
SN-020997	The SAS/ACCESS® Interface to PC files on UNIX cannot read Excel column names that contain Asian phonetic text strings	E9PF05
SN-030657	Missing values can occur in SAS if you use SAS/ACCESS® Interface to PC Files 9.1.3 to pull data from an Excel workbook that resides under UNIX	E9PF06
SN-030646	The SHEET= and RANGE= options are now available in the EXPORT procedure when you use SAS/ACCESS® Interface to PC Files 9.1.3 in the UNIX environment	E9PF06
SN-030961	When using SAS/ACCESS® Interface to PC Files on UNIX platforms to write to Excel, some types of data result in a corrupted XLS file	E9PF06
SN-031711	Formatting errors might occur when exporting SAS® data sets to Stata	E9PF07
SN-031715	Memory request errors occur when using PROC IMPORT DBMS=XLS to import complex Excel spreadsheets	E9PF07
SN-032702*	ALERT - Missing values can be incorrectly filled when you import a Microsoft Access file with the DBSASTYPE= option in a LIBNAME statement	E9PF07
SN-036679	An incorrect Microsoft Excel sheet might be read when you use the XLS engine to read Excel ranges	E9PF08
SN-036681	Invalid header-file errors occur when use the IMPORT procedure with the JMP engine to read JMP® 8 files	E9PF08
SN-034258	An error occurs when you use PROC IMPORT to read an SPSS file with a user-defined format that has the same name as a SAS format	E9PF08
SN-036667*	Time values that exceed 24 hours do not properly export when you use the EXCEL engine	E9PF08
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
PC:	Windows

Top ^

Hot Fix Releases for the Week of: June 29, 2009

E9BC96 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017784	Item in Verion 6 Legacy Radio Box might become unselectable on Linux	E9BA23
SN-019976	Delete key not working when maskCharacter attribute set for Text Entry Control	E9BB73
SN-036214	Segmentation violation error in masked text entry box	E9BC96
Select an Available Operating System:
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: June 22, 2009

E9BC97 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017915	Memory leak in transcoding routine from MBCS to MBCS	E9BA35
SN-019115	TRANWRD() function has different performance in SAS® 6, and SAS® 8 and SAS® 9.1.3	E9BA80
SN-020676	PROC CIMPORT may fail or generate errors when the file contains SBCS Katakana data	E9BB51
SN-030987	Performance problems occur in DBCS SAS® software when you use the RLINK or DLM= options in the FILENAME statement	E9BB97
SN-031391	Transcoding problem occurs between SAS® Japanese encoding shift-jis and EUC	E9BC02
SN-019088	KCVT function has problem handling trailing null character	E9BC23
SN-036269	Inconsistent transcoding using the KCVT function produces incorrect results in SAS® 9.2	E9BC97
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
ATTENTION(1) : To fully implement the fix for SN-019088, you must also download and install SAS/CONNECT hot fix E9CT05. If you are running SAS with Asian Language Support, please download E9CT05 (Asian Language Support). The fix for the problem documented in this SAS Note will not be fully functional unless both E9BC97 and E9CT05 are applied. ATTENTION(2) : This hot fix is available for PC, VMS and z/OS (OS/390) customers only. Customers running on UNIX should download E9BD40. If you are running SAS with Asian Language Support, download E9BD40 (Asian Language Support).

Top ^

E9SB08 for SAS/ACCESS INTERFACE TO SYBASE
Issue(s) Addressed:		Introduced:
SN-017567	Connection to Sybase not released when using PROC DBLOAD with the SAS/ACCESS® Interface to Sybase	E9SB01
SN-018210	Incorrect amount of data may be returned when using SAS/ACCESS® Interface to Sybase with threads	E9SB02
SN-017889	Notes, Warnings, or Errors not being issued when attempting to insert into a SYBASE table with triggers	E9SB02
SN-018400	Different column Format is given when using ORDER BY and a date literal within a SELECT statement using the Sybase engine	E9SB03
SN-018792	Text strings greater than 32767 are stored as a blank field when read into SAS® with the DBMAX_TEXT option set	E9SB04
SN-019240	Selecting a column that contains null values for autopartitioning when DBSLICEPARM=ALL might generate incorrect data	E9SB04
SN-019099	SAS/ACCESS® Interface to Sybase with the bulkcopy feature may return a warning when an actual error was issued	E9SB04
SN-019748	Incorrect results can occur when you use the DBSLICEPARM= option with SAS/ACCESS® Interface to Sybase	E9SB05
SN-033901	An error occurs in releases of Sybase that support the data types Date and Time	E9SB06
SN-033896	Performance degradation occurs when you run programs in SAS/ACCESS® Interface to Sybase after you have migrated from SAS® 8.2 to SAS® 9.1.3	E9SB06
SN-035927	ALERT - An error occurs when you append a SAS® data set to Sybase table that has a VARCHAR column with a length greater than 255	E9SB08
Select an Available Operating System:
UNIX:	AIX

Top ^

Hot Fix Releases for the Week of: June 15, 2009

E9GR16 for SAS/GRAPH
Issue(s) Addressed:		Introduced:
SN-030713	If you use SAS/GRAPH® software with fonts that support only Western characters in non-English locales, text and spacing problems might occur	E9GR10
SN-032294	Text characters might appear as boxes when using the SASEMF or SASWMF device drivers	E9GR11
SN-033596	Overlapping font characters when using fixed-spaced Asian fonts with the SASEMF and SASWMF device drivers	E9GR15
SN-035913	Top of text on the first graph title might be clipped	E9GR16
SN-035914	Incorrect characters could appear on graphics output when using a TrueType font with the SASEMF device driver	E9GR16
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64
Released June 17, 2009 on Windows, Windows for IPF (64 bit), z/OS (OS/390) Released June 12, 2009 on HPUX, Solaris (64-bit), AIX, Tru 64, Linux, HPUX for Itanium, Linux for Itanium, Solaris for x64

Top ^

Hot Fix Releases for the Week of: June 1, 2009

E9D216 for SAS/ACCESS INTERFACE TO DB2
Issue(s) Addressed:		Introduced:
SN-019987	PROC DBLOAD fails to insert the correct number of rows using SAS/ACCESS® Interface to DB2	E9D205
SN-019993	SAS/ACCESS® Interface to DB2 has been enhanced to use the new DB2 API interface for bulk loading and importing to DB2	E9D205
SN-019989	A floating-point exception error can occur when you use SAS® Data Integration Studio 3.4 to update table metadata in the SAS/ACCESS® Interface to DB2	E9D205
SN-020976	An error might occur when you perform concurrent uploads to DB2 partitioned databases	E9D208
SN-020977	SAS/ACCESS® Interface to DB2 cannot obtain the last inserted identity value unless you issue a separate SELECT statement after the INSERT statement	E9D208
SN-021112	A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server	E9D210
SN-033912	The SYSDBRC and SYSDBMSG macro variables are not populated after a bulk-loading failure	E9D214
SN-033902	Incorrect error messages are generated for errors that result when you try to insert rows into DB2 and you use the BULKLOAD=YES option	E9D214
SN-033663	Bulk loading fails when you use the DB2 9.5 client with SAS/ACCESS® Interface to DB2	E9D214
SN-035928	An error occurs when you access data of types BLOB and CLOB from a DB2 table	E9D216
Select an Available Operating System:
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
ATTENTION: This hot fix is intended for Unix and Windows customers running the DB2 Client 8.1 Fix Pack 9 or later. Customers running earlier versions of the DB2 Client should install hot fix E9D203. ATTENTION: To obtain the complete fix for SN-021112 you must also download and install SAS/BASE hot fix E9BC76. The issues detailed in SN-021112 will not be fully fixed until both E9D216 and E9BC76 are applied.

Top ^

Hot Fix Releases for the Week of: May 25, 2009

E9BC68 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017841	Extraneous characters appear for catalog entry descriptions when using PROC CIMPORT	E9BB50
SN-020578	PROC CIMPORT generates "Warning: The transport file is from an earlier SAS release"	E9BB50
SN-020673	Using PROC CIMPORT in DBCS version of SAS® may result in errors or garbage characters if transport file contains data with indexes	E9BB50
SN-020675	Garbage characters may result when using PROC CIMPORT to import a transport file containing double-byte character set data	E9BB50
SN-034280	A "426 Connection closed; transfer aborted" message might appear in your SAS® log when using FTP to send a transport file that was created with CPORT	E9BC68
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

E9ML02 for SAS/IML
Issue(s) Addressed:		Introduced:
SN-034588	ALERT - IML suffers performance problems on HP/UNIX	E9ML02
Select an Available Operating System:
UNIX:	HPUX_for_Itanium

Top ^

Hot Fix Releases for the Week of: May 4, 2009

E9YQ04 for SAS/ACCESS INTERFACE TO MYSQL
Issue(s) Addressed:		Introduced:
SN-018824	Use of MySQL 5.0 client on Windows platforms	E9YQ01
SN-018039	"ERROR: numeric expression requires numeric format"	E9YQ01
SN-018165	A MySQL decimal column is incorrectly being seen as a text column with MySQL 5.0 within SAS®	E9YQ01
SN-018494	Column length is doubled when MySQL LIBNAME engine settings are changed to any DBCS encoding values	E9YQ02
SN-031117	The MySQL client might run out of memory if a large results set is produced with SAS/ACCESS® Interface to MYSQL	E9YQ03
SN-033404	A segmentation violation occurs when a MySQL table contains a binary large object (BLOB) variable	E9YQ03
SN-033847	An error occurs when you run a stored procedure on a MYSQL client with SAS/ACCESS® Interface to MySQL	E9YQ04
SN-035475	SCL code passes a number instead of date when you connect to the MySQL database with SAS/ACCESS® Interface to MySQL	E9YQ04
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX,   Solaris_(64-bit),   Linux,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: April 20, 2009

E9BC81 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-019773	Abend U1314 or traceback notes and messages attempting to read a migrated view from SAS® 8	E9BB11
SN-035112	ALERT - Invalid binary data when tranferring SAS data sets with PROC COPY or CPORT/CIMPORT.	E9BC81
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

E9R304 for SAS/ACCESS INTERFACE TO R/3
Issue(s) Addressed:		Introduced:
SN-035243	An invalid password error is returned when logging on to an SAP system from SAS®	E9R304
Select an Available Operating System:
PC:	Windows
ATTENTION (1): This hot fix should be applied to SAS/Access to R/3 4.2 only. It should not be applied to any other release of this product.

Top ^

Hot Fix Releases for the Week of: April 6, 2009

E9ST10 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-013510	Invalid reference value error if REF='level' used for two or more variables	E9ST03
SN-017517	SCALE= option may be ignored when PARAM=REF or PARAM=EFFECT is specified	E9ST03
SN-019162	Excessive time or memory required with many levels of CLASS variable	E9ST07
SN-016848	ALERT - Incorrect output statistics with DIST=MULT and full-rank CLASS coding	E9ST10
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: March 16, 2009

E9BC43 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-040359	You can use the CATALOG access method in the FILENAME statement to reuse an open fileref in SAS® 9.1.3	E9BA81
SN-019166	Possible memory-related failures when using the CATALOG access method	E9BA81
SN-033414	An error occurs when you include the ENCODING option in the FILENAME statement	E9BC43
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: March 9, 2009

E9BC72 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-020299	PROC PRINT may show missing columns in HTML, LISTING or RTF output	E9BA37
SN-017976	Error about running out of space using PROC PRINT in certain situations	E9BA37
SN-034756	Column data might be blank using the List Data task in SAS® Enterprise Guide®	E9BC72
SN-035147	A variable is missing from PROC PRINT output when using ODS Listing or ODS HTML	E9BC72
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: February 16, 2009

E9BC65 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-034470	Errors can be generated when using PROC SQL to generate XML files with the XML LIBNAME engine	E9BC65
SN-034466	Specifying an invalid width for informats in an XML Map can result in missing values in the data set	E9BC65
Select an Available Operating System:
UNIX:	Solaris_(64-bit)

Top ^

Hot Fix Releases for the Week of: December 15, 2008

E9BC12 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-021021	ALERT - Some national characters in variable names might be converted to other characters when the options VALIDVARNAME=ANY and GETNAMES=YES	E9BB71
SN-034254	How to allow a numeric value enclosed in quotation marks to be read in as numeric variable with PROC IMPORT or the IMPORT WIZARD	E9BC12
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: December 1, 2008

E9BC58 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-033995	Error: "IOM call failed. Internal server exception: floating point divide by zero."	E9BC58
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

E9BC59 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017767*	Export and Import Wizards require Metadata Server fixes	E9BA20
SN-017743*	Login to SAS® web application fails when using an email address as the userid with LDAP authentication	E9BA20
SN-017761*	ALERT - Jobs that are duplicated within a Project repository may lose their connection to Target objects	E9BA20
SN-017860*	ALERT - BI Manager "Import" might cause metadata to be destroyed for all stored processes that contain parameters in SAS 9.1.3 Service Pack 4	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 metadata Project repository	E9BA20
SN-017857*	Exception may occur while exporting a block of objects from the Data Integration Studio custom tree	E9BA20
SN-017854*	ALERT - Incorrect behavior might occur when all items are not selected within a package when performing a metadata import	E9BA20
SN-018452	ALERT - 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
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: November 17, 2008

E9BC54 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-033879	SAS® utilities abend when some diagnostic traps are set on z/OS	E9BC54
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)

Top ^

E9BC55 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-033882*	SAS® might receive a 0C4 abend while performing TCP functions	E9BC55
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)

Top ^

E9BC56 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-019742	An error occurs when attempting to connect to the SAS® Metadata Server and the METAUSER= system option contains an embedded space	E9BB65
SN-033883*	The SAS® object spawner might abend with a 0C4 if certain diagnostic traps are enabled	E9BC56
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
ATTENTION: This hot fix is available for z/OS (OS/390) customers only. Customers running on PC, VMS and UNIX should download E9BB65.

Top ^

E9GR13 for SAS/GRAPH
Issue(s) Addressed:		Introduced:
SN-020254	The SAS® 9 SAS/GRAPH Java applets have an expired digital signature	E9GR06
SN-021087	Application of hotfix E9GR06 causes problems with ODS Graphics and the JAVAIMG device driver	E9GR08
SN-033169	Link tips are not displayed unless the "Show all links" option is checked	E9GR12
SN-033830	Constellation threshold scrollbar does not interact with diagram	E9GR13
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium

Top ^

E9TO01 for SAS/TOOLKIT
Issue(s) Addressed:		Introduced:
SN-033881	SAS/TOOLKIT® modules might receive a 0C4 abend with certain diagnostic traps enabled	E9TO01
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)

Top ^

Hot Fix Releases for the Week of: November 3, 2008

E9BC49 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-018011	SPECIFIED RESOURCE DOES NOT EXIST message with ENCODING=(W5|W6|W9) and SPDE engine	E9BA39
SN-018254	MDX WHERE clause might return incorrect number of rows resulting in a performance loss	E9BA57
SN-018911	"ERROR: System Exiting Status=401" message occurs when multiple processes update a SPD Engine data set	E9BA57
SN-032674	PROC OLAP stops responding even though CPU usage is high	E9BC28
SN-033673	Encountered error in DA-subsystem.	E9BC49
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64
Released November 6, 2008 on HPUX, Solaris (64-bit), AIX, Linux, HPUX for Itanium, Linux for Itanium, Solaris for x64, z/OS (OS/390) Released October 24, 2008 on Windows, Windows for IPF (64 bit)
ATTENTION: To fully implement the fix for SN-018254, you must also download and install SAS Base hot fix E9BD24. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD24 and E9BC49 are applied.

Top ^

Hot Fix Releases for the Week of: October 20, 2008

E9BC45 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-033461	The METAOPERATE procedure does not set the value of the SYSERR automatic macro variable when an error occurs	E9BC45
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: October 6, 2008

E9BC10 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-019947	Writing a SAS® data set to a WebDAV library may fail	E9BB21
SN-020153	"ERROR: An I/O error has occurred on file" when WebDAV server sends back an invalid or unexpected response	E9BB30
SN-030802	A memory overwrite occurs when using WebDAV LIBNAME or FILENAME with hot fix E9BB30 applied	E9BB77
SN-032797	HTTP requests to an HTTPS server fail when the requests are made through a proxy	E9BC10
SN-033408	An error might appear in the SAS log when using the Web-based Distributed Authoring and Versioning (WebDav) filename engine	E9BC10
Select an Available Operating System:
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

E9YQ03 for SAS/ACCESS INTERFACE TO MYSQL
Issue(s) Addressed:		Introduced:
SN-018039	"ERROR: numeric expression requires numeric format"	E9YQ01
SN-018165	A MySQL decimal column is incorrectly being seen as a text column with MySQL 5.0 within SAS®	E9YQ01
SN-018494	Column length is doubled when MySQL LIBNAME engine settings are changed to any DBCS encoding values	E9YQ02
SN-031117	The MySQL client might run out of memory if a large results set is produced with SAS/ACCESS® Interface to MYSQL	E9YQ03
SN-033404	A segmentation violation occurs when a MySQL table contains a binary large object (BLOB) variable	E9YQ03
Select an Available Operating System:
UNIX:	AIX

Top ^

Hot Fix Releases for the Week of: September 29, 2008

E9BC29 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-032570	PROC COPY might not honor the OBS= option	E9BC29
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

E9BC39 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-018202*	'Cannot start remote process' or 'spawner prompt not found' errors might occur when connecting to a UNIX spawner program (sastcpd)	E9BA96
SN-019354*	An error occurs when you use SAS/CONNECT® software to sign on to a remote UNIX machine that is running a UNIX spawner program	E9BA96
SN-016689*	SAS/CONNECT® software spawner does not invoke a remote SAS® session without the full path to SAS	E9BC39
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

E9BC40 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017270	Style not applied properly when sending ODS email	E9BA06
SN-017354	SMTP email only uses the e-mail user ID (rather than the full e-mail address) for authentication	E9BA06
SN-007782	Time stamp calculation when emailing from OS/390	E9BA94
SN-019638	Sending e-mail attachments using SMTP causes a read-access violation	E9BB16
SN-020323	SAS® 9.1.3 and earlier SMTP e-mails do not timeout when block waiting for a response from a SMTP server	E9BB39
SN-018044	Using SMTP e-mail with SAS® 9.1.3 (English version with DBCS and Unicode support) might cause truncated or missing e-mail output	E9BB56
SN-031148	Unable to authenticate e-mail on z/OS	E9BC05
SN-033129	The Simple Mail Transfer Protocol (SMTP) e-mail facility stops sending all e-mails when it encounters an invalid address	E9BC40
SN-010962	SMTP e-mail might stop when an invalid address is encountered	E9BC40
SN-033077	A Read-access violation occurs when a Zip file is attached to e-mail in a DBCS SAS® session	E9BC40
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium

Top ^

Hot Fix Releases for the Week of: September 15, 2008

E9BA59 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-033285	z/OS diagnostic traps might cause Base SAS® software to abend	E9BA59
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)

Top ^

Hot Fix Releases for the Week of: September 8, 2008

E9BC34 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-018857	Using the WebDAV filename option without specifying a full file path might cause problems when writing to or reading from a directory	E9BA70
SN-032831	An error might occur if you use the Web-based Distributed Authoring and Versioning (WebDAV) FILENAME statement	E9BC34
Select an Available Operating System:
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: August 18, 2008

E9BC31 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017241	"ERROR: System abend 0C4 occurred in module SASYHRE8 function YHRMHMR at offset 000420"	E9BA32
SN-032682	Error causes SAS/SHARE® server running with the TTCP option to fill log with error messages	E9BC31
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: August 11, 2008

E9BC33 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-031851	User accounts might show as in the SAS® OLAP Server Monitor in SAS® Management Console	E9BC33
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

E9BC36 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-018812	SAS® Information Map might fail to open in SAS® Enterprise Guide®	E9BA74
SN-019360*	"ERROR: Proc InfoMaps is not available on this operating system." on 64-bit HP-UX and the mainframe	E9BA97
SN-020496	SAS® Information Map Libname Engine might generate "ERROR: Write Access Violation in Task"	E9BB47
SN-020991	SAS® Information Maps with more than 999 data items might fail to open with the SAS Information Map Libname Engine (IMLE)	E9BB69
SN-031143*	Information Map Libname Engine is not supported on Solaris x64	E9BB69
SN-031142*	PROC INFOMAPS is not supported on Solaris x64	E9BB69
SN-030898	Slow processing when using PROC INFOMAPS	E9BB83
SN-019093	Measure captions are limited to 30 characters for OLAP information maps	E9BB83
SN-030897	Error with PROC INFOMAPS when the data source is an OLAP Cube and the password is not stored in the metadata	E9BB83
SN-032856	Denying ReadMetadata on a column does not always prevent denied users from seeing the column	E9BC36
* Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems.
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   HPUX_for_Itanium,   Solaris_for_x64

Top ^

Hot Fix Releases for the Week of: July 14, 2008

E9BC19 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-032177	Negative percentages might be displayed in parentheses when using some language settings	E9BC19
Select an Available Operating System:
PC:	Windows
UNIX:	Solaris_(64-bit),   AIX,   HPUX_for_Itanium

Top ^

Hot Fix Releases for the Week of: June 23, 2008

E9BC26 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-032426	Selection lists or pop-up menus might display behind SAS/AF® frames	E9BC26
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^

E9BC27 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-030979	Performance degradation might occur in SAS®9 if you process VSAM files on a Remote Library Services (RLS) server	E9BB92
SN-032421	Reading VSAM RLS file results in zero records read	E9BC27
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)

Top ^

Hot Fix Releases for the Week of: June 9, 2008

E9BA72 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-018969	Specifying an encoding for the _WEBOUT fileref does not work when you run a stored process with the Stored Process Server	E9BA72
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium
Released June 10, 2008 on z/OS (OS/390)

Top ^

Hot Fix Releases for the Week of: June 2, 2008

E9BC20 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017906	The I/O subsystem has returned error message 'WHERE clause is not allowed with preset index.'	E9BA26
SN-017800	ALERT - WHERE clause is not allowed with preset index	E9BA26
SN-032112	Performance degradation might occur with the SAS® Metadata Server	E9BC20
Select an Available Operating System:
MAINFRAME:	z/OS_(OS/390)
PC:	Windows,   Windows_for_IPF_(64_bit)
UNIX:	HPUX,   Solaris_(64-bit),   AIX,   Tru_64,   Linux,   HPUX_for_Itanium,   Linux_for_Itanium,   Solaris_for_x64

Top ^