| 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 82BX08 Bundle for OS/390: | Introduced in BUNDLE: | ||
| 82BA19 | |||
| SN-005868 | New procedure CV2VIEW is available to assist in converting SAS/Access view descriptors to LIBNAME views | 82BX01 | |
| 82BA22 | |||
| SN-006241 | Memory Leak may be experienced in WebAF when accessing MDDB | 82BX01 | |
| 82BA34 | |||
| SN-005030 | Using the DROP= (or KEEP=) option with NODUPKEY in PROC SORT may require FORCE option | 82BX02 | |
| 82BA41 | |||
| SN-005408 | $ASCIIw. informat may overwrite other variables | 82BX01 | |
| 82BA43 | |||
| SN-000153 | RETURN CODE of zero if SYSIN DD references non-existent PDS member | 82BX01 | |
| 82BA63 | |||
| 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-006761 | The case of DBMS column and table names is not preserved when using the DBCS image | 82BX01 | |
| SN-006874 | The option DBGEN_NAME= renames variables incorrectly | 82BX01 | |
| SN-005276 | Error joining multiple ACCESS views or DBMS tables from different librefs with CONNECTION=GLOBALSHARED | 82BX01 | |
| 82BA65 | |||
| SN-006836 | $BINARYw. format produces incorrect results under DBCS environment | 82BX01 | |
| 82BA70 | |||
| SN-007030 | TRANWRD performance problems on DBCS systems | 82BX01 | |
| 82BA76 | |||
| SN-006935 | Insufficient Authorization on HFS | 82BX01 | |
| 82BA82 | |||
| SN-007057 | Segmentation Violation may occur with multiple array aliasing in PROC NLIN | 82BX01 | |
| 82BB11 | |||
| SN-008149 | 6.09 SAS/CONNECT CMS server hangs when 8.2 SAS/CONNECT OS/390 client attempts signon through APPC Communication Access Method | 82BX02 | |
| 82BB20 | |||
| SN-006684 | TSO timeouts not honored with SAS/CONNECT sessions | 82BX01 | |
| SN-007404 | SAS Ignores TCPIP_DATA SAS/C environment variable when using Connect Spawner CLIST | 82BX02 | |
| SN-008740 | Certain special conditions may cause the SAS/IntrNet Application Server to "hang" | 82BX04 | |
| 82BB30 | |||
| SN-009073 | The PROC SOURCE BEFORE statement with ALIAS option does not actually generate the resulting output file card before the member | 82BX05 | |
| 82BB35 | |||
| SN-008405 | Write-access violation error message appears when reading file with URL engine | 82BX07 | |
| SN-008973 | Problems reading redirected web pages with the URL engine | 82BX07 | |
| SN-008974 | Problems using the URL engine to read web pages from sites that set cookies | 82BX07 | |
| SN-009209 | HTTP 1.1 support for URL access method | 82BX07 | |
| 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 | 82BX04 | |
| SN-005223 | BREAK statement and GROUP under an ACROSS may cause an error | 82BX04 | |
| SN-005211 | GROUP values under ACROSS may be missing if BREAK/COMPUTE AFTER variable is requested | 82BX04 | |
| SN-005767 | Nested ACROSS variables may result in system specific errors | 82BX04 | |
| SN-005770 | Row variable values may be printed under wrong variable column | 82BX04 | |
| SN-005766 | Rows of data may be missing from output with multiple ACROSS variables in PROC REPORT | 82BX04 | |
| 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 | 82BX06 | |
| SN-010063 | PROC REPORT option NOCOMPLETECOLS may apply only to last variable listed under a nested ACROSS | 82BX06 | |
| SN-010051 | Label for OTHER format range may display in RBREAK summary line | 82BX06 | |
| 82BB48 | |||
| SN-009957 | HOSTEDIT command on MVS may in rare instances not work | 82BX06 | |
| 82BB65 | |||
| SN-010386 | "ERROR: Invalid Argument" or incorrect results when using ZIP code functions | 82BX06 | |
| 82BB70 | |||
| 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 | 82BX02 | |
| SN-004536 | PROC SQL UPDATE statement may use excessive CPU time | 82BX02 | |
| SN-006773 | Calls to the CONSTANT function can cause READ ACCESS violations in PROC SQL | 82BX02 | |
| SN-004451 | Query submitted to DBMS may generate incorrect results | 82BX02 | |
| SN-006403 | "ERROR: Invalid position -2147483308 for utility file" may be issued when using PROC SQL against SAS/ACCESS SQL views | 82BX02 | |
| SN-006582 | Opening a PROC SQL view twice using %SYSFUNC(OPEN()) causes SAS to terminate and the Display Manager windows to disappear | 82BX02 | |
| SN-006768 | Incorrect results from PROC SQL when a query contains the UNION operator and subqueries | 82BX02 | |
| SN-006624 | SQLPLAN Internal Error occurs when grouping by variable created by subquery | 82BX02 | |
| 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 | 82BX02 | |
| 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 | 82BX02 | |
| SN-007824 | Incorrect implicit pass-through SQL can be generated from PROC SQL queries leading to incorrect results | 82BX02 | |
| SN-007820 | Dataset options IDXWHERE and IDXNAME available for use with PROC SQL | 82BX02 | |
| SN-007319 | Downloading a SAS Version 6 data set using the V6TRANSPORT option may corrupt data | 82BX02 | |
| SN-007829 | PROC SQL query containing boolean logic can return incorrect results in specific cases | 82BX02 | |
| SN-007827 | Segmentation violation produced from PROC SQL query containing subqueries where both a SAS data set and a DBMS table are referenced | 82BX02 | |
| SN-007831 | PROC SQL join of a view and a SAS data set can return different results | 82BX02 | |
| SN-007822 | Access violation or system abend when executing a PROC SQL direct join against an Oracle table | 82BX02 | |
| SN-007636 | DISTINCT keyword in SQL subquery produces incorrect results or no results in SAS/ACCESS to ODBC or SAS/ACCESS to DB2 | 82BX02 | |
| SN-007826 | PROC SQL generates incorrect pass through code when there are multiple OR'd expressions in the WHERE clause | 82BX02 | |
| SN-007871 | Password value is displayed in SAS log when defining an SQL view with a USING clause which contains a password parameter | 82BX02 | |
| SN-008356 | Integer divide by zero error when displaying column with length of 32767 | 82BX06 | |
| SN-008314 | SASHELP.VTABLE displays data set labels unexpectedly | 82BX06 | |
| SN-007222 | Outer join of two (2) DBMS tables via a LIBNAME engine with WHERE clause subsets may generate incorrect results | 82BX06 | |
| SN-009491 | Implicit SQL Passthru may drop important parenthesis from WHERE condition | 82BX06 | |
| SN-009727 | Aliased columns in SQL views which perform a simple calculation may lose part of the condition | 82BX06 | |
| SN-009529 | Performing a COUNT or COUNT DISTINCT on a renamed column that is part of a view may result in performance degradation | 82BX06 | |
| 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 * | |
| 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 | |
| 82BB74 | |||
| 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 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 | 82BX01 | |
| SN-006963 | Values within %SYSFUNC on a %DO loop are incorrectly uppercased | 82BX01 | |
| SN-006566 | SAS SHARE server abends with S0C4 in VSRACR1 | 82BX01 | |
| SN-006847 | COMPRESS=BINARY may cause problems | 82BX01 | |
| SN-007001 | Missing semicolon on a %LOCAL statement causes system specific errors | 82BX01 | |
| SN-008106 | Missing format on the SAS/SHARE server may cause S0C4 abend | 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-010875 | "Error: System abend 0C4 occurred in function YHLLOAD" from SAS/SHARE | 82BX08 * | |
| SN-011148 | PROC APPEND Abends with S0C4, U2096, Segementation Violation, Stack Overflow or Read/Write Access Violations in Task Append | 82BX08 * | |
| 82BB76 | |||
| SN-004892 | Long encrypted message can cause errors in spawner | 82BX08 * | |
| SN-004893 | "Zombie" processes left active on MVS using SAS/CONNECT spawner | 82BX08 * | |
| SN-004936 | OS/390 spawner does not detect expired OS/390 passwords | 82BX08 * | |
| SN-005371 | New RACF Terminal ID Security Support in OS/390 Connect Spawner | 82BX08 * | |
| SN-008812 | OS/390 SAS/CONNECT spawner terminates with a ERRNO=52 or ERRNO=63 due to EPIPE or fork errors | 82BX08 * | |
| SN-011433 | SAS/CONNECT Spawner & Client session "hang" after executing erroneous code. | 82BX08 * | |
| 82BB82 | |||
| SN-011373 | Order of pages in PROC TABULATE output changed between SAS 6.12 and SAS 8 | 82BX08 * | |
| 82BB84 | |||
| 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-005261 | The CHARSET= and ENCODING= ODS options are ignored by the HTML and XML destinations | 82BX01 | |
| SN-005850 | DBCS characters may not display properly when using ODS RTF | 82BX01 | |
| SN-005851 | Certain DBCS characters prevent RTF files from being opened by Microsoft Word | 82BX01 | |
| SN-005425 | Invalid files generated for ODS printer destinations in Asian encodings | 82BX01 | |
| SN-005950 | ODS PDF does not render Latin1 (ISO 8859-1) encoding correctly | 82BX01 | |
| SN-005951 | ODS PDF and RTF can not produce double-byte encoded output | 82BX01 | |
| SN-005949 | ODS PDF will only use Times, Helvetica, and Courier as default font | 82BX01 | |
| SN-005596 | Output data set may not be generated when using the ODS OUTPUT statement | 82BX01 | |
| SN-007190 | Incorrect Japanese character appears in ODS RTF output on DBCS systems | 82BX01 | |
| SN-007191 | Generating ODS/RTF output using the ESCAPECHAR option causes errors on DBCS systems | 82BX01 | |
| 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 * | |
| 82BB86 | |||
| SN-004555 | Subsequent records not read after invalid VBS segment detected | 82BX01 | |
| SN-004078 | FILENAME statement requests three tape mounts for a single tape | 82BX01 | |
| SN-004439 | BY variable position may cause errors | 82BX01 | |
| SN-004435 | Abend S0C1 received in PROC SORT step | 82BX01 | |
| SN-004629 | RC=0 incorrectly issued when running out of directory space writing to PDS | 82BX01 | |
| SN-004465 | LIBNAME statement WAIT= option may cause incorrect engine assignment | 82BX01 | |
| SN-007318 | DIALOG WINDOW of PMENU may issue message indicating an incorrect command | 82BX01 | |
| SN-005862 | SASXAL module has increased in size from 300K to 730K from Release 8.1 to 8.2 | 82BX01 | |
| SN-005121 | U315, U317, U319, S0C4 and Page Validation Errors when creating or deleting catalog entries | 82BX01 | |
| SN-005971 | Cannot connect to OS/390 Spawner with MAXASSIZE=2G in BPXPRM** | 82BX01 | |
| SN-005642 | SAS Notes referring to Version 8 multivolume SASIO problems | 82BX01 | |
| SN-006100 | Invalid package files (*.spk) are generated when running with Asian Language Support (DBCS) installed | 82BX01 | |
| SN-006320 | PROC PRINT does not honor SPLIT= option (DBCS compliant version only) | 82BX01 | |
| SN-006321 | Japanese version of SAS 8.2 cannot read a back slash correctly from a directory server | 82BX01 | |
| SN-006322 | Byte order of UCS2 character is wrong with the KCVT function (DBCS compliant version only) | 82BX01 | |
| SN-006609 | PROC SOURCE abends when processing many members | 82BX04 | |
| SN-007032 | ZDVw.d informat incorrectly rejects a value of '9' | 82BX04 | |
| SN-006754 | Performance degradation due to support for long character string variables | 82BX04 | |
| SN-007000 | When attempting to connect to SAS/SHARE server, an @ sign in the userid receives "Invalid value" message | 82BX04 | |
| SN-007065 | Loop in SAS/SHARE during termination of server task | 82BX04 | |
| SN-007066 | Abend SEC6 in BPXAS address space using FTP with MP-Connect for OS/390 | 82BX04 | |
| SN-007513 | System abend S0C1 due to bad call from YN1NDMS at +x'166' after applying 82BA77 hot fix | 82BX04 | |
| SN-007634 | Code generation problem could cause data integrity under OS/390 | 82BX06 | |
| SN-007455 | Small numeric values causing problems on OS/390 in Release 8.2 | 82BX04 | |
| SN-006237 | INPUT function returns 0 with invalid data on OS/390 | 82BX08 * | |
| SN-007722 | Publish fails when the French-encoded EBCDIC version is used | 82BX04 | |
| SN-007220 | S400 abend, S0C9 abend, or Insufficient Space messages | 82BX04 | |
| SN-007210 | OS/390 sites may receive S282-048 abend | 82BX04 | |
| SN-007952 | Blank lines written to terminal when SAS CLIST is called from a CLIST | 82BX04 | |
| SN-008252 | When using SAS/SECURE with Spawner script signon, -noinheritance must be specified | 82BX04 | |
| SN-008432 | Insufficient USS capability causes authorization messages with certain hot fixes applied | 82BX04 | |
| SN-006517 | B37 abend may cause looping when building an index | 82BX04 | |
| SN-008820 | SAS failing due to not enough buffers available | 82BX04 | |
| SN-008435 | System abend S0C1 in function VSPRNTF | 82BX04 | |
| SN-009007 | Supplied SASEXIT does not work as is for EXITSPPI exit | 82BX05 | |
| SN-009368 | FILE IN USE message potentially caused by MVS temp data sets being allocated with the same physical data set name | 82BX05 | |
| SN-009223 | Errors received when specifying LABEL=EXPDT=YYYDD or EXPDT=YYYY/DDD on FILENAME statement | 82BX05 | |
| SN-008831 | OC1 and OC4 abends when executing SAS on Fujitsu mainframe MSP-EX | 82BX04 | |
| SN-009109 | Problems using Java and SAS/CONNECT for some encoded versions of SAS | 82BX05 | |
| SN-007394 | Experimental SECPROFILE SAS System option along with a new SVC routine, allows use of the RACF Secured Signon function | 82BX04 | |
| SN-008927 | PROC SQL can produce incorrect results when short numeric variables are summed | 82BX05 | |
| SN-009352 | Multivolume sequential file with 0 space on first volume cannot be read | 82BX05 | |
| SN-005800 | Excessive amounts of memory requested by the SAS System can cause unpredictable results when running memory-intensive procedures | 82BX05 | |
| SN-009622 | IGD306I messages potentially caused by MVS temp data sets being allocated with the same physical data set name | 82BX05 | |
| SN-004056 | FILESYSOUT= system option not working correctly | 82BX06 | |
| SN-007759 | "ERROR: Library <libref> is not in a valid format for access method SASE7" if library was allocated externally | 82BX06 | |
| SN-008206 | "ERROR: Library <libref> is not in a valid format for access method SASEx" | 82BX06 | |
| SN-009162 | "ERROR: Library <libref> is not in a valid format for access method SASE7" in CA/MICS jobs | 82BX06 | |
| SN-010816 | FILENAME CLEAR does not clear the second file in a concatenation | 82BX07 | |
| SN-009685 | "ERROR: Undetermined I/O Failure." after installing hot fix 82BB43 | 82BX08 * | |
| SN-011622 | A SAS Share client using TCPIP that receives a Sx22 may be hung and require a cancel | 82BX08 * | |
| SN-011821 | Concurrent access of a sequential SAS data library defined to a SAS/SHARE server may result in lost data | 82BX08 * | |
| 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 * | |
| 82BB92 | |||
| SN-006117 | Communication subsystem failure XVT is already active | 82BX01 | |
| SN-008801 | The object spawner requires parameters exceeding 100 characters when communicating with an LDAP server | 82BX06 | |
| 82BX08 * | 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.