| E9BD38 for z/OS (OS/390) |
| Released: Aug 2010 |
| Issue(s) Addressed: | Introduced: |
| SN-017410 |
SAS® OLAP Server process may crash if slicer contains infinite loop |
E9BA01 |
| SN-017408 |
Permission condition memory is not released when OLAP session closed |
E9BA01 |
| SN-017409 |
SAS® OLAP Server performance enhancements available in SAS 9.1.3 Service Pack 4 |
E9BA01 |
| SN-018037 |
PROC OLAP DEFINE statement can allow duplicate calculated members to be created |
E9BA34 |
| SN-017931 |
NUNIQUE values may be incorrect depending on the setting for "Maximum number of region execution threads" |
E9BA34 |
| SN-017445 |
Listing active queries on SAS® OLAP Server can cause server crash |
E9BA34 |
| SN-017523 |
Selecting an OLAP Session in the OLAP Server monitor may cause SAS® Management Console to hang |
E9BA34 |
| SN-018020 |
ALERT - SAS® OLAP Server may error when empty data is passed to certain SAS® functions |
E9BA34 |
| SN-017871 |
ALERT - Drilldown may cause calculated member values to return from the SAS® OLAP Server as missing in Service Pack 4 |
E9BA34 |
| SN-018018 |
Complex MDX query within a WITH expression might generate an access violation |
E9BA34 |
| SN-018030 |
SAS® OLAP Server might abend with an OLS_NAMESPACEDELETE traceback |
E9BA34 |
| SN-017907 |
ALERT - OLAP cubes with deep hierarchies may return incorrect result sets |
E9BA34 |
| SN-018089 |
Detailed SAS® OLAP Server logging now outputs SAS OLAP Server option settings |
E9BA34 |
| SN-018012 |
Threadpool options for the SAS® OLAP Server are being overwritten |
E9BA34 |
| SN-018198 |
TKASSERT error might be received when querying a SAS® OLAP cube on z/OS |
E9BA34 |
| SN-017449 |
NON EMPTY CROSSJOIN optimization in SAS® OLAP Server |
E9BA47 |
| SN-018254 |
MDX WHERE clause might return incorrect number of rows resulting in a performance loss |
E9BA56 |
| SN-018701 |
ALERT - Session and Global calculated members might be dropped when using NonEmpty Optimization |
E9BA56 |
| SN-018580 |
Disabling NonEmpty Crossjoin optimization does not have any effect |
E9BA56 |
| SN-018794 |
ALERT - DrillDownMemberTop function might cause crashes in the SAS® OLAP Server |
E9BA56 |
| SN-018702 |
ALERT - Global calculated members might cause crash in SAS OLAP Server with Optimization of Non Empty Crossjoins |
E9BA56 |
| SN-018795 |
ALERT - OLAP queries might return empty results if requesting missing values |
E9BA56 |
| SN-018796 |
ALERT - MDX iif functions that return null values might incorrectly return empty result sets |
E9BA56 |
| SN-019048 |
ALERT - Calculated measures might be dropped from the OLAP result set when using Non Empty Crossjoin Optimization |
E9BA56 |
| SN-019164 |
Memory degradation or access violation could occur when querying a SAS® OLAP cube with member-level security applied |
E9BA84 |
| SN-018253 |
DBCS drillthrough labels might not be rendered correctly |
E9BA89 |
| SN-019226 |
ALERT - Sorted OLAP queries might return incorrect results |
E9BA89 |
| SN-019314 |
Use of global MDX String functions could halt the SAS® OLAP Server |
E9BA93 |
| SN-019418 |
AGGREGATE MDX function might cause slow query performance when member-level security is defined to the OLAP cube |
E9BA99 |
| SN-019725 |
AGGREGATE functions using calculated members containing NUNIQUE measures might cause SAS® OLAP Server to crash |
E9BB07 |
| SN-019820 |
ALERT - NONEMPTYCROSSJOIN function might cause data loss in an OLAP Query |
E9BB19 |
| SN-020202 |
Incorrect totals calculated when aggregate has members in same dimension of the NUNIQUE measure being used |
E9BB33 |
| SN-020292 |
SAS® OLAP Server performance might be worse after applying hotfix E9BA34 or later |
E9BB38 |
| SN-020291 |
ALERT - SAS® OLAP Server AGGREGATE function might return incorrect results on certain calculated members |
E9BB38 |
| SN-030537 |
SAS MDX isEmpty function will not evaluate cells containing character data |
E9BB68 |
| SN-020146 |
ALERT - Total calculations might be incorrect when an NUNIQUE measure is used |
E9BB68 |
| SN-013365 |
Drill-through and ROLAP aggregation tables can fail if the MDX query contains a numeric member |
E9BC15 |
| SN-020028 |
Empty drillthrough result when format width for a column is too small |
E9BC15 |
| SN-020652 |
NON EMPTY CROSSJOIN optimization might drop members from result set |
E9BC73 |
| SN-035621 |
SAS® OLAP Server appears to hang and must be frequently restarted |
E9BC88 |
| SN-033970 |
NON EMPTY CROSSJOIN optimization might cause slower performance with secured data |
E9BC92 |
| SN-036393 |
ERROR: "An OLAP server thread has failed" occurs when a drill-through query returns no records |
E9BD03 |
| SN-038401 |
MDX queries using totals in SAS® Web reports are not optimized by the SAS® OLAP Server |
E9BD21 |
| SN-038374 |
An error related to AVL trees might be returned by OLAP queries |
E9BD23 |
| SN-038652 |
Performance problems might occur on SAS® OLAP Servers that are running multiple requests |
E9BD24 |
| SN-038708 |
"Internal server exception: access violation" and _pthread_body errors received during an OLAP query |
E9BD24 |
| SN-040398 |
The SAS® OLAP Server might fail on Microsoft Windows Server installations |
E9BD38 |
| Install Instructions: E9BD38os.txt |
(These install instructions may contain recent updates which are not included in the instructions packaged in the hot fix download.) |
|
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BD38.
Download: E9BD38 for
z/OS (OS/390) (File Size: 1.7M) |
ATTENTION: If you are running SAS Management Console 9.1.3 Service Pack 4, with Implementation-Version=9.1.20050622.20001, you must also download and install SAS Management Console hot fix 913SMC02 to address the issue described in SN-017449. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD38 and 913SMC02 are applied.
You do not need to install 913SMC02 if you have any other Implementation-Version of SAS Management Console.
ATTENTION: To fully implement the fix for SN-018254, you must also download and install SAS Base hot fix E9BC49. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD38 and E9BC49 are applied. |
| E9BD42 for z/OS (OS/390) |
| Released: Nov 2010 |
| Issue(s) Addressed: | Introduced: |
| SN-017745 |
WHERE clause processing against an SQL view can cause Read Access or Segmentation Violations |
E9BA28 |
| SN-031607 |
Using the BY statement with the formatted ODS destinations can generate incorrect output |
E9BA36 |
| 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 |
E9BA36 |
| SN-017876 |
Creating index may cause SAS® to loop |
E9BA36 |
| SN-017981 |
ALERT - Incorrect output with WHERE and BY statements |
E9BA36 |
| SN-015813 |
Read Access Violation in Task (CONNECT) caused by long comments |
E9BA50 |
| SN-018156 |
Invoking an autocall macro which is stored as a SOURCE entry within a catalog may cause errors |
E9BA50 |
| SN-018305 |
Garbage characters in SAS log when localized DBCS SAS is used with products related to the Workspace server |
E9BA50 |
| SN-018396 |
Queries or WHERE clauses run against large data sets can cause SAS/SHARE® server to hang |
E9BA50 |
| SN-015882 |
A DBCS character that contains the hexadecimal value for a single or double quote might be misinterpreted by the SAS® tokenizer |
E9BA67 |
| SN-019372 |
Performance is poor in the SQL procedure when you use the COUNT(Distinct xxxx) function |
E9BB02 |
| SN-019601 |
The option VALIDVARNAME=UPCASE is not working as expected |
E9BB02 |
| SN-019978 |
Specifying LOGPARM system option may generate INSUFFICIENT AUTHORIZATION messages |
E9BB13 |
| SN-019984 |
Output in the listing is truncated using the DBCS version of SAS |
E9BB13 |
| SN-019344 |
SAS® may ignore indexes during query on 64-Bit UNIX systems |
E9BB13 |
| SN-019578 |
Update Flags from PROC SQL views are propagated by SAS® procedures with OUT= option |
E9BB13 |
| SN-020208 |
The ACCESS=READONLY option in the CATNAME statement is not working correctly |
E9BB35 |
| SN-020562 |
PROC APPEND step may damage BASE data set |
E9BB52 |
| SN-021003 |
Using the %v or #v LOGPARM path directive might cause the workspace server to fail to start and processes to stop responding |
E9BB63 |
| SN-030428 |
Aliased constant values become missing in outer joins and unions |
E9BB72 |
| SN-030390 |
Improvements are now available in relational database optimization via the SQL procedure |
E9BB72 |
| SN-019655 |
Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio |
E9BB72 |
| SN-031300 |
Poor performance occurs when you use views that consist of inner joins from DBMS tables |
E9BB98 |
| SN-032375 |
Errors might occur reading XML files using the XML engine with very long strings |
E9BC16 |
| 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 |
E9BC51 |
| SN-036281 |
PROC REPORT output generated by the CALL EXECUTE routine does not include text or variables generated by a COMPUTE block |
E9BC61 |
| SN-034018 |
MPRINT output generated twice when CALL EXECUTE is used within a macro |
E9BC61 |
| SN-035492 |
Could not find value or Record ID (RID) to do delete on index |
E9BC85 |
| SN-035117 |
ANYDTDTE informat incorrectly interprets invalid date value as a SAS date |
E9BC86 |
| SN-035895 |
An error occurred Executing the Workspace Job The server is disconnected message might occur if you run a job in SAS® Enterprise Guide® |
E9BC89 |
| SN-035991 |
A generic IOM error occurs when executing a stored process that produces graphics output |
E9BC89 |
| SN-034012 |
Column aliases are not passed correctly to GROUP BY or ORDER BY clauses in the SAS® Scalable Performance Data Server® |
E9BC93 |
| SN-036280 |
ALERT - The SQL procedure generates incorrect results when you copy a SAS® data set from one platform to another platform |
E9BC93 |
| SN-033084 |
An SQLPLAN internal error might occur when reference a variable from an in-line view that created the variable from a constant |
E9BC93 |
| SN-040951 |
Arithemetic performed on DATA and TIME data types is not passed to the underlying DBMS in SAS/ACCESS® 9.1.3 software |
E9BC93 |
| 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 |
E9BC93 |
| SN-036177 |
Incorrect results might occur when you run a PROC SQL join with an additional WHERE clause against Teradata tables |
E9BC93 |
| SN-036202 |
SQLPLAN internal errors might occur when you reference calculated columns in an SQL procedure |
E9BC93 |
| SN-036070 |
Extraneous code might be added if CALL EXECUTE is used to generate many ODS HTML statements |
E9BD01 |
| SN-036592 |
ALERT - DELETE statement sometimes does not remove qualifying observations |
E9BD10 |
| 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 |
E9BD15 |
| SN-038698 |
SAS® Enterprise Guide® becomes unresponsive and the SAS® Workspace Server log grows extremely large |
E9BD22 |
| SN-040558 |
Invoking nested autocall macros using des= option causes error |
E9BD42 |
| Install Instructions: E9BD42os.txt |
(These install instructions may contain recent updates which are not included in the instructions packaged in the hot fix download.) |
|
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BD42.
Download: E9BD42 for
z/OS (OS/390) (File Size: 12.9M) |
ATTENTION (1): To complete the installation of this hot fix, you must also download and install SAS Base hot fixes E9BD61 and E9BD48.
Download E9BD61
Download E9BD61 for SAS with Asian Language Support (DBCS) Download E9BD48
Download E9BD48 for SAS with Asian Language Support (DBCS) This hot fix will NOT be fully functional without E9BD61 and E9BD48 applied.
ATTENTION (2): For additional configuration instructions for improving relational database optimization, see Problem Note SN-030390 above. |
| E9BD54 for z/OS (OS/390) |
| Released: Apr 2011 |
| Issue(s) Addressed: | Introduced: |
| SN-017147 |
Output to RECFM=FB SASLIST file may contain carriage control |
E9BA11 |
| SN-017380 |
Client TSO session loops while processing FSBROWSE on library allocated to a SAS/SHARE® server |
E9BA11 |
| SN-019281 |
PROC CIMPORT fails when the transport file is a member of an uncataloged partitioned data set |
E9BA41 |
| SN-017797 |
"ERROR: Physical file does not exist, SYS06144.T115731.RA000.N389610T.INCL.H04" message from %INCLUDE |
E9BA41 |
| SN-018423 |
Control incorrectly appears to return to SAS/AF® application when sorting data on the mainframe |
E9BA52 |
| SN-013425 |
Autoexec may continue processing when leaving MENU entry defined to SHARE server in SAS/AF |
E9BA52 |
| SN-013720 |
TSO may hang when leaving SAS after running SAS/AF application with SAS/SHARE |
E9BA52 |
| SN-016476 |
System abend 0C4 in module SASTK |
E9BA52 |
| SN-018430 |
ERROR: Unable to initialize TCP/IP subsystem returns Condition Code 0 |
E9BA52 |
| SN-019299 |
Division-by-zero processing causes severe performance degradation |
E9BA75 |
| SN-020327 |
Contents of a variable change when you pass the variable to the FILEEXIST function |
E9BB03 |
| SN-018637 |
ALTLOG and ALTLIST files may be missing if directed to HFS |
E9BB03 |
| SN-019065 |
DISP is ignored in LIBNAME statement when existing allocation already exists |
E9BB03 |
| SN-019522 |
The FILENAME function for an HFS pathSAS argument generates incorrect results |
E9BB03 |
| SN-017038 |
Limited support in SAS® 9.1.3 SP4 for DSNTYPE=LARGE data sets when running under z/OS Releases V1R7 and later |
E9BB25 |
| SN-019842 |
SAS® 9 software reads all generations of a generation data group controlled by the Storage Management Subsystem |
E9BB25 |
| SN-020035 |
The RELEASE procedure can damage a currently assigned SAS® data library, resulting in an I/O error or U315 abnormal ending message |
E9BB34 |
| SN-020459 |
Performance issues found in SAS® software memory management on the z/OS platform |
E9BB44 |
| SN-020583 |
Concatenation of 257 physical sequential data sets fails when you run SAS® software on z/OS |
E9BB57 |
| SN-020905 |
Warning messages might appear when you read a large file from a UNIX file system |
E9BB67 |
| SN-030981 |
MP CONNECT (multi-process CONNECT) might fail when you use the XMS Access Method in Base SAS® in the z/OS environment |
E9BB90 |
| SN-010972 |
An error occurs when you use the %INCLUDE statement with a fileref that begins with an underscore |
E9BC06 |
| SN-033865 |
Base SAS® software might enter a loop after an input/output (I/O) error or “out of space†error occurs |
E9BC53 |
| SN-032798 |
The system ends abnormally with an S0C4 abend code during SAS termination |
E9BC53 |
| 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 |
E9BC53 |
| SN-034459 |
Using the NODLTRUNCK option to process truncated libraries can result in data loss |
E9BC64 |
| SN-033892 |
A SAS/SHARE® server does not free a library when a client times out |
E9BC70 |
| SN-035332 |
The message "Libname libref is not assigned" might appear if you do not specify an engine |
E9BC82 |
| SN-035116 |
An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70 |
E9BC82 |
| SN-035225 |
An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70 |
E9BC82 |
| SN-036164 |
ERROR: "Library data set temp.dataset.name does not comply with RECFM=FS requirements or is truncated" |
E9BD04 |
| 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 |
E9BD16 |
| SN-039847 |
The error "...NO UNIT AVAILABLE" occurs when you allocate an existing data set |
E9BD31 |
| SN-041191 |
The FILEVAR= option in the INFILE or FILE statement does not work properly with the INFILE/FILE user exit |
E9BD45 |
| SN-041261 |
ALERT - A SAS® job that is running in a z/OS 1.12 operating environment might stop responding when an external file I/O error occurs |
E9BD45 |
| SN-041220 |
Mixed-case passwords that are submitted to a SAS® server in a z/OS operating environment return a security verification failure to the client |
E9BD54 |
| Install Instructions: E9BD54os.txt |
(These install instructions may contain recent updates which are not included in the instructions packaged in the hot fix download.) |
|
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BD54.
Download: E9BD54 for
z/OS (OS/390) (File Size: 5.1M) |
| ATTENTION: To fully implement the fix for SN-041220, you must also download and install SAS Base hot fix E9BD55. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD54 and E9BD55 are applied. |
| E9BD56 for z/OS (OS/390) |
| Released: Jun 2011 |
| Issue(s) Addressed: | Introduced: |
| SN-017072 |
Metadata server service might show starting state but never start |
E9BA19 |
| SN-020274 |
Grid sign-on fails to honor the TCPPORTFIRST and the TCPPORTLAST options |
E9BB36 |
| SN-019386 |
SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]" |
E9BB58 |
| SN-020817 |
Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routine |
E9BB58 |
| SN-031719 |
Some components from version 6 of SAS/AF® software might cause a read-access violation with repeated use |
E9BC09 |
| SN-031795 |
Dragging the cursor to an unselected item within the Radio Box control can unexpectedly update the internal value for the unselected item |
E9BC09 |
| SN-031400 |
Resetting system time backwards causes negative "real time" value in STIMER output |
E9BC09 |
| SN-019028 |
Truncation errors might occur when using Unicode SAS with UTF-8 encoding to process 8-bit characters |
E9BC18 |
| SN-032113 |
The $EBCDIC format/informat generates incorrect results if ENCODING=UTF8 is set |
E9BC18 |
| SN-019330 |
Problems might occur when you invoke SAS® macros using Microsoft Object Linking and Embedding (OLE) automation submit method |
E9BC18 |
| 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 |
E9BC18 |
| SN-032521 |
ALERT - A Multi-Processing (MP) CONNECT session might not respond in UNIX environments |
E9BC18 |
| SN-032547 |
Data sets written to tape in SAS® 8.2 are not readable in SAS® 9.1.3 |
E9BC18 |
| SN-033403 |
Segmentation violation and bridge stub errors on AIX |
E9BC60 |
| SN-036130 |
Running large SQL queries in the AIX operating environment can generate results with missing values |
E9BC60 |
| SN-034651 |
Using a Japanese or DBCS character in a pathname may cause truncation of file name |
E9BC67 |
| SN-034955 |
The SAS® Metadata Server stops accepting new client connections and returns an error when too many files are open |
E9BD12 |
| SN-041361 |
Modification datetime stamp is changed on existing version of a SAS® data set when you create a new data set with same name |
E9BD44 |
| Install Instructions: E9BD56os.txt |
(These install instructions may contain recent updates which are not included in the instructions packaged in the hot fix download.) |
|
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BD56.
Download: E9BD56 for
z/OS (OS/390) (File Size: 221K) |
ATTENTION (1): To obtain the complete fix for SN-020817 and SN-019386 you must also download and install SAS/CONNECT hot fix E9CT05. The issues described in SN-020817 and SN-019386 will not be fully fixed until both E9BD56 and E9CT05 are applied.
ATTENTION (2): To obtain the complete fix for SN-021112 you must also download and install SAS/ACCESS Interface to DB2 hot fix E9D216. The issue described in SN-021112 will not be fully fixed until both E9BD56 and E9D216 are applied. This is not applicable to z/OS sites.
Customers running on VMS should download E9BD44.
Customers running on Windows should download E9BD59. |
| E9BD61 for z/OS (OS/390) |
| Released: Oct 2011 |
| Issue(s) Addressed: | Introduced: |
| SN-017873 |
ALERT - Extra WHERE clause may get added to query passed to databases |
E9BA31 |
| SN-017888 |
Segmentation Violation error issued when using PROC SQL and SAS/ACCESS® with a LENGTH= option larger than 32 |
E9BA31 |
| SN-018108 |
Segmentation violation when executing multiple queries against a PROC SQL view containing a LIBNAME statement |
E9BA44 |
| SN-018176 |
ALERT - Import of table through Information Map Library Engine deletes physical table |
E9BA48 |
| SN-020479 |
Batch jobs might end with a return code of 4 with no warning in the SAS® log |
E9BA53 |
| SN-018487 |
Compress() function returns incorrect results when used on PROC SQL INSERT statement after applying SAS® 9.1.3 Service Pack 4 |
E9BA53 |
| SN-016074 |
"WARNING: At least one nonessential grouping column reference has been removed from a GROUP BY's reference list" |
E9BA53 |
| SN-019170 |
Errors issued when integer references for column is used in a PROC SQL GROUP BY statement |
E9BA83 |
| SN-019372 |
Performance is poor in the SQL procedure when you use the COUNT(Distinct xxxx) function |
E9BB04 |
| SN-019527 |
Specifying the NOIPASSTHRU option in PROC SQL does not disable implicit passthru |
E9BB04 |
| SN-016547 |
Correlated subqueries using column aliases may not be passed to your dbms when using SAS/ACCESS LIBNAME statement |
E9BB10 |
| SN-019930 |
Using more than 36 tables in a UNION operation within an SQL procedure generates an error message |
E9BB26 |
| SN-020130 |
Aliases columns or aliased tables in the SQL procedure blocks Implicit Pass-Through |
E9BB29 |
| SN-030428 |
Aliased constant values become missing in outer joins and unions |
E9BB29 |
| SN-020162 |
Using functions without parameters in WHERE clauses can block Implicit Pass-Through |
E9BB29 |
| SN-020126 |
SAS/ACCESS® software now provides full support of the INNER JOIN syntax |
E9BB29 |
| SN-020116 |
SAS/ACCESS® software fails to use table aliases correctly when you use in-line SELECT statements |
E9BB29 |
| SN-020123 |
Incorrect SQL text is generated when inner and left joins are used |
E9BB29 |
| SN-020125 |
Using implicit pass-through might cause an incorrect table reference assignment |
E9BB29 |
| SN-020129 |
An incorrect Implicit Pass-Through query is generated when you use a combination of inner and outer Joins |
E9BB29 |
| SN-020122 |
Performance issues occur because SQL code is not passed to the database |
E9BB29 |
| SN-030390 |
Improvements are now available in relational database optimization via the SQL procedure |
E9BB70 |
| SN-019655 |
Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio |
E9BB70 |
| SN-020635 |
Incorrect textualization of SQL Implicit Pass-Through queries occurs when you combine multiple inner joins with one or more outer joins |
E9BB70 |
| SN-032085 |
Incorrect SQL optimization may produce incorrect results |
E9BB76 |
| SN-030942 |
The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHAR |
E9BB76 |
| SN-030923 |
Aliased summary functions in Base SAS® software are not passed to databases |
E9BB76 |
| SN-030893 |
Using an ORDER BY clause in the SQL procedure causes performance problems |
E9BB76 |
| SN-031102 |
A segmentation-violation error might occur after you apply Hot Fix E9BA83 and you access Oracle |
E9BB76 |
| SN-031191 |
Support is now available for the PROC SQL CREATE TABLE statement for the SAS® Scalable Performance Data Server® |
E9BB93 |
| SN-031122 |
SQLPLAN internal errors might occur when you select columns from an SQL view |
E9BB93 |
| SN-031121 |
Implicit Pass-Through errors occur when accessing Oracle tables |
E9BB93 |
| 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 |
E9BB99 |
| SN-031211 |
Errors occur in the SQL procedure's Implicit Pass-Through facility after you apply hot fixes E9BB72, E9BB76, and E9BB80 |
E9BB99 |
| SN-031249 |
SQLPLAN errors occur when you reference a calculated column on an SQL WHERE clause |
E9BB99 |
| SN-031905 |
Enhancements to the Implicit SQL Pass-Through facility enable more of a query to be passed to a database |
E9BC11 |
| SN-031863 |
ALERT - Using the EQT operator in the SQL procedure incorrectly classifies rows with missing values as a match |
E9BC11 |
| SN-031564 |
Performance problems occur when you use the CASE expression with DBMS tables |
E9BC11 |
| 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 |
E9BC11 |
| SN-033763 |
Using the CALCULATED keyword in a WHERE clause in a PROC SQL inner join generates a cartesian product |
E9BC25 |
| SN-033649 |
Calculations that involve DBMS datetime values can return incorrect results |
E9BC25 |
| SN-033073 |
Using the CALCULATED keyword in a WHERE clause generates a Carteisan product |
E9BC25 |
| SN-032636 |
A Read-access violation might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99 |
E9BC25 |
| SN-032537 |
ALERT - Incorrect query results might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99 or you run SAS® 9.2 |
E9BC25 |
| SN-032925 |
An error occurs when you use the IDXNAME= and the WHERE= data set options in an SQL procedure query |
E9BC32 |
| SN-032472 |
Concatenating libraries can result in Read-access violations in the SQL procedure |
E9BC32 |
| SN-032545 |
An SQLPLAN error might occur after you apply hot fixes E9BB98 and E9BB99 |
E9BC32 |
| SN-032406 |
Outer joins that contain a WHERE clause with the STRIP() and PUT() functions cause abnormal endings |
E9BC32 |
| 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 |
E9BC32 |
| SN-034012 |
Column aliases are not passed correctly to GROUP BY or ORDER BY clauses in the SAS® Scalable Performance Data Server® |
E9BC32 |
| SN-032542 |
An error message incorrectly appears when you use the IDXNAME= and the WHERE= option data set options together in an SQL procedure |
E9BC32 |
| SN-011210 |
Incorrect results occur when you use a WHERE= option with indexed tables in the SQL procedure |
E9BC46 |
| 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 |
E9BC46 |
| SN-035011 |
A Read-access violation occurs in the SQL procedure when the WHERE= data set option is placed in an ORDER BY clause |
E9BC46 |
| SN-033094 |
ALERT - Incorrect results might be generated when you use the LIBNAME statement to join multiple Oracle tables |
E9BC46 |
| SN-033648 |
ALERT - The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2 |
E9BC62 |
| SN-034993 |
An error occurs when you run an SQL query with the ORACLE LIBNAME engine |
E9BC62 |
| SN-034975 |
Segmentation violations might occur after you apply Hot Fix E9BC46 in queries that reference DBMS tables |
E9BC62 |
| SN-034391 |
An SQLPLAN error might occur when you use a calculated field to subset a table |
E9BC62 |
| SN-036280 |
ALERT - The SQL procedure generates incorrect results when you copy a SAS® data set from one platform to another platform |
E9BC94 |
| SN-033084 |
An SQLPLAN internal error might occur when reference a variable from an in-line view that created the variable from a constant |
E9BC94 |
| 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 |
E9BC94 |
| SN-036177 |
Incorrect results might occur when you run a PROC SQL join with an additional WHERE clause against Teradata tables |
E9BC94 |
| SN-036202 |
SQLPLAN internal errors might occur when you reference calculated columns in an SQL procedure |
E9BC94 |
| SN-036748 |
The MULTI_DATASRC_OPT= option is ignored when multiple WHERE clause predicates are used in an SQL join operation |
E9BD08 |
| SN-034153 |
Option DBIDIRECTEXEC prevents SAS® Enterprise Guide from opening tables created by PROC SQL |
E9BD13 |
| 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 |
E9BD13 |
| SN-037611 |
Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment |
E9BD13 |
| SN-040951 |
Arithemetic performed on DATA and TIME data types is not passed to the underlying DBMS in SAS/ACCESS® 9.1.3 software |
E9BD20 |
| SN-038458 |
SQLPLAN internal errors might occur when you reference a view in a query that has variables that are defined with the the LENGTH= column modifier |
E9BD20 |
| SN-040492 |
Incorrect textualization of SQL Implicit Pass-Through queries occurs when you combine multiple inner joins with the UNION operator |
E9BD20 |
| SN-038519 |
Specifying both the DBSLICPARM= and the MULTI_DATASRC_OPT= options might generate incorrect results |
E9BD26 |
| SN-039304 |
SQL views of DBMS tables may not return aliased column names |
E9BD26 |
| SN-039129 |
Formatting a newly created, missing numeric variable might result in a "Format not found" error |
E9BD32 |
| SN-039125 |
An SQLPLAN error might occur when you use a new column variable in a correlated subquery |
E9BD32 |
| SN-039271 |
ALERT - Outer join condition may not appear on WHERE clause when performing query against Oracle |
E9BD32 |
| SN-039984 |
An SQL procedure view does not return any rows when it is used in DATA step or a PRINT procedure |
E9BD43 |
| SN-041785 |
Read Access Violation errors occur when creating a long macro variable with the PROC SQL / INTO: macro interface |
E9BD43 |
| SN-042030 |
Oracle PREPARE error issued when SAS table is empty and no keys are in the WHERE clause |
E9BD47 |
| SN-044069 |
Performance might be affected if your query joins multiple tables or views in which variables are being renamed |
E9BD61 |
| Install Instructions: E9BD61os.txt |
(These install instructions may contain recent updates which are not included in the instructions packaged in the hot fix download.) |
|
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BD61.
Download: E9BD61 for
z/OS (OS/390) (File Size: 852K) |
ATTENTION (1): E9BD61 for Windows is also available for the following languages:
German, Spanish, French, Italian, Japanese, Polish, Simplified Chinese
ATTENTION (2): Customers running SAS Base SQL must also download and install SAS Base hot fixes E9BD42 and E9BD48.
Download E9BD42
Download E9BD42 for SAS with Asian Language Support (DBCS) Download E9BD48
Download E9BD48 for SAS with Asian Language Support (DBCS) ATTENTION (3): OpenVMS Alpha customers should install SAS BASE hot fix E9BD32.
Download E9BD32 |
| E9D222 for z/OS (OS/390) |
| Released: Jun 2011 |
| Issue(s) Addressed: | Introduced: |
| SN-017707 |
Order by list with column numbers need spaces after each comma when DB2DECPT is set to a comma |
E9D201 |
| SN-017998 |
Accessing a DB2 table via a LIBNAME may result in a +239 error |
E9D202 |
| SN-019111 |
Calling a DB2 stored procedure may cause an infinite loop under some circumstances or it might retrieve the wrong data |
E9D204 |
| SN-020147 |
Accessing DB2 9 using the SAS/ACCESS® Interface to DB2 might result in an error |
E9D206 |
| SN-020869 |
A DB2 error might occur when you call a DB2 stored procedure running SAS/ACCESS® Interface to DB/2 on z/OS |
E9D207 |
| SN-014174 |
Support status for running DB2 Version 8 in the z/OS operating environment |
E9D209 |
| SN-030937 |
Length of DB2 error message increased |
E9D211 |
| SN-032067 |
An error might occur when you call a DB2 stored procedure that has an argument longer than 256 characters |
E9D212 |
| SN-013450 |
Additional SAS® functions might be passed to DB2 |
E9D213 |
| SN-033648 |
ALERT - The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2 |
E9D215 |
| SN-037611 |
Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment |
E9D217 |
| SN-037033 |
ALERT - Using the DBKEY= option in the SQL procedure might cause incorrect results |
E9D218 |
| SN-038580 |
Calling a stored procedure with a null parameter in SAS/ACCESS® Interface to DB2 might result in a -804 DB2 error |
E9D219 |
| SN-041225 |
Incorrect DB2 table names are created when you use the DB2LOAD or DBLOAD procedures with a DBCS edition of the third maintenance release for SAS® 9.1 |
E9D220 |
| SN-042133 |
ALERT - Using Bulkload to insert into an already existing data set can result in incorrect data |
E9D221 |
| SN-042979 |
Using the DBKEY= option in the SQL procedure might cause incorrect results |
E9D222 |
| Install Instructions: E9D222os.txt |
(These install instructions may contain recent updates which are not included in the instructions packaged in the hot fix download.) |
|
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9D222.
Download: E9D222 for
z/OS (OS/390) (File Size: 274K) |
ATTENTION (1): Customers must also download and install SAS Base hot fixes E9BD61 and E9BD48.
Download E9BD61
Download E9BD61 for SAS with Asian Language Support (DBCS) Download E9BD48
Download E9BD48 for SAS with Asian Language Support (DBCS) |
Service Pack
Return to 9.1.3 DBCS Hot Fix Home