What's New? (ARCHIVE)

 

LATEST HOT FIX RELEASES

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

82ML04 for SAS/IML
Issue(s) Addressed:		Introduced:
SN-034587	ALERT - CALL EIGEN in the IML Procedure might modify the input matrix	82ML04
Select an Available Operating System:
PC:	Windows

Top ^

PREVIOUS WEEKS

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

82ST19 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-005135	ALERT - PROC MIXED Produces Incorrect Satterthwaite or KR Degrees of Freedomwith TYPE=FA0(2) on RANDOM Statement and a profile residual variance	82ST03
SN-005132	ALERT - PROC MIXED May Report Wrong Satterthwaite or KR Degrees of Freedom withHeterogeneous Covariance Structures on the RANDOM statement	82ST03
SN-005780	ALERT - The DDFM=SATTERTHWAITE option can cause incorrect results when used inthe presence of both a RANDOM and a REPEATED statement	82ST08
SN-011543	ALERT - The HTYPE=2 option on the MODEL statement in PROC MIXED producesincorrect results	82ST18
SN-011541	ALERT - Incorrect Parameter Estimates When Same Variable List Used on RandomStatement and Model Statement	82ST18
SN-011540	ALERT - ASYCOV Matrix May Be Computed Incorrectly When Scoring Does Not Stop	82ST18
SN-011542	ALERT - Incorrect Covariance Parameter Estimates When LOCAL Option Used withKronecker Product Structures on REPEATED Statement	82ST18
SN-017503	ALERT - Incorrect results with RANDOM statement and TYPE=SP() when random effectinvolves a continuous effect	82ST19
SN-017255	ALERT - PROC MIXED can produce incorrect results for CONTRAST or ESTIMATEstatement involving levels of random effects	82ST19
SN-017511	ALERT - Incorrect output when REPEATED statement uses TYPE=ANTE(1) and data notsorted by repeated effect within each subject	82ST19
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux
Released November 16, 2008 on CMS Released August 18, 2006 on OS/390 Released August 17, 2006 on HPUX 32bit SAS, Solaris 32bit SAS, AIX 32bit SAS, Tru 64, HPUX 64bit SAS, Solaris 64bit SAS, Linux, Windows

Top ^

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

82SB12 for SAS/ACCESS INTERFACE TO SYBASE
Issue(s) Addressed:		Introduced:
SN-004321	Unable to execute multiple SELECT statements with Access to Sybase inVersion 7 and Version 8 of the SAS System	82SB01
SN-005897	BULKLOAD of DOLLAR 12.2 format using SAS/ACCESS Interface to SYBASEproduces an OVERFLOW error	82SB01
SN-005909	Unable to append to a SYBASE table with BULKCOPY if an identity columnexists on the table	82SB01
SN-006327	SQL Pass-Through to Sybase EXECUTE statement allows only one statement	82SB02
SN-006335	Using PROC DBLOAD APPEND with BULKCOPY may cause data corruption	82SB02
SN-008034*	Segmentation Violation in SAS/ACCESS Interface to Sybase when loadinga table with BULKCOPY on Solaris	82SB03
SN-008355	PROC DBLOAD password is not X'd-out in the SAS log when using SAS/ACCESSInterface to Sybase	82SB04
SN-008473	"Error in results set for update" when updating a Sybase view with DATAstep MODIFY	82SB04
SN-008967	SAS/ACCESS Interface to Sybase incorrectly reads the Sybase value'JUN 21 2001 2:03:46:793AM' and generates a warning message	82SB05
SN-009796*	Sybase Open Client 12.5 will not connect with Sybase 11.1 image on AIX	82SB06
SN-009951*	New image for Sybase 12.5 on HPUX	82SB07
SN-010317	Access to Sybase V8.2 is not honoring the database= option for updates	82SB08
SN-010867	Unable to update a Sybase table with an Identity field with SAS V8.2	82SB09
SN-012997	With SAS 8.2 ACCESS TO SYBASE, Notes, warning or errors are not beingissued when attempting to insertinto a Sybase table with triggers using RAISERROR with PROC APPEND	82SB10
SN-001373	ALERT - SAS/ACCESS Version 6 incompatibility issues with SAS Version 7 andVersion 8	82SB10
SN-010795	Wrong Sybase table accessed when using the SCHEMA LIBNAME option	82SB10
SN-015017	Segmentation Violation error issued intermittently when accessing aSybase server that is not available	82SB12
* 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_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux
ATTENTION (1): Before applying this hot fix on Solaris, you must first be running Open Client 12.5. ATTENTION (2): The AIX version of this hot fix should only be applied to systems running AIX 4.3.3 or older.

Top ^

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

82BC43 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004892	Long encrypted message can cause errors in spawner	82BA15
SN-004893*	"Zombie" processes left active on MVS using SAS/CONNECT spawner	82BA15
SN-004936*	OS/390 spawner does not detect expired OS/390 passwords	82BA15
SN-005371*	New RACF Terminal ID Security Support in OS/390 Connect Spawner	82BA15
SN-008812*	OS/390 SAS/CONNECT spawner terminates with a ERRNO=52 or ERRNO=63 due toEPIPE or fork errors	82BB22
SN-010951*	SAS/CONNECT client times out or fails to authenticate when supplyingvalid credentials to UNIX SAS Job Spawner	82BB76
SN-011433	SAS/CONNECT Spawner & Client session "hang" after executing erroneouscode	82BB95
SN-015175*	SAS 8.2 OS/390 Spawner Doesn't set GROUPID correctly when allocating anHFS data set	82BC26
SN-004201*	Potential security exposure for sites that have installed the spawnerprograms (objspawn or sastcpd)	82BC43
* 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:	OS/390
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux
ATTENTION: If you are using the sasauth authentication module with the SAS/CONNECT job spawner, then you must also install hotfix 82BB58. Customers running in a DBCS environment should download 82BB58.

Top ^

Hot Fix Releases for the Week of: August 20, 2007

82BC42 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004606	PROC TABULATE abnormally terminates when the PRINTMISS option is used	82BA16
SN-005685	ALERT - PROC TABULATE may generate unweighted percentage with weighted analysisvariable	82BA47
SN-007709	PROC TABULATE prints 'AND' in page heading section of table in listingoutput	82BB03
SN-011373	Pages are ordered incorrectly when using ALL in the page dimension inTABULATE	82BB82
SN-012302	PROC TABULATE fails to produce error in the ODS destinations in SAS 8.2regarding limit on potential interactions	82BB96
SN-020359	Variable labels that contain multi-byte character set strings do notsplit correctly	82BC42
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: June 11, 2007

82OC08 for SAS/ACCESS INTERFACE TO ORACLE
Issue(s) Addressed:		Introduced:
SN-005272	V8 formats are not compatible with V6 formats with SQL Pass-throughfacility for Char and Number	82OC01
SN-006708	"ERROR: Oracle execute error: ORA-01403: no data found" issued whenattempting to update table using PROC DBLOAD with criteria if no rowsmatch the criteria	82OC02
SN-008203	Bulkload userid/password are passed to the Unix Shell	82OC03
SN-001162	No data found error may occur when trying to update oracle table	82OC04
SN-012675	Using DBSASTYPE=(VAR="CHAR17")) gets value padded with '00'x (binary 0)rather than blanks in Oracle 9 in SAS 8.2	82OC06
SN-009383	Datetime value containing 24 as hour value fails to load into Oracle	82OC07
SN-020088	The SAS/ACCESS® Interface to Oracle returns incorrect byte lengths for the CHAR and VARCHAR2 columns	82OC08
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Solaris_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: May 28, 2007

82BC41 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004241	ALERT - PROC SQL may return incorrect number of observations when using uniqueindex	82BA07
SN-003976	Inconsistent results returned from the PROC SQL pass-through facilityversus the LIBNAME Access engine	82BA12
SN-005899	PROC SQL set operators UNION and OUTER UNION CORRESPONDING returnthe wrong number of rows when used with subqueries	82BA08
SN-005712	ERROR: where clause processing could not obtain memory	82BA46
SN-006247	Reflexive join operations which execute successfully using the SQLprocedure in previous releases of SAS fail in Release 8.2	82BA59
SN-006274	Error: sqlplan internal error: cannot find symbol RIFNOTE, var=1 tag=3occurs using SQL view	82BA59
SN-006741	PROC SQL syntax errors occur when using SET operators UNION and/or OUTERUNION CORR within subqueries	82BA85
SN-004536	PROC SQL UPDATE statement may use excessive CPU time	82BA85
SN-006773	Calls to the CONSTANT function can cause READ ACCESS violations in PROCSQL	82BA85
SN-004451	ALERT - Query submitted to DBMS may generate incorrect results	82BA85
SN-006403	"ERROR: Invalid position -2147483308 for utility file" may beissued when using PROC SQL against SAS/ACCESS SQL views	82BA85
SN-006582	Opening a PROC SQL view twice using %SYSFUNC(OPEN()) causes SAS toterminate and the Display Manager windows to disappear	82BA85
SN-006768	ALERT - Incorrect results from PROC SQL when a query contains the UNION operatorand subqueries	82BA85
SN-006624	SQLPLAN Internal Error occurs when grouping by variable created bysubquery	82BA85
SN-006772	ALERT - Incorrect results from PROC SQL when UNION operator used in a subquery	82BA85
SN-005608	SQL views cannot be used with procedures that do multipass processing	82BA85
SN-005808	PROC SQL ORDER BY uses additional disk space to cache intermediateutility file	82BA50
SN-006829	SAS 8.2 PROC SQL appears to loop when using multiple reflexive joinreferences	82BA85
SN-007824	Incorrect implicit pass-through SQL can be generated from PROC SQLqueries leading to incorrect results	82BA99
SN-007820	Dataset options IDXWHERE and IDXNAME available for use with PROC SQL	82BA99
SN-007319	ALERT - Downloading a SAS Version 6 data set using the V6TRANSPORT option maycorrupt data	82BA99
SN-007829	PROC SQL query containing boolean logic can return incorrect results inspecific cases	82BA99
SN-007827	Segmentation violation produced from PROC SQL query containingsubqueries where both a SAS data set and a DBMS table are referenced	82BA99
SN-007831	PROC SQL join of a view and a SAS data set can return different results	82BA99
SN-007822	Access violation or system abend when executing a PROC SQL direct joinagainst an Oracle table	82BA99
SN-007636	DISTINCT keyword in SQL subquery produces incorrect results or noresults in SAS/ACCESS to ODBC or SAS/ACCESS to DB2	82BA99
SN-007826	ALERT - PROC SQL generates incorrect pass through code when there are multipleOR'd expressions in the WHERE clause	82BA99
SN-007871	Password value is displayed in SAS log when defining an SQL view with aUSING clause which contains a password parameter	82BA99
SN-008356	Integer divide by zero error when displaying column with length of 32767	82BB14
SN-008314	SASHELP.VTABLE displays data set labels unexpectedly	82BB41
SN-007222	ALERT - Outer join of two (2) DBMS tables via a LIBNAME engine with WHERE clausesubsets may generate incorrect results	82BB41
SN-009491	Implicit SQL Passthru may drop important parenthesis from WHEREcondition	82BB41
SN-009727	Aliased columns in SQL views which perform a simple calculation maylose part of the condition	82BB41
SN-009529	Performing a COUNT or COUNT DISTINCT on a renamed column that is part ofa view may result in performance degradation	82BB41
SN-008877*	ALERT - Incorrect results or abends in PROC SQL working with shortened numerics	82BB41
SN-010745	Part of join criteria is lost joining DBMS tables via LIBNAME engine	82BB70
SN-011220	Numeric literals in an ON clause with outer join of some DBMS tables maynot return correct results	82BB70
SN-011239	Final WHERE clause not included in the SQL to be proccessed by thedatabase when using the LIBNAME ACCESS engine	82BB70
SN-018349	"Error Fetching from Cursor" issued when accessing Oracle using PROC SQL	82BB70
SN-011210	Incorrect results from PROC SQL using WHERE= option with indexed tables	82BB70
SN-011802	"Error: sqlplan internal error" when joining a table with an inline view	82BB70
SN-012854	Using LIBNAME engine may result in an incorrect query being generated	82BC08
SN-009514	Accessing DBMS tables with column aliases defined via a view may preventimplicit pass-thru	82BC08
SN-012757	SAS/ACCESS query may return incorrect results when duplicate variablenames exist	82BC08
SN-012760	Applying hotfix 82BB70 causes SQLPLAN Internal Error	82BC08
SN-004451	ALERT - Query submitted to DBMS may generate incorrect results	82BC14
SN-015943	Installation of HOTFIX 82BC08 can cause performance degradation by notusing available index	82BC30
SN-017366	ALERT - The CV() function in PROC SQL returns missing values when the mean ofthe value is less than or equal to 0	82BC39
SN-020046	An error occurs when you apply hot-fix bundle 82bx09 in SAS® 8.2 and SAS®9.1.3	82BC41
* 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:	OS/390,   CMS
PC:	Windows
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux
Released May 30, 2007 on CMS Released May 22, 2007 on HPUX 32bit SAS, Solaris 32bit SAS, AIX 32bit SAS, Tru 64, Intel ABI, IRIX, HPUX 64bit SAS, Solaris 64bit SAS, Linux, Windows, OpenVMS Alpha, OpenVMS VAX, OS/390

Top ^

Hot Fix Releases for the Week of: April 30, 2007

82BC40 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004555*	Subsequent records not read after invalid VBS segment detected	82BA39
SN-004078*	FILENAME statement requests three tape mounts for a single tape	82BA52
SN-004439*	BY variable position may cause errors	82BA52
SN-004435*	Abend S0C1 received in PROC SORT step	82BA52
SN-004629*	RC=0 incorrectly issued when running out of directory space writingto PDS	82BA52
SN-004465*	LIBNAME statement WAIT= option may causeincorrect engine assignment	82BA52
SN-007318*	DIALOG WINDOW of PMENU may issue message indicating an incorrectcommand	82BA08
SN-010474*	The "Save as" function does not work in the French version of SAS® 8.2 in UNIX environments	82BA52
SN-005862*	SASXAL module has increased in size from 300K to 730K from Release 8.1to 8.2	82BA52
SN-005121*	U315, U317, U319, S0C4 and Page Validation Errors when creating ordeleting catalog entries	82BA52
SN-005971*	Cannot connect to OS/390 Spawner with MAXASSIZE=2G in BPXPRM**	82BA57
SN-005642*	SAS Notes referring to Version 8 multivolume SASIO problems	82BA57
SN-006609*	PROC SOURCE abends when processing many members	82BA77
SN-007032*	ZDVw.d informat incorrectly rejects a value of '9'	82BA77
SN-006754*	Performance degradation due to support for long character stringvariables	82BA77
SN-007000*	When attempting to connect to SAS/SHARE server, an @ sign in the useridreceives "Invalid value" message	82BA77
SN-007065*	Loop in SAS/SHARE during termination of server task	82BA77
SN-007066*	Abend SEC6 in BPXAS address space using FTP with MP-Connect for OS/390	82BA77
SN-007513*	System abend S0C1 due to bad call from YN1NDMS at +x'166' after applying82BA77 hot fix	82BA97
SN-007634*	ALERT - Code generation problem could cause data integrity under OS/390	82BA97
SN-007455*	Small numeric values causing problems on OS/390 in Release 8.2	82BA97
SN-006237*	INPUT function returns 0 with invalid data on OS/390	82BA97
SN-007722*	An error can occur when you try to publish with the French-encoded, EBCDIC version of SAS® Integration Technologies	82BB05
SN-007220*	S400 abend, S0C9 abend, or Insufficient Space messages	82BB05
SN-007210*	OS/390 sites may receive S282-048 abend	82BB05
SN-007952*	Blank lines written to terminal when SAS CLIST is called from a CLIST	82BB05
SN-008252*	When using SAS/SECURE with Spawner script signon, -noinheritance must bespecified	82BB15
SN-008432*	Insufficient USS capability causes authorization messages with certainhot fixes applied	82BB15
SN-006517*	B37 abend may cause looping when building an index	82BB21
SN-008820*	SAS failing due to not enough buffers available	82BB21
SN-008435*	System abend S0C1 in function VSPRNTF	82BB21
SN-009007*	Supplied SASEXIT does not work as is for EXITSPPI exit	82BB34
SN-009368*	FILE IN USE message potentially caused by MVS temp data sets beingallocated with the same physical data set name	82BB34
SN-009223*	Errors received when specifying LABEL=EXPDT=YYYDD or EXPDT=YYYY/DDD onFILENAME statement	82BB34
SN-009109*	Problems using Java and SAS/CONNECT for some encoded versions of SAS	82BB34
SN-007394*	Experimental SECPROFILE SAS System option along with a new SVC routine,allows use of the RACF Secured Signon function	82BB34
SN-008927*	ALERT - PROC SQL can produce incorrect results when short numeric variables aresummed	82BB34
SN-009352*	Multivolume sequential file with 0 space on first volume cannot be read	82BB43
SN-005800*	ALERT - Excessive amounts of memory requested by the SAS System can causeunpredictable results when running memory-intensive procedures	82BB43
SN-009622*	IGD306I messages potentially caused by MVS temp data sets beingallocated with the same physical data set name	82BB43
SN-004056*	FILESYSOUT= system option not working correctly	82BB54
SN-007759*	"ERROR: Library is not in a valid format for access methodSASE7" if library was allocated externally in SAS 8.2	82BB68
SN-008206*	"ERROR: Library is not in a valid format for access methodSASEx" in SAS 8.2	82BB68
SN-009162*	"ERROR: Library is not in a valid format for access methodSASE7" in CA/MICS jobs	82BB68
SN-010816*	ALERT - FILENAME CLEAR does not clear the second file in a concatenation	82BB72
SN-009685*	"ERROR: Undetermined I/O Failure." after installing hot fix 82BB43	82BB83
SN-011622*	A SAS Share client that receives a Sx22 abend may be hung and require a cancel	82BB86
SN-011821*	Concurrent access of a sequential SAS data library defined to aSAS/SHARE® server may result in lost data	82BB86
SN-012306*	PMENUS selection of FILE/SAVE AS generates ERROR: Cannot open file	82BC03
SN-014656*	Client task hangs or may abnormally terminate during SAS terminationwhen remote connections exist	82BC22
SN-015538*	PROC SORT fails when routing SORTWKxx data sets to tape	82BC29
SN-014153*	U999/S0C2 abends may occur during SAS/CONNECT spawned client sessiondisconnect if not explicitly clearing LIBNAME before SIGNOFF	82BC29
SN-015716*	Possible incorrect DATETIME/TIME values returned when leap secondsdefined	82BC31
SN-017033	Timestamp on emails are 30+ minutes off from the time it was sent	82BC31
SN-019438	SAS® initialization ends abnormally with an 0C4 error when PCCA moves above the 16M line under Release 1.9 z/OS	82BC40
* 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:	OS/390

Top ^

Hot Fix Releases for the Week of: January 29, 2007

82BB91 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-011620	Data set password no longer valid after transporting SAS libraries withCPORT/CIMPORT	82BB91
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

82BC38 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-019166	Possible memory-related failures when using the CATALOG access method	82BC38
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: November 13, 2006

82BC37 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-014297	z/OS INFILE options may cause FLOWOVER behavior	82BC37
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: October 2, 2006

82IH21 for SAS INTEGRATION TECHNOLOGIES
Issue(s) Addressed:		Introduced:
SN-007626	SAS IOM Server requires manual intervention to cancel orphaned or "hung"SAS process	82IH06
SN-010254*	SAS/Integration Technologies Object Spawner terminates when using blankpassword	82IH11
SN-011902*	Error: Unable to bind to port xxxx (10038 - WSAENOTSOCK) when startingthe Object Spawner	82IH15
SN-013228*	"Conversion of environment block failure" in ObjectSpawner log caused byObject Spawner not sizing DBCS Characters in the Windows environmentvariables correctly	82IH17
SN-013381	SIGHANDLER caught signal 20 or Segmentation Violation in Task (PEBridg) using Object Spawner	82IH18
SN-014312	SAS IOM WorkSpace Server may fail to launch when environment variablecontains DBCS in value	82IH19
SN-018651	A segmentation violation may occur when the Object Spawner is using LDAPauthentication	82IH21
* 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:	Solaris_32bit_SAS
ATTENTION (1): If you are using the sasauth authentication module with the Integration Technologies object spawner, then you must also install hotfix 82BB58. ATTENTION (2): This hot fix has been created for Solaris (32-bit SAS) only. Customers running on other platforms should download 82IH19.

Top ^

Hot Fix Releases for the Week of: January 30, 2006

82SH09 for SAS/SHARE
Issue(s) Addressed:		Introduced:
SN-004909	Cross-architecture catalog access fails to reflect updates by samearchitect clients in a SAS/SHARE environment	82BA30
SN-006581	Cross-architecture RLS catalog access fails to reflect updates by serverside in a SAS/CONNECT environment	82BA30
SN-005507	Loop in SAS/SHARE server with Yielding to Wait messages	82SH01
SN-006053	ALERT - Concurrent updates against shared data on a SAS/SHARE server mightcompromise data integrity	82SH01
SN-005185	"WZX: conversion buffer overflowed" error with SAS/CONNECT RLS	82SH02
SN-005745	ALERT - Version 6 data set header corruption by Version 8 SAS/SHAREcross-architecture client	82SH02
SN-005694	ALERT - VIEWTABLE, Table Viewer, and Data Table WHERE clauses might returnincorrect results through SAS/CONNECT RLS	82SH02
SN-006387	ALERT - Explicit locking against Version 6 SAS/SHARE server can compromise dataintegrity	82SH02
SN-005187	"WZX: conversion buffer overflowed" error with SAS/SHARE RLS	82SH02
SN-005697	ALERT - VIEWTABLE, Table Viewer, and Data Table WHERE clauses might returnincorrect results through SAS/SHARE RLS	82SH02
SN-007225	Using PROC FSEDIT with a WHERE statement in SAS/SHARE across platformsand releases generates error message	82SH04
SN-006337	Memory abends may occur when processing SAS data with a WHERE clausethrough remote library services.	82SH05
SN-009498	CLOSE function through REMOTE engine abends CONNECT server side	82SH06
SN-009371	KEY= value not found in SAS/SHARE cross-platform and cross-releaseenvironment	82SH06
SN-009499	CLOSE function through REMOTE engine abends SHARE server side	82SH06
SN-009549	"Library damaged" error message appears when reading large catalog entrythrough REMOTE engine	82SH06
SN-007490	PROC OPERATE and DISPLAY USER returning two rows of output to SAS/SHAREserver SAS Log	82SH06
SN-010004	Creating new catalog via RLS (Remote Library Services) throughSAS/CONNECT results in appending to existing catalog	82SH07
SN-010876	ALERT - S0C4 in SAS/SHARE Server	82SH07
SN-011360	PROC SQL with SHARE via XMS produces incorrect results	82SH07
SN-014465	"WARNING: Task is in hold-term"	82SH08
SN-016778	ALERT - The NOALLOC option is not completely honored for a server in certain cases	82SH09
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux
ATTENTION: For this hot fix to be fully functional, it must be installed on both the client and server.

Top ^

Hot Fix Releases for the Week of: December 12, 2005

82TE09 for SAS/ACCESS INTERFACE TO TERADATA
Issue(s) Addressed:		Introduced:
SN-005626	FASTLOADING using SAS/ACCESS Interface to TERADATA may cause SAS tocrash in different ways	82TE01
SN-008268	Setting the value for Teradata response buffer length outside of SAS	82TE02
SN-009378	ALERT - Implicit SQL Pass Through query returns incorrect results from the Teradata DBMS	82TE03
SN-010021	SAS/Access to Teradata V8.2 does not work with TUF Version 7.0 andV2R5.0	82TE03
SN-011547	Locking modifiers are not handled correctly when DBKEY= is used	82TE04
SN-011549	Out of memory error may occur if DBKEY= is used to query a Teradatatable	82TE04
SN-011713	SAS allows only CONNECTION=UNIQUE when READ_ISOLATION_LEVEL=ACCESS isused in a LIBNAME statement in SAS/ACCESS Interface to Teradata	82TE05
SN-011822	ALERT - Incorrect WHERE passed to Teradata when OR condition is used with a DATEvariable	82TE05
SN-012331*	SAS/ACCESS Interface to Teradata on AIXR requires a new sastra modulewhen using Teradata TTU 7.1	82TE06
SN-012478	'Error: CLI2: BADBUFRQ(302): Invalid buffer size' returned withSAS/ACCESS Interface to Teradata	82TE07
SN-012639	ALERT - TERADATA large decimal values not inserted correctly with the SAS/ACCESSInterface to Teradata	82TE08
SN-016653*	TTU 8 gives "ERROR: sastra code appendage could not be loaded" messageon MP-RAS	82TE09
* 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:	Intel_ABI
ATTENTION: This hot fix has been created for ABI+ for Intel Architecture customers only. Customers running on other platforms should download 82te08.

Top ^

Hot Fix Releases for the Week of: November 28, 2005

82BC24 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004077*	Running SAS in batch or with the -nodms option causes a secure shellserver to close client	82BA02
SN-004264*	-LOG, -ALTLOG, -PRINT, and -ALTPRINT system options require a file(not a directory) in V8	82BA02
SN-005158*	ALERT - IntrNet Application Server may crash on Windows 2000	82BA33
SN-010845*	Windows 2000 SAS® Integration Technologies server terminates clientconnections	82BA33
SN-004914*	I/O Errors on UNIX encountered due to out of space conditions	82BA02
SN-004509*	ALERT - SAS/SHARE secured server fails to honor host security file access	82BA02
SN-005204*	Nesting the %QLEFT function inside the %QTRIM function causes unexpectederrors	82BA02
SN-005283*	External I/O performance degradation	82BA02
SN-005353*	Problems with PROC PROTO and externally written functions	82BA02
SN-005048	Incorrect output results from PROC FORMAT with the MULTILABEL option	82BA02
SN-005384*	Starting a SAS SSCU Service on Windows 2000 might result in the errormessage "Process terminated abnormally"	82BA02
SN-004316	WHERE returns incorrect number of observations	82BA02
SN-005243	CALL EXECUTE may truncate or repeat generated code	82BA02
SN-004820*	Alpha VMS incorrectly produces negative zero result	82BA28
SN-004870*	Performance problems using Digital TCP/IP services on OpenVMS Alpha	82BA28
SN-005374*	Pull-down menus in SAS Display Manager on OS/390 may be affected byEuropean locales	82BA40
SN-005696*	ERROR: READ ACCESS VIOLATION IN TASK [DATASTEP] message	82BA45
SN-004992	Interrupting and cancelling a DATA step replaces exiting data set	82BA45
SN-005655*	SAS® loops when the X server is terminated	82BA45
SN-005744	WHERE statement returns incorrect results	82BA45
SN-004633	"Error: The yieobtn function is not supported by the SASE7 engine" mightappear when you examine remote SQL views via the SQL dictionary table	82BA45
SN-005975	ERROR: Macro variable name & must start with a letter or underscore	82BA45
SN-006647*	ALERT - Hot fix needed to add SAS/DIRECT to EMC in SAS V8.2 on AIX platforms	82BA62
SN-006109	Exiting SAS within a macro window causes an infinite loop	82BA62
SN-006963	Values within %SYSFUNC on a %DO loop are incorrectly uppercased	82BA78
SN-006566	SAS SHARE server abends with S0C4 in VSRACR1	82BA78
SN-006847	COMPRESS=BINARY may cause problems	82BA78
SN-007001	Missing semicolon on a %LOCAL statement causes system specific errors	82BA78
SN-007193*	"Erroneous internal condition encountered" when using SAS/SHARE	82BA78
SN-007342*	Memory errors running iterative macros on Solaris	82BA78
SN-007983*	Effective group id not honored properly on UNIX	82BB06
SN-007953*	SAS/SHARE server fails after multiple client attempts to update data set	82BB06
SN-008106*	Missing format on the SAS/SHARE server may cause S0C4 abend	82BB06
SN-006932*	Floating exception(coredump) produced when division by 0 occurs on Tru64	82BB06
SN-007882*	ALERT - LIBNAME statement may be assigned to the wrong directory in the 64-bitimplementation of SAS® 8.2 on AIX and Solaris	82BB06
SN-007997*	Copying catalogs with quotas enabled does not report when quotas havebeen exceeded	82BB06
SN-008160*	"Invalid item code or option code" using PARAM= on FILENAME statement	82BB06
SN-008119	Error message generated when creating a V6 SAS data set from a DBMStable containing a character column greater than 200 bytes	82BB16
SN-004165	Catalog becomes corrupted leaving header information unreadable	82BB16
SN-008130*	"Lock is not available" error message appears when running multiple SASjobs with data files pointing to the same directory	82BB16
SN-008571*	Potential performance improvements for SAS batch jobs that create large*.log or *.lst files	82BB16
SN-008638*	SAS crashes with "FILLM exceeds compile-time FD_SETSIZE" on OpenVMS	82BB16
SN-008902	Segmentation Violation or other abend possible when running SAS macrocode from within Risk Dimensions	82BB16
SN-008911	Macro causes errors when tokenizer reads past an end of line	82BB16
SN-009224*	Access via RLS to a large dataset on VMS may cause communication toterminate.	82BB16
SN-008919	WHERE with user-written informat produces incorrect results	82BB32
SN-009349	Errors from EFI, PROC IMPORT, or PROC EXPORT followinghot fix installation	82BB32
SN-009294	Long character value might not be visible in the FSVIEW window	82BB32
SN-009299	PROC UNIVARIATE may abend with the PLOTS option and BY statement	82BB32
SN-009625	PROC TRANSPOSE produces errors when VALIDVARNAME=V6 is specified and82BX04 HotFix is applied	82BB32
SN-009528*	Segmentation Violation in Task ( DATASTEP ] on Solaris and HPUX	82BB42
SN-010150*	Interrupting a SAS process can result in compromised data integrity	82BB42
SN-010057*	"ERROR: I/O error has occurred" when using SASFILE statement on Tru64	82BB42
SN-011025*	X Windows server disconnection leaves a defunct process on UNIX systems	82BB74
SN-011148	PROC APPEND Abends with S0C4, U2096, Segmentation Violation, StackOverflow or Read/Write Access Violations in Task Append	82BB74
SN-011219*	Error condition not trapped when 2K byte parameter limit ofSAS/Integration Technologies Stored Process facility is exceeded	82BB74
SN-011250*	SAS/CONNECT's WAITFOR _ANY_ statement only waits for asynchronousprocesses	82BB74
SN-011386*	Possible Bus Error when using FILENAME PIPE on HP-UX	82BB74
SN-011501*	PROC APPEND takes longer on data sets containing integrity constraints	82BB74
SN-012080*	Secure SAS/SHARE server may allow unprivileged access to files onOpenVMS	82BB94
SN-012376	ALERT - Stratified sample may be incorrect when DATA= and SAMPSIZE= read thesame indexed data set	82BB94
SN-012162	MODIFY Statement uses more I/O in Version 8 than in Version 6	82BB94
SN-012745*	$EBCDIC. informat does not produce correct results in SAS 8.2	82BC02
SN-013275*	The DATETIME() function might return incorrect values over DaylightSaving cutovers for long-running processes such as SAS/SHARE® servers	82BC02
SN-013333*	Sporadic X command failures on Solaris	82BC02
SN-006334*	Ending from Output window may return to Program Editor instead of the AFwindow	82BC11
SN-008832*	SAS code in SUBMIT block may suspend execution	82BC11
SN-007336*	Program Editor window may display on top of fullscreen window	82BC11
SN-013577	ALERT - WHERE clause returns incorrect results with overlapping ranges	82BC11
SN-012911*	Ending from Output window may change execution order of AF windows onUNIX	82BC11
SN-015024*	Illegal Instruction In Task ( DATASTEP ] on Tru64 when submitting alarge DATA step	82BC24
SN-015882	A DBCS character that contains the hexadecimal value for a single or doublequote might be misinterpreted by the SAS® tokenizer	82BC24
SN-016283	A Japanese character that contains the hex value for a single or doublequote may cause the Program Editor to have an incorrect color	82BC24
* 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:	OS/390,   CMS
PC:	Windows
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: November 14, 2005

82BC34 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-005606	Abend after modifying a Master/Detail application and clicking on aVersion 8 control	82BA49
SN-009979	Column label cells may not align properly in _createHTML output	82BB50
SN-013940	Decimal value entered in Table Viewer cell might not match decimal value displayed	82BC18
SN-016426	Special circumstance might clear a DropDownComboBox selection in a TableViewer Control in SAS 8.2	82BC34
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64

Top ^

Hot Fix Releases for the Week of: September 12, 2005

82BC32 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006576*	FTP filename engine fails from Win2000 and WinXP to MVS FTP host	82BB01
SN-006088*	Using FILENAME FTP with MACH= option causes Error: Unknown .netrckeyword	82BB01
SN-012582*	Fatal Unrecoverable I/O error detected in the execution of a DATA Stepwhen using FTP	82BC06
SN-012912	FTP engine may cause SAS to terminate abnormally	82BC32
* 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:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux

Top ^

82RI09 for RISK DIMENSIONS
Issue(s) Addressed:		Introduced:
SN-009079	ALERT - Missing simulated risk factor values result in incorrect informationmeasure and ERROR: Floating Point Overflow	82RI05
SN-010268	Some currencies codes are not supported	82RI06
SN-013938	Support for the Turkish Lira currency code in SAS® Risk Dimensions®	82RI08
SN-016115	SAS Risk Dimensions 3.3 - The Romanian New Leu is Not Supported	82RI09
SN-015769	SAS Risk Dimensions 3.3 - If a project contains a scenario simulationthat does not affect the portfolio value, the project stops and allother analyses are skipped	82RI09
SN-016114	Tolerance for Non Positive Semi Definite Covariance Matrix can not beset in SAS Risk Dimensions 3.3	82RI09
Select an Available Operating System:
PC:	Windows
UNIX:	Solaris_32bit_SAS,   AIX_32bit_SAS
ATTENTION: Risk Dimensions Release 3.3 must be applied before installing this hot fix.

Top ^

Hot Fix Releases for the Week of: July 4, 2005

82BC27 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004336	ERROR: Missing numeric suffix on numbered variable list	82BA68
SN-008830	LVARLEVEL and SORTLIST functions may not clear memory correctly	82BB25
SN-008988*	Various abends might occur with SAS/IntrNet® on OS/390 when running SCLprograms	82BB25
SN-010975*	Segmentation violation in SAS/AF application on Solaris	82BB78
SN-011715	ALERT - webEIS fails when accessing an MDDB containing THAI data and labels	82BB85
SN-012368	_CHANGEMETHOD calls in SAS/AF® applications might generate memory leak	82BB98
SN-010505	May receive Write Access violation when SYSTEM function executes CDcommand	82BC17
SN-013657	VIEWTABLE window may be slow to close after creating WHERE subset with"Lookup distinct values"	82BC17
SN-014134	Slow performance with FWRITE function in SAS Component Language	82BC20
SN-015187	Current token length warning when remote submitting long SAS statementfrom SCL program	82BC27
* 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:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Solaris_64bit_SAS,   Linux
Released July 6, 2005 on HPUX 32bit SAS, Solaris 32bit SAS, AIX 32bit SAS, Tru 64, Solaris 64bit SAS, Linux, OS/390 Released June 6, 2005 on Windows

Top ^

Hot Fix Releases for the Week of: June 13, 2005

82BC28 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-015525	Setting a diagnostic trap might cause an abend for XMS servers in SAS/SHARE® or SAS/CONNECT® software under z/OS	82BC28
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: May 16, 2005

82OC07 for SAS/ACCESS INTERFACE TO ORACLE
Issue(s) Addressed:		Introduced:
SN-005272	V8 formats are not compatible with V6 formats with SQL Pass-throughfacility for Char and Number	82OC01
SN-008203	Bulkload userid/password are passed to the Unix Shell	82OC03
SN-001162	No data found error may occur when trying to update oracle table	82OC04
SN-012675	Using DBSASTYPE=(VAR="CHAR17")) gets value padded with '00'x (binary 0)rather than blanks in Oracle 9 in SAS 8.2	82OC06
SN-009383	Datetime value containing 24 as hour value fails to load into Oracle	82OC07
Select an Available Operating System:
VMS:	OpenVMS_Alpha

Top ^

82TE08 for SAS/ACCESS INTERFACE TO TERADATA
Issue(s) Addressed:		Introduced:
SN-005626	FASTLOADING using SAS/ACCESS Interface to TERADATA may cause SAS tocrash in different ways	82TE01
SN-008268	Setting the value for Teradata response buffer length outside of SAS	82TE02
SN-009378	ALERT - Implicit SQL Pass Through query returns incorrect results from the Teradata DBMS	82TE03
SN-010021	SAS/Access to Teradata V8.2 does not work with TUF Version 7.0 andV2R5.0	82TE03
SN-011547	Locking modifiers are not handled correctly when DBKEY= is used	82TE04
SN-011549	Out of memory error may occur if DBKEY= is used to query a Teradatatable	82TE04
SN-011713	SAS allows only CONNECTION=UNIQUE when READ_ISOLATION_LEVEL=ACCESS isused in a LIBNAME statement in SAS/ACCESS Interface to Teradata	82TE05
SN-011822	ALERT - Incorrect WHERE passed to Teradata when OR condition is used with a DATEvariable	82TE05
SN-012331*	SAS/ACCESS Interface to Teradata on AIXR requires a new sastra modulewhen using Teradata TTU 7.1	82TE06
SN-012478	'Error: CLI2: BADBUFRQ(302): Invalid buffer size' returned withSAS/ACCESS Interface to Teradata	82TE07
SN-012639	ALERT - TERADATA large decimal values not inserted correctly with the SAS/ACCESSInterface to Teradata	82TE08
* 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:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS
ATTENTION: This hot fix should only be applied to systems running AIX 5.1 or greater. ATTENTION: This hot fix should only be downloaded by customers running HP-UX, Solaris, AIX, Windows, and OS/390. Customers running ABI+ for Intel Architecture should download 82te09 instead.

Top ^

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

82BC23 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004359	ALERT - PROC MEANS/SUMMARY/TABULATE/REPORT may produce additional classificationgroups and not apply format to printed output	82BA09
SN-005747	PROC MEANS/SUMMARY may produce incorrect output with numeric CLASSvariables	82BA53
SN-010802	ALERT - PROC MEANS/SUMMARY produces null ID values in the output data set	82BB73
SN-014737	ALERT - PROC MEANS/SUMMARY incorrectly assigning missing value to weightedstatistic	82BC23
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: March 7, 2005

82BC21 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-003691	SMTP email method ignores the -EMAILID option	82BA04
SN-007172*	"Bus Error In Task [ DATASTEP ]" when sending electronic mail fromwithin 64-bit SAS Version 8.2 with SMTP access method	82BA04
SN-013786	By default all EMAIL attachment filenames are given an extension	82BC21
* 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:	OS/390
PC:	Windows
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux

Top ^

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

82BC19 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-008880	Attachments within Form Viewer or Data Form are lost when frame is saved	82BB26
SN-004028	FRAME entry with custom tab order might become corrupted aftersynchronization	82BC19
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64
Released February 15, 2005 on HPUX 32bit SAS, Solaris 32bit SAS, AIX 32bit SAS, Tru 64 Released February 2, 2005 on Windows

Top ^

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

82FS03 for SAS/FSP
Issue(s) Addressed:		Introduced:
SN-006147	Potential security exposure with SAS/FSP	82FS01
SN-010748	ALERT - Underscores or pad character may remain as part of value	82FS02
SN-014026	Generic critical error when resizing the FSVIEW window in X WindowSystem environment	82FS03
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: January 31, 2005

82D226 for SAS/ACCESS INTERFACE TO DB2
Issue(s) Addressed:		Introduced:
SN-006004	"ERROR: CLI open cursor error: [IBM][CLI Driver] CLI0125E Functionsequence error" issued when using SAS/ACCESS Interface to DB2	82D203
SN-005708	ERROR: SQL0514N The cursor "SQLCURCS297" is not in prepared state	82D203
SN-006276	New special queries added for ODBC and DB2: SQLDataSources and SQLDBMSInfo	82D203
SN-005997	Access AS400 data using Access Interface to ODBC can causeERROR:[merant][ODBC driver][DB2/400] Keyword FOR not expected.	82D203
SN-005996	Access Interface to ODBC when accessing MSAccess data may causedata to be overwritten if using APPEND operations	82D203
SN-005330	PROC APPEND to SQL Server using BCP option will insert data incorrectly	82D203
SN-004053	CLI ODBC driver error occurs when using SAS/ACCESS Interface to ODBC toaccess LANDMARK DBMS, through LANDMARK ODBC driver	82D203
SN-006323	Unable to get a single connection when using CONNECTION=GLOBALREAD asdocumentation would suggest	82D204
SN-006293	Read Isolation Level defaults to CR when using SAS/Access Interface toDB2	82D203
SN-006312	CLI prepare error using NEON ODBC Driver to access DB2 on MVS withAccess to ODBC on Windows	82D208
SN-007694*	NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows	82D210
SN-008603	"No data found" error occurs when trying to update or delete from a DB2table with SQL	82D216
SN-009478	SAS/Access to ODBC accessing Sql Server 2000 generates errors whencreating a temporary table	82D220
SN-009773	Incorrect data when KEEP= contains a field with a binary data type	82D220
SN-009914	/UNIQUE option does not work with ODBC engine for character typedvariables	82D220
SN-011355*	WARNING: SQL3107W There is at least one warning message in the messagefile received when using the bulkload feature of SAS/ACCESS	82D220
SN-012061	"ERROR: No matching observation was found in MASTER data set" is issuedafter applying HOTFIX 82D220	82D222
SN-013571	Bus Error accessing DBMS table via SAS/ACCESS to ODBC with rowset_size>1	82D225
SN-013504	SQL3061N received bulkloading to a DB2 table in a DBCS database	82D225
SN-013980	DB2 bulk loader does not run with ALLOW READ ACCESS enabled	82D226
SN-008941	Segmentation violation when specifying DBCOMMIT= on the LIBNAMEstatement for DB2	82D226
* 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_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Linux
ATTENTION (1): To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied. ATTENTION (2): The HP-UX version of this hot fix should only be applied to systems running HP-UX 11.x.

Top ^

82OD09 for SAS/ACCESS INTERFACE TO ODBC SERVER
Issue(s) Addressed:		Introduced:
SN-006004	"ERROR: CLI open cursor error: [IBM][CLI Driver] CLI0125E Functionsequence error" issued when using SAS/ACCESS Interface to DB2	82OD01
SN-005708	ERROR: SQL0514N The cursor "SQLCURCS297" is not in prepared state	82OD01
SN-006276	New special queries added for ODBC and DB2: SQLDataSources and SQLDBMSInfo	82OD02
SN-005997	Access AS400 data using Access Interface to ODBC can causeERROR:[merant][ODBC driver][DB2/400] Keyword FOR not expected.	82OD01
SN-005996	Access Interface to ODBC when accessing MSAccess data may causedata to be overwritten if using APPEND operations	82OD01
SN-005330	PROC APPEND to SQL Server using BCP option will insert data incorrectly	82OD01
SN-004053	CLI ODBC driver error occurs when using SAS/ACCESS Interface to ODBC toaccess LANDMARK DBMS, through LANDMARK ODBC driver	82OD01
SN-006323	Unable to get a single connection when using CONNECTION=GLOBALREAD asdocumentation would suggest	82OD02
SN-006293	Read Isolation Level defaults to CR when using SAS/Access Interface toDB2	82OD02
SN-006312	CLI prepare error using NEON ODBC Driver to access DB2 on MVS withAccess to ODBC on Windows	82OD03
SN-007694*	NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows	82OD04
SN-008603	"No data found" error occurs when trying to update or delete from a DB2table with SQL	82OD05
SN-009478	SAS/Access to ODBC accessing Sql Server 2000 generates errors whencreating a temporary table	82OD06
SN-009773	Incorrect data when KEEP= contains a field with a binary data type	82OD06
SN-009914	/UNIQUE option does not work with ODBC engine for character typedvariables	82OD06
SN-011355*	WARNING: SQL3107W There is at least one warning message in the messagefile received when using the bulkload feature of SAS/ACCESS	82OD06
SN-012061	"ERROR: No matching observation was found in MASTER data set" is issuedafter applying HOTFIX 82D220	82OD07
SN-013571	Bus Error accessing DBMS table via SAS/ACCESS to ODBC with rowset_size>1	82OD08
SN-013504	SQL3061N received bulkloading to a DB2 table in a DBCS database	82OD08
SN-013980	DB2 bulk loader does not run with ALLOW READ ACCESS enabled	82OD09
SN-008941	Segmentation violation when specifying DBCOMMIT= on the LIBNAMEstatement for DB2	82OD09
* 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_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Linux
ATTENTION (1): To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied. ATTENTION (2): The HP-UX version of this hot fix should only be applied to systems running HP-UX 11.x.

Top ^

82IH19 for SAS INTEGRATION TECHNOLOGIES
Issue(s) Addressed:		Introduced:
SN-007626	SAS IOM Server requires manual intervention to cancel orphaned or "hung"SAS process	82IH06
SN-010254*	SAS/Integration Technologies Object Spawner terminates when using blankpassword	82IH11
SN-011902*	Error: Unable to bind to port xxxx (10038 - WSAENOTSOCK) when startingthe Object Spawner	82IH15
SN-013228*	"Conversion of environment block failure" in ObjectSpawner log caused byObject Spawner not sizing DBCS Characters in the Windows environmentvariables correctly	82IH17
SN-013381	SIGHANDLER caught signal 20 or Segmentation Violation in Task (PEBridg) using Object Spawner	82IH18
SN-014312	SAS IOM WorkSpace Server may fail to launch when environment variablecontains DBCS in value	82IH19
* 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:	OS/390
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux
ATTENTION (1): If you are using the sasauth authentication module with the Integration Technologies object spawner, then you must also install hotfix 82BB58. ATTENTION (2): To complete the installation of this hot fix on Windows systems, you must also download and install hot fix 82BB92 for Windows. The Integration Technologies object spawner will not work for Windows systems without both 82IH19 and 82BB92 applied. ATTENTION (3): Customers running on Solaris (32-bit SAS) should download 82IH21.

Top ^

Hot Fix Releases for the Week of: January 10, 2005

82ML03 for SAS/IML
Issue(s) Addressed:		Introduced:
SN-013523	IML MAD function may loop or hang	82ML02
SN-013913	IML MAD function can cause Privileged Instruction Violation	82ML03
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: December 13, 2004

82BC15 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-013656	Using PROC SORT with the TAGSORT option causes a bus error or unalignedaccess messages	82BC15
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: November 29, 2004

82BC01 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-012361	Production version of the enhanced XML Engine is available for SAS 8.2via hotfix	82BC01
Select an Available Operating System:
MAINFRAME:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux
Released December 1, 2004 on OS/390 Released July 30, 2004 on Windows

Top ^

82BC12 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-005070*	Authentication through SSPI not functioning properly in SAS Release 8.2	82BA24
SN-004499	The UNIX and PC Spawner program using the -INHERITANCE option causesVQTCP FATAL ERROR messages	82BA92
SN-010354	ERROR: Administrator permission denied	82BB62
SN-010293*	Kerberos SSPI authentication fails in SAS® 8.2	82BB62
SN-011759	WSAECONNREFUSED when using SAS Connect in 3270 Full Screen Mode (TN3270)	82BC12
* 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_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: November 22, 2004

82BC14 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004241	ALERT - PROC SQL may return incorrect number of observations when using uniqueindex	82BA07
SN-003976	Inconsistent results returned from the PROC SQL pass-through facilityversus the LIBNAME Access engine	82BA12
SN-005899	PROC SQL set operators UNION and OUTER UNION CORRESPONDING returnthe wrong number of rows when used with subqueries	82BA08
SN-005712	ERROR: where clause processing could not obtain memory	82BA46
SN-006247	Reflexive join operations which execute successfully using the SQLprocedure in previous releases of SAS fail in Release 8.2	82BA59
SN-006274	Error: sqlplan internal error: cannot find symbol RIFNOTE, var=1 tag=3occurs using SQL view	82BA59
SN-006741	PROC SQL syntax errors occur when using SET operators UNION and/or OUTERUNION CORR within subqueries	82BA85
SN-004536	PROC SQL UPDATE statement may use excessive CPU time	82BA85
SN-006773	Calls to the CONSTANT function can cause READ ACCESS violations in PROCSQL	82BA85
SN-004451	ALERT - Query submitted to DBMS may generate incorrect results	82BA85
SN-006403	"ERROR: Invalid position -2147483308 for utility file" may beissued when using PROC SQL against SAS/ACCESS SQL views	82BA85
SN-006582	Opening a PROC SQL view twice using %SYSFUNC(OPEN()) causes SAS toterminate and the Display Manager windows to disappear	82BA85
SN-006768	ALERT - Incorrect results from PROC SQL when a query contains the UNION operatorand subqueries	82BA85
SN-006624	SQLPLAN Internal Error occurs when grouping by variable created bysubquery	82BA85
SN-006772	ALERT - Incorrect results from PROC SQL when UNION operator used in a subquery	82BA85
SN-005608	SQL views cannot be used with procedures that do multipass processing	82BA85
SN-005808	PROC SQL ORDER BY uses additional disk space to cache intermediateutility file	82BA50
SN-006829	SAS 8.2 PROC SQL appears to loop when using multiple reflexive joinreferences	82BA85
SN-007824	Incorrect implicit pass-through SQL can be generated from PROC SQLqueries leading to incorrect results	82BA99
SN-007820	Dataset options IDXWHERE and IDXNAME available for use with PROC SQL	82BA99
SN-007319	ALERT - Downloading a SAS Version 6 data set using the V6TRANSPORT option maycorrupt data	82BA99
SN-007829	PROC SQL query containing boolean logic can return incorrect results inspecific cases	82BA99
SN-007827	Segmentation violation produced from PROC SQL query containingsubqueries where both a SAS data set and a DBMS table are referenced	82BA99
SN-007831	PROC SQL join of a view and a SAS data set can return different results	82BA99
SN-007822	Access violation or system abend when executing a PROC SQL direct joinagainst an Oracle table	82BA99
SN-007636	DISTINCT keyword in SQL subquery produces incorrect results or noresults in SAS/ACCESS to ODBC or SAS/ACCESS to DB2	82BA99
SN-007826	ALERT - PROC SQL generates incorrect pass through code when there are multipleOR'd expressions in the WHERE clause	82BA99
SN-007871	Password value is displayed in SAS log when defining an SQL view with aUSING clause which contains a password parameter	82BA99
SN-008356	Integer divide by zero error when displaying column with length of 32767	82BB14
SN-008314	SASHELP.VTABLE displays data set labels unexpectedly	82BB41
SN-007222	ALERT - Outer join of two (2) DBMS tables via a LIBNAME engine with WHERE clausesubsets may generate incorrect results	82BB41
SN-009491	Implicit SQL Passthru may drop important parenthesis from WHEREcondition	82BB41
SN-009727	Aliased columns in SQL views which perform a simple calculation maylose part of the condition	82BB41
SN-009529	Performing a COUNT or COUNT DISTINCT on a renamed column that is part ofa view may result in performance degradation	82BB41
SN-008877*	ALERT - Incorrect results or abends in PROC SQL working with shortened numerics	82BB41
SN-010745	Part of join criteria is lost joining DBMS tables via LIBNAME engine	82BB70
SN-011220	Numeric literals in an ON clause with outer join of some DBMS tables maynot return correct results	82BB70
SN-011239	Final WHERE clause not included in the SQL to be proccessed by thedatabase when using the LIBNAME ACCESS engine	82BB70
SN-011210	Incorrect results from PROC SQL using WHERE= option with indexed tables	82BB70
SN-011802	"Error: sqlplan internal error" when joining a table with an inline view	82BB70
SN-012854	Using LIBNAME engine may result in an incorrect query being generated	82BC08
SN-009514	Accessing DBMS tables with column aliases defined via a view may preventimplicit pass-thru	82BC08
SN-012757	SAS/ACCESS query may return incorrect results when duplicate variablenames exist	82BC08
SN-012760	Applying hotfix 82BB70 causes SQLPLAN Internal Error	82BC08
SN-004451	ALERT - Query submitted to DBMS may generate incorrect results	82BC14
* 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:	AIX_64bit_SAS

Top ^

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

82BC13 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-013669	PROC APPEND incorrectly sets SYSERR	82BC13
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

82BC16 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006986	Version 8 on CMS does not recognize Version 5 style user-written formatsand informats	82BA69
SN-008881	"ERROR: SORT could not complete because of insufficient memory" on CMS	82BB23
SN-013712	NOLOG and NOPRINT options do not work on CMS	82BC16
Select an Available Operating System:
MAINFRAME:	CMS

Top ^

Hot Fix Releases for the Week of: November 1, 2004

82ET03 for SAS/ETS
Issue(s) Addressed:		Introduced:
SN-013491	ALERT - Differencing of dependent and independent variables may not be performedas specified	82ET03
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: October 18, 2004

82SB11 for SAS/ACCESS INTERFACE TO SYBASE
Issue(s) Addressed:		Introduced:
SN-004321	Unable to execute multiple SELECT statements with Access to Sybase inVersion 7 and Version 8 of the SAS System	82SB01
SN-005897	BULKLOAD of DOLLAR 12.2 format using SAS/ACCESS Interface to SYBASEproduces an OVERFLOW error	82SB01
SN-005909	Unable to append to a SYBASE table with BULKCOPY if an identity columnexists on the table	82SB01
SN-006327	SQL Pass-Through to Sybase EXECUTE statement allows only one statement	82SB02
SN-006335	Using PROC DBLOAD APPEND with BULKCOPY may cause data corruption	82SB02
SN-008034*	Segmentation Violation in SAS/ACCESS Interface to Sybase when loadinga table with BULKCOPY on Solaris	82SB03
SN-008355	PROC DBLOAD password is not X'd-out in the SAS log when using SAS/ACCESSInterface to Sybase	82SB04
SN-008473	"Error in results set for update" when updating a Sybase view with DATAstep MODIFY	82SB04
SN-008967	SAS/ACCESS Interface to Sybase incorrectly reads the Sybase value'JUN 21 2001 2:03:46:793AM' and generates a warning message	82SB05
SN-009796*	Sybase Open Client 12.5 will not connect with Sybase 11.1 image on AIX	82SB06
SN-009951*	New image for Sybase 12.5 on HPUX	82SB07
SN-010317	Access to Sybase V8.2 is not honoring the database= option for updates	82SB08
SN-010867	Unable to update a Sybase table with an Identity field with SAS V8.2	82SB09
SN-012997	With SAS 8.2 ACCESS TO SYBASE, Notes, warning or errors are not beingissued when attempting to insertinto a Sybase table with triggers using RAISERROR with PROC APPEND	82SB10
SN-001373	ALERT - SAS/ACCESS Version 6 incompatibility issues with SAS Version 7 andVersion 8	82SB10
SN-010795	Wrong Sybase table accessed when using the SCHEMA LIBNAME option	82SB10
SN-012913	ALERT - "A Sybase Context Allocation Failed. sassyb:s_ctx: init of open clientfailed" error when using SAS/ACCESS Interface to Sybase on AIX	82SB11
* 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:	AIX_32bit_SAS
ATTENTION This hot fix should only be applied to systems running AIX 5.1 or greater. AIX customers running AIX 4.3.3 or an earlier version must download 82SB12.

Top ^

Hot Fix Releases for the Week of: October 11, 2004

82BC10 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004436	Assert Data error message after hiding statistic labels and expanding awebEIS report	82BA06
SN-005262	Column order may change after performing an Analysis Sort	82BA06
SN-005259	Error displaying a hierarchy level when all values are hidden	82BA06
SN-005260	Computed columns calculated from restricted analysis variables arevisible	82BA06
SN-005265	MDDB Table Exception invalid dimension error running with MiddlewareServer	82BA06
SN-005263	HOLAP Data Group Values marked SHOW in Access Control not found	82BA06
SN-004934	Holap data sources may not always be correctly joined	82BA06
SN-005668	Modifying column colors or fonts may not work and could generate errors	82BA06
SN-005670	ALERT - Formats on Computed Values are not honored using a Bookmark in WebEIS	82BA06
SN-003072	Values for a class variable that have been restricted in Access Controlmay display in Subset by Dimension window.	82BA06
SN-005669	Java exception received when accessing Bookmarks using Access Control	82BA06
SN-005671	ERROR: Invalid list item index message received in WebEIS using NUNIQUEand ACL	82BA06
SN-005196	Cannot register an MDDB if SAS/MDDB Server common products not licensed	82BA06
SN-005264	Informat not honored in WHERE statement of PROC SQL when using a StarSchema	82BA06
SN-007171	Olap reports may fail when using user-defined display formats and noinformats	82BA67
SN-007174	Mixed case variable names could generate error on _GET_UNIQUE_VALUES_	82BA67
SN-007163	Columns Database not used when synchronizing MDDB metadata	82BA67
SN-007176	Only the computed values on current level of report get saved	82BA67
SN-007177	Drilling back up after applying a subset may not display correct report	82BA67
SN-007169	Metabase sort order not honored for registered MDDB tables	82BA67
SN-007179	Mixed case analysis variable used in a computed value may generateerrors	82BA67
SN-007168	Unable to programatically register computed columns with long names	82BA67
SN-007178	Computed values may not appear when level is expanded and subset applied	82BA67
SN-007180	Subset specified on a drill variable may not be applied	82BA67
SN-007181	Computed columns defined with mixed case analysis variable names may notdisplay	82BA67
SN-007042	Program halt in SASHELP.MDDB.TRANSLATE.SCL when EIS catalog notavailable	82BA67
SN-010373	ASSERT DATA and segmentation violation in task SASAZF errors whensorting MDDB column	82BB64
SN-013296	Analysis Variable sort is extremely slow	82BC10
Select an Available Operating System:
MAINFRAME:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS

Top ^

Hot Fix Releases for the Week of: September 20, 2004

82IH16 for SAS INTEGRATION TECHNOLOGIES
Issue(s) Addressed:		Introduced:
SN-008715	OS/390 Integration Technologies object spawner supports UNIX System Services	82IH16
Select an Available Operating System:
MAINFRAME:	OS/390
ATTENTION: To complete the installation of this hot fix, you must also download and install hot fix 82BB92 for OS/390. This hot fix will NOT be fully functional without both 82IH16 and 82BB92 applied.

Top ^

Hot Fix Releases for the Week of: September 13, 2004

82BC07 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004969	Incorrect results returned when using the LIBNAME statement or ACCESSview to query a DBMS	82BA29
SN-006278	"ERROR: The maximum number of DBMS opens for this engine has beenreached"	82BA58
SN-005276	Error joining multiple ACCESS views or DBMS tables from differentlibrefs with CONNECTION=GLOBALSHARED	82BA63
SN-009683	New DB2 LIBNAME option to reduce number of concurrent DB2 threads	82BB44
SN-012757	SAS/ACCESS query may return incorrect results when duplicate variablenames exist	82BC07
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux
ATTENTION: To complete the installation of this hot fix, you must also download and install hot fix 82BC08. This hot fix will NOT be fully functional without 82BC08 applied.

Top ^

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

82BC09 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004378	Detail data not subsetted correctly when class variable value has an "="character	82BA05
SN-004379	Detail data may not be subsetted correctly after changing filter byvalues	82BA05
SN-004377	All variables may not be displayed when reaching through to the detaildata	82BA05
SN-004376	Download to spreadsheet may not work when class variable value containsan "&" character	82BA05
SN-004437	Reach Through to detail data in MDDB Report Viewer returns ERROR:Calling function DELLIST	82BA05
SN-006298	Javascript Error when analysis variables names are in mixed case	82BA05
SN-006300	Javascript Error on the Options page after viewing a Graph	82BA05
SN-006011	Java Script Error in MDDB Report Viewer	82BA05
SN-006301	Detail data is not subsetted when variable value contains "+" character	82BA05
SN-006297	Applying a filter may remove drilldown capabilities	82BA05
SN-006296	MDDB Report Viewer does not fully support secure server	82BA05
SN-004375	Filters may not work when you specify a label for the class variable	82BA05
SN-004858	MDDB Report Viewer problem when using Access Controls or AUTH=HOSTauthentication	82BA05
SN-006715	Filters may not be applied when class value contains special characters	82BA05
SN-006726	Statistic values may be shifted left in the MDDB Report Viewer	82BA05
SN-006727	Detail data returns only columns registered in the Repository for MRV	82BA05
SN-006728	Values unavailable by ACL may still be listed under MRV filters	82BA05
SN-006719	Error when using Access Control and Total are turned off	82BA05
SN-006718	Where Clause not applied to Detail Data correctly	82BA05
SN-006716	Graph may not display when Standard Graph GIF is selected	82BA05
SN-007047	After drilldown on a value with '+', applying a filter causes error	82BB93
SN-012367	Errors with filter functionality in MDDB Report Viewer	82BB99
SN-012821	Sorting fails in MDDB Report Viewer with custom statistic labels	82BB99
SN-012823	Down action occurs in MDDB Report Viewer with filters	82BB99
SN-012822	Graph Applet might fail when running MDDB Report Viewer hot fix 82bb93	82BB99
Select an Available Operating System:
MAINFRAME:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS

Top ^

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

82D223 for SAS/ACCESS INTERFACE TO DB2
Issue(s) Addressed:		Introduced:
SN-004819	SAS/ACCESS view referencing DB2 table with character column wider than200 bytes may produce errors	82D201
SN-004982	CPU time significantly higher with SQL pass-through to DB2	82D201
SN-005647	ALERT - Using LOCATION= in PROC ACCESS can cause error or incorrecttable to be used	82D202
SN-006736	Specifying DBKEY= to reference a composite index can produce one ofseveral error messages	82D206
SN-007182	YEAR, MONTH and DAY functions may be passed to DB2	82D207
SN-007857	Performance problem when using a libref pointing to a remote locationthat includes the option preserve_names=yes	82D212
SN-007858	Incorrect list of tables is displayed when a libref is pointing to aremote location	82D212
SN-008508	Specifying a composite index with DBKEY= may cause a S0C4 abend	82D215
SN-007859	Setting a special register via DBCONINIT does not always work	82D219
SN-009720	Extra and unexpected commits may occur after applying DB2 hotfix	82D219
SN-002892	DB2 SQLCODE +535 received updating DB2 table	82D221
SN-013020	Performance issues with regard to padding of decimals	82D223
Select an Available Operating System:
MAINFRAME:	OS/390
ATTENTION: To complete the installation of this hot fix, you must also download and install hot fix 82BC07 for OS/390. This hot fix will NOT be fully functional without both 82D223 and 82BC07 applied.

Top ^

82D224 for SAS/ACCESS INTERFACE TO DB2
Issue(s) Addressed:		Introduced:
SN-006505	ALERT - PROC DB2UTIL passes incorrect datetime to DB2 when updating a DB2timestamp column	82D209
SN-007854	Running PROC DB2UTIL may cause a S0C4 abend	82D211
SN-006839	SAS DATETIME format is used in PROC DB2UTIL delete operations ratherthan the correct DB2 format	82D214
SN-008806	Non-zero return codes when executing PROC DB2UTIL do not set the jobreturn code to 4	82D217
SN-009054	ALERT - PROC DB2UTIL's SSID= option does not work correctly starting in Version8	82D218
SN-013018	ALERT - DB2UTIL passes incorrect value when updating a decimal variable	82D224
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

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

82BC04 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-009073	The PROC SOURCE BEFORE statement with ALIAS option does not actuallygenerate the resulting output file card before the member	82BB30
SN-012572	PROC SOURCE adds the ./ ALIAS syntax when generating IEBCOPY controlcards for a particular member with alias	82BC04
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

82GR09 for SAS/GRAPH
Issue(s) Addressed:		Introduced:
SN-012514	PROC GREMOVE incorrectly defines polygons where holes should be	82GR09
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

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

82BC05 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004155	ALERT - Value in combo box may display incorrectly when using Pageup/Pagedownkeys	82BA17
SN-006146	May receive ERROR: Parameter 1 to method setcamText was not character	82BA23
SN-006942*	ALERT - Value may not be stored with combo box using Dropdown List	82BA91
SN-010956	Memory is not freed when terminating all objects in a Work Area	82BB77
* 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_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: June 14, 2004

82BB97 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004574	Spanned headers in PROC REPORT may cause incorrect cellwidth when usingODS	82BA10
SN-004501	PROC TABULATE repeats statistics in all ODS destinations except listingand output data sets	82BA10
SN-004756*	ODS RTF and ODS PRINTER may take a long time to process	82BA10
SN-005256*	Column headers may wrap incorrectly when generating output with the ODSRTF destination	82BA10
SN-005950*	ODS PDF does not render Latin1 (ISO 8859-1) encoding correctly	82BA54
SN-005951*	ODS PDF and RTF can not produce double-byte encoded output	82BA54
SN-005949*	ODS PDF will only use Times, Helvetica, and Courier as default font	82BA54
SN-005596	Output data set may not be generated when using the ODS OUTPUT statement	82BA44
SN-009281	The OVERPRINT system option does not work correctly with the ODS PRINTERand PDF destinations	82BB37
SN-010318	User-defined format can not be updated when applied to a variablecreated with ODS OUTPUT	82BB61
SN-010411	ALERT - Customized template may cause observations to not appear in ODS PRINTERoutput	82BB61
SN-005994	Using a PREIMAGE= specification and STARTPAGE= with ODS PRINTER causeserrors	82BB61
SN-009366	ODS PRINTER does not close registry keys properly	82BB84
SN-012168*	Gaining file compression with ODS PDF in SAS 8.2	82BB97
SN-005481*	"File is damaged but is being repaired" message when opening PDF filescreated by ODS	82BB97
SN-005486*	PDF output generated with ODS and the DATA step may have columns withincorrect alignment	82BB97
SN-012125*	Setting CONTENTS= to null using ODS PDF generates errors	82BB97
SN-005089*	Recursive node generated in PDF table of contents when DESCRIPTION= orCONTENTS= options set to null	82BB97
SN-006634*	Errors generated when multiple styles applied to ODS PDF output	82BB97
SN-011001*	Viewing PDF files with Adobe Reader 6.0 may display strange characters	82BB97
SN-012660*	Creating links to other pages from within a PDF file created by ODS	82BB97
SN-006928*	Page breaks suppressed using a null TITLE statement and NONUMBER andNODATE options	82BB97
* 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:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: April 19, 2004

82MQ01 for SAS/ACCESS INTERFACE TO MICROSOFT SQL SERVER
Issue(s) Addressed:		Introduced:
SN-009609	SAS/ACCESS Interfaceto Microsoft SQL Server fails when running on HPUX11using the sabhhpt binary	82MQ01
Select an Available Operating System:
UNIX:	HPUX_32bit_SAS

Top ^

Hot Fix Releases for the Week of: April 5, 2004

82RB02 for SAS/ACCESS INTERFACE TO ORACLE RDB
Issue(s) Addressed:		Introduced:
SN-009955	WHERE clause may not be passed to Rdb database for processing, causingpoor performance	82RB01
SN-012091	"Unterminated string" and "Access violation" errors when runningSAS/ACCESS Interface to Oracle/Rdb	82RB02
Select an Available Operating System:
VMS:	OpenVMS_Alpha,   OpenVMS_VAX

Top ^

82GR08 for SAS/GRAPH
Issue(s) Addressed:		Introduced:
SN-012056	Error: Write access to member is denied	82GR08
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: March 29, 2004

82BB92 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006832*	Performance of TCP/IP may be slow on CMS	82BA64
SN-006117*	Communication subsystem failure XVT is already active	82BA64
SN-008801*	The object spawner requires parameters exceeding 100 characters whencommunicating with an LDAP server	82BB10
SN-011902*	Error: Unable to bind to port xxxx (10038 - WSAENOTSOCK) when startingthe Object Spawner	82BB92
* 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:	OS/390,   CMS
PC:	Windows
ATTENTION (1): To complete the installation of Integration Technologies hot fix 82IH16 on OS/390, this hot fix (82BB92) must also be applied. ATTENTION (2): To complete the installation of Integration Technologies hot fix 82IH17 on Windows, this hot fix (82BB92) must also be applied. The Integration Technologies object spawner will not work without both 82IH17 and 82BB92 applied.

Top ^

Hot Fix Releases for the Week of: March 22, 2004

82TE05 for SAS/ACCESS INTERFACE TO TERADATA
Issue(s) Addressed:		Introduced:
SN-005626	FASTLOADING using SAS/ACCESS Interface to TERADATA may cause SAS tocrash in different ways	82TE01
SN-008268	Setting the value for Teradata response buffer length outside of SAS	82TE02
SN-009378	ALERT - Implicit SQL Pass Through query returns incorrect results from the Teradata DBMS	82TE03
SN-010021	SAS/Access to Teradata V8.2 does not work with TUF Version 7.0 andV2R5.0	82TE03
SN-011547	Locking modifiers are not handled correctly when DBKEY= is used	82TE04
SN-011549	Out of memory error may occur if DBKEY= is used to query a Teradatatable	82TE04
SN-011713	SAS allows only CONNECTION=UNIQUE when READ_ISOLATION_LEVEL=ACCESS isused in a LIBNAME statement in SAS/ACCESS Interface to Teradata	82TE05
SN-011822	ALERT - Incorrect WHERE passed to Teradata when OR condition is used with a DATEvariable	82TE05
Select an Available Operating System:
UNIX:	AIX_32bit_SAS
ATTENTION: The AIX version of this hot fix should only be applied to systems running AIX 4.3.3 or older. AIX customers running AIX 5.1 or greater must download 82TE07.

Top ^

Hot Fix Releases for the Week of: March 15, 2004

82BB89 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-011775	XVT ALREADY ACTIVE message after abnormal termination when XMSSAS/Connect processes were active	82BB89
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: March 8, 2004

82BB88 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004576	ALERT - IN operator in PROC SQL sometimes gives incorrect results	82BA13
SN-011805	Result of assignment of an array element may be incorrect	82BB88
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: March 1, 2004

82BB90 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-011798	Memory leak accessing Excel data using OLE Automation	82BB90
Select an Available Operating System:
PC:	Windows

Top ^

82ET02 for SAS/ETS
Issue(s) Addressed:		Introduced:
SN-011597	ALERT - Results are incorrect for models with transformed input variables	82ET02
Select an Available Operating System:
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: February 23, 2004

82IH14 for SAS INTEGRATION TECHNOLOGIES
Issue(s) Addressed:		Introduced:
SN-009451	Unexpected client termination during long running job hangs SAS session	82IH09
SN-011772	SHOW DETAIL against a large MDDB while simultaneously opening a tablemay cause SAS Human Capital Management to hang	82IH14
Select an Available Operating System:
MAINFRAME:	OS/390
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

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

82QC05 for SAS/QC
Issue(s) Addressed:		Introduced:
SN-005428	ALERT - Interval censoring syntax may lead to incorrect results	82QC01
SN-011688	Unable to Read Utility File and/or Read Access Violation error(s) withbinomial or Poisson analysis	82QC05
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: February 9, 2004

82GR07 for SAS/GRAPH
Issue(s) Addressed:		Introduced:
SN-007110	SAS/GRAPH Java applets do not load properly with Java plug-in 1.3.1_01or later	82GR07
Select an Available Operating System:
MAINFRAME:	OS/390
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: February 2, 2004

82IF04 for SAS/ACCESS INTERFACE TO INFORMIX
Issue(s) Addressed:		Introduced:
SN-005027	Unable to query an INFORMIX table containing a DATETIME precisiondatatype	82IF01
SN-005894	"ERROR: Informix EXECUTE Error: Already in transaction" is issued inSAS 8.2	82IF01
SN-007957	TEXT fields are truncated when using SAS/ACCESS Interface to Informixwith PROC SQL Passthrough	82IF02
SN-002782	Using the dbkey= option results in 0 rows being selected from a Informixtable	82IF03
SN-007212	INFORMIX table names cannot be longer than 18 characters when usingthe LIBNAME Access method	82IF04
Select an Available Operating System:
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64

Top ^

Hot Fix Releases for the Week of: January 12, 2004

82BB58 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-007277	ALERT - SAS/Integration Technologies Object Spawner does not honor expiredpasswords when using SASAUTH authentication	82BA89
SN-010961*	SAS® servers do not honor expired passwords when using C2 EnhancedSecurity on Compaq Tru64 UNIX servers	82BB58
SN-010238	SAS Clients fail to authenticate when using blank or empty password	82BB58
* 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_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux
ATTENTION (1): If you are using the sasauth authentication module with the Integration Technologies object spawner, then you must also install hotfix 82IH19. ATTENTION (2):If you are using the sasauth authentication module with the SAS/CONNECT job spawner, then you must also install hotfix 82BC43. Customers running in a DBCS environment should download 82BC43.

Top ^

82CT09 for SAS/CONNECT
Issue(s) Addressed:		Introduced:
SN-005062	"Warning: Current token length of x is not supported; token has beentruncated"	82CT01
SN-006280	Transfer of catalogs between different host platforms causessegmentation violations	82CT02
SN-006288	ERROR: COMMUNICATION SUBSYSTEM PROTOCOL ERROR: SEND ATTEMPTED IN RECEIVESTATE.	82CT02
SN-007725	SAS Stray Processes remaining on Remote Hosts	82CT05
SN-009775	'Write Access Violation in Task (CONNECT)' when performing a controlbreak of a PROC UPLOAD/DOWNLOAD within SAS/CONNECT	82CT06
SN-010167	Remote submit of 29 or more %sysrput statements may result in "OUT OFRESOURCES" error.	82CT07
SN-010727	Client/Server processes can hang when an asynchronous process abnormallyterminates	82CT08
SN-010655	RLS assignment after SIGNON causes Segmentation Violation	82CT08
SN-007758	HTML output is not visible in the RESULTS window when producing HTMLoutput from a remote submit	82CT09
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux
ATTENTION: For this hot fix to be fully functional, it must be installed on both the Release 8.2 client and the Release 8.2 server.

Top ^

Hot Fix Releases for the Week of: December 8, 2003

82GN03 for SAS/GENETICS
Issue(s) Addressed:		Introduced:
SN-008626	ALERT - The Chi-Square statistic in PROC FAMILY may be incorrectly reported forthe COMBINED STDT	82GN01
SN-008611	ALERT - Haplotype frequencies and linkage disequilibrium measures in PROC ALLELEmay be incorrectly reported	82GN01
SN-008644	ALERT - PROC FAMILY with RCTDT option and some missing genotypes may giveincorrect results	82GN01
SN-008629	ALERT - PROC FAMILY may incorrectly report TDT Chi-square results when the SDTand COMBINE options are also specified	82GN01
SN-008628	ALERT - PROC FAMILY with SDT option and one allele with zero contribution oftenincorrectly reports degrees of freedom for the SDT	82GN01
SN-008627	ALERT - PROC FAMILY reports incorrect results when using character variables	82GN01
SN-008625	ALERT - The Likelihood Ratio Test Statistic for the Marker-Trait Association inPROC HAPLOTYPE is incorrect	82GN01
SN-008624	ALERT - Tests for Haplotype-Trait Association table in PROC HAPLOTYPE mayreport incorrect chi-square and p-value	82GN01
SN-008620	The NDATA option causes the WHERE statement not to function with four ofthe SAS GENETICS procedures	82GN01
SN-008737	READ ACCESS VIOLATION may occur in PROC ALLELE when requesting linkagedisequilbrium measures	82GN01
SN-009096	ALERT - PROC ALLELE incorrectly computes haplotype frequencies when two locihave the same exact allele and genotype frequencies	82GN02
SN-011381	ALERT - PROC ALLELE generates floating point zero divide error	82GN03
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

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

82BB80 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-009317	Using the LIKE condition with an escape sequence against an indexedcolumn returns 0 matches	82BB27
SN-011266	SQL join using LIKE syntax on variables fails with Illegal Instructionerror	82BB80
Select an Available Operating System:
MAINFRAME:	OS/390,   CMS
PC:	Windows,   OS/2
VMS:	OpenVMS_Alpha,   OpenVMS_VAX
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Intel_ABI,   IRIX,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

Hot Fix Releases for the Week of: November 10, 2003

82BB81 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-011146	Session can lock when hitting PF-Keys too fast	82BB81
Select an Available Operating System:
MAINFRAME:	CMS

Top ^

Hot Fix Releases for the Week of: October 27, 2003

82BB73 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004359	ALERT - PROC MEANS/SUMMARY/TABULATE/REPORT may produce additional classificationgroups and not apply format to printed output	82BA09
SN-005747	PROC MEANS/SUMMARY may produce incorrect output with numeric CLASSvariables	82BA53
SN-010802	ALERT - PROC MEANS/SUMMARY produces null ID values in the output data set	82BB73
Select an Available Operating System:
PC:	OS/2
UNIX:	AIX_64bit_SAS

Top ^

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

82IG02 for SAS/ACCESS INTERFACE TO CA-OPENINGRES
Issue(s) Addressed:		Introduced:
SN-008460	SAS/ACCESS Interface to CA-OpenIngres does not support MULTINATIONAL4dates	82IG01
SN-010494	Deleting from an empty Ingres table generates an error instead of awarning	82IG02
Select an Available Operating System:
UNIX:	Solaris_32bit_SAS

Top ^

82BB75 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-010789	Batch job ends with RC=0 when uncompiled or nonexistant SCL fails toexecute	82BB75
Select an Available Operating System:
MAINFRAME:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64

Top ^

Hot Fix Releases for the Week of: October 13, 2003

82FS02 for SAS/FSP
Issue(s) Addressed:		Introduced:
SN-006147	Potential security exposure with SAS/FSP	82FS01
SN-010748	ALERT - Underscores or pad character may remain as part of value	82FS02
Select an Available Operating System:
UNIX:	AIX_64bit_SAS

Top ^

82IH12 for SAS INTEGRATION TECHNOLOGIES
Issue(s) Addressed:		Introduced:
SN-010493	SAS processes consume high CPU resources after client application isabnormally terminated	82IH12
Select an Available Operating System:
MAINFRAME:	OS/390
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

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

82BB79 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006975	The SAS System Release 8.2 PC Spawner Program may stop runningunexpectedly	82BB29
SN-010003	Multiple SAS/CONNECT PC Spawner Programs can be run at the same time	82BB59
SN-010237	Hotfix 82bb52 causes SAS/CONNECT SIGNON problems	82BB59
SN-011006	Attempting to run multiple Spawners may fail.	82BB79
Select an Available Operating System:
PC:	Windows
ATTENTION: Before installing the updated spawner included in this hot fix, you must first delete the existing spawner service and re-install it after applying this hot fix. Failing to do so will prevent this hot fix from working properly. Refer to TS-638 for additional information about installing the PC spawner program.

Top ^

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

82BW03 for SAS/ACCESS INTERFACE TO SAP BW
Issue(s) Addressed:		Introduced:
SN-006764	Runtime error when extracting or displaying InfoCube with 0DATEattribute from InfoObject	82BW01
SN-006766	Cannot extract InfoCubes from SAS/ACCESS to SAP BW which have compoundcharacteristics where reference character of compound in SID table doesnot match InfoObject name	82BW01
SN-006765	SQL star view requires excessive space for temporary files in SAS/ACCESSto SAP BW	82BW01
SN-007682	Error creating formats for class variables during InfoCube dataextraction within SAS/ACCESS Interface to SAP BW	82BW02
SN-007675	Full extraction versus change data capture for InfoCubes and ODS inSAS/ACCESS Interface to SAP BW	82BW02
SN-007719	SAS/ACCESS Interface to SAP BW extraction does not recognize certainerror conditions	82BW02
SN-007674	Metadata extractions with FIELDS and TABLES selected from SAS/ACCESSInterface to SAP BW returns metadata about non-relevant tables	82BW02
SN-010160	Extractions of InfoCubes or ODS tables within SAS/ACCESS Interface toSAP BW using remote host metadata fails	82BW03
SN-008892	Misleading error message written when extracting ODS tables that containInfoObjects with compound keys from SAS/ACCESS Interface to SAP BW	82BW03
SN-010159	Change Data Capture feature in SAS/ACCESS Interface to SAP BW mayproduce incorrect InfoCube data for compressed InfoCubes in SAP BW	82BW03
SN-010158	Format names created for infocubes in SAS/ACCESS to SAP BW are notdescriptive	82BW03
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64
ATTENTION: To complete the installation of this hot fix, you must also download and install hot fix 82R302 for your operating system. Customers running in a DBCS environment should download 82R302. This hot fix will NOT be fully functional without both 82BW02 and 82R302 applied.

Top ^

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

82BB35 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-008405	Write-access violation error message appears when reading file with URLengine	82BB17
SN-008973	Problems reading redirected web pages with the URL engine	82BB31
SN-008974	Problems using the URL engine to read web pages from sites that setcookies	82BB31
SN-009209	HTTP 1.1 support for URL access method	82BB35
Select an Available Operating System:
MAINFRAME:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   HPUX_64bit_SAS,   Solaris_64bit_SAS,   AIX_64bit_SAS,   Linux

Top ^

82BB69 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004466	ALERT - PROC SQL query with SELECT DISTINCT may return incorrect results onVMS	82BA18
SN-004737	Sorting problems using the VMS host sort in Release 8.1/8.2 and numericvariables of length < 8	82BA18
SN-010586	SORTSIZE=8M on OpenVMS only allocates 2M	82BB69
Select an Available Operating System:
VMS:	OpenVMS_Alpha,   OpenVMS_VAX

Top ^

Hot Fix Releases for the Week of: August 25, 2003

82R301 for SAS/ACCESS INTERFACE TO R/3
Issue(s) Addressed:		Introduced:
SN-006980	Error using transport files to install SAP objects for SAS/ACCESSInterface to R/3	82R301
SN-007683	Transport files to load SAP ABAP objects are available for SAS/ACCESSInterface to SAP BW	82R301
SN-010245	Function module Z_SAS_IOBJ_GETDETAIL_LIST for SAS/ACCESS Interface toSAP BW increases performance for extraction of metadata aboutInfoObjects	82R301
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64

Top ^

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

82OL05 for SAS/ACCESS INTERFACE TO OLE DB
Issue(s) Addressed:		Introduced:
SN-004249	PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file	82OL01
SN-005811	Syntax error when using WGDB option with PROC IMPORT procedure	82OL01
SN-005812	PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine	82OL01
SN-004195	PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly	82OL01
SN-005506	Importing from Excel 97 or 2000 where the sheet name contains an &fails.	82OL01
SN-006001	Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared'	82OL01
SN-000494	Can SAS access Microsoft SQL Server OLAP cubes?	82OL01
SN-007399	ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed	82OL01
SN-007477	Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390	82OL03
SN-007806	Accessing OLAP cube that contains a currency type will return $0	82OL04
SN-005809	ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table	82OL05
SN-010553	Unable to list tables or retrieve data using the Ihistorian OLE DBprovider	82OL05
Select an Available Operating System:
PC:	Windows

Top ^

82PF05 for SAS/ACCESS INTERFACE TO PC FILE FORMATS
Issue(s) Addressed:		Introduced:
SN-004249	PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file	82PF01
SN-005811	Syntax error when using WGDB option with PROC IMPORT procedure	82PF01
SN-005812	PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine	82PF01
SN-004195	PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly	82PF01
SN-005506	Importing from Excel 97 or 2000 where the sheet name contains an &fails.	82PF01
SN-006001	Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared'	82PF01
SN-000494	Can SAS access Microsoft SQL Server OLAP cubes?	82PF01
SN-007399	ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed	82PF01
SN-007477	Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390	82PF03
SN-007806	Accessing OLAP cube that contains a currency type will return $0	82PF04
SN-005809	ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table	82PF05
SN-010553	Unable to list tables or retrieve data using the Ihistorian OLE DBprovider	82PF05
Select an Available Operating System:
PC:	Windows

Top ^