| 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. |
|
| 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. |
|
| 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. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| 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. |
|
| 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. |
|
| 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 |
|
| 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 |
|
| IMPORTANT: You must also install hot fixes B25169, B25261 and D28016 to fully implement the fixes for the issues addressed in this hot fix. |
| 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. |
|
| 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. |
|
General Information about Hot Fixes