| The following fixes are included in the E9BX05 Bundle for OS/390: | 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 | E9BX01 | |
| 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 | |
| E9BA14 | |||
| SN-016954 | SAS/Integration Technologies 9.1 Object Spawner consumes excessive CPU when an ERROR=122 (EIO) occurs | 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 | |
| E9BA46 | |||
| SN-015522 | "ERROR: System abend s0C4 occurred in module unknown - vxvtc at offset 00082C" | E9BX01 | |
| E9BA51 | |||
| SN-018393 | Accessing a member from MEMLIST produces "ERROR: Invalid Device Type" | E9BX01 | |
| E9BA59 | |||
| SN-033285 | z/OS diagnostic traps might cause Base SASŪ software to abend | E9BX04 | |
| E9BA62 | |||
| 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 | |
| SN-018737 | Hot fix E9BA45 replaced by E9BA62 for z/OS | 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 | E9BX04 | |
| E9BA86 | |||
| SN-019227 | NOWARN option for PROC APPEND | E9BX01 | |
| E9BA87 | |||
| SN-019218 | ERRORS produced when ODS PDF output contains a long byline | E9BX01 | |
| E9BA91 | |||
| SN-016283 | A Japanese character that contains the hex value for a single or double quote may cause the Program Editor to have an incorrect color | E9BX01 | |
| E9BA98 | |||
| SN-019388 | "Read Access Violation in Task [ Application Window ]" with SAS/AF Table Viewer Control | 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 | |
| E9BB49 | |||
| SN-020409 | CDF, SDF, and QUANTILE functions might return missing values for the Beta distribution and small values of first shape parameter | 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 | |
| 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 | |
| E9BC04 | |||
| SN-017125 | LOCATEC/N function is counting deleted rows in its search | 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 * | |
| 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 | |
| E9BC27 | |||
| SN-030979 | Performance degradation might occur in SASŪ9 if you process VSAM files on a Remote Library Services (RLS) server | E9BX03 | |
| SN-032421 | Reading VSAM RLS file results in zero records read | 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 | |
| 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 * | |
| E9BC49 | |||
| SN-018011 | SPECIFIED RESOURCE DOES NOT EXIST message with ENCODING=(W5|W6|W9) and SPDE engine | E9BX01 | |
| SN-018254 | MDX WHERE clause might return incorrect number of rows resulting in a performance loss | E9BX01 | |
| SN-018911 | "ERROR: System Exiting Status=401" message occurs when multiple processes update a SPD Engine data set | E9BX01 | |
| SN-032674 | PROC OLAP stops responding even though CPU usage is high | E9BX04 | |
| SN-033673 | Encountered error in DA-subsystem. | E9BX04 | |
| E9BC54 | |||
| SN-033879 | SAS® utilities abend when some diagnostic traps are set on z/OS | E9BX05 * | |
| E9BC55 | |||
| SN-033882 | SAS® might receive a 0C4 abend while performing TCP functions | E9BX05 * | |
| E9BC56 | |||
| SN-019742 | An error occurs when attempting to connect to the SASŪ Metadata Server and the METAUSER= system option contains an embedded space | E9BX03 | |
| SN-033883 | The SAS® object spawner might abend with a 0C4 if certain diagnostic traps are enabled | E9BX05 * | |
| E9BC58 | |||
| SN-033995 | Error: "IOM call failed. Internal server exception: floating point divide by zero." | E9BX05 * | |
| E9BC59 | |||
| SN-017767 | Export and Import Wizards require Metadata Server fixes | E9BX01 | |
| SN-017743 | Login to SASŪ web application fails when using an email address as the userid with LDAP authentication | E9BX01 | |
| SN-017761 | Jobs that are duplicated within a Project repository may lose their connection to Target objects | E9BX01 | |
| SN-017860 | BI Manager "Import" might cause metadata to be destroyed for all stored processes that contain parameters in SAS 9.1.3 Service Pack 4 | E9BX01 | |
| SN-017852 | External table objects may get inadvertently deleted from metadata when importing or exporting metadata multiple times | E9BX01 | |
| SN-017855 | Server code does not support exporting and importing from a metadata Project repository | E9BX01 | |
| SN-017857 | Exception may occur while exporting a block of objects from the Data Integration Studio custom tree | E9BX01 | |
| SN-017854 | Incorrect behavior might occur when all items are not selected within a package when performing a metadata import | E9BX01 | |
| SN-018452 | Unauthorized access to metadata server content | E9BX01 | |
| SN-030465 | Adding new records to a metadata repository after performing a metadata restore adds multiple metadata objects with the same internal ID value | E9BX03 | |
| SN-031345 | Metadata objects stored in a custom repository are not returned by client applications or metadata query results when they should be | E9BX04 | |
| SN-033984 | Poor performance occurs in client applications when the metadata environment contains a large number of repositories | E9BX05 * | |
| SN-034096 | Content is added to a parent repository, even when you do not have Check In Metadata permissions | 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-032805 | Trusted Peer Connections between a SASŪ process in a Windows environment and a Metadata Server in a z/OS environment run as public user connections | E9BX04 | |
| 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-017072 | Metadata server service might show starting state but never start | E9BX03 | |
| SN-020274 | Grid sign-on fails to honor the TCPPORTFIRST and the TCPPORTLAST options | E9BX03 | |
| 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-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 | E9BX05 * | |
| 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-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 * | |
| 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 | E9BX04 | |
| 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 | E9BX04 | |
| 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 * | |
| E9BD03 | |||
| SN-017410 | SASŪ OLAP Server process may crash if slicer contains infinite loop | E9BX01 | |
| SN-017408 | Permission condition memory is not released when OLAP session closed | E9BX01 | |
| SN-017409 | SASŪ OLAP Server performance enhancements available in SAS 9.1.3 Service Pack 4 | E9BX01 | |
| SN-018037 | PROC OLAP DEFINE statement can allow duplicate calculated members to be created | E9BX01 | |
| SN-017931 | NUNIQUE values may be incorrect depending on the setting for "Maximum number of region execution threads" | E9BX01 | |
| SN-017445 | Listing active queries on SASŪ OLAP Server can cause server crash | E9BX01 | |
| SN-017523 | Selecting an OLAP Session in the OLAP Server monitor may cause SASŪ Management Console to hang | E9BX01 | |
| SN-018020 | SASŪ OLAP Server may error when empty data is passed to certain SASŪ functions | E9BX01 | |
| SN-017871 | Drilldown may cause calculated member values to return from the SASŪ OLAP Server as missing in Service Pack 4 | E9BX01 | |
| SN-018018 | Complex MDX query within a WITH expression might generate an access violation | E9BX01 | |
| SN-018030 | SASŪ OLAP Server might abend with an OLS_NAMESPACEDELETE traceback | E9BX01 | |
| SN-017907 | OLAP cubes with deep hierarchies may return incorrect result sets | E9BX01 | |
| SN-018089 | Detailed SASŪ OLAP Server logging now outputs SAS OLAP Server option settings | E9BX01 | |
| SN-018012 | Threadpool options for the SAS® OLAP Server are being overwritten | E9BX01 | |
| SN-018198 | TKASSERT error might be received when querying a SASŪ OLAP cube on z/OS | E9BX01 | |
| SN-017449 | NON EMPTY CROSSJOIN optimization in SASŪ OLAP Server | E9BX01 | |
| SN-018254 | MDX WHERE clause might return incorrect number of rows resulting in a performance loss | E9BX01 | |
| SN-018701 | Session and Global calculated members might be dropped when using NonEmpty Optimization | E9BX01 | |
| SN-018580 | Disabling NonEmpty Crossjoin optimization does not have any effect | E9BX01 | |
| SN-018794 | DrillDownMemberTop function might cause crashes in the SASŪ OLAP Server | E9BX01 | |
| SN-018702 | Global calculated members might cause crash in SAS OLAP Server with Optimization of Non Empty Crossjoins | E9BX01 | |
| SN-018795 | OLAP queries might return empty results if requesting missing values | E9BX01 | |
| SN-018796 | MDX iif functions that return null values might incorrectly return empty result sets | E9BX01 | |
| SN-019048 | Calculated measures might be dropped from the OLAP result set when using Non Empty Crossjoin Optimization | E9BX01 | |
| SN-019164 | Memory degradation or access violation could occur when querying a SAS® OLAP cube with member-level security applied | E9BX01 | |
| SN-018253 | DBCS drillthrough labels might not be rendered correctly | E9BX01 | |
| SN-019226 | Sorted OLAP queries might return incorrect results | E9BX01 | |
| SN-019314 | Use of global MDX String functions could halt the SASŪ OLAP Server | E9BX01 | |
| SN-019418 | AGGREGATE MDX function might cause slow query performance when member-level security is defined to the OLAP cube | E9BX01 | |
| SN-019725 | AGGREGATE functions using calculated members containing NUNIQUE measures might cause SASŪ OLAP Server to crash | E9BX02 | |
| SN-019820 | NONEMPTYCROSSJOIN function might cause data loss in an OLAP Query | E9BX02 | |
| SN-020202 | Incorrect totals calculated when aggregate has members in same dimension of the NUNIQUE measure being used | E9BX02 | |
| SN-020292 | SASŪ OLAP Server performance might be worse after applying hotfix E9BA34 or later | E9BX02 | |
| SN-020291 | SASŪ OLAP Server AGGREGATE function might return incorrect results on certain calculated members | E9BX02 | |
| SN-030537 | SAS MDX isEmpty function will not evaluate cells containing character data | E9BX03 | |
| SN-020146 | Total calculations might be incorrect when an NUNIQUE measure is used | E9BX02 | |
| SN-013365 | Drill-through and ROLAP aggregation tables can fail if the MDX query contains a numeric member | E9BX04 | |
| SN-020028 | Empty drillthrough result when format width for a column is too small | E9BX04 | |
| SN-020652 | NON EMPTY CROSSJOIN optimization might drop members from result set | E9BX05 * | |
| SN-035621 | SASŪ OLAP Server appears to hang and must be frequently restarted | E9BX05 * | |
| SN-033970 | NON EMPTY CROSSJOIN optimization might cause slower performance with secured data | E9BX05 * | |
| SN-036393 | ERROR: "An OLAP server thread has failed" occurs when a drill-through query returns no records | 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 * | |
| E9BD07 | |||
| SN-030992 | A memory shortage might cause a loop and SC78 abend to occur in SASŪ Metadata Server in the z/OS environment | E9BX03 | |
| SN-031147 | Performance issues might occur with the SASŪ OLAP Server in the z/OS environment | E9BX03 | |
| SN-031661 | Using the TKOPT_CPOOL3= threaded-kernel environment variable causes large amounts of memory to be used | E9BX05 * | |
| SN-036446 | SASŪ session intermittently becomes non-responsive upon SAS termination | 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 | E9BX04 | |
| 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 * | |
| SN-037611 | Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment | E9BX05 * | |
| E9BD14 | |||
| SN-016428 | DBSLICEPARM creates incorrect syntax when DB2DECPT=, | E9BX01 | |
| SN-018162 | System abend SA03 during SASŪ termination when DB2 LIBNAME engine with DEFER=YES specified | E9BX03 | |
| 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-037611 | Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment | 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-015882 | A DBCS character that contains the hexadecimal value for a single or double quote might be misinterpreted by the SASŪ tokenizer | 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 | E9BX04 | |
| 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 | E9BX04 | |
| 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 * | |
| E9BD16 | |||
| SN-017147 | Output to RECFM=FB SASLIST file may contain carriage control | E9BX01 | |
| SN-017380 | Client TSO session loops while processing FSBROWSE on library allocated to a SAS/SHAREŪ server | E9BX01 | |
| SN-019281 | PROC CIMPORT fails when the transport file is a member of an uncataloged partitioned data set | E9BX03 | |
| SN-017797 | "ERROR: Physical file does not exist, SYS06144.T115731.RA000.N389610T.INCL.H04" message from %INCLUDE | E9BX01 | |
| SN-013425 | Autoexec may continue processing when leaving MENU entry defined to SHARE server in SAS/AF | E9BX01 | |
| SN-018423 | Control incorrectly appears to return to SAS/AFŪ application when sorting data on the mainframe | E9BX01 | |
| SN-013720 | TSO may hang when leaving SAS after running SAS/AF application with SAS/SHARE | E9BX01 | |
| SN-016476 | System abend 0C4 in module SASTK | E9BX01 | |
| SN-018430 | ERROR: Unable to initialize TCP/IP subsystem returns Condition Code 0 | E9BX01 | |
| SN-019299 | Division-by-zero processing causes severe performance degradation | E9BX01 | |
| SN-020327 | Contents of a variable change when you pass the variable to the FILEEXIST function | E9BX02 | |
| SN-018637 | ALTLOG and ALTLIST files may be missing if directed to HFS | E9BX01 | |
| SN-019065 | DISP is ignored in LIBNAME statement when existing allocation already exists | E9BX01 | |
| SN-019522 | The FILENAME function for an HFS pathSAS argument generates incorrect results | E9BX01 | |
| SN-017038 | Limited support in SASŪ 9.1.3 SP4 for DSNTYPE=LARGE data sets when running under z/OS Releases V1R7 and later | E9BX02 | |
| SN-019842 | SASŪ 9 software reads all generations of a generation data group controlled by the Storage Management Subsystem | E9BX02 | |
| SN-020035 | The RELEASE procedure can damage a currently assigned SASŪ data library, resulting in an I/O error or U315 abnormal ending message | E9BX02 | |
| SN-020459 | Performance issues found in SASŪ software memory management on the z/OS platform | E9BX02 | |
| SN-020583 | Concatenation of 257 physical sequential data sets fails when you run SASŪ software on z/OS | E9BX03 | |
| SN-020905 | Warning messages might appear when you read a large file from a UNIX file system | E9BX03 | |
| SN-030981 | MP CONNECT (multi-process CONNECT) might fail when you use the XMS Access Method in Base SASŪ in the z/OS environment | E9BX03 | |
| SN-010972 | An error occurs when you use the %INCLUDE statement with a fileref that begins with an underscore | E9BX03 | |
| SN-031411 | Unused allocated space on a volume other than the last volume of an existing library will generate a warning rather than an error | E9BX03 | |
| SN-033865 | Base SASŪ software might enter a loop after an input/output (I/O) error or âout of spaceâ error occurs | E9BX04 | |
| SN-032798 | The system ends abnormally with an S0C4 abend code during SAS termination | E9BX04 | |
| SN-033040 | A %INCLUDE statement for an explicit path of a cataloged disk data set might fail in Base SASŪ in the z/OS environment | E9BX04 | |
| SN-034459 | Using the NODLTRUNCK option to process truncated libraries can result in data loss | E9BX05 * | |
| SN-033892 | A SAS/SHAREŪ server does not free a library when a client times out | E9BX05 * | |
| SN-035332 | The message "Libname libref is not assigned" might appear if you do not specify an engine | E9BX05 * | |
| SN-035116 | An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70 | E9BX05 * | |
| SN-035225 | An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70 | E9BX05 * | |
| SN-036164 | ERROR: "Library data set temp.dataset.name does not comply with RECFM=FS requirements or is truncated" | E9BX05 * | |
| SN-037166 | An abend occurs when you specify a user exit in an INFILE or FILE statement or with the ENGINE= option in the FILENAME statement | 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.