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
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux
Released August 18, 2006 on OS/390 Released August 17, 2006 on HPUX 32bit SAS, Solaris 32bit SAS, AIX 32bit SAS, Tru 64, 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:	Solaris_32bit_SAS

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
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

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-006100	Invalid package files (*.spk) are generated when running with AsianLanguage Support (DBCS) installed	82BA57
SN-006320	PROC PRINT does not honor SPLIT= option (DBCS compliant version only)	82BA57
SN-006321	Japanese version of SAS 8.2 cannot read a back slash correctly from adirectory server	82BA57
SN-006322	Byte order of UCS2 character is wrong with the KCVT function (DBCScompliant version only)	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-008831*	OC1 and OC4 abends when executing SAS on Fujitsu mainframe MSP-EX	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:
PC:	Windows
UNIX:	HPUX_32bit_SAS

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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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-006578	Variable name(s) might be broken up when accessing data with SAS/CONNECTRLS	82SH02
SN-006579	ALERT - Variable name(s) might be broken up when accessing data with SAS/SHARERLS	82SH02
SN-007225	Using PROC FSEDIT with a WHERE statement in SAS/SHARE across platformsand releases generates error message	82SH04
SN-008185	DBCS version of SAS/SHARE server unable to open datasets created inEnglish environment	82SH05
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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

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-005631*	$EBCDIC informat uses incorrect translation table (DBCS compliantversion only)	82BA45
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-007013*	ERROR: Read Access Violation In Task ( SAS/EIS ] Exception occurred at(630133A0)	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-009155*	Lack of transcoding support for GBK charset causes failure from jdbc	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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

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,   Linux

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:
PC:	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: 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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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-007035	DBCS version of SAS fails to send Japanese characters with Lotus Notesemail	82BA71
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
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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 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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

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

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,   Linux

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:
PC:	Windows
UNIX:	AIX_32bit_SAS

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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

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-006761	The case of DBMS column and table names is not preserved when using theDBCS image	82BA63
SN-006874	The option DBGEN_NAME= renames variables incorrectly	82BA63
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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

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

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: August 2, 2004

82BB84 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-005261	ALERT - The CHARSET= and ENCODING= ODS options are ignored by the HTML and XMLdestinations	82BA10
SN-005850	DBCS characters may not display properly when using ODS RTF	82BA51
SN-005851	Certain DBCS characters prevent RTF files from being opened by MicrosoftWord	82BA51
SN-005425*	Invalid files generated for ODS printer destinations in Asian encodings	82BA42
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-007190	Incorrect Japanese character appears in ODS RTF output on DBCS systems	82BA83
SN-007191	Generating ODS/RTF output using the ESCAPECHAR option causes errors onDBCS systems	82BA83
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-010821*	ODS RTF incorrectly displays some symbol characters defined from DBCSsystems	82BB61
SN-009366	ODS PRINTER does not close registry keys properly	82BB84
* 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,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux
ATTENTION: If you downloaded hot fix 82BB97 before August 4, 2004, you must back off 82BB97 and re-install 82BB84. 82BB97 is currently NOT available for DBCS supported installations.

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 ^

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,   Linux

Top ^

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

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
PC:	Windows
ATTENTION (1): To complete the installation of Integration Technologies hot fix 82IH13 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 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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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,   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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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,   Linux

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,   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-007063	Numeric Value is Byte-Swapped with Upload Procedure	82CT03
SN-007192	SIGNOFF command for MPConnect session causes SAS to hang on DBCS systems	82CT04
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
PC:	Windows
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   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: October 13, 2003

82IH12 for SAS INTEGRATION TECHNOLOGIES
Issue(s) Addressed:		Introduced:
SN-005801	ALERT - Garbage is displayed when DBCS characters are used in a SAS IntegrationTechnologies Server	82IH02
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,   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

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,   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

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-006709	PROC IMPORT of Excel 2000 data containing double byte characters aretruncated in SAS	82OL02
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-006709	PROC IMPORT of Excel 2000 data containing double byte characters aretruncated in SAS	82PF02
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 ^

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

82BB46 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-005210	ALERT - LINE statement may display incorrect data with COMPUTE BEFORE and theFLOW option	82BA36
SN-005223	BREAK statement and GROUP under an ACROSS may cause an error	82BA36
SN-005211	ALERT - GROUP values under ACROSS may be missing if BREAK/COMPUTE AFTER variableis requested	82BA36
SN-005767	ALERT - Nested ACROSS variables may result in system specific errors	82BA36
SN-005770	ALERT - Row variable values may be printed under wrong variable column	82BA36
SN-005766	ALERT - Rows of data may be missing from output with multiple ACROSS variablesin PROC REPORT	82BA36
SN-007784	ALERT - PROC REPORT quantile values may be incorrect	82BA98
SN-007785	ALERT - ACROSS values may be missing in the REPORT WINDOW of PROC REPORT	82BA98
SN-007786	BY statement in PROC REPORT may cause memory problems	82BA98
SN-007888	ALERT - All but the first column under an ACROSS variable may contain missingvalues	82BA98
SN-005776	CALL DEFINE specified in COMPUTE block may produce an abend	82BA98
SN-009218	ALERT - Data missing when ANALYSIS variable is requested over multiple ACROSSvariables	82BB33
SN-009829	PROC REPORT _PAGE_ location LINE statements are missing when onlysummary rows are printed on a page	82BB46
SN-010063	PROC REPORT option NOCOMPLETECOLS may apply only to last variable listedunder a nested ACROSS	82BB46
SN-010051	Label for OTHER format range may display in RBREAK summary line	82BB46
SN-010380*	The FLOW option on a DEFINE statement may generate garbage characters	82BB46
* 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,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

82ST17 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-010513	Out of memory error may occur when running PROC CLUSTER with a largedistance matrix as input	82ST17
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,   Linux

Top ^

Hot Fix Releases for the Week of: July 28, 2003

82BB66 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006316	Run-time error '-2147217407 (80041004)':Error: The requested function was not performed due to an invalid orexpired product license.	82BB28
SN-008938	No results returned or connection fails when opening an OLE DBConnection in ArcCATALOG or ArcMAP	82BB28
SN-010442	Unable to navigate file system in Enterprise Guide.	82BB66
SN-010480	.NET applications may fail when using IOM methods that make use ofdatetime values.	82BB66
Select an Available Operating System:
PC:	Windows

Top ^

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

82BB65 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-010386	"ERROR: Invalid Argument" or incorrect results when using ZIP codefunctions	82BB65
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,   Linux

Top ^

Hot Fix Releases for the Week of: July 7, 2003

82IH10 for SAS INTEGRATION TECHNOLOGIES
Issue(s) Addressed:		Introduced:
SN-005484	Publishing to an HTTP 1.0 WebDAV-compliant server results in a hang.	82IH03
SN-005494	Publishing package is replaced when publishing to a WebDAV compliantserver	82IH03
SN-005789	ALERT - Publish fails when DBCS(double byte character set) is used.	82IH03
SN-009495*	Ability to publish with WEBDAV fails when publishing to a non-SAScollection	82IH10
* 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,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

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

82BB60 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-007086*	KANJI conversion works until subsequent windows are opened afterinvoking SAS	82BA75
SN-007085*	Double byte (DBCS) characters cannot be entered using the IMM window	82BA75
SN-007948*	IMM window does not send Japanese characters to the Program Editorwindow	82BB07
SN-007809*	DBCS characters are not displayed properly in the IMM window	82BB07
SN-007808*	X LOCALE warnings may be generated when running SAS with DBCS support	82BB07
SN-009655*	AF application performance is extremely slow in Japanese environments onHP-Unix systems	82BB45
SN-010014*	DMS support added for Release 8.2 with DBCS support on AIX 5L	82BB53
SN-010165*	Unable to input half-width Katakana via IMM window	82BB53
SN-010295*	SEGMENTATION VIOLATION IN TASK [RESULTS] error when invoking SAS withChinese locale	82BB60
* 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

Top ^

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

82BB53 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-007086*	KANJI conversion works until subsequent windows are opened afterinvoking SAS	82BA75
SN-007085*	Double byte (DBCS) characters cannot be entered using the IMM window	82BA75
SN-007948*	IMM window does not send Japanese characters to the Program Editorwindow	82BB07
SN-007809*	DBCS characters are not displayed properly in the IMM window	82BB07
SN-007808*	X LOCALE warnings may be generated when running SAS with DBCS support	82BB07
SN-009655*	AF application performance is extremely slow in Japanese environments onHP-Unix systems	82BB45
SN-010014*	DMS support added for Release 8.2 with DBCS support on AIX 5L	82BB53
SN-010165*	Unable to input half-width Katakana via IMM window	82BB53
* 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,   AIX_32bit_SAS,   Tru_64
ATTENTION (1): This hot fix should only be applied to HP-UX systems running HP-UX 11.x. ATTENTION (2): Solaris (for 32 bit support) customers should download hot fix 82BB60.

Top ^

Hot Fix Releases for the Week of: May 19, 2003

82BB48 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-009957	HOSTEDIT command on MVS may in rare instances not work	82BB48
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: May 12, 2003

82QC04 for SAS/QC
Issue(s) Addressed:		Introduced:
SN-009835	ALERT - PROC OPTEX fails to output correct design with the NUMBER=*BEST optionson the OUTPUT statement when using CRITERION=A	82QC04
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,   Linux

Top ^

Hot Fix Releases for the Week of: April 7, 2003

82BB38 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-009286*	Lack of transcoding support for GBK charset causes problems	82BB38
SN-009756*	Unable to set TRANTAB option in Release 8.2 on Linux	82BB38
* 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

Top ^

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

82BB40 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-009445	TOOLKIT engine may not properly handle member names over 8 characters	82BB40
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,   Linux

Top ^

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

82AD02 for SAS/ACCESS INTERFACE TO ADABAS
Issue(s) Addressed:		Introduced:
SN-009206	Error: Periodic group / multiple value status has changed for field	82AD02
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

82BB18 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006354*	Using Syncsort with the SAS System for Windows	82BA21
SN-008666*	SyncSort support available for 64-bit HP, 64-bit Solaris and Linux	82BB18
* 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:	Linux

Top ^

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

82GR02 for SAS/GRAPH
Issue(s) Addressed:		Introduced:
SN-008888	Incorrect values returned from _GetLegendPosition method for Scattercontrol	82GR02
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64

Top ^

82QC02 for SAS/QC
Issue(s) Addressed:		Introduced:
SN-004863	The column headings on the parameters tab under FIT DETAILS areincorrectly labeled in the ADX Interface	82QC02
SN-008913	ALERT - Design Points on the Residual Plots may not be plotted and plots may notbe updated in the ADX Interface	82QC02
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

82QC03 for SAS/QC
Issue(s) Addressed:		Introduced:
SN-004864	ALERT - The mean response values are incorrectly displayed in cube plots andfactorial plots in the ADX Interface	82QC03
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

Hot Fix Releases for the Week of: November 25, 2002

82BB12 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-004619	Risk Dimensions documentation will not display after SAS System Helphas been invoked	82BA32
SN-005042	Margin settings are ignored in Release 8.2.	82BA32
SN-005201	Read-access violation submitting a simple data step on Windows ME	82BA32
SN-005938	The SAS system abends after you select File from the menu bar	82BA56
SN-004882	FIND and REPEAT FIND (RFIND) keys do not work in the Enhanced Editor inRelease 8.2	82BA56
SN-007046	ALERT - SAS® Enterprise Guide might crash when using RTF result format type	82BA74
SN-006943	ALERT - Combo Box may not display blank value using Dropdown List	82BA74
SN-007007	Abnormal SAS termination entering a long string in a Text Pad Control	82BA74
SN-007766	ALERT - When opening SAS System Help 8.2, browser opens and "The page cannot befound" error message appears	82BB04
SN-008335	Scrolling the wheel of an Intelli Mouse while the END command is issuedcrashes SAS	82BB12
SN-008755	Webhound child processes may hang during the reporting phase	82BB12
Select an Available Operating System:
PC:	Windows

Top ^

82BB20 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006684	TSO timeouts not honored with SAS/CONNECT sessions	82BA26
SN-007404	SAS Ignores TCPIP_DATA SAS/C environment variable when using ConnectSpawner CLIST	82BA90
SN-008740	Certain special conditions may cause the SAS/IntrNet® Application Serverto "hang"	82BB20
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

82BB21 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-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-006100	Invalid package files (*.spk) are generated when running with AsianLanguage Support (DBCS) installed	82BA57
SN-006320	PROC PRINT does not honor SPLIT= option (DBCS compliant version only)	82BA57
SN-006321	Japanese version of SAS 8.2 cannot read a back slash correctly from adirectory server	82BA57
SN-006322	Byte order of UCS2 character is wrong with the KCVT function (DBCScompliant version only)	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-007394*	Experimental SECPROFILE SAS System option along with a new SVC routine,allows use of the RACF Secured Signon function	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-007455*	Small numeric values causing problems on OS/390 in Release 8.2	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-008831*	OC1 and OC4 abends when executing SAS on Fujitsu mainframe MSP-EX	82BB21
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
* 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
VMS:	OpenVMS_Alpha
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

82IH08 for SAS INTEGRATION TECHNOLOGIES
Issue(s) Addressed:		Introduced:
SN-008847	Object Spawner STC address space loops and consumes excessive CPU	82IH08
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: November 18, 2002

82AD01 for SAS/ACCESS INTERFACE TO ADABAS
Issue(s) Addressed:		Introduced:
SN-008569	ADABAS view descriptor subset WHERE clause GT 72 characters in length isnot passed to the data base	82AD01
SN-006013	SUBSET WHERE used in ADABAS access descriptor returns zero rows	82AD01
SN-008697	NAT3061 error when creating ADABAS descriptor using 4 digit SYSFILE parm	82AD01
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

82BB13 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-008454	Invalid Operation Error may occur in PROC UNIVARIATE with a HISTOGRAMstatement	82BB13
Select an Available Operating System:
PC:	Windows

Top ^

82BB19 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-008686	Only one revision is saved when entry name length is greater than 40	82BB19
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64

Top ^

82ST15 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-004855	ALERT - NEGBIN Distribution Produces Incorrect Results in PROC NLMIXED	82ST02
SN-008683	PROC NLMIXED fails to process all levels of BY variable when a floatingpoint overflow error occurs	82ST15
SN-008759	ALERT - PROC NLMIXED may display incorrect labels for some by-groups	82ST15
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,   Linux

Top ^

82ST16 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-008764	ALERT - PROC GLM may not compute the correct error sums of squares when solvingthe Expected Mean Squares for RANDOM effects	82ST16
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,   Linux

Top ^

Hot Fix Releases for the Week of: September 30, 2002

82ST14 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-005594	NLIN may give Error: Could not compute the change vector and fail toconverge	82ST05
SN-005692	PROC NLIN may give a Floating Point Zero Divide error with a BOUNDS	82ST07
SN-006607	PROC NLIN may terminate abnormally if ARRAY variables begin with "der"	82ST10
SN-006626	Invalid Operation error possible with BOUNDS and OUTPUT statements inPROC NLIN	82ST10
SN-008501*	NLIN may terminate with a Floating Point Overflow when a weight is used	82ST14
* 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,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

Hot Fix Releases for the Week of: August 19, 2002

82BB11 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-008149	6.09 SAS/CONNECT CMS server hangs when 8.2 SAS/CONNECT OS/390 clientattempts signon through APPC Communication Access Method	82BB11
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: July 22, 2002

82ST13 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-007028	ALERT - Incorrect results from IPF estimation if response variable has more than256 levels	82ST13
SN-007732	Abnormal Termination in PROC CATMOD when response effects have longvariable names	82ST13
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,   Linux

Top ^

Hot Fix Releases for the Week of: July 8, 2002

82R303 for SAS/ACCESS INTERFACE TO R/3
Issue(s) Addressed:		Introduced:
SN-007638	CALLRFC function used within SAS/ACCESS to R/3 and SAS/ACCESS to SAP BWfails for SAP Version 6.x	82R303
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: June 24, 2002

82BA34 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-005030	Using the DROP= (or KEEP=) option with NODUPKEY in PROC SORT may requireFORCE option	82BA34
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,   Linux

Top ^

Hot Fix Releases for the Week of: June 17, 2002

82IH05 for SAS INTEGRATION TECHNOLOGIES
Issue(s) Addressed:		Introduced:
SN-007044	Hot Fix is required to support National characters in LDAP version 3.0	82IH05
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,   Linux

Top ^

Hot Fix Releases for the Week of: May 27, 2002

82ST12 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-007120	ALERT - Incorrect parameter estimates and standard errors on mainframe systems	82ST12
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: April 29, 2002

82R302 for SAS/ACCESS INTERFACE TO R/3
Issue(s) Addressed:		Introduced:
SN-007103	Extract job continues to run when error encountered without abending inACCESS to R/3	82R302
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64

Top ^

82ST11 for SAS/STAT
Issue(s) Addressed:		Introduced:
SN-005560	ALERT - Incorrect standard errors for repeated, multinomial models	82ST06
SN-006439	ALERT - Incorrect results when BY statement and AGGREGATE= option used together	82ST09
SN-007104	ALERT - Incorrect results with FREQ and/or WEIGHT statement when DIST=NEGBIN	82ST11
SN-007143	ALERT - Weights incorrectly applied when REPEATED statement is used	82ST11
SN-007297	ALERT - Incorrect results possible when the REPEATED statement is used with aFREQ or WEIGHT statement	82ST11
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,   Linux

Top ^

Hot Fix Releases for the Week of: April 8, 2002

82BA82 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-007057	Segmentation Violation may occur with multiple array aliasing in PROCNLIN	82BA82
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,   Linux

Top ^

82ML01 for SAS/IML
Issue(s) Addressed:		Introduced:
SN-007033	ALERT - CALL SVD, GINV and HOMOGEN functions may return incorrect results	82ML01
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,   Linux

Top ^

Hot Fix Releases for the Week of: March 18, 2002

82BA76 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006935	Insufficient Authorization on HFS	82BA76
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: March 11, 2002

82BA70 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-007030*	TRANWRD performance problems on DBCS systems	82BA70
* 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,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

Hot Fix Releases for the Week of: February 18, 2002

82BA65 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006836	$BINARYw. format produces incorrect results under DBCS environment	82BA65
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,   Linux

Top ^

Hot Fix Releases for the Week of: January 14, 2002

82DT06 for SAS ENTERPRISE MINER
Issue(s) Addressed:		Introduced:
SN-003568	ALERT - Specifying transaction window length may prevent some sequences frombeing detected	82DT06
Select an Available Operating System:
MAINFRAME:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS,   Solaris_32bit_SAS,   AIX_32bit_SAS,   Tru_64,   Linux

Top ^

Hot Fix Releases for the Week of: December 10, 2001

82BA60 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006423	Incorrect AUTOLIB shipped with encoded version of SAS	82BA60
Select an Available Operating System:
MAINFRAME:	OS/390

Top ^

Hot Fix Releases for the Week of: November 26, 2001

82BA22 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-006241	Memory Leak may be experienced in WebAF when accessing MDDB	82BA22
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,   Linux

Top ^