Hot Fix Downloads for OpenVMS on HP Integrity

General Information about Hot Fixes

B25003 was replaced by B25249

B25004 was replaced by B25227

B25007 was replaced by B25260

B25012 was replaced by B25260

B25014 for OpenVMS on HP Integrity
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40209	SAS session using SPDE library hangs and does not finish	B25014
Released: July 26, 2010       Documentation: B25014vi.html         Download: B25014vi.exe

Top ^

B25016 for OpenVMS on HP Integrity
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: July 20, 2010       Documentation: B25016vi.html         Download: B25016vi.exe

Top ^

B25018 was replaced by B25250

B25019 was replaced by B25079

B25023 was replaced by B25260

B25026 was replaced by B25260

B25027 was replaced by B25249

B25028 was replaced by B25219

B25030 for OpenVMS on HP Integrity
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: B25030vi.html         Download: B25030vi.exe

Top ^

B25034 was replaced by B25260

B25036 was replaced by B25260

B25038 for OpenVMS on HP Integrity
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: B25038vi.html         Download: B25038vi.exe

Top ^

B25041 was replaced by B25111

B25043 for OpenVMS on HP Integrity
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: September 21, 2010       Documentation: B25043vi.html         Download: B25043vi.exe

Top ^

B25046 was replaced by B25218

B25047 was replaced by B25249

B25048 was replaced by B25068

B25049 was replaced by B25218

B25052 for OpenVMS on HP Integrity
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: B25052vi.html         Download: B25052vi.exe

Top ^

B25056 was replaced by B25250

B25057 for OpenVMS on HP Integrity
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: B25057vi.html         Download: B25057vi.exe

Top ^

B25058 was replaced by B25260

B25059 was replaced by B25181

B25061 was replaced by B25218

B25062 for OpenVMS on HP Integrity
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: B25062vi.html         Download: B25062vi.exe

Top ^

B25066 was replaced by B25219

B25067 was replaced by B25227

B25068 for OpenVMS on HP Integrity
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41067	Using the XML92 engine might generate an error or shut down the SAS� System when the data contains specific characters	B25048
41765	XML output might be encoded unnecessarily when using either the XML or XML92 LIBNAME engine	B25068
41772	A "Write Access Violation" error might be issued when using the XML92 LIBNAME engine with the SQL procedure	B25068
Released: January 25, 2011       Documentation: B25068vi.html         Download: B25068vi.exe

Top ^

B25069 for OpenVMS on HP Integrity
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41667	ALERT - SAS/AF� Graph Output Control might not correctly display graph data	B25069
Released: December 09, 2010       Documentation: B25069vi.html         Download: B25069vi.exe

Top ^

B25070 for OpenVMS on HP Integrity
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: B25070vi.html         Download: B25070vi.exe

Top ^

B25071 was replaced by B25260

B25076 was replaced by B25111

B25078 was replaced by B25218

B25079 for OpenVMS on HP Integrity
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
40433	EFI, Proc Import, Import Wizard reads a value with a single quote incorrectly	B25019
41767	Import:List Window blank when importing an external file using EFI and User-Defined Formats	B25079
Released: February 24, 2011       Documentation: B25079vi.html         Download: B25079vi.exe

Top ^

B25080 for OpenVMS on HP Integrity
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: B25080vi.html         Download: B25080vi.exe

Top ^

B25082 was replaced by B25152

B25084 for OpenVMS on HP Integrity
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: B25084vi.html         Download: B25084vi.exe

Top ^

B25085 was replaced by B25111

B25086 was replaced by B25260

B25088 was replaced by B25249

B25090 for OpenVMS on HP Integrity
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: B25090vi.html         Download: B25090vi.exe

Top ^

B25092 was replaced by B25218

B25095 was replaced by B25111

B25104 was replaced by B25218

B25105 for OpenVMS on HP Integrity
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: B25105vi.html         Download: B25105vi.exe

Top ^

B25109 was replaced by B25218

B25111 for OpenVMS on HP Integrity
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
Released: April 28, 2011       Documentation: B25111vi.html         Download: B25111vi.exe

Top ^

B25112 was replaced by B25260

B25113 for OpenVMS on HP Integrity
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 30, 2011       Documentation: B25113vi.html         Download: B25113vi.exe

Top ^

B25114 for OpenVMS on HP Integrity
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: B25114vi.html         Download: B25114vi.exe

Top ^

B25117 was replaced by B25219

B25123 was replaced by B25250

B25124 was replaced by B25218

B25129 was replaced by B25218

B25132 for OpenVMS on HP Integrity
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: B25132vi.html         Download: B25132vi.exe

Top ^

B25133 was replaced by B25218

B25135 for OpenVMS on HP Integrity
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: B25135vi.html         Download: B25135vi.exe

Top ^

B25137 for OpenVMS on HP Integrity
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: B25137vi.html         Download: B25137vi.exe

Top ^

B25138 was replaced by B25260

B25145 was replaced by B25218

B25148 was replaced by B25218

B25149 was replaced by B25260

B25151 for OpenVMS on HP Integrity
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: B25151vi.html         Download: B25151vi.exe

Top ^

B25152 for OpenVMS on HP Integrity
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: B25152vi.html         Download: B25152vi.exe
IMPORTANT: If you install this hot fix, you must install Base SAS hot fix B25218.

Top ^

B25153 was replaced by B25181

B25158 was replaced by B25260

B25159 was replaced by B25250

B25161 was replaced by B25218

B25163 for OpenVMS on HP Integrity
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: B25163vi.html         Download: B25163vi.exe

Top ^

B25165 was replaced by B25218

B25166 was replaced by B25260

B25167 was replaced by B25218

B25170 was replaced by B25260

B25174 for OpenVMS on HP Integrity
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
NOTE: Customers running on z/OS must install hot fix B25214.
Released: February 02, 2012       Documentation: B25174vi.html         Download: B25174vi.exe

Top ^

B25177 for OpenVMS on HP Integrity
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: B25177vi.html         Download: B25177vi.exe

Top ^

B25178 was replaced by B25218

B25179 was replaced by B25250

B25180 for OpenVMS on HP Integrity
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: B25180vi.html         Download: B25180vi.exe

Top ^

B25181 for OpenVMS on HP Integrity
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: B25181vi.html         Download: B25181vi.exe

Top ^

B25183 was replaced by B25260

B25188 was replaced by B25218

B25195 was replaced by B25219

B25199 was replaced by B25218

B25201 was replaced by B25218

B25205 was replaced by B25250

B25206 was replaced by B25218

B25208 was replaced by B25260

B25211 was replaced by B25219

B25212 for OpenVMS on HP Integrity
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: B25212vi.html         Download: B25212vi.exe

Top ^

B25218 for OpenVMS on HP Integrity
Base SAS 9.21_M3
Issue(s) Addressed:		Introduced:
41013	Errors might occur when you use the SASTRACE= system option with the SAS/ACCESS� engines	B25046
41115	Loading a large SAS data file into memory can cause macro slowdown	B25078
41574	Double-byte character sets (DBCS) might not display properly in the ARM log	B25078
42240	The LIBNAME statement's FILELOCKWAIT= option might not check for a lock in all cases	B25078
42392	Truncated value for automatic macro variable &SYSPROCESSNAME	B25104
42394	Number of open files decreases when opening/closing a data set over multiple iterations	B25104
42857	Poor performance when reading non-local files with SAS� 9.2 on OpenVMS on HP Integrity	B25109
42894	SHR= option on a FILENAME statement is not honored	B25129
42969	"Invalid data" note received when reading files with variable-length records using DECNET	B25129
42974	Erroneous data set created when reading a file with fixed-length records when there is an odd number of bytes per record	B25129
42998	Performance degradation occurs when dividing with missing values	B25129
43857	When creating external files containing fixed-length records, record attributes are created as NONE	B25148
43858	SAS� 9.2 creates an incorrectly formatted fixed-length record file when the record length is an odd number	B25148
43920	Specifying the Albany AMT font when creating SAS/GRAPH� output can cause SAS� to fail	B25148
44472	Overwriting a SAS� data set in a UNIX operating environment removes any existing ACL	B25165
44584	SAS� Enterprise Guide� does not import UTF-16 files correctly using a UTF-8 SAS� server	B25167
46251	Directories cannot be created under the Files folder in SAS� Enterprise Guide�	B25206
44257	A segmentation violation might occur and your server might not function when you run a SAS� Stored Process that accesses a database	B25218
Released: August 17, 2012       Documentation: B25218vi.html         Download: B25218vi.exe

Top ^

B25219 for OpenVMS on HP Integrity
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: B25219vi.html         Download: B25219vi.exe

Top ^

B25220 was replaced by B25250

B25226 for OpenVMS on HP Integrity
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: B25226vi.html D         Download: B25226vi.exe
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 OpenVMS on HP Integrity
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
Released: September 28, 2012       Documentation: B25227vi.html         Download: B25227vi.exe

Top ^

B25233 for OpenVMS on HP Integrity
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: B25233vi.html         Download: B25233vi.exe

Top ^

B25243 was replaced by B25249

B25248 was replaced by B25260

B25249 for OpenVMS on HP Integrity
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: June 17, 2013       Documentation: B25249vi.html         Download: B25249vi.exe

Top ^

B25250 for OpenVMS on HP Integrity
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: B25250vi.html         Download: B25250vi.exe

Top ^

B25258 was replaced by B25260

B25260 for OpenVMS on HP Integrity
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: B25260vi.html         Download: B25260vi.exe

Top ^