| The following fixes are included in the E9BX05 Bundle for COMPAQ TRU64 UNIX: | Introduced in BUNDLE: | ||
| E9BA02 | |||
| SN-017049 | Deleted observations can get added to new data set when migrating | E9BX01 | |
| E9BA03 | |||
| SN-017176 | JDBC connection to SAS/SHARE Server encounters transcoding error for non-English locale | E9BX03 | |
| E9BA09 | |||
| SN-017440 | SQRT function now supported in MDX code for SAS® OLAP Server | E9BX01 | |
| E9BA12 | |||
| SN-017694 | Missing Output when specifying APPLEVEL parameter on IOM Server definition in SAS Management Console or OBJECTSERVERPARMS SAS Option | E9BX01 | |
| E9BA27 | |||
| SN-017801 | XMLSELECT with OMI_MATCH_CASE does not honor multiple attributes in a search | E9BX01 | |
| E9BA43 | |||
| SN-013603 | IRR and INTRR function may generate INVALID ARGUMENT message in SAS 9.1 | E9BX01 | |
| E9BA45 | |||
| SN-017208 | A long format length might cause a system error in PROC REPORT | E9BX01 | |
| SN-018200 | FLOW option on DEFINE statement may cause system error | E9BX01 | |
| E9BA72 | |||
| SN-018969 | Specifying an encoding for the _WEBOUT fileref does not work when you run a stored process with the Stored Process Server | E9BX01 | |
| E9BA86 | |||
| SN-019227 | NOWARN option for PROC APPEND | E9BX01 | |
| E9BA90 | |||
| SN-019243 | FILENAME URL access method cannot access URLs more than 2K in length | E9BX01 | |
| E9BA92 | |||
| SN-017785 | Combo Box Control placed in an Extended Table object generates program halt | E9BX01 | |
| SN-019176 | Models in SAS/AF software that support multiple interfaces only recognize one interface | E9BX01 | |
| E9BA98 | |||
| SN-019388 | "Read Access Violation in Task [ Application Window ]" with SAS/AF Table Viewer Control | E9BX02 | |
| E9BB06 | |||
| SN-019756 | Incorrect results when lists contain more than 128 method blocks | E9BX02 | |
| E9BB08 | |||
| SN-019525 | Startup of elssrv may fail with 'ERROR: Cannot start thread support service' or 'ERROR: Communication error with launch server' | E9BX02 | |
| E9BB12 | |||
| SN-019711 | Tabbing order might be incorrect in a SAS/AF® Frame entry containing Version 6 objects | E9BX02 | |
| E9BB15 | |||
| SN-019766 | SAS/AF® application prematurely terminates after repeated calls to LISTC, LISTN, or SHOWLIST functions | E9BX02 | |
| E9BB17 | |||
| SN-019231 | JAVAOBJ component object fails to free semaphores | E9BX02 | |
| SN-019812 | Values are quoted when DBCS value has same hex code as delimiter character | E9BX02 | |
| E9BB23 | |||
| SN-020755 | SAS® Enterprise Guide® might generate memory leaks under UNIX | E9BX03 | |
| E9BB49 | |||
| SN-020409 | CDF, SDF, and QUANTILE functions might return missing values for the Beta distribution and small values of first shape parameter | E9BX03 | |
| E9BB61 | |||
| SN-019223 | New SASMSG function added to support internationalization | E9BX02 | |
| SN-019946 | SASMSG FUNCTION causes memory leaks | E9BX02 | |
| SN-021045 | The SASMSG function cannot differentiate traditional Chinese from Simplified Chinese | E9BX03 | |
| SN-021044 | The SASMSG function causes an access violation in batch mode when called with %SYSFUNC | E9BX03 | |
| SN-021046 | An access violation might occur if the input data set is not created as expected | E9BX03 | |
| E9BB62 | |||
| SN-020804 | SPD Engine WHERE CLAUSE processor does not support ESCAPE OPERATOR | E9BX03 | |
| SN-020887 | When you invoke SAS® by using the SAS system option DMSEXP, a segmentation violation might occur if you rename a SAS® Scalable Performance Data Engine (SAS® SPDE) data set | E9BX03 | |
| E9BB65 | |||
| SN-019742 | An error occurs when attempting to connect to the SAS® Metadata Server and the METAUSER= system option contains an embedded space | E9BX03 | |
| E9BB66 | |||
| SN-021053 | The SAS® Stored Process Server and SAS® Workspace Server load balancing is not distributed across hosts with the lowest cost algorithm | E9BX03 | |
| E9BB78 | |||
| SN-015924 | DATETIMEw.d format can produce incorrect results | E9BX01 | |
| SN-030622 | Error generated when MDYAMPM format is used in a FOOTNOTE | E9BX03 | |
| E9BB81 | |||
| SN-018463 | Access Violation or 0C4 abend in module SASSFM01 when using procedures that use multi-label formats | E9BX01 | |
| SN-020189 | Statistic labels in PROC TABULATE not displayed in uppercase in table output | E9BX02 | |
| SN-020444 | Error in PROC TABULATE NLS versions after applying hot fix E9BB28 | E9BX02 | |
| SN-020359 | Variable labels that contain multi-byte character set strings do not split correctly | E9BX02 | |
| SN-030679 | Page dimension "and" in PROC TABULATE not displayed in uppercase in table output | E9BX03 | |
| E9BB91 | |||
| SN-018909 | "ClassFormatError exception is thrown" Java runtime error when string constants contain umlaut characters | E9BX01 | |
| E9BC04 | |||
| SN-017125 | LOCATEC/N function is counting deleted rows in its search | E9BX04 | |
| E9BC10 | |||
| SN-019947 | Writing a SAS® data set to a WebDAV library may fail | E9BX02 | |
| SN-020153 | "ERROR: An I/O error has occurred on file" when WebDAV server sends back an invalid or unexpected response | E9BX02 | |
| SN-030802 | A memory overwrite occurs when using WebDAV LIBNAME or FILENAME with hot fix E9BB30 applied | E9BX03 | |
| SN-032797 | HTTP requests to an HTTPS server fail when the requests are made through a proxy | E9BX04 | |
| SN-033408 | An error might appear in the SAS log when using the Web-based Distributed Authoring and Versioning (WebDav) filename engine | E9BX04 | |
| E9BC12 | |||
| SN-021021 | Some national characters in variable names might be converted to other characters when the options VALIDVARNAME=ANY and GETNAMES=YES | E9BX05 * | |
| SN-034254 | How to allow a numeric value enclosed in quotation marks to be read in as numeric variable with PROC IMPORT or the IMPORT WIZARD | E9BX05 * | |
| E9BC17 | |||
| SN-017725 | The PUTC function in SAS® Component Language might return unformatted results | E9BX01 | |
| SN-019922 | A problem has been encountered on the server, [Fatal Error]:1:1:Content is not allowed in prolog | E9BX02 | |
| SN-019979 | Memory overrun causes segmentation violation with the VIEWTABLE window | E9BX02 | |
| SN-030936 | "Generic function error SASHELP.RSASMOD.MDAXIS.SCL" from server method _GETPOINTINDEXES when accessing MDDB using Java and an IOM connection | E9BX03 | |
| SN-031999 | SAS® Enterprise Miner(TM) Java client hangs at the SAS Enterprise Miner splash screen after submitting log on to SAS Analytics Platform | E9BX04 | |
| E9BC20 | |||
| SN-017906 | The I/O subsystem has returned error message 'WHERE clause is not allowed with preset index.' | E9BX04 | |
| SN-017800 | WHERE clause is not allowed with preset index | E9BX01 | |
| SN-032112 | Performance degradation might occur with the SAS® Metadata Server | E9BX04 | |
| E9BC26 | |||
| SN-032426 | Selection lists or pop-up menus might display behind SAS/AF® frames | E9BX04 | |
| E9BC29 | |||
| SN-032570 | PROC COPY might not honor the OBS= option | E9BX04 | |
| E9BC31 | |||
| SN-017241 | "ERROR: System abend 0C4 occurred in module SASYHRE8 function YHRMHMR at offset 000420" | E9BX01 | |
| SN-032682 | Error causes SAS/SHARE® server running with the TTCP option to fill log with error messages | E9BX04 | |
| E9BC33 | |||
| SN-031851 | User accounts might show as | E9BX04 | |
| E9BC34 | |||
| SN-018857 | Using the WebDAV filename option without specifying a full file path might cause problems when writing to or reading from a directory | E9BX01 | |
| SN-032831 | An error might occur if you use the Web-based Distributed Authoring and Versioning (WebDAV) FILENAME statement | E9BX04 | |
| E9BC39 | |||
| SN-018202 | 'Cannot start remote process' or 'spawner prompt not found' errors might occur when connecting to a UNIX spawner program (sastcpd) | E9BX02 | |
| SN-019354 | An error occurs when you use SAS/CONNECT® software to sign on to a remote UNIX machine that is running a UNIX spawner program | E9BX01 | |
| SN-016689 | SAS/CONNECT® software spawner does not invoke a remote SAS® session without the full path to SAS | E9BX04 | |
| E9BC40 | |||
| SN-017270 | Style not applied properly when sending ODS email | E9BX01 | |
| SN-017354 | SMTP email only uses the e-mail user ID (rather than the full e-mail address) for authentication | E9BX01 | |
| SN-007782 | Time stamp calculation when emailing from OS/390 | E9BX01 | |
| SN-019638 | Sending e-mail attachments using SMTP causes a read-access violation | E9BX02 | |
| SN-020323 | SAS® 9.1.3 and earlier SMTP e-mails do not timeout when block waiting for a response from a SMTP server | E9BX02 | |
| SN-018044 | Using SMTP e-mail with SAS® 9.1.3 (English version with DBCS and Unicode support) might cause truncated or missing e-mail output | E9BX03 | |
| SN-031148 | Unable to authenticate e-mail on z/OS | E9BX03 | |
| SN-033129 | The Simple Mail Transfer Protocol (SMTP) e-mail facility stops sending all e-mails when it encounters an invalid address | E9BX04 | |
| SN-010962 | SMTP e-mail might stop when an invalid address is encountered | E9BX04 | |
| SN-033077 | A Read-access violation occurs when a Zip file is attached to e-mail in a DBCS SAS® session | E9BX04 | |
| E9BC43 | |||
| SN-019166 | Possible memory-related failures when using the CATALOG access method | E9BX01 | |
| SN-033414 | An error occurs when you include the ENCODING option in the FILENAME statement | E9BX05 * | |
| E9BC45 | |||
| SN-033461 | The METAOPERATE procedure does not set the value of the SYSERR automatic macro variable when an error occurs | E9BX04 | |
| E9BC47 | |||
| SN-013932 | "File does not exist" error message and problem accessing VIEWs from remote concatenated library | E9BX01 | |
| SN-013931 | "File does not exist" error message and problems accessing remote VIEWs in concatenated library | E9BX01 | |
| SN-019477 | PROC FREQ with WHERE statement causes connection failure using Remote Library Services | E9BX02 | |
| SN-031047 | Chaining remote library assignments across SAS/CONNECT® or SAS/SHARE® servers might return incorrect data | E9BX03 | |
| SN-034212 | Loss of precision can occur when you insert numeric values into a table that resides in a chained RLS library | E9BX05 * | |
| E9BC58 | |||
| SN-033995 | Error: "IOM call failed. Internal server exception: floating point divide by zero." | E9BX05 * | |
| E9BC68 | |||
| SN-017841 | Extraneous characters appear for catalog entry descriptions when using PROC CIMPORT | E9BX03 | |
| SN-020578 | PROC CIMPORT generates "Warning: The transport file is from an earlier SAS release" | E9BX03 | |
| SN-020673 | Using PROC CIMPORT in DBCS version of SAS® may result in errors or garbage characters if transport file contains data with indexes | E9BX03 | |
| SN-020675 | Garbage characters may result when using PROC CIMPORT to import a transport file containing double-byte character set data | E9BX03 | |
| SN-034280 | A "426 Connection closed; transfer aborted" message might appear in your SAS® log when using FTP to send a transport file that was created with CPORT | E9BX05 * | |
| E9BC69 | |||
| SN-017704 | An update to ensure proper authentication logging on to an Integration Technology Server | E9BX01 | |
| SN-020384 | If your z/OS user ID begins with special characters, you cannot see pre-assigned libraries from SAS® Enterprise Guide® 4.1 | E9BX02 | |
| SN-020418 | "ACCESS DENIED" authentication error is not displayed as expected when the Metadata server using a Japanese version of Windows | E9BX02 | |
| SN-031165 | IOM messages are truncated in the SAS® Metadata Server log | E9BX03 | |
| SN-034913 | The SAS® Metadata Server stops responding if a long user ID or password is submitted for authentication | E9BX05 * | |
| SN-034915 | Submitting a blank user ID when logging in to the SAS® Metadata Server causes the server memory usage to increase suddenly | E9BX05 * | |
| E9BC72 | |||
| SN-020299 | PROC PRINT may show missing columns in HTML, LISTING or RTF output | E9BX05 * | |
| SN-017976 | Error about running out of space using PROC PRINT in certain situations | E9BX01 | |
| SN-034756 | Column data might be blank using the List Data task in SAS® Enterprise Guide® | E9BX05 * | |
| SN-035147 | A variable is missing from PROC PRINT output when using ODS Listing or ODS HTML | E9BX05 * | |
| E9BC76 | |||
| SN-017667 | Segmentation Violation in task [ DATASETS ] using DELETE statement | E9BX01 | |
| SN-017072 | Metadata server service might show starting state but never start | E9BX03 | |
| SN-020233 | Increasing timeout value on UNIX may improve performance | E9BX02 | |
| SN-020274 | Grid sign-on fails to honor the TCPPORTFIRST and the TCPPORTLAST options | E9BX02 | |
| SN-020438 | Unix cleanwork utility does not remove UTILLOC directories | E9BX02 | |
| SN-019386 | SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]" | E9BX03 | |
| SN-020817 | Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routine | E9BX03 | |
| SN-021112 | A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server | E9BX03 | |
| SN-031719 | Some components from version 6 of SAS/AF® software might cause a read-access violation with repeated use | E9BX05 * | |
| SN-031795 | Dragging the cursor to an unselected item within the Radio Box control can unexpectedly update the internal value for the unselected item | E9BX05 * | |
| SN-031400 | Resetting system time backwards causes negative "real time" value in STIMER output | E9BX04 | |
| SN-019028 | Truncation errors might occur when using Unicode SAS with UTF-8 encoding to process 8-bit characters | E9BX05 * | |
| SN-032113 | The $EBCDIC format/informat generates incorrect results if ENCODING=UTF8 is set | E9BX04 | |
| SN-019330 | Problems might occur when you invoke SAS® macros using Microsoft Object Linking and Embedding (OLE) automation submit method | E9BX05 * | |
| SN-032096 | ERROR "SAS Error Event: Error sending status, 1, to SCM. Error 6: The handle is invalid." occurs when stopping the SAS® Metadata Server | E9BX05 * | |
| SN-032521 | A Multi-Processing (MP) CONNECT session might not respond in UNIX environments | E9BX04 | |
| SN-032547 | Data sets written to tape in SAS® 8.2 are not readable in SAS 9.1.3 | E9BX05 * | |
| SN-033403 | Segmentation violation and bridge stub errors on AIX | E9BX05 * | |
| SN-035477 | Invalid physical name error when a FILE statement contains certain Shift-JIS characters | E9BX05 * | |
| SN-035481 | Java DBCS encoding on Windows uses incorrect Japanese encoding resulting in garbage characters | E9BX05 * | |
| E9BC81 | |||
| SN-019773 | Abend U1314 or traceback notes and messages attempting to read a migrated view from SAS® 8 | E9BX02 | |
| SN-035112 | Invalid binary data when tranferring SAS data sets with PROC COPY or CPORT/CIMPORT. | E9BX05 * | |
| E9BC91 | |||
| SN-036111 | Potential memory leak in SORT module causes Workspace server to fail | E9BX05 * | |
| E9BC96 | |||
| SN-017784 | Item in Verion 6 Legacy Radio Box might become unselectable on Linux | E9BX03 | |
| SN-019976 | Delete key not working when maskCharacter attribute set for Text Entry Control | E9BX03 | |
| SN-036214 | Segmentation violation error in masked text entry box | E9BX05 * | |
| E9BC97 | |||
| SN-017915 | Memory leak in transcoding routine from MBCS to MBCS | E9BX03 | |
| SN-019115 | TRANWRD() function has different performance in SAS® 6, and SAS® 8 and SAS® 9.1.3 | E9BX01 | |
| SN-020676 | PROC CIMPORT may fail or generate errors when the file contains SBCS Katakana data | E9BX03 | |
| SN-030987 | Performance problems occur in DBCS SAS® software when you use the RLINK or DLM= options in the FILENAME statement | E9BX03 | |
| SN-031391 | Transcoding problem occurs between SAS® Japanese encoding shift-jis and EUC | E9BX03 | |
| SN-019088 | KCVT function has problem handling trailing null character | E9BX01 | |
| SN-036269 | Inconsistent transcoding using the KCVT function produces incorrect results in SAS® 9.2 | E9BX05 * | |
| E9BC98 | |||
| SN-020378 | A segmentation violation might occur during execution of the DOWNLOAD procedure | E9BX03 | |
| SN-031087 | A floating-point exception error might occur if you use the DOWNLOAD procedure to move a file that is larger than 2 GB | E9BX03 | |
| SN-013122 | WZX: Invalid Conversion Map Specified | E9BX05 * | |
| SN-032983 | Invalid results occur when you use the DOWNLOAD procedure with the V6TRANSPORT option in SAS® 9.1.3 in the z/OS environment | E9BX04 | |
| SN-035807 | Observations might be missing after you use the UPLOAD procedure to transfer data sets | E9BX05 * | |
| SN-033576 | SAS® Enterprise Guide® does not detect when SAS data sets are created, updated, or deleted through a grid | E9BX05 * | |
| SN-036081 | The UPLOAD and DOWNLOAD procedures add null values to the ends of variables when you specify a SAS view with the DATA= data set option | E9BX05 * | |
| E9BD05 | |||
| SN-031241 | "ERROR: Library LIBREF is not assigned" when running the METALIB procedure | E9BX04 | |
| SN-017581 | ERROR: Invalid physical name for library XXXX is displayed when using Update Table Metadata or PROC METALIB with concatenated libraries | E9BX01 | |
| SN-017580 | ERROR: This Library is already assigned or cannot be reassigned | E9BX01 | |
| SN-017849 | PROC METALIB fails to update an SPDS library table metadata with "Error: Invalid Option User." | E9BX01 | |
| SN-019486 | "ERROR: Invalid memptr" occurs and the SAS® session becomes unresponsive when trying to access a view via a libref with the META LIBNAME engine | E9BX02 | |
| SN-020460 | Joining two tables can cause your system to stop responding or can cause an access-violation problem | E9BX04 | |
| SN-031002 | Database passwords are displayed in the SAS® log in clear text | E9BX04 | |
| SN-032284 | A Read-access violation occurs when running PROC METALIB to update tables that originate from an Adabas database | E9BX04 | |
| SN-016116 | Pre-Assigned Library fails with an unexpected error has occurred | E9BX04 | |
| SN-032376 | Access violation occurs when updating metadata for a table that contains multiple indexes with long index names | E9BX04 | |
| SN-034840 | Running PROC METALIB on a DB2 libray and attempting to update a table that has a foreign key relationship with another table might cause an error | E9BX05 * | |
| SN-036544 | ERROR: "Libname lref not available for use" occurs when assigning a library using the META engine | E9BX05 * | |
| E9BD11 | |||
| SN-036617 | SAS® might become unresponsive if the FILEDIALOG function is called from an SCL entry on Unix platforms | E9BX05 * | |
| E9BD13 | |||
| SN-017873 | Extra WHERE clause may get added to query passed to databases | E9BX01 | |
| SN-017888 | Segmentation Violation error issued when using PROC SQL and SAS/ACCESS® with a LENGTH= option larger than 32 | E9BX01 | |
| SN-018108 | Segmentation violation when executing multiple queries against a PROC SQL view containing a LIBNAME statement | E9BX01 | |
| SN-018176 | Import of table through Information Map Library Engine deletes physical table | E9BX01 | |
| SN-020479 | Batch jobs might end with a return code of 4 with no warning in the SAS® log | E9BX03 | |
| SN-018487 | Compress() function returns incorrect results when used on PROC SQL INSERT statement after applying SAS® 9.1.3 Service Pack 4 | E9BX01 | |
| SN-016074 | "WARNING: At least one nonessential grouping column reference has been removed from a GROUP BY's reference list" | E9BX01 | |
| SN-019170 | Errors issued when integer references for column is used in a PROC SQL GROUP BY statement | E9BX01 | |
| SN-019372 | Performance is poor in the SQL procedure when you use the COUNT(Distinct xxxx) function | E9BX02 | |
| SN-019527 | Specifying the NOIPASSTHRU option in PROC SQL does not disable implicit passthru | E9BX02 | |
| SN-016547 | Correlated subqueries using column aliases may not be passed to your dbms when using SAS/ACCESS LIBNAME statement | E9BX02 | |
| SN-019930 | Using more than 36 tables in a UNION operation within an SQL procedure generates an error message | E9BX02 | |
| SN-020130 | Aliases columns or aliased tables in the SQL procedure blocks Implicit Pass-Through | E9BX03 | |
| SN-030428 | Aliased constant values become missing in outer joins and unions | E9BX03 | |
| SN-020162 | Using functions without parameters in WHERE clauses can block Implicit Pass-Through | E9BX03 | |
| SN-020126 | SAS/ACCESS® software now provides full support of the INNER JOIN syntax | E9BX03 | |
| SN-020116 | SAS/ACCESS® software fails to use table aliases correctly when you use in-line SELECT statements | E9BX03 | |
| SN-020123 | Incorrect SQL text is generated when inner and left joins are used | E9BX03 | |
| SN-020125 | Using implicit pass-through might cause an incorrect table reference assignment | E9BX03 | |
| SN-020129 | An incorrect Implicit Pass-Through query is generated when you use a combination of inner and outer Joins | E9BX03 | |
| SN-020122 | Performance issues occur because SQL code is not passed to the database | E9BX03 | |
| SN-030390 | Improvements are now available in relational database optimization via the SQL procedure | E9BX03 | |
| SN-019655 | Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio | E9BX03 | |
| SN-020635 | Incorrect textualization of SQL Implicit Pass-Through queries occurs when you combine multiple inner joins with one or more outer joins | E9BX03 | |
| SN-032085 | Incorrect SQL optimization may produce incorrect results | E9BX04 | |
| SN-030942 | The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHAR | E9BX03 | |
| SN-030923 | Aliased summary functions in Base SAS® software are not passed to databases | E9BX03 | |
| SN-030893 | Using an ORDER BY clause in the SQL procedure causes performance problems | E9BX03 | |
| SN-031102 | A segmentation-violation error might occur after you apply Hot Fix E9BA83 and you access Oracle | E9BX03 | |
| SN-031191 | Support is now available for the PROC SQL CREATE TABLE statement for the SAS® Scalable Performance Data Server® | E9BX03 | |
| SN-031122 | SQLPLAN internal errors might occur when you select columns from an SQL view | E9BX03 | |
| SN-031121 | Implicit Pass-Through errors occur when accessing Oracle tables | E9BX03 | |
| SN-031291 | Errors occur in SAS® Scalable Performance Data Server® for numeric columns that are defined with the MISSING statement when it is used in WHERE processing | E9BX03 | |
| SN-031211 | Errors occur in the SQL procedure's Implicit Pass-Through facility after you apply hot fixes E9BB72, E9BB76, and E9BB80 | E9BX03 | |
| SN-031249 | SQLPLAN errors occur when you reference a calculated column on an SQL WHERE clause | E9BX03 | |
| SN-031905 | Enhancements to the Implicit SQL Pass-Through facility enable more of a query to be passed to a database | E9BX04 | |
| SN-031863 | Using the EQT operator in the SQL procedure incorrectly classifies rows with missing values as a match | E9BX04 | |
| SN-031564 | Performance problems occur when you use the CASE expression with DBMS tables | E9BX04 | |
| SN-031825 | After applying hot fixes E9BB98 and E9BB99, column aliases are passed to the SQL GROUP BY clause in place of the corresponding real column names | E9BX04 | |
| SN-033763 | Using the CALCULATED keyword in a WHERE clause in a PROC SQL inner join generates a cartesian product | E9BX04 | |
| SN-033649 | Calculations that involve DBMS datetime values can return incorrect results | E9BX04 | |
| SN-033073 | Using the CALCULATED keyword in a WHERE clause generates a Carteisan product | E9BX04 | |
| SN-032636 | A Read-access violation might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99 | E9BX04 | |
| SN-032537 | Incorrect query results might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99 or you run SAS® 9.2 | E9BX04 | |
| SN-032925 | An error occurs when you use the IDXNAME= and the WHERE= data set options in an SQL procedure query | E9BX04 | |
| SN-032472 | Concatenating libraries can result in Read-access violations in the SQL procedure | E9BX04 | |
| SN-032545 | An SQLPLAN error might occur after you apply hot fixes E9BB98 and E9BB99 | E9BX04 | |
| SN-032406 | Outer joins that contain a WHERE clause with the STRIP() and PUT() functions cause abnormal endings | E9BX04 | |
| SN-035779 | The LENGTH= column modifier is handled incorrectly when you use PROC SQL to create character columns in SAS® Scalable Performance Data Server® tables | E9BX05 * | |
| SN-034012 | Column aliases are not passed correctly to GROUP BY or ORDER BY clauses in the SAS® Scalable Performance Data Server® | E9BX05 * | |
| SN-032542 | An error message incorrectly appears when you use the IDXNAME= and the WHERE= option data set options together in an SQL procedure | E9BX04 | |
| SN-011210 | Incorrect results from PROC SQL using WHERE= option with indexed tables | E9BX04 | |
| SN-034564 | The COUNT() or N() functions return incorrect results when used in a query containing a WHERE clause or a WHERE= data set option | E9BX05 * | |
| SN-035011 | A Read-access violation occurs in the SQL procedure when the WHERE= data set option is placed in an ORDER BY clause | E9BX05 * | |
| SN-033094 | Incorrect results might be generated when you use the LIBNAME statement to join multiple Oracle tables | E9BX04 | |
| SN-033648 | The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2 | E9BX05 * | |
| SN-034993 | An error occurs when you run an SQL query with the ORACLE LIBNAME engine | E9BX05 * | |
| SN-034975 | Segmentation violations might occur after you apply Hot Fix E9BC46 in queries that reference DBMS tables | E9BX05 * | |
| SN-034391 | An SQLPLAN error might occur when you use a calculated field to subset a table | E9BX05 * | |
| SN-036280 | The SQL procedure generates incorrect results when you copy a SAS® data set from one platform to another platform | E9BX05 * | |
| SN-033084 | An SQLPLAN internal error might occur when reference a variable from an in-line view that created the variable from a constant | E9BX05 * | |
| SN-034678 | An SQLPLAN error occurs when you submit a query with a CALCULATED column reference in a CASE expression that contains a GROUP BY clause | E9BX05 * | |
| SN-036177 | Incorrect results might occur when you run a PROC SQL join with an additional WHERE clause against Teradata tables | E9BX05 * | |
| SN-036202 | SQLPLAN internal errors might occur when you reference calculated columns in an SQL procedure | E9BX05 * | |
| SN-036748 | The MULTI_DATASRC_OPT= option is ignored when multiple WHERE clause predicates are used in an SQL join operation | E9BX05 * | |
| SN-034153 | Option DBIDIRECTEXEC prevents SAS® Enterprise Guide from opening tables created by PROC SQL | E9BX05 * | |
| SN-034234 | Incorrect results might occur if you use the LIBNAME statement option IP=YES with an SQL procedure that contains data calculations in a WHERE clause | E9BX05 * | |
| E9BD14 | |||
| SN-016428 | DBSLICEPARM creates incorrect syntax when DB2DECPT=, | E9BX01 | |
| SN-030942 | The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHAR | E9BX03 | |
| SN-031862 | A U1314 abend might occur when a job sorts an SQL procedure view that references a DB2 table | E9BX04 | |
| SN-016338 | Using PROC APPEND to insert rows into an Oracle table may report an error as a note | E9BX05 * | |
| SN-033648 | The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2 | E9BX05 * | |
| SN-035895 | An error occurred Executing the Workspace Job | E9BX05 * | |
| SN-035991 | A generic IOM error occurs when executing a stored process that produces graphics output | E9BX05 * | |
| SN-036748 | The MULTI_DATASRC_OPT= option is ignored when multiple WHERE clause predicates are used in an SQL join operation | E9BX05 * | |
| SN-035879 | Data imported from a DB2 library may be corrupt | E9BX05 * | |
| E9BD15 | |||
| SN-017745 | WHERE clause processing against an SQL view can cause Read Access or Segmentation Violations | E9BX01 | |
| SN-031607 | Using the BY statement with the formatted ODS destinations can generate incorrect output | E9BX04 | |
| SN-017962 | The first blank space in the name literal table names gets removed when you set the SYSLAST macro variable or _LAST_ system option | E9BX01 | |
| SN-017876 | Creating index may cause SAS® to loop | E9BX01 | |
| SN-017981 | Incorrect output with WHERE and BY statements | E9BX01 | |
| SN-015813 | Read Access Violation in Task (CONNECT) caused by long comments | E9BX01 | |
| SN-018156 | Invoking an autocall macro which is stored as a SOURCE entry within a catalog may cause errors | E9BX01 | |
| SN-018305 | Garbage characters in SAS log when localized DBCS SAS is used with products related to the Workspace server | E9BX01 | |
| SN-018396 | Queries or WHERE clauses run against large data sets can cause SAS/SHARE® server to hang | E9BX01 | |
| SN-019372 | Performance is poor in the SQL procedure when you use the COUNT(Distinct xxxx) function | E9BX02 | |
| SN-019601 | The option VALIDVARNAME=UPCASE is not working as expected | E9BX02 | |
| SN-019978 | Specifying LOGPARM system option may generate INSUFFICIENT AUTHORIZATION messages | E9BX02 | |
| SN-019984 | Output in the listing is truncated using the DBCS version of SAS | E9BX02 | |
| SN-019344 | SAS® may ignore indexes during query on 64-Bit UNIX systems | E9BX02 | |
| SN-019578 | Update Flags from PROC SQL views are propagated by SAS® procedures with OUT= option | E9BX02 | |
| SN-020208 | The ACCESS=READONLY option in the CATNAME statement is not working correctly | E9BX02 | |
| SN-020562 | PROC APPEND step may damage BASE data set | E9BX02 | |
| SN-021003 | Using the %v or #v LOGPARM path directive might cause the workspace server to fail to start and processes to stop responding | E9BX03 | |
| SN-030390 | Improvements are now available in relational database optimization via the SQL procedure | E9BX03 | |
| SN-030428 | Aliased constant values become missing in outer joins and unions | E9BX03 | |
| SN-019655 | Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio | E9BX03 | |
| SN-031300 | Poor performance occurs when you use views that consist of inner joins from DBMS tables | E9BX03 | |
| SN-032375 | Errors might occur reading XML files using the XML engine with very long strings | E9BX04 | |
| SN-033744 | An incorrect buffer break occurs when calling a macro from an EXECUTE statement that specifies a parameter with an "at" sign (@) in the parameter name | E9BX05 * | |
| SN-035492 | Could not find value or Record ID (RID) to do delete on index | E9BX05 * | |
| SN-035895 | An error occurred Executing the Workspace Job | E9BX05 * | |
| SN-035991 | A generic IOM error occurs when executing a stored process that produces graphics output | E9BX05 * | |
| SN-034012 | Column aliases are not passed correctly to GROUP BY or ORDER BY clauses in the SAS® Scalable Performance Data Server® | E9BX05 * | |
| SN-036280 | The SQL procedure generates incorrect results when you copy a SAS® data set from one platform to another platform | E9BX05 * | |
| SN-033084 | An SQLPLAN internal error might occur when reference a variable from an in-line view that created the variable from a constant | E9BX05 * | |
| SN-034678 | An SQLPLAN error occurs when you submit a query with a CALCULATED column reference in a CASE expression that contains a GROUP BY clause | E9BX05 * | |
| SN-036177 | Incorrect results might occur when you run a PROC SQL join with an additional WHERE clause against Teradata tables | E9BX05 * | |
| SN-036202 | SQLPLAN internal errors might occur when you reference calculated columns in an SQL procedure | E9BX05 * | |
| SN-036281 | PROC REPORT output generated by the CALL EXECUTE routine does not include text or variables generated by a COMPUTE block | E9BX05 * | |
| SN-034018 | MPRINT output generated twice when CALL EXECUTE is used within a macro | E9BX05 * | |
| SN-036070 | Extraneous code might be added if CALL EXECUTE is used to generate many ODS HTML statements | E9BX05 * | |
| SN-036592 | DELETE statement sometimes does not remove qualifying observations | E9BX05 * | |
| SN-034234 | Incorrect results might occur if you use the LIBNAME statement option IP=YES with an SQL procedure that contains data calculations in a WHERE clause | E9BX05 * | |
| E9BX05 * | 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.