| 82D226 for Linux |
| Released: Feb 2005 |
| 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-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 |
| Install Instructions: 82D226lx.txt |
| Download: 82D226 for Linux (File Size: 813K) |
| 82OD09 for Linux |
| Released: Feb 2005 |
| 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-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 |
| Install Instructions: 82OD09lx.txt |
| Download: 82OD09 for Linux (File Size: 813K) |
| 82BB46 for Linux |
| Released: Aug 2003 |
| This Hot Fix is included in Hot Fix Bundle 82BX09. |
| 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 |
| Install Instructions: 82BB46lx.txt |
| Download: 82BB46 for Linux (File Size: 805K) |
| 82BB84 for Linux |
| Released: Aug 2004 |
| This Hot Fix is included in Hot Fix Bundle 82BX09. |
| 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-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-009366 |
ODS PRINTER does not close registry keys properly |
82BB84 |
| Install Instructions: 82BB84lx.txt |
| Download: 82BB84 for Linux (File Size: 2.1M) |
| 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. |
| 82BC24 for Linux |
| Released: Dec 2005 |
| Issue(s) Addressed: | Introduced: |
| SN-004264 |
-LOG, -ALTLOG, -PRINT, and -ALTPRINT system options require a file(not a directory) in V8 |
82BA02 |
| 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-005048 |
Incorrect output results from PROC FORMAT with the MULTILABEL option |
82BA02 |
| SN-004316 |
WHERE returns incorrect number of observations |
82BA02 |
| SN-005243 |
CALL EXECUTE may truncate or repeat generated code |
82BA02 |
| 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-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-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-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-008571 |
Potential performance improvements for SAS batch jobs that create large*.log or *.lst files |
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-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 may 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-010150 |
Interrupting a SAS process can result in compromised data integrity |
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-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 |
DATETIME() function might return incorrect values over DaylightSaving cutovers for long-running processes such as SAS/SHARE servers |
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-015882 |
A Japanese character that contains the hex value for a single or doublequote may 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 |
| Install Instructions: 82BC24lx.txt |
| Download: 82BC24 for Linux (File Size: 6.2M) |
| 82BC41 for Linux |
| Released: May 2007 |
| 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 |
