| H9T001 for z/OS 64-bit |
| Base SAS 9.4_M3 |
| Issue(s) Addressed: | Introduced: |
| 59928 | SAS® Object Spawner crashes due to excessive file descriptors being open |
H9T001 |
| 59950 | The SAS® Object Spawner might fail suddenly when you are using grid-launched SAS® Workspace Servers configured for Kerberos authentication |
H9T001 |
| 60459 | Due to a buffer overflow, the SAS® IOM Object Spawner might become unresponsive |
H9T001 |
| 60758 | Workspace servers launched by SAS® Grid Manager fail in Kerberos environments |
H9T001 |
| 61253 | The grid process launcher might overwrite the caller KRB5CCNAME environment variable |
H9T001 |
| 66130 | Grid-launched workspace server sessions fail intermittently with the error message "Unknown error in grid provider module" |
H9T001 |
| 56822 | Programs submitted to SAS® Grid Manager for Hadoop fail and return the error "GSS failure in function gss_init_sec_context..." |
H9T001 |
| 56953 | The HTTP procedure might cause SAS® to exit abnormally with a stack trace when you upgrade from SAS® 9.4 TS1M2 to SAS® 9.4 TS1M3 |
H9T001 |
| 57217 | When a LIBNAME statement is issued to PI Web API from SAS/ACCESS® Interface to the PI System, a segmentation violation occurs |
H9T001 |
| 57661 | SAS® Grid Manager for Hadoop abnormally terminates when a SAS® program is submitted |
H9T001 |
| 58161 | SAS® Metadata Server crashes unexpectedly when using Quest Authentication Services to enable Integrated Windows Authentication |
H9T001 |
| NOTE: If you install this hot fix and need the fix documented in SAS Note 59950, you must also install hot fix V72017. |
|
| V01093 for z/OS 64-bit |
| Base SAS 9.4_M3 |
| Issue(s) Addressed: | Introduced: |
| 57701 | A Read-access or segmentation violation occurs when you update metadata with the "Update Metadata" option or with the METALIB procedure |
V01049 |
| 58625 | Error and warning messages are generated when you use the METALIB procedure to register or update metadata for a Hadoop table |
V01049 |
| 58630 | A security vulnerability exists in PROC METALIB |
V01049 |
| 59529 | Remote Library Services library allocation fails with "ERROR: Invalid libref..." |
V01069 |
| 59785 | Updating an Oracle table via the META engine results in a U1335 error |
V01069 |
| 60564 | Running the METALIB procedure results in a segmentation violation and duplicate index objects |
V01093 |
| 60910 | An access violation occurs when you update metadata for a table that contains more than 50 indexes |
V01093 |
| NOTE: If you install this hot fix, you must also install hot fix V01099 for Base SAS 9.4_M3. |
|
| V01099 for z/OS 64-bit |
| Base SAS 9.4_M3 |
| Issue(s) Addressed: | Introduced: |
| 52698 | A user 1319 abend occurs in a SAS/SHARE® server |
V01011 |
| 57105 | The PLM procedure might end abnormally when the item store includes model variables with associated formats |
V01020 |
| 57254 | The &SYSCC automatic macro variable returns an incorrect value when the SASAUTOS= system option contains an unmatched quotation mark |
V01028 |
| 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 |
V01028 |
| 57088 | The error "applied buffer too small for requested data" might be generated when you use the ODS destination for Excel |
V01035 |
| 57904 | A Decision Tree node gives "Run time error was encountered ... see the log in the node Results window for more details ..." with Audit log Trace |
V01036 |
| 57797 | An ABORT CANCEL statement can cause your SAS® session to stop responding if your program contains DM statements |
V01041 |
| 58357 | A %GLOBAL statement with the READONLY option can generate a traceback error |
V01046 |
| 58459 | You encounter a segmentation violation when you run a SAS/SHARE® server in a multiple user environment |
V01046 |
| 59785 | Updating an Oracle table via the META engine results in a U1335 error |
V01066 |
| 59529 | Remote Library Services library allocation fails with "ERROR: Invalid libref..." |
V01074 |
| 60086 | "ERROR: An exception has been encountered" occurs when registering a table in a concatenated library that contains a SAS® metadata-bound library |
V01074 |
| 61157 | When you try to access tables in a metadata-bound library using SAS/SHARE®, the tables incorrectly require an ENCRYPTKEY to open |
V01087 |
| 61881 | The system becomes unresponsive when you attempt to disable SASCMD sign-on by removing the sasxdmr.dll file |
V01094 |
| 61906 | You encounter poor performance with the DATA step in SAS® 9.4 TS1M3 under z/OS |
V01099 |
| 62724 | ALERT - A WHERE clause that contains an OR condition returns incorrect results when the first two arguments of the OR condition are the same |
V01099 |
| NOTE: If you install this hot fix, you must also install hot fix V01093 for Base SAS 9.4_M3. |
|
| V01107 for z/OS 64-bit |
| Base SAS 9.4_M3 |
| Issue(s) Addressed: | Introduced: |
| 58624 | The PDS BLKSIZE value is corrupted and you cannot add a new member to the PDS |
V01051 |
| 58841 | In SAS® 9.4 TS1M0 and later releases, sort jobs fail with a VM1335, 0C4, or 0C2 Error |
V01053 |
| 58492 | Reading tape data sets fails with "ERROR: LIBRARY WEEK31 IS NOT IN A VALID FORMAT FOR ACCESS METHOD SASV7SEQ" |
V01055 |
| 59070 | Using zHPF with SAS® 9.4 TS1M3 results in a system abend S0C1 |
V01058 |
| 59290 | Attempting to open a library causes an 0C4 Abend in SAS® 9.4 TS1M3 |
V01061 |
| 58360 | Jobs loop and fail to complete in the DATA step in SAS® 9.4 under z/OS |
V01065 |
| 56599 | When you work in a low-memory environment, you might encounter sporadic U1335 abends |
V01075 |
| 60174 | When the QSASnnnn allocation is reached, "ERROR: File in use, QSASnnnn" occurs |
V01076 |
| 59428 | Pass ticket support fails for connections to z/OS |
V01078 |
| 60729 | In the z/OS operating environment, you encounter "ERROR: System abend 0C4 occurred in module SASVX function VXTEMP..." |
V01083 |
| 61713 | SAS® does not finish reading data sets that contain the RECFM=N DCB attribute |
V01091 |
| 63721 | You encounter a segmentation violation in the SAS DATASTEP task when you use SAS® Fraud Management on the z64 platform |
V01104 |
| 64237 | "ERROR:The requested LPAR name...does not match the actual LPAR name" occurs when you run sub-capacity setinits and apply IBM security patches (APARs) |
V01107 |
|
| V21022 for z/OS 64-bit |
| Base SAS 9.4_M3 |
| Issue(s) Addressed: | Introduced: |
| 57593 | Leaving a metadata-bound table open when you exit a client like SAS® Studio might cause the client to hang when restarting |
V21007 |
| 56186 | The object spawner might fail when you use load balancing with SAS® Cost and Profitability Management 8.1 |
V21007 |
| 57428 | In a SAS® Metadata Server cluster, the master node does not send redirection requests to a slave node that is a part of the quorum |
V21007 |
| 58101 | SAS® Metadata Server abnormally terminates with an "unhandled Exception" and the traceback indicates a failure in the KeepAliveThread |
V21009 |
| 58262 | SAS® Stored Process Server load-balancing problems occur if you select the "Recycle Activation Limit" option |
V21011 |
| 58452 | All servers stop responding in a load-balanced cluster |
V21013 |
| 59097 | SAS® Object Spawner memory use increases over time |
V21017 |
| 60150 | When you launch grid-launched workspace servers on SAS® Enterprise Guide®, 'A connection to the server "SASApp" could not be established' occurs |
V21019 |
| 61702 | ALERT - Load-balanced object spawners or metadata server cluster nodes do not successfully reconnect after quorum loss |
V21022 |
| NOTE: If you install this hot fix, you must also install hot fix V72017 for SAS Threaded Kernel Grid 9.4_M3. |
|
| V21025 for z/OS 64-bit |
| Base SAS 9.4_M3 |
| Issue(s) Addressed: | Introduced: |
| 59039 | The SAS® import procedure causes an out of memory condition, corruption of metadata, or a loss of quorum for a clustered SAS® Metadata Server |
V21015 |
| 56751 | SAS® 9.4 Metadata Server cluster might become unresponsive after a user bulkload program is completed |
V21015 |
| 57224 | Adding a new login containing a user ID that is already associated with an existing identity damages the Foundation repository |
V21015 |
| 57367 | A SAS® 9.4 metadata user bulk load can take many hours to complete when the SAS® Metadata Server is clustered |
V21015 |
| 59405 | Excessive delays occur the first time a new user logs on and is authenticated by the SAS® Metadata Server |
V21018 |
| 59404 | A vulnerability on authorizations to metadata table objects exists in SAS® Metadata Server |
V21018 |
| 60595 | Connections between work tables and database libraries are incorrectly removed when these objects are included in metadata import processing |
V21021 |
| 61801 | SAS® Metadata Server contains a denial of service vulnerability |
V21023 |
| 62183 | A SAS® Metadata Server cluster might encounter "INTERNAL ERROR: Attempting to release a non-wrapped journal entry . . ." |
V21023 |
| 62850 | FeatureMap associations (FeatureSources or FeatureTargets type) are randomly deleted during check-in of objects from SAS® Data Integration Studio |
V21025 |
|
| V21026 for z/OS 64-bit |
| Base SAS 9.4_M3 |
| Issue(s) Addressed: | Introduced: |
| 57099 | WebHDFS REST API does not work correctly on SAS/ACCESS® Interface to Hadoop when high availability is configured in the Hadoop cluster |
V21005 |
| 57551 | A time-out occurs when the HTTP procedure does not transfer data segments |
V21006 |
| 59167 | A 403 error occurs when you load segments into SAS® Customer Intelligence 360 from SAS® Customer Intelligence |
V21016 |
| 60132 | A failure occurs when you use two-way SSL or client authentication using TLS/SSL on SAS® 9.4 in Microsoft Windows operating environments |
V21020 |
| 62214 | The HADOOP procedure contains a memory leak that can affect performance in SAS/ACCESS® Interface to Hadoop |
V21024 |
| 63656 | You see an exception error in the object spawner log when you use the HADOOP procedure with Kerberos in an Apache Hadoop grid |
V21026 |
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Hadoop 9.43 installed, you must also install hot fix W11011.
If you install this hot fix and have SAS Threaded Kernel Core Routines 9.4_M3 installed, you must also install hot fix V63005. |
|
| V53007 for z/OS 64-bit |
| SAS/Secure SSL 9.4_M3 hot fix for Base SAS 9.4_M3 |
| Issue(s) Addressed: | Introduced: |
| 56385 | ALERT - OpenSSL security vulnerabilities (11 Jun 2015 and 9 Jul 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products |
V53001 |
| 57686 | OpenSSL security vulnerabilities (4 Dec 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products |
V53002 |
| 58391 | OpenSSL version 1.0.2h is available for SAS® 9.3 and 9.4 on UNIX and z/OS |
V53003 |
| 58609 | The error "SSL negotiation could not complete because the socket was closed by the partner" occurs in SAS® 360 Discover |
V53004 |
| 59244 | OpenSSL vulnerabilities exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products (OpenSSL advisories through 26 September 2016) |
V53005 |
| 61700 | OpenSSL vulnerabilities exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products (OpenSSL advisories through 02 November 2017) |
V53006 |
| 58785 | ALERT - The HTTP procedure generates an exception error |
V53007 |
| 66213 | Certificates that shipped in SAS® 9.4 contain an expired certificate from Sectigo AddTrust (expired on May 30, 2020) |
V53007 |
| Released: August 31, 2020 | | 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