Hot Fix Downloads for z/OS

General Information about Hot Fixes

B25001 was replaced by B25256

B25002 was replaced by B25259

B25003 was replaced by B25249

B25004 was replaced by B25227

B25006 was replaced by B25259

B25007 was replaced by B25260

B25012 was replaced by B25260

B25013 was replaced by B25241

B25015 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40451	Enabling the use of authorized TSO commands for SAS� 9.2 spawners in the z/OS operating environment	B25015
Released: September 10, 2010       Documentation: B25015os.html D         Download: B25015os.bin
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.

Top ^

B25016 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40188	CALL IS8601_CONVERT generates error messages if a null argument is passed to the routine	B25016
Released: August 18, 2010       Documentation: B25016os.html         Download: B25016os.bin

Top ^

B25017 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
38206	Table of contents text is illegible in a PDF file created on z/OS	B25017
Released: August 24, 2010       Documentation: B25017os.html         Download: B25017os.bin

Top ^

B25018 was replaced by B25250

B25020 was replaced by B25242

B25022 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40428	Read Access Violation might occur after closing a SAS/AF� Frame entry containing an SCL List Model attached to a Table Viewer control	B25022
Released: August 18, 2010       Documentation: B25022os.html         Download: B25022os.bin

Top ^

B25023 was replaced by B25260

B25025 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39199	CIMPORT issues "Given transport file is damaged (obs header is damaged)" error if the transport file is created from data sets on tape	B25025
Released: August 19, 2010       Documentation: B25025os.html         Download: B25025os.bin

Top ^

B25026 was replaced by B25260

B25027 was replaced by B25249

B25028 was replaced by B25219

B25029 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40596	SAS� 9.3 BI Clients and SAS� Business Solutions cannot log on to SAS� 9.2 servers	B25029
Released: July 12, 2011       Documentation: B25029os.html         Download: B25029os.bin

Top ^

B25030 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39183	Data corruption occurs when you use the SELECT DISTINCT statement in the SQL procedure to select distinct rows from a SAS table	B25030
Released: September 08, 2010       Documentation: B25030os.html         Download: B25030os.bin

Top ^

B25031 was replaced by B25242

B25032 was replaced by B25259

B25034 was replaced by B25260

B25035 was replaced by B25241

B25036 was replaced by B25260

B25038 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40339	NLDATM informat does not read some month values correctly	B25038
Released: September 09, 2010       Documentation: B25038os.html         Download: B25038os.bin

Top ^

B25039 was replaced by B25242

B25040 was replaced by B25171

B25041 was replaced by B25111

B25043 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40916	The read timeout is limited to 30 seconds when you use the SAS� 9.2 SOAP procedure with the Axis2 engine	B25043
Released: May 18, 2011       Documentation: B25043os.html D         Download: B25043os.bin
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.

Top ^

B25044 was replaced by B25261

B25045 was replaced by B25263

B25047 was replaced by B25249

B25051 was replaced by B25256

B25052 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41012	Graphics output generated with ODS HTML might not display correctly on a UNIX machine that is configured for Japanese DBCS support	B25052
Released: October 28, 2010       Documentation: B25052os.html         Download: B25052os.bin

Top ^

B25054 was replaced by B25242

B25055 was replaced by B25263

B25056 was replaced by B25250

B25057 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41424	"ERROR: Invalid string" or "ERROR: Requested function is not supported" might occur when attempting to create graphics output with ODS Graphics	B25057
Released: November 02, 2010       Documentation: B25057os.html         Download: B25057os.bin

Top ^

B25058 was replaced by B25260

B25059 was replaced by B25181

B25062 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39517	"Read Access Violation" or "Segmentation Violation" errors might be generated when creating ODS RTF output	B25008
12601	ODS PRINTER generates "out of memory" errors	B25062
38109	Justification, font, color, and height specifications do not replay to non-Listing ODS destinations when using PROC DOCUMENT	B25062
40140	URLs generated on the mainframe when using the ODS HTML or the ODS TAGSETS.MVSHTML destination are incorrect in SAS� 9.2	B25062
41024	Row headings might overwrite in PROC TABULATE output with ODS PRINTER (PCL/PDF/PS) destinations	B25062
41445	Memory issues might occur when more than 19 DEFINE statements contain style options in PROC REPORT	B25062
NOTE: If you install this hot fix, you must also install Base SAS hot fix B25260. NOTE: This hot fix is available for OpenVMS on HP Integrity and z/OS. Customers running on all other platforms must install hot fix B25106 instead.
Released: March 07, 2011       Documentation: B25062os.html         Download: B25062os.bin

Top ^

B25063 was replaced by B25259

B25064 was replaced by B25241

B25065 was replaced by B25263

B25066 was replaced by B25219

B25067 was replaced by B25227

B25070 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41922	ALERT - Metadata disappears or becomes corrupted after committing an update to a metadata object	B25070
Released: December 22, 2010       Documentation: B25070os.html         Download: B25070os.bin

Top ^

B25071 was replaced by B25260

B25073 was replaced by B25263

B25075 was replaced by B25256

B25076 was replaced by B25111

B25077 was replaced by B25242

B25080 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41661	"Segmentation Violation In Task [ RANK ]" might be received when ranking a large data set with PROC RANK	B25080
Released: January 13, 2011       Documentation: B25080os.html         Download: B25080os.bin

Top ^

B25082 was replaced by B25152

B25084 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
42092	MINGUO format does not handle 3-digit year properly for widths 7 and 9	B25084
Released: January 18, 2011       Documentation: B25084os.html         Download: B25084os.bin

Top ^

B25085 was replaced by B25111

B25086 was replaced by B25260

B25087 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
42301	The PROC SQL LIKE operator exhausts memory when it is used with a DBCS version of SAS�	B25087
Released: March 03, 2011       Documentation: B25087os.html         Download: B25087os.bin

Top ^

B25088 was replaced by B25249

B25090 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
42187	SAS� software becomes unresponsive when publishing large packages to WebDAV	B25090
Released: March 11, 2011       Documentation: B25090os.html         Download: B25090os.bin

Top ^

B25091 was replaced by B25171

B25095 was replaced by B25111

B25097 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
42555	Incorrect messages are possible in SAS� Analytics modules with UTF-8 encoding enabled	B25097
Released: March 15, 2011       Documentation: B25097os.html         Download: B25097os.bin

Top ^

B25098 was replaced by B25254

B25099 was replaced by B25210

B25100 was replaced by B25242

B25103 was replaced by B25259

B25105 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39621	Floating point exception in SAS program using hash table	B25105
42684	Write Access Violation in tkeaa.dll	B25105
42783	"Termination due to floating point exception..", "invalid operation.." errors occur when parsing textual data	B25105
Released: May 04, 2011       Documentation: B25105os.html         Download: B25105os.bin

Top ^

B25110 was replaced by B25263

B25111 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41738	Sporadic abends of the SAS� Metadata Server occur during start-up	B25076
41921	ERROR: ORACLE connection error: ORA-01017: invalid username/password; logon denied.	B25076
41220	Mixed-case passwords that are submitted to a SAS� server in a z/OS operating environment return a security verification failure to the client	B25111
Released: April 28, 2011       Documentation: B25111os.html         Download: B25111os.bin
IMPORTANT: You must also install hot fix B25263 to fully implement the fix for the issue described in 41220 .

Top ^

B25112 was replaced by B25260

B25113 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
42806	Reading XML files that contain elements with long values might generate "segmentation violation" errors	B25113
42807	Data elements might be replaced rather than concatenated when using the XML LIBNAME engine	B25113
Released: March 31, 2011       Documentation: B25113os.html         Download: B25113os.bin

Top ^

B25114 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
42802	"ERROR: Read Access Violation In Task [ DISPLAY ]" could be received when refreshing the Organization Chart object in a SAS/AF� application	B25114
Released: April 14, 2011       Documentation: B25114os.html         Download: B25114os.bin

Top ^

B25115 was replaced by B25256

B25117 was replaced by B25219

B25118 was replaced by B25242

B25121 was replaced by B25242

B25123 was replaced by B25250

B25125 was replaced by B25263

B25126 was replaced by B25264

B25127 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
43064	TRANWRD function can crash DBCS SAS when translating same variable to itself	B25127
Released: May 09, 2011       Documentation: B25127os.html         Download: B25127os.bin

Top ^

B25130 was replaced by B25242

B25131 was replaced by B25261

B25132 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40494	ALERT - A SAS/SHARE� server fails or does not respond when it is run as a Microsoft Windows service	B25132
Released: July 01, 2011       Documentation: B25132os.html         Download: B25132os.bin

Top ^

B25135 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
43541	ALERT - The SAS� 9.2 Stored Process Server becomes unresponsive in some conditions	B25135
NOTE: SAS Integration Technologies customers who use the SAS Stored Process Server are required to install this fix for the issue described in SN-43541
Released: June 22, 2011       Documentation: B25135os.html         Download: B25135os.bin

Top ^

B25136 was replaced by B25259

B25137 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
43337	B8601DT, B8601DA, B8601TM, and B8601DZ informats produce incorrect results	B25137
Released: June 23, 2011       Documentation: B25137os.html         Download: B25137os.bin

Top ^

B25138 was replaced by B25260

B25140 was replaced by B25242

B25141 was replaced by B25263

B25142 was replaced by B25242

B25146 was replaced by B25263

B25149 was replaced by B25260

B25151 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
43686	The last text character in the SAS/AF� preview buffer might be truncated	B25151
Released: October 18, 2011       Documentation: B25151os.html         Download: B25151os.bin

Top ^

B25152 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41574	Double-byte character sets (DBCS) might not display properly in the ARM log	B25082
43854	ARM4 "Segmentation Violation" error	B25152
Released: August 12, 2011       Documentation: B25152os.html         Download: B25152os.bin

Top ^

B25153 was replaced by B25181

B25154 was replaced by B25210

B25155 was replaced by B25259

B25158 was replaced by B25260

B25159 was replaced by B25250

B25160 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
35111	A note in the SAS log displays the incorrect release of the software	B25160
Released: September 15, 2011       Documentation: B25160os.html         Download: B25160os.bin

Top ^

B25163 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
45705	ALERT - Optimizer might "fail to respond" because of floating point error	B25163
Released: October 11, 2011       Documentation: B25163os.html         Download: B25163os.bin

Top ^

B25166 was replaced by B25260

B25168 was replaced by B25259

B25169 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
44714	Large utility file might unnecessarily be generated by SAS� OLAP Server	B25169
Released: November 04, 2011       Documentation: B25169os.html         Download: B25169os.bin
IMPORTANT: You must also install hot fixes B25259 to fully implement the fixes for the issues addressed in this hot fix.

Top ^

B25170 was replaced by B25260

B25171 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40507	Problems occur when the TKMVSENV environment variable TKOPT_KEEPPOOL is enabled	B25040
42312	ALERT - An S0C4 abend occurs when implementing LOG4SAS for the SAS/CONNECT� Spawner in a z/OS operating environment	B25091
44711	A system abend S0C4 might occur when you stop the SAS� object spawner	B25171
Released: November 28, 2011       Documentation: B25171os.html         Download: B25171os.bin

Top ^

B25173 was replaced by B25263

B25174 was replaced by B25214

B25175 was replaced by B25210

B25176 was replaced by B25261

B25177 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
45291	Performing a drag-and-drop operation within a SAS/AF� Version 6 Organizational Chart object might cause a read-access violation	B25177
Released: February 22, 2012       Documentation: B25177os.html         Download: B25177os.bin

Top ^

B25179 was replaced by B25250

B25180 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
43399	Scalable vector graphics (SVG) files with tooltips might cause 64-bit Microsoft Internet Explorer 9 to crash	B25180
Released: February 03, 2012       Documentation: B25180os.html         Download: B25180os.bin

Top ^

B25181 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41183	Graphic Text Control in SAS/AF� software might not correctly display some characters	B25059
43973	SAS/AF� Version 6 Critical Success Factor object is unreadable in SAS� 9.2	B25153
45484	The SAS/AF� Graphics Text Control issue documented in SAS Note 41183 and fixed with Hot Fix B23059 is no longer resolved after applying Hot Fix B25153	B25181
Released: January 30, 2012       Documentation: B25181os.html         Download: B25181os.bin

Top ^

B25182 was replaced by B25263

B25183 was replaced by B25260

B25184 was replaced by B25242

B25185 was replaced by B25234

B25190 was replaced by B25256

B25191 was replaced by B25263

B25192 was replaced by B25259

B25193 was replaced by B25263

B25194 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
45501	Information maps with incorrectly truncated data item names cannot be opened in SAS� Enterprise Guide� and the SAS� Add-In for Microsoft Office	B25194
Released: April 11, 2012       Documentation: B25194os.html         Download: B25194os.bin

Top ^

B25195 was replaced by B25219

B25198 was replaced by B25256

B25203 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
45362	Intermittent errors reported in client session running a DISPLAY LIBRARY _ALL_ statement to a SAS/SHARE� Server	B25203
Released: May 01, 2012       Documentation: B25203os.html         Download: B25203os.bin

Top ^

B25204 was replaced by B25254

B25205 was replaced by B25250

B25207 was replaced by B25259

B25208 was replaced by B25260

B25210 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
42629	Authentication error might appear when opening an information map in SAS� Enterprise Guide� or the SAS� Add-In for Microsoft Office	B25099
44122	Performance degradation can occur when opening information maps in SAS� Enterprise Guide� and the SAS� Add-In for Microsoft Office	B25154
45152	SAS� Information Maps engine might incorrectly acquire a WRITE lock on SAS� libraries in z/OS	B25175
45153	SAS� Enterprise Guide� and the SAS� Add-In for Microsoft Office do not support general prefilters that are prompted	B25175
46590	An internal error might occur when opening an information map in SAS� Enterprise Guide� and the SAS� Add-In for Microsoft Office	B25210
Released: June 04, 2012       Documentation: B25210os.html D         Download: B25210os.bin
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.

Top ^

B25211 was replaced by B25219

B25212 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
46612	Incorrect summed value for a data set variable might appear in PROC REPORT Listing output	B25212
Released: June 26, 2012       Documentation: B25212os.html         Download: B25212os.bin

Top ^

B25214 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
45200	The FDSTART option of the ARG statement might generate an incorrect argument list and thus cause errors	B25174
46573	CALL MODULE routine generates a system abend 0C2 in module UWUMODUL	B25214
NOTE: Customers running on Unix, PC or VMI systems must install hot fix B25174.
Released: June 13, 2012       Documentation: B25214os.html         Download: B25214os.bin

Top ^

B25215 was replaced by B25259

B25217 was replaced by B25240

B25219 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39997	A database error can occur when you submit an SQL query with a LIBNAME statement that uses the MULTI_DATASRC_OPT=IN_CLAUSE option	B25028
41745	Accessing DB2 can result in System abend 0C4 in module SASIODB2	B25066
41748	Using the LIBNAME option MULTI_DATASRC_OPT=IN_CLAUSE can result in an error	B25066
43275	A CLI error occurs when you access DB2 via SAS/ACCESS� 9.2 Interface to ODBC and PROC SQL implicit pass-through processing	B25117
45162	ALERT - Slow performance and incorrect results might occur if you use DBCREATE_TABLE_OPTS to create a primary index for a Teradata table	B25195
45375	Using the DBSASTYPE data set option on a z/OS system might result in an error	B25211
46851	Errors occur when you perform tasks that require a reread of a DB2 table	B25219
47898	The CREATE TABLE command spawns multiple connections when you use SAS/ACCESS� Interface to Teradata with UTILCONN_TRANSIENT=YES in a LIBNAME statement	B25219
NOTE: If you install this hot fix, you must also install Base SAS 9.21_M3 hot fix B25226. Customers running SAS/ACCESS Interface to DB2 9.21_M2 must also install hot fix B94020. Customers running SAS/ACCESS Interface to Teradata 9.21_M2 must also install hot fix C71007. Customers running SAS/ACCESS Interface to Teradata 9.21_M1 on Windows for x64 must also install hot fix D35006. Customers running SAS/ACCESS Interface to Oracle 9.21_M2 must also install hot fix C36005.
Released: November 05, 2012       Documentation: B25219os.html         Download: B25219os.bin

Top ^

B25220 was replaced by B25250

B25224 was replaced by B25263

B25226 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39125	An SQLPLAN error might occur when you use a new column variable in a correlated subquery	B25021
39129	Formatting a newly created, missing numeric variable might result in a "Format not found" error	B25021
39304	SQL views of DBMS tables may not return aliased column names	B25021
39984	An SQL procedure view does not return any rows when it is used in DATA step or a PRINT procedure	B25021
40714	SQL procedure queries might take longer to run in SAS� 9.2 TS2M2 and TS2M3	B25021
41875	SAS/ACCESS� Interface to DB2 might produce incorrect results when left joining two or more DB2 tables	B25053
41619	Using PROC FORMAT in conjunction with PROC SQL to access a database gives different results between SAS� 9.1.3 and SAS� 9.2	B25060
41785	Read Access Violation errors occur when creating a long macro variable with the PROC SQL / INTO: macro interface	B25060
42129	PROC SQL join operations result in "Floating Point Zero Divide" errors when the join columns are character and are extremely large	B25060
48733	PROC SQL joins might result in errors if the join columns are character data type and the column lengths are too large for the current index page size	B25060
34687	ALERT - Incorrect results might occur if you use the PUT() function in a WHERE clause to convert a DB2 timestamp to a character value	B25083
38759	An error can occur when you run a query against a DBMS and the query contains a column that is renamed and that is then used in a GROUP BY clause	B25083
42093	Using the PROC SQL BTRIM() function causes insufficient memory errors	B25083
43970	Errors occur when you use input() or put() in a JOIN operation with a database table in a remote library	B25083
44688	An INPUT() function used in PROC SQL might return incorrect results	B25083
42425	SQLPLAN error might occur when creating a new variable based on another new variable	B25116
43021	The SAS� System might not consider the DBKEY= data set option when you join a SAS data set and a DBMS table	B25116
43262	Queries that reference tables in libraries that are assigned using the META libname engine might perform poorly	B25134
46712	Option for debugging META Libname Engine libraries	B25134
42737	ALERT - Incorrect results occur in implicit pass-through when you use CALCULATED keyword on GROUP BY statement	B25157
43787	Performance is adversely affected by SQL queries that use unique indexes through SAS/SHARE� software	B25157
44069	Performance might be affected if your query joins multiple tables or views in which variables are being renamed	B25157
44190	Unicode server performance is degraded when character literals in a WHERE clause are not passed to a database correctly	B25157
45162	ALERT - Slow performance and incorrect results might occur if you use DBCREATE_TABLE_OPTS to create a primary index for a Teradata table	B25196
45689	The SAS� Stored Process Server might stop functioning properly if you cancel a request that is running PROC SQL code	B25202
46830	ALERT - Specifying a LENGTH= modifier in an SQL procedure might result in a data integrity issue	B25216
46832	ALERT - Incorrect results might occur when processing an SQL procedure query	B25216
47967	"SPDS_ERROR: Column XXXXX could not be found in the table identified with the correlation name YYYYY" when running PROC SQL	B25226
NOTE: Customers running on Solaris (64-bit) or AIX (64-bit) must install hot fix B25255 instead. If you install this hot fix, you must also install Base SAS 9.21_M3 hot fixes B25250, B25260, and B25219. Customers running SAS/ACCESS Interface to Teradata 9.21_M2 must also install hot fix C71007. Customers running SAS/ACCESS Interface to Teradata 9.21_M1 on Windows for x64 must also install hot fix D35006. Customers running SAS/ACCESS Interface to Oracle 9.21_M2 must also install hot fix C36005.
Released: September 26, 2012       Documentation: B25226os.html D         Download: B25226os.bin
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.

Top ^

B25227 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39839	FILENAME FTP, URL and SOCKET access methods may fail to function correctly in some circumstances	B25004
40538	Web addresses that contain a colon can cause the URL filename engine to fail with an error of "Hostname host not found"	B25067
47885	Using the FILENAME URL engine in SAS� 9.2 in z/OS operating environments causes the connection to time out	B25227
Released: September 28, 2012       Documentation: B25227os.html         Download: B25227os.bin

Top ^

B25228 was replaced by B25259

B25229 was replaced by B25263

B25232 was replaced by B25242

B25233 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
48238	The error "Unable to contact the LDAP server" occurs when you use the LDAPS_OPEN CALL routine	B25233
Released: November 09, 2012       Documentation: B25233os.html         Download: B25233os.bin

Top ^

B25234 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
45160	The message: NOTE: Invalid argument to function FINANCE at line nnn column x. might occur when using the FINANCE function to calculate the XIRR	B25185
48473	More robust algorithm implemented for properly determining internal rate of return when multiple solutions exist	B25234
Released: November 26, 2012       Documentation: B25234os.html         Download: B25234os.bin

Top ^

B25235 was replaced by B25259

B25240 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
46844	Client connections to the SAS� Stored Process Server may fail when there is a delay starting the listen port.	B25217
48314	A SAS� Stored Process connection to a load-balanced SAS� OLAP server might randomly fail under heavy load conditions	B25217
49441	The SAS� Workspace Server for local access is not enabled appropriately in some situations in SAS 9.2� and SAS 9.3�	B25240
NOTE: If you install this hot fix and need the fix documented in SAS Note 48314, you must also install hot fix B25242.
Released: May 14, 2013       Documentation: B25240os.html         Download: B25240os.bin

Top ^

B25241 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40136	PROC TABULATE might give incorrect frequency statistics when only the N statistic is requested and memory is constrained	B25013
40733	The SUMMARY, MEANS, TABULATE, and REPORT procedures might display an error message when accessing data using a SAS/ACCESS library engine	B25035
41643	PROC SURVEYMEANS may terminate with the message: "NOTE: The SAS System stopped processing this step because of errors"	B25064
48956	Using the PRELOADFMT option in a summary procedure and the OTHER= keyword in PROC FORMAT might generate error messages	B25241
Released: March 20, 2013       Documentation: B25241os.html         Download: B25241os.bin

Top ^

B25242 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
38906	The SAS� metadata engine LIBNAME statement fails to interpret access password specification for the Remote Engine Library server	B25020
40125	A slow response might occur when you connect to a SAS application server from client applications	B25020
40366	ALERT - The error "Libname _PMTA01_ is not assigned" occurs when you try to update metadata for a work table	B25020
39371	SAS� Stored Process Server might hang during shut down if the SAS Workspace Server is being monitored	B25031
40920	You are denied access to the SAS Workspace Server after you use SAS� Enterprise Guide� to connect to the SAS� Metadata Server	B25039
39768	Existing client connections to SAS Workspace Servers are closed when the SAS Object Spawner is stopped or refreshed.	B25054
41542	ALERT - SAS Object Spawner may crash when shutting down a SAS Pooled Workspace Server.	B25054
41921	ERROR: ORACLE connection error: ORA-01017: invalid username/password; logon denied.	B25077
42178	SAS Workspace server connections may fail when the SAS� Grid Manager load balancing algorithm is used.	B25118
42748	A validation failure occurs for a SAS� Workspace Server in the SAS� 9.2 environment	B25118
43110	SAS� OLAP Server might stop responding when the number of connected clients is high	B25121
43204	The TIMEOUTSECONDS parameter might cause the SAS� OLAP Server to stop responding	B25130
43690	Library allocation messages are incorrectly reported at the WARN level instead of INFO	B25140
43570	If one of the peers in a load balanced cluster of 3 or more peers is refreshed or restarted it causes load balancing to behave incorrectly.	B25142
45627	Improved functionality to detect and stop orphaned SAS� Workspace Server processes	B25184
45661	Load balanced SAS� OLAP Servers may abend and hang on shutdown	B25184
48314	A SAS� Stored Process connection to a load-balanced SAS� OLAP server might randomly fail under heavy load conditions	B25232
49795	The SAS� pooled workspace server recycle activation limit is broken after applying Hot Fix B25086	B25242
NOTE: If you install this hot fix and need the fix documented in SAS Note 41921, you must also install Base SAS hot fix B25111. NOTE: If you install this hot fix and need the fix documented in SAS Note 43204, you must also install hot fix B25171 (z/OS only). NOTE: If you install this hot fix and need the fix documented in SAS Note 40125, you must also install Base SAS hot fix B25250. NOTE: If you install this hot fix and need the fix documented in SAS Note 39768, you must also install hot fix B25260. NOTE: If you install this hot fix and need the fix documented in SAS Note 48314, you must also install hot fix B25240.
Released: May 08, 2013       Documentation: B25242os.html         Download: B25242os.bin

Top ^

B25243 was replaced by B25249

B25244 was replaced by B25261

B25245 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
50025	Transporting an FSVIEW formula corrupts the catalog	B25245
NOTE: Hot fix I22036 must be applied to your SAS 9.3 TS1M2 installation prior to importing the transport catalog.
Released: August 15, 2013       Documentation: B25245os.html         Download: B25245os.bin

Top ^

B25246 was replaced by B25256

B25247 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
50948	SAS/CONNECT� software returns an incorrect observation number when you access a DATA step view from a Remote Library Services LIBNAME statement	B25247
Released: September 06, 2013       Documentation: B25247os.html         Download: B25247os.bin

Top ^

B25248 was replaced by B25260

B25249 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39614	"ERROR: No email addresses specified" when sending email from SAS� using SMTP	B25003
40143	E-mail output from SAS� 9.2 fails when attachments have an LRECL value greater than 1000	B25027
40178	The sender header field is truncated when you use SAS� software for SMTP e-mail	B25027
40978	The subject lines for e-mails sent from SAS� might get truncated in some e-mail clients	B25047
41926	ERROR: "Email: The connection was reset by a peer"	B25088
41550	SMTP email access method randomly fails with "ERROR: Email: The specified address is not available" or "Email server did not respond"	B25243
50070	A SAS� program sends one or more e-mails successfully, but a subsequente e-mail fails	B25249
Released: September 30, 2013       Documentation: B25249os.html         Download: B25249os.bin

Top ^

B25250 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
38906	The SAS� metadata engine LIBNAME statement fails to interpret access password specification for the Remote Engine Library server	B25018
40125	A slow response might occur when you connect to a SAS application server from client applications	B25018
40231	"ERROR: Libname _PMTA01_ is not assigned" occurs when running the METALIB procedure	B25018
40366	ALERT - The error "Libname _PMTA01_ is not assigned" occurs when you try to update metadata for a work table	B25018
39550	A Read access violation occurs when you use the METALIB procedure to import or register database tables into the SAS� Metadata Repository	B25056
38707	An error occurs when you add the DBSASTYPE= option to a database table in SAS� Management Console and you run a query that uses the metadata engine	B25123
43224	An error message appears in your SAS� log if you use the METALIB procedure to register or update a view that is defined in a Sybase database	B25123
43262	Queries that reference tables in libraries that are assigned using the META libname engine might perform poorly	B25123
46712	Option for debugging META Libname Engine libraries	B25123
44153	Libraries referenced in PROC METALIB or a META LIBNAME statement look for DBMS credentials in metadata even when Authentication Type is "NONE"	B25159
44180	"ERROR: Read Access Violation In Task [SQL]" might occur when using the META engine on a LIBNAME statement	B25159
41093	An error occurs and you cannot access an Oracle table when you use a schema name or a user ID that contains a dollar sign ($)	B25205
46153	The META libname engine ignores the Default Login associated with a relational database library	B25205
46405	META libname engine no longer reports column length inconsistencies when it should	B25205
46408	Access to third party database tables via the META libname engine fails when the userid contains special characters	B25205
47017	The META LIBNAME engine permits a user to add rows to a table even when the user has been denied CREATE permission on the table	B25220
43097	The error "No available engine session manager slots" occurs when you access Teradata tables with the META LIBNAME engine	B25250
44120	Assigning DBMS libraries might fail in SAS� Enterprise Guide�	B25250
49607	The maximum number of database connections is exceeded when you access databases that are registered in metadata	B25250
NOTE: If you install this hot fix, you must also install Base SAS 9.21_M3 hot fixes B25242 and B25226.
Released: August 07, 2013       Documentation: B25250os.html         Download: B25250os.bin

Top ^

B25251 was replaced by B25256

B25252 was replaced by B25259

B25253 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
50673	Searching in SAS� Web Report Studio from the SAS Folders root folder might cause the SAS� Metadata Server to become unresponsive	B25253
Released: August 12, 2013       Documentation: B25253os.html         Download: B25253os.bin

Top ^

B25254 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
42496	Computed columns defined to an MDDB do not display without a SAS/AF� license	B25098
46318	"ERROR: Invalid Operation. ERROR: Termination due to Floating Point Exception"	B25204
50730	"WARNING: FMPFMT: outbuf too small" might appear unexpectedly when you run SAS/AF� applications that have been migrated to SAS� 9.2 or later	B25254
Released: August 15, 2013       Documentation: B25254os.html         Download: B25254os.bin

Top ^

B25256 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39833	The SAS� Metadata Server might terminate abnormally	B25001
41201	The SAS� Metadata Server might report that the members of the SAS Metadata Server fixed roles no longer have the associated privileges	B25051
42284	The EXPORT Wizard may fail with: [Fatal Error] :154:345: An invalid XML character	B25075
42768	Long member-level permission conditions for SAS� OLAP cubes might cause the SAS� Metadata Server to fail	B25115
43114	An error might occur when you use SAS� Management Console to change the association of one metadata object to another	B25115
45686	New SAS� Metadata Server logging functionality is available with SAS� 9.2 TS2M3 hot fix	B25190
46160	Check In fails with an "Error checking in metadata.." error in SAS� Data Integration Studio	B25198
49740	ALERT - The SAS� Metadata Server might become unresponsive because of a memory overlay	B25246
50290	An error occurs intermittently when you try to update metadata objects from SAS� client applications	B25251
51079	An existing target table's column informat value might not be overwritten when you import a table with a column informat value that is set to (None)	B25256
Released: September 23, 2013       Documentation: B25256os.html         Download: B25256os.bin

Top ^

B25258 was replaced by B25260

B25259 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39480	Queries that contain the PROPERTIES function might return a formula error on some operating systems	B25002
39955	ALERT - VisualTotals and other calculated members might return unexpected values in OLAP-based reporting	B25006
40077	MDX to-date functions might return incorrect values when used with other calculated members	B25006
40091	AGGREGATE_TOTAL function in the SAS� OLAP Server can restrict access to members with unexpected results	B25032
40549	Optimization code might cause additional queries when accessing aggregation data	B25032
40550	VisualTotals with MDX functions using the .CURRENTMEMBER function can return unexpected results	B25032
40551	Performance issues might occur when using flattened results from MDX queries after appying hot fix B25006	B25032
41005	Use of the NONEMPTYCROSSJOIN function and multiple-selection filters might result in missing rows	B25063
41078	Queries to SAS OLAP cubes that are built using ROLAP or external aggregations might perform slowly	B25063
41175	SECURITY_SUBSET not honored for totals after import of cube metadata	B25063
41234	The NonEmptyCrossjoin function might return incorrect results after applying hot fix B25032	B25063
41637	Large memory usage might occur on Solaris machines when an invalid dimension name is used in the VisualTotals_Behavior property	B25063
41642	Multiple member filters on the hidden dimension or slicer axis might return incorrect results when totals are displayed on both rows and columns	B25063
40911	Do not use reserved words in dimension names when working with external aggregations	B25103
41577	Queries might perform slowly if ties are included when using TOPCOUNT	B25103
41939	Columns for categorical data that contain only missing values might be removed from the output of a flattened OLAP query	B25103
42160	Variables with more than 16777215 unique values cause a floating point exception in PROC OLAP	B25103
42406	SAS� session might stop responding when using the DISABLE CUBES statement	B25136
42827	Drill-through to detail data for an OLAP cube might fail if UTF-8 encoding is used and member values contain non-English characters	B25136
43542	"The server encountered an error accessing a source data table" received when macro references exist in a member caption for a ROLAP cube	B25136
43554	PROC OLAPOPERATE and other administrative calls to the SAS� OLAP Server could cause the OLAP Server to fail	B25136
43556	Options NECJPERCENTTOTAL and NECJWHEREMAX have been added to the SAS� OLAP Server to help disable NONEMPTY CROSSJOIN optimization for dense data	B25136
43557	SQL range optimization is bypassed for data ordered by formatted values for a SAS� OLAP cube	B25136
44260	Continuous DISABLE CUBE operations might cause the SAS� OLAP Server to stop responding	B25155
44267	MDX ORDER function might generate a large number of subqueries	B25155
44277	Final subquery to satisfy a query against a SAS� OLAP cube might be unnecessary and impact performance	B25155
44715	Performance enhancement enables the underlying data source to calculate TOPCOUNT and BOTTOMCOUNT for an OLAP query	B25168
44742	General performance improvements for SAS� OLAP cubes are included with Hot Fix B25168 for the third maintenance release for SAS 9.2 (TS2M3)	B25168
44751	Poor performance when drilling to detail data from a SAS� OLAP cube	B25168
42667	Empty results from a non empty crossjoin query might result in slow performance from the SAS� OLAP Server	B25192
45266	Visual totals might be incorrect when single member on slicer and two hierarchies from the same dimension are on different axes	B25192
45491	"Error: Insufficient memory" might appear when very large sets are crossjoined and the maximum number of members is exceeded	B25192
45608	"Read Access Violation" using DATAPATH or INDEXPATH options creating SPDE library	B25192
45633	Read Access Violation might be generated for PROC OLAP when there are many levels in a dimension with multiple hierarchies	B25192
46447	The ORDER function might return incorrect results when the default measure is used in both the set and the numeric expression parameters	B25207
46550	The SAS� OLAP Server might stop responding after a client attempts to cancel a query that is running on the SAS OLAP Server	B25207
46828	Infinite recursion error might occur when using both calculated members and measures in an OLAP cube	B25215
47925	Using the TOPCOUNT function might produce errors when it is used with a set containing NUNIQUE measures	B25228
47941	OLAP queries that use the NONEMPTYCROSSJOIN function, calculated members, and calculated measures might produce incorrect results	B25228
47974	A data integrity issue might occur if the NWAY is not compacted when you build a SAS� OLAP cube that uses a star schema	B25228
48308	The SAS� OLAP Server might stop responding if a nonstandard method is used to cancel the query	B25228
48614	Intermittent access violation errors might occur when using SAS� Web Report Studio to query an OLAP cube	B25235
50352	The SAS� OLAP Server might stop responding when you use PROC OLAPOPERATE DISABLE CUBE	B25252
50220	A library assignment error might occur when you drill to detail records from a SAS� OLAP cube	B25259
Released: November 26, 2013       Documentation: B25259os.html         Download: B25259os.bin
IMPORTANT: You must also install hot fixes B25169, B25261 and D28016 to fully implement the fixes for the issues addressed in this hot fix.

Top ^

B25260 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39807	Global macro variable values and scope may be set incorrectly when PROC RISK is within a macro	B25007
40220	EFI, PROC IMPORT and IMPORT WIZARD read a quoted 4 digit number incorrectly	B25007
40252	R interface in Proc IML does not work on 64-bit Windows Operating Systems	B25012
40382	CALL SYMPUT may not update existing global macro variable	B25023
40438	Extremely wide data sets created on a 64-bit operating system produce incorrect or missing values on 32-bit operating systems	B25026
40521	SAS appears to hang in an endless loop if you use Cross Environment Data Access (CEDA) and select a large number of variables	B25026
40449	ANYDTDTE doesn't read a period value properly	B25034
40737	Calling user defined functions using %SYSFUNC can result in an error or termination of SAS	B25036
41114	WHERE clauses that reference functions will execute slowly in SCL code	B25058
41119	Multiple WHERE ALSO statements in the DATA Step returns incorrect results or errors	B25058
39768	Existing client connections to SAS Workspace Servers are closed when the SAS Object Spawner is stopped or refreshed.	B25086
41651	A segmentation violation might occur when performing a large number of asynchronous signons	B25086
42252	ALERT - DATA step views are not accessible when you submit and pass them to a SAS grid from SAS� Enterprise Guide�	B25086
31887	Problems with macro variables created in an AUTOEXEC.SAS file when executing SAS� on a workspace server	B25112
42925	You cannot audit SAS� library Open objects in the standard SAS logging facility	B25112
43537	The last character of a double-byte character set variable is truncated when the variable length is 257	B25138
43671	A memory leak may occur in SAS� Integration Technologies server processes.	B25138
43967	Indexes on data sets can become corrupt when run against the same data multiple times	B25149
44190	Unicode server performance is degraded when character literals in a WHERE clause are not passed to a database correctly	B25158
39846	Errors occur in a Foundation SAS� session when you try to connect with a SAS� Integration Technologies Server	B25166
44674	Referencing an autocall macro stored in a catalog causes a message window to appear upon exiting SAS	B25170
45589	An index might be ignored in BY processing after importing the indexed data set from transport format from another operating system	B25183
46164	&SYSSITE incorrectly returns site numbers with leading zeros	B25208
48439	Global macro variables are incorrectly set within a workspace server	B25208
49737	Catalog concatenation might result in locked catalogs	B25248
51701	ALERT - When you run SAS� Foundation, non-allocated memory might be overwritten	B25260
NOTE: If you install this hot fix, you must also install hot fix B25226 for Base SAS 9.21_M3. NOTE: SAS Integration Technologies customers must also install hot fix B25242 to fully implement the fix for the issue described in SN-39768. NOTE: SAS Enterprise Guide customers must also install hot fix B99010 to fully implement the fix for the issue described in SN-42252.
Released: January 16, 2014       Documentation: B25260os.html         Download: B25260os.bin

Top ^

B25261 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
39408	SPDE data sets unexpectedly locked or not available	B25044
43279	Unable to rename SPDE (Scalable Performance Data Engine) data sets	B25131
44902	SPDE (Scalable Performance Date Engine ) LIBNAME statement can generate an HSSTER error or cause SAS to terminate	B25176
49827	SAS� Scalable Performance Data Engine might fail or might not respond during Read processing in which a WHERE clause is used.	B25244
52286	Creating an index on an empty SAS� Scalable Performance Data Engine data set fails in AIX operating environments	B25261
Released: February 27, 2014       Documentation: B25261os.html         Download: B25261os.bin
IMPORTANT: You must also install hot fixes B85005 to fully implement the fixes for the issues addressed in this hot fix.

Top ^

B25263 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41008	Variable spanned records with an LRECL= system option value greater than 32760 are not handled correctly in SAS� 9.2 resulting in an ABEND002-4	B25045
40475	SAS� 9.2 creates an output file with a different logical record length (LRECL) than what is produced by SAS 8.2	B25055
40882	Output from the PRINTTO procedure is produced as unblocked in SAS� 9.2	B25055
41191	The FILEVAR= option in the INFILE or FILE statement does not work properly with the INFILE/FILE user exit	B25065
41261	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	B25065
41866	A system abend A03 occurs with an interactive SAS� session	B25073
41220	Mixed-case passwords that are submitted to a SAS� server in a z/OS operating environment return a security verification failure to the client	B25110
42615	An error might occur due to a space management problem that causes a SAS bound library size to grow without limit	B25125
43137	ALERT - SAS Enterprise Guide error saving stored process code when connected to z/OS	B25125
43370	PIBw.d informat reads valid value as zero on z/OS	B25141
43488	The WORK library is limited in how it can be allocated on a client or server machine in the z/OS operating environment	B25141
43515	SAS� fails when you use a %INCLUDE statement that references an explicit data set stored on a volume whose serial name contains less than 6 characters	B25146
43817	A %INCLUDE statement for an externally allocated data set might fail in the z/OS environment	B25146
45685	System abend 0C4 occurs when the FILENAME option MGTCLAS is used with an unresolved macro variable	B25146
45059	The message "ERROR: SVC99 error rc=4, reason=02D6" occurs in SAS� 9.2 when the UNIT value is not valid	B25173
45363	ALERT - Sorting a SAS� data set using IBM DFSORT as the host sort utility might cause the last byte of the data set to be replaced with x'00'	B25182
45596	In SAS� Enterprise Guide� 4.2 and 4.3, SAS libraries that are z/OS GDGs cannot be seen in the server list under Bound Libraries	B25191
45711	An intermittent abend or loop can occur due to a race condition	B25191
45833	UTILLOC files are not always allocated with optimal block size	B25193
47353	Processing many files using the FILEVAR option in SAS� 9.2 might cause errors	B25229
51045	System Management Facility type 14 and 15 records reflect the current date as the creation date for certain BSAM files processed by SAS� software	B25263
NOTE: Hot fix B25171 MUST be applied prior to applying this hotfix. You must also install hot fix B25264 to fully implement the fixes for the issues addressed in this hot fix.
Released: July 18, 2014       Documentation: B25263os.html         Download: B25263os.bin

Top ^

B25264 for z/OS
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
43137	ALERT - SAS Enterprise Guide error saving stored process code when connected to z/OS	B25126
51045	System Management Facility type 14 and 15 records reflect the current date as the creation date for certain BSAM files processed by SAS� software	B25264
NOTE: You must also install hot fixes B25171 and B25263 to fully implement the fixes for the issues addressed in this hot fix.
Released: July 18, 2014       Documentation: B25264os.html         Download: B25264os.bin

Top ^