| M88050 for z/OS |
| Base SAS 9.4_M1 |
| Issue(s) Addressed: | Introduced: |
| 54168 | Using the DBCREATE_TABLE_OPTS= data set option to create a temporary Teradata table might fail and return an execute error |
M88032 |
| 52327 | SQL procedure code that used to work properly now leads to issues such as missing table columns, incorrect results, or an incorrect query being passed |
M88042 |
| 54658 | When you submit a query with a WHERE clause, you might get unexpected results |
M88042 |
| 56256 | Querying a relational DBMS table using the IN clause operator might return unexpected results |
M88050 |
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Teradata 9.4M1 installed, you must also install hot fix R32001 for SAS/ACCESS Interface to Teradata 9.4M1.
|
|
| M88066 for z/OS |
| Base SAS 9.4_M1 |
| Issue(s) Addressed: | Introduced: |
| 52643 | A VM 1335 error occurs due to out-of-memory condition |
M88015 |
| 53666 | Using SAS/GRAPH® software with the ODS HTML statement in the z/OS operating environment might result in an S0C4 abend |
M88026 |
| 52920 | The SAS/SHARE® server fails to close a member that a client is attempting to access |
M88028 |
| 54179 | The SAS® system option SVC11SCREEN does not work in SAS® 9.4 |
M88038 |
| 54353 | A SAS® tasking logic error might cause unresponsive SAS® tasks or orphaned SAS® spawned sessions in the z/OS operating environment |
M88041 |
| 55723 | A Catalog Search Interface (CSI) failure occurs when you are accessing MVS Bound Libraries and User Defined folders from SAS® Enterprise Guide® |
M88048 |
| 56599 | When you work in a low-memory environment, you might encounter sporadic U1335 abends |
M88053 |
| 58624 | The PDS BLKSIZE value is corrupted and you cannot add a new member to the PDS |
M88061 |
| 58841 | In SAS® 9.4 TS1M0 and later releases, sort jobs fail with a VM1335, 0C4, or 0C2 Error |
M88062 |
| 58854 | You receive "ERROR: OPEN is aborted for file PDS..." under z/OS |
M88063 |
| 59428 | Pass ticket support fails for connections to z/OS |
M88066 |
|
| N22015 for z/OS |
| Base SAS 9.4_M1 |
| Issue(s) Addressed: | Introduced: |
| 52540 | Required SAS® 9.4_M1 hot fix for SAS® Visual Analytics 6.4 |
N22001 |
| 52887 | SAS® Enterprise Guide® and the SAS® Add-In for Microsoft Office might not display output SAS® data sets that are created by a stored process |
N22002 |
| 53195 | Macros are not executing from memory on z/OS operating systems |
N22003 |
| 53211 | A traceback error might be generated if an error occurs within a macro |
N22004 |
| 53676 | Executing large macros from disk in the z/OS operating environment causes performance loss |
N22004 |
| 53841 | An extraneous underscore might be added to an ODS RTF TEXT= value |
N22005 |
| 54059 | The SAS/IntrNet® Application Dispatcher stops responding when a SAS® program creates a PDF document |
N22006 |
| 54549 | A SAS® program that uses PROC PRINTTO with a FILENAME that uses the EMAIL engine fails with a system 0C4 in SAS® 9.4 |
N22007 |
| 54723 | Large user-defined formats might cause an insufficient memory message and a message about insufficient contiguous storage |
N22008 |
| 54989 | An error occurs when you use PROC COPY to copy a metadata-bound data set with a recorded encryption key to a non-bound library |
N22008 |
| 39915 | ODS PDF TEXT= produces a header "Continuing contents of page NN" |
N22008 |
| 54106 | ODS PDF bookmarks link to an incorrect table |
N22008 |
| 57138 | Data tips might be displayed as raw HTML in your web browser when you create ODS Graphics output in a z/OS operating environment |
N22011 |
| 57254 | The &SYSCC automatic macro variable returns an incorrect value when the SASAUTOS= system option contains an unmatched quotation mark |
N22011 |
| 57348 | SAS® Drug Development 4.3.2 - Incorrect completion status might occur when mismatched or single quotation marks are in SAS® code including for Jobs |
N22011 |
|
| N22016 for z/OS |
| Base SAS 9.4_M1 |
| Issue(s) Addressed: | Introduced: |
| 55199 | An upgrade of SAS® 9.4 software might fail or an out-of-memory condition might occur and result in the corruption of metadata |
N22001 |
| 52796 | A grid-launched workspace server fails to start when you use Microsoft Integrated Windows Authentication |
N22009 |
| 53765 | The load balancer might fail when it tries to reuse a grid-launched, pooled workspace server |
N22009 |
| 53944 | A SAS® Workspace Server connection failure can occur in SAS® Studio when you use SAS® token authentication |
N22009 |
| 53770 | An orphaned gridrun.exe process occurs when users close a SAS® Enterprise Guide® session that is running in a SAS® grid environment |
N22009 |
| 54819 | High job submission rates might result in grid-launched workspace servers failing to start |
N22009 |
| 55021 | Clustered SAS® Metadata Servers lose their quorum status |
N22009 |
| 55014 | The SAS® import procedure fails and returns errors to the SAS® Metadata Server log file |
N22009 |
| 55945 | A SAS Metadata Server backup with the "Reorganize repositories" option enabled might damage the Foundation repository |
N22010 |
| 55985 | The error "Too many files are open" is logged when you have clustered SAS® Metadata Servers |
N22010 |
| 56751 | SAS® 9.4 Metadata Server cluster might become unresponsive after a user bulkload program is completed |
N22012 |
| 57367 | A SAS® 9.4 metadata user bulk load can take many hours to complete when the SAS® Metadata Server is clustered |
N22012 |
| 59329 | SAS® Metadata Server becomes unresponsive or crashes with an AccessViolation error |
N22014 |
| 59404 | A security vulnerability exists in SAS® Metadata Server |
N22016 |
NOTE: You must also install hot fix R37001 for SAS Studio 3.1_M1 to fully implement the fix for the issue described in 53944.
You must also install hot fix N27004 for SAS Threaded Kernel Grid 9.4_M1 to fully implement the fix for the issue described in 54819. |
|
| S32007 for z/OS |
| SAS/Secure SSL 9.4_M1 hot fix for Base SAS 9.4_M1 |
| Issue(s) Addressed: | Introduced: |
| 53245 | ALERT - OpenSSL security vulnerabilities (05 Jun 2014) exist in SAS/SECURE™ software |
S32001 |
| 54073 | ALERT - OpenSSL security vulnerabilities (6 Aug 2014) exist in SAS/SECURE™ software |
S32001 |
| 54374 | ALERT - Secure Sockets Layer (SSL) capability in SAS® Foundation products is susceptible to the POODLE security vulnerability |
S32001 |
| 53953 | Errors might occur when you connect to a server with SAS® clients and programs that use the Secure Sockets Layer (SSL) protocol |
S32001 |
| 55767 | ALERT - OpenSSL security vulnerabilities (19 Mar 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products |
S32002 |
| 56161 | Error messages appear in the SAS® log and the step terminates when you use the AUTHTLS option in the FILENAME FTP statement |
S32002 |
| 56385 | ALERT - OpenSSL security vulnerabilities (11 Jun 2015 and 9 Jul 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products |
S32003 |
| 57686 | OpenSSL security vulnerabilities (4 Dec 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products |
S32004 |
| 58391 | OpenSSL version 1.0.2h is available for SAS® 9.3 and 9.4 on UNIX and z/OS |
S32005 |
| 58785 | ALERT - The HTTP procedure generates an exception error |
S32005 |
| 59244 | OpenSSL vulnerabilities exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products (OpenSSL advisories through 26 September 2016) |
S32006 |
| 61700 | OpenSSL vulnerabilities exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products (OpenSSL advisories through 02 November 2017) |
S32007 |
| Released: February 16, 2018 | | D | | |
|
| IMPORTANT: Please contact SAS Technical Support for information on accessing this hot fix and reference SAS Note 61700 |
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes