| www.sas.com > Service and Support > Technical Support |
| |
|
 |
||
| TS Home | Intro to Services | News and Info | Contact TS | Site Map | FAQ | Feedback |  |
|
| The following fixes are included in the 82BX09 Bundle for CMS: | Introduced in BUNDLE: | ||
| 82BA11 | |||
| SN-004952 | German characters not displaying correctly under OS/390 | 82BX01 | |
| 82BA22 | |||
| SN-006241 | Memory Leak may be experienced in WebAF when accessing MDDB | 82BX01 | |
| 82BA25 | |||
| SN-005146 | MDDB Error When Running Middleware Server With IOM Connection | 82BX01 | |
| 82BA34 | |||
| SN-005030 | Using the DROP= (or KEEP=) option with NODUPKEY in PROC SORT may require FORCE option | 82BX03 | |
| 82BA35 | |||
| SN-005323 | $BIDIw. format for bi-directional text processing | 82BX01 | |
| 82BA41 | |||
| SN-005408 | $ASCIIw. informat may overwrite other variables | 82BX01 | |
| 82BA72 | |||
| SN-006752 | PROC COPY of an MDDB greater than 2g in size to an HFS file may result in S0C4 abend in E7CWRIT | 82BX02 | |
| 82BA82 | |||
| SN-007057 | Segmentation Violation may occur with multiple array aliasing in PROC NLIN | 82BX02 | |
| 82BB40 | |||
| SN-009445 | TOOLKIT engine may not properly handle member names over 8 characters | 82BX05 | |
| 82BB46 | |||
| SN-005210 | LINE statement may display incorrect data with COMPUTE BEFORE and the FLOW option | 82BX01 | |
| SN-005223 | BREAK statement and GROUP under an ACROSS may cause an error | 82BX01 | |
| SN-005211 | GROUP values under ACROSS may be missing if BREAK/COMPUTE AFTER variable is requested | 82BX01 | |
| SN-005767 | Nested ACROSS variables may result in system specific errors | 82BX01 | |
| SN-005770 | Row variable values may be printed under wrong variable column | 82BX01 | |
| SN-005766 | Rows of data may be missing from output with multiple ACROSS variables in PROC REPORT | 82BX01 | |
| SN-007784 | PROC REPORT quantile values may be incorrect | 82BX04 | |
| SN-007785 | ACROSS values may be missing in the REPORT WINDOW of PROC REPORT | 82BX04 | |
| SN-007786 | BY statement in PROC REPORT may cause memory problems | 82BX04 | |
| SN-007888 | All but the first column under an ACROSS variable may contain missing values | 82BX04 | |
| SN-005776 | CALL DEFINE specified in COMPUTE block may produce an abend | 82BX04 | |
| SN-009218 | Data missing when ANALYSIS variable is requested over multiple ACROSS variables | 82BX05 | |
| SN-009829 | PROC REPORT _PAGE_ location LINE statements are missing when only summary rows are printed on a page | 82BX07 | |
| SN-010063 | PROC REPORT option NOCOMPLETECOLS may apply only to last variable listed under a nested ACROSS | 82BX07 | |
| SN-010051 | Label for OTHER format range may display in RBREAK summary line | 82BX07 | |
| 82BB57 | |||
| SN-004660 | Library used by DATA step view executing on SAS/SHARE Server remains locked | 82BX01 | |
| SN-005758 | Assignment statements using Boolean logic may produce incorrect results | 82BX01 | |
| SN-004681 | UNEXPECTED ERROR occurs when running a selection rule that references a dynamic SAS modeling score | 82BX01 | |
| SN-007025 | Memory overlay possible with $CHARw., $ASCIIw., and $EBCDICw. informats and character variable length mismatch | 82BX02 | |
| SN-004659 | DATA step view containing Boolean comparisons can return incorrect results | 82BX03 | |
| SN-009334 | Error occurred in the code generation subsystem during program load | 82BX07 | |
| SN-010252 | Segmentation violation using the FILEVAR= option with the FTP engine on a FILE statement | 82BX07 | |
| 82BB65 | |||
| SN-010386 | "ERROR: Invalid Argument" or incorrect results when using ZIP code functions | 82BX07 | |
| 82BB73 | |||
| SN-004359 | PROC MEANS/SUMMARY/TABULATE/REPORT may produce additional classification groups and not apply format to printed output | 82BX01 | |
| SN-005747 | PROC MEANS/SUMMARY may produce incorrect output with numeric CLASS variables | 82BX01 | |
| SN-010802 | PROC MEANS/SUMMARY produces null ID values in output data set | 82BX07 | |
| 82BB80 | |||
| SN-009317 | Using the LIKE condition with an escape sequence against an indexed column returns 0 matches | 82BX07 | |
| SN-011266 | SQL join using LIKE syntax on variables fails with illegal instruction error | 82BX07 | |
| 82BB81 | |||
| SN-011146 | Session can lock when hitting PF-Keys too fast | 82BX07 | |
| 82BB88 | |||
| SN-004576 | IN operator in PROC SQL sometimes gives incorrect results | 82BX01 | |
| SN-011805 | Result of assignment of an array element may be incorrect | 82BX08 | |
| 82BB91 | |||
| SN-011620 | Data set password no longer valid after transporting SAS libraries with CPORT/CIMPORT | 82BX08 | |
| 82BB92 | |||
| SN-006832 | Performance of TCP/IP may be slow on CMS | 82BX02 | |
| 82BB96 | |||
| SN-004606 | PROC TABULATE abnormally terminates when the PRINTMISS option is used | 82BX01 | |
| SN-005685 | PROC TABULATE may generate unweighted percentage with weighted analysis variable | 82BX01 | |
| SN-007709 | PROC TABULATE prints 'AND' in page heading section of table in listing output | 82BX09 * | |
| SN-011373 | Pages are ordered incorrectly when using ALL in the page dimension in TABULATE | 82BX08 | |
| SN-012302 | PROC TABULATE fails to produce error in the ODS destinations in SAS 8.2 regarding limit on potential interactions | 82BX09 * | |
| 82BB97 | |||
| SN-004574 | Spanned headers in PROC REPORT may cause incorrect cellwidth when using ODS | 82BX01 | |
| SN-004501 | PROC TABULATE repeats statistics in all ODS destinations except listing and output data sets | 82BX01 | |
| SN-005596 | Output data set may not be generated when using the ODS OUTPUT statement | 82BX07 | |
| SN-009281 | The OVERPRINT system option does not work correctly with the ODS PRINTER and PDF destinations | 82BX07 | |
| SN-010318 | User-defined format can not be updated when applied to a variable created with ODS OUTPUT | 82BX07 | |
| SN-010411 | Customized template may cause observations to not appear in ODS PRINTER output | 82BX07 | |
| SN-005994 | Using a PREIMAGE= specification and STARTPAGE= with ODS PRINTER causes errors | 82BX07 | |
| SN-009366 | ODS PRINTER does not close registry keys properly | 82BX08 | |
| 82BC07 | |||
| SN-004969 | Incorrect results returned when using the LIBNAME statement or ACCESS view to query a DBMS | 82BX01 | |
| SN-006278 | "ERROR: The maximum number of DBMS opens for this engine has been reached" | 82BX01 | |
| SN-005276 | Error joining multiple ACCESS views or DBMS tables from different librefs with CONNECTION=GLOBALSHARED | 82BX02 | |
| SN-009683 | New DB2 LIBNAME option to reduce number of concurrent DB2 threads | 82BX07 | |
| SN-012757 | SAS/ACCESS query may return incorrect results when duplicate variable names exist | 82BX09 * | |
| 82BC11 | |||
| SN-005048 | Incorrect output results from PROC FORMAT with the MULTILABEL option | 82BX01 | |
| SN-004316 | WHERE returns incorrect number of observations | 82BX01 | |
| SN-005243 | CALL EXECUTE may truncate or repeat generated code | 82BX01 | |
| SN-004992 | Interrupting and cancelling a DATA step replaces exiting data set | 82BX01 | |
| SN-005744 | WHERE statement returns incorrect results | 82BX01 | |
| SN-004633 | "Error: The yieobtn function is not supported by the SASE7 engine" might appear when you examine remote SQL views via the SQL dictionary table | 82BX01 | |
| SN-005975 | ERROR: Macro variable name & must start with a letter or underscore | 82BX01 | |
| SN-006109 | Exiting SAS within a macro window causes an infinite loop | 82BX02 | |
| SN-006963 | Values within %SYSFUNC on a %DO loop are incorrectly uppercased | 82BX02 | |
| SN-006566 | SAS SHARE server abends with S0C4 in VSRACR1 | 82BX02 | |
| SN-006847 | COMPRESS=BINARY may cause problems | 82BX02 | |
| SN-007001 | Missing semicolon on a %LOCAL statement causes system specific errors | 82BX02 | |
| SN-008119 | Error message generated when creating a V6 SAS data set from a DBMS table containing a character column greater than 200 bytes | 82BX04 | |
| SN-004165 | Catalog becomes corrupted leaving header information unreadable | 82BX04 | |
| SN-008902 | Segmentation Violation or other abend possible when running SAS macro code from within Risk Dimensions | 82BX04 | |
| SN-008911 | Macro causes errors when tokenizer reads past an end of line | 82BX04 | |
| SN-008919 | WHERE with user-written informat produces incorrect results | 82BX05 | |
| SN-009349 | Errors from EFI, PROC IMPORT, or PROC EXPORT following hot fix installation | 82BX05 | |
| SN-009294 | Long character value may not be visible in the FSVIEW window | 82BX05 | |
| SN-009299 | PROC UNIVARIATE may abend with the PLOTS option and BY statement | 82BX05 | |
| SN-009625 | PROC TRANSPOSE produces errors when VALIDVARNAME=V6 is specified and 82BX04 HotFix is applied | 82BX05 | |
| SN-011148 | PROC APPEND Abends with S0C4, U2096, Segementation Violation, Stack Overflow or Read/Write Access Violations in Task Append | 82BX08 | |
| SN-012376 | SURVEYSELECT may produce incorrect results | 82BX09 * | |
| SN-013577 | WHERE clause returns incorrect results with overlapping ranges | 82BX09 * | |
| 82BC13 | |||
| SN-013669 | PROC APPEND incorrectly sets SYSERR | 82BX09 * | |
| 82BC14 | |||
| SN-004241 | PROC SQL may return incorrect number of observations when using unique index | 82BX01 | |
| SN-003976 | Inconsistent results returned from the PROC SQL pass-through facility versus the LIBNAME Access engine | 82BX01 | |
| SN-005899 | PROC SQL set operators UNION and OUTER UNION CORRESPONDING return the wrong number of rows when used with subqueries | 82BX01 | |
| SN-005712 | ERROR: where clause processing could not obtain memory | 82BX01 | |
| SN-006247 | Reflexive join operations which execute successfully using the SQL procedure in previous releases of SAS fail in Release 8.2 | 82BX01 | |
| SN-006274 | Error: sqlplan internal error: cannot find symbol RIFNOTE, var=1 tag=3 occurs using SQL view | 82BX01 | |
| SN-006741 | PROC SQL syntax errors occur when using SET operators UNION and/or OUTER UNION CORR within subqueries | 82BX03 | |
| SN-004536 | PROC SQL UPDATE statement may use excessive CPU time | 82BX03 | |
| SN-006773 | Calls to the CONSTANT function can cause READ ACCESS violations in PROC SQL | 82BX03 | |
| SN-004451 | Query submitted to DBMS may generate incorrect results | 82BX03 | |
| SN-006403 | "ERROR: Invalid position -2147483308 for utility file" may be issued when using PROC SQL against SAS/ACCESS SQL views | 82BX03 | |
| SN-006582 | Opening a PROC SQL view twice using %SYSFUNC(OPEN()) causes SAS to terminate and the Display Manager windows to disappear | 82BX03 | |
| SN-006768 | Incorrect results from PROC SQL when a query contains the UNION operator and subqueries | 82BX03 | |
| SN-006624 | SQLPLAN Internal Error occurs when grouping by variable created by subquery | 82BX03 | |
| SN-006772 | Incorrect results from PROC SQL when UNION operator used in a subquery | 82BX08 | |
| SN-005608 | SQL views cannot be used with procedures that do multipass processing | 82BX03 | |
| SN-005808 | PROC SQL ORDER BY uses additional disk space to cache intermediate utility file | 82BX01 | |
| SN-006829 | SAS 8.2 PROC SQL appears to loop when using multiple reflexive join references | 82BX03 | |
| SN-007824 | Incorrect implicit pass-through SQL can be generated from PROC SQL queries leading to incorrect results | 82BX03 | |
| SN-007820 | Dataset options IDXWHERE and IDXNAME available for use with PROC SQL | 82BX03 | |
| SN-007319 | Downloading a SAS Version 6 data set using the V6TRANSPORT option may corrupt data | 82BX03 | |
| SN-007829 | PROC SQL query containing boolean logic can return incorrect results in specific cases | 82BX03 | |
| SN-007827 | Segmentation violation produced from PROC SQL query containing subqueries where both a SAS data set and a DBMS table are referenced | 82BX03 | |
| SN-007831 | PROC SQL join of a view and a SAS data set can return different results | 82BX03 | |
| SN-007822 | Access violation or system abend when executing a PROC SQL direct join against an Oracle table | 82BX03 | |
| SN-007636 | DISTINCT keyword in SQL subquery produces incorrect results or no results in SAS/ACCESS to ODBC or SAS/ACCESS to DB2 | 82BX03 | |
| SN-007826 | PROC SQL generates incorrect pass through code when there are multiple OR'd expressions in the WHERE clause | 82BX03 | |
| SN-007871 | Password value is displayed in SAS log when defining an SQL view with a USING clause which contains a password parameter | 82BX03 | |
| SN-008356 | Integer divide by zero error when displaying column with length of 32767 | 82BX07 | |
| SN-008314 | SASHELP.VTABLE displays data set labels unexpectedly | 82BX07 | |
| SN-007222 | Outer join of two (2) DBMS tables via a LIBNAME engine with WHERE clause subsets may generate incorrect results | 82BX07 | |
| SN-009491 | Implicit SQL Passthru may drop important parenthesis from WHERE condition | 82BX07 | |
| SN-009727 | Aliased columns in SQL views which perform a simple calculation may lose part of the condition | 82BX07 | |
| SN-009529 | Performing a COUNT or COUNT DISTINCT on a renamed column that is part of a view may result in performance degradation | 82BX07 | |
| SN-010745 | Part of join criteria is lost joining DBMS tables via LIBNAME engine | 82BX08 | |
| SN-011220 | Numeric literals in an ON clause with outer join of some DBMS tables may not return correct results | 82BX08 | |
| SN-011239 | Final WHERE clause not included in the SQL to be proccessed by the database when using the LIBNAME ACCESS engine | 82BX08 | |
| SN-011210 | Incorrect results from PROC SQL using WHERE= option with indexed tables | 82BX08 | |
| SN-011802 | "Error: sqlplan internal error" when joining a table with an inline view | 82BX08 | |
| SN-012854 | Using LIBNAME engine may result in an incorrect query being generated | 82BX09 * | |
| SN-009514 | Accessing DBMS tables with column aliases defined via a view may prevent implicit pass-thru | 82BX09 * | |
| SN-012757 | SAS/ACCESS query may return incorrect results when duplicate variable names exist | 82BX09 * | |
| SN-012760 | Applying hotfix 82BB70 causes SQLPLAN Internal Error | 82BX09 * | |
| SN-004451 | Query submitted to DBMS may generate incorrect results | 82BX03 | |
| 82BC15 | |||
| SN-013656 | Using PROC SORT with the TAGSORT option causes a bus error or unaligned access messages | 82BX09 * | |
| 82BC16 | |||
| SN-006986 | Version 8 on CMS does not recognize Version 5 style user-written formats and informats | 82BX02 | |
| SN-008881 | "ERROR: SORT could not complete because of insufficient memory" on CMS | 82BX04 | |
| SN-013712 | NOLOG and NOPRINT options do not work on CMS | 82BX09 * | |
| 82BX09 * | Indicates fixes that are appearing in a bundle for the first time. |
Back to the Main Hot Fix Downloads Page
You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). this Code is designed to either correct an error in the Software or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered tradema rks or trademarks of their respective companies.
Copyright (c) 2002 SAS Institute Inc. All Rights Reserved.