INSTALLATION INSTRUCTIONS FOR HOT FIX 82BC14 ON OS/2 BEFORE DOWNLOADING: The hot fix 82BC14 addresses the issue(s) in Release 8.2 (TS2M0) of Base SAS software on OS/2 as documented in SAS Note(s): SN-004241 PROC SQL may return incorrect number of observations when using unique index SN-003976 Inconsistent results returned from the PROC SQL pass-through facility versus the LIBNAME Access engine SN-005899 PROC SQL set operators UNION and OUTER UNION CORRESPONDING return the wrong number of rows when used with subqueries SN-005712 ERROR: where clause processing could not obtain memory SN-006247 Reflexive join operations which execute successfully using the SQL procedure in previous releases of SAS fail in Release 8.2 SN-006274 Error: sqlplan internal error: cannot find symbol RIFNOTE, var=1 tag=3 occurs using SQL view SN-006741 PROC SQL syntax errors occur when using SET operators UNION and/or OUTER UNION CORR within subqueries SN-004536 PROC SQL UPDATE statement may use excessive CPU time SN-006773 Calls to the CONSTANT function can cause READ ACCESS violations in PROC SQL SN-004451 Query submitted to DBMS may generate incorrect results SN-006403 "ERROR: Invalid position -2147483308 for utility file" may be issued when using PROC SQL against SAS/ACCESS SQL views SN-006582 Opening a PROC SQL view twice using %SYSFUNC(OPEN()) causes SAS to terminate and the Display Manager windows to disappear SN-006768 Incorrect results from PROC SQL when a query contains the UNION operator and subqueries SN-006624 SQLPLAN Internal Error occurs when grouping by variable created by subquery SN-006772 Incorrect results from PROC SQL when UNION operator used in a subquery SN-005608 SQL views cannot be used with procedures that do multipass processing SN-005808 PROC SQL ORDER BY uses additional disk space to cache intermediate utility file SN-006829 SAS 8.2 PROC SQL appears to loop when using multiple reflexive join references SN-007824 Incorrect implicit pass-through SQL can be generated from PROC SQL queries leading to incorrect results SN-007820 Dataset options IDXWHERE and IDXNAME available for use with PROC SQL SN-007319 Downloading a SAS Version 6 data set using the V6TRANSPORT option may corrupt data SN-007829 PROC SQL query containing boolean logic can return incorrect results in specific cases SN-007827 Segmentation violation produced from PROC SQL query containing subqueries where both a SAS data set and a DBMS table are referenced SN-007831 PROC SQL join of a view and a SAS data set can return different results SN-007822 Access violation or system abend when executing a PROC SQL direct join against an Oracle table SN-007636 DISTINCT keyword in SQL subquery produces incorrect results or no results in SAS/ACCESS to ODBC or SAS/ACCESS to DB2 SN-007826 PROC SQL generates incorrect pass through code when there are multiple OR'd expressions in the WHERE clause SN-007871 Password value is displayed in SAS log when defining an SQL view with a USING clause which contains a password parameter SN-008356 Integer divide by zero error when displaying column with length of 32767 SN-008314 SASHELP.VTABLE displays data set labels unexpectedly SN-007222 Outer join of two (2) DBMS tables via a LIBNAME engine with WHERE clause subsets may generate incorrect results SN-009491 Implicit SQL Passthru may drop important parenthesis from WHERE condition SN-009727 Aliased columns in SQL views which perform a simple calculation may lose part of the condition SN-009529 Performing a COUNT or COUNT DISTINCT on a renamed column that is part of a view may result in performance degradation SN-008877 Incorrect results or abends in PROC SQL working with shortened numerics SN-010745 Part of join criteria is lost joining DBMS tables via LIBNAME engine SN-011220 Numeric literals in an ON clause with outer join of some DBMS tables may not return correct results SN-011239 Final WHERE clause not included in the SQL to be proccessed by the database when using the LIBNAME ACCESS engine SN-011210 Incorrect results from PROC SQL using WHERE= option with indexed tables SN-011802 "Error: sqlplan internal error" when joining a table with an inline view SN-012854 Using LIBNAME engine may result in an incorrect query being generated SN-009514 Accessing DBMS tables with column aliases defined via a view may prevent implicit pass-thru SN-012757 SAS/ACCESS query may return incorrect results when duplicate variable names exist SN-012760 Applying hotfix 82BB70 causes SQLPLAN Internal Error SN-004451 Query submitted to DBMS may generate incorrect results which may be reviewed at: http://support.sas.com/techsup/unotes/SN/004/004241.html http://support.sas.com/techsup/unotes/SN/003/003976.html http://support.sas.com/techsup/unotes/SN/005/005899.html http://support.sas.com/techsup/unotes/SN/005/005712.html http://support.sas.com/techsup/unotes/SN/006/006247.html http://support.sas.com/techsup/unotes/SN/006/006274.html http://support.sas.com/techsup/unotes/SN/006/006741.html http://support.sas.com/techsup/unotes/SN/004/004536.html http://support.sas.com/techsup/unotes/SN/006/006773.html http://support.sas.com/techsup/unotes/SN/004/004451.html http://support.sas.com/techsup/unotes/SN/006/006403.html http://support.sas.com/techsup/unotes/SN/006/006582.html http://support.sas.com/techsup/unotes/SN/006/006768.html http://support.sas.com/techsup/unotes/SN/006/006624.html http://support.sas.com/techsup/unotes/SN/006/006772.html http://support.sas.com/techsup/unotes/SN/005/005608.html http://support.sas.com/techsup/unotes/SN/005/005808.html http://support.sas.com/techsup/unotes/SN/006/006829.html http://support.sas.com/techsup/unotes/SN/007/007824.html http://support.sas.com/techsup/unotes/SN/007/007820.html http://support.sas.com/techsup/unotes/SN/007/007319.html http://support.sas.com/techsup/unotes/SN/007/007829.html http://support.sas.com/techsup/unotes/SN/007/007827.html http://support.sas.com/techsup/unotes/SN/007/007831.html http://support.sas.com/techsup/unotes/SN/007/007822.html http://support.sas.com/techsup/unotes/SN/007/007636.html http://support.sas.com/techsup/unotes/SN/007/007826.html http://support.sas.com/techsup/unotes/SN/007/007871.html http://support.sas.com/techsup/unotes/SN/008/008356.html http://support.sas.com/techsup/unotes/SN/008/008314.html http://support.sas.com/techsup/unotes/SN/007/007222.html http://support.sas.com/techsup/unotes/SN/009/009491.html http://support.sas.com/techsup/unotes/SN/009/009727.html http://support.sas.com/techsup/unotes/SN/009/009529.html http://support.sas.com/techsup/unotes/SN/008/008877.html http://support.sas.com/techsup/unotes/SN/010/010745.html http://support.sas.com/techsup/unotes/SN/011/011220.html http://support.sas.com/techsup/unotes/SN/011/011239.html http://support.sas.com/techsup/unotes/SN/011/011210.html http://support.sas.com/techsup/unotes/SN/011/011802.html http://support.sas.com/techsup/unotes/SN/012/012854.html http://support.sas.com/techsup/unotes/SN/009/009514.html http://support.sas.com/techsup/unotes/SN/012/012757.html http://support.sas.com/techsup/unotes/SN/012/012760.html http://support.sas.com/techsup/unotes/SN/004/004451.html The hot fix package downloaded is a self extracting executable named 82bc14o2.exe which will install the following files: * sasesql.dll the replacement module containing the hot fix * sassqlt.dll the replacement module containing the hot fix * sassqpd.dll the replacement module containing the hot fix * sassqxe.dll the replacement module containing the hot fix * sassqxn.dll the replacement module containing the hot fix * sassqxs.dll the replacement module containing the hot fix * sassql.dll the replacement module containing the hot fix * sassqlu.dll the replacement module containing the hot fix * sassqxb.dll the replacement module containing the hot fix * sassqxi.dll the replacement module containing the hot fix * sassqxo.dll the replacement module containing the hot fix * sassqxu.dll the replacement module containing the hot fix * sassqlp.dll the replacement module containing the hot fix * sassqp.dll the replacement module containing the hot fix * sassqxc.dll the replacement module containing the hot fix * sassqxj.dll the replacement module containing the hot fix * sassqxp.dll the replacement module containing the hot fix * sassqz.dll the replacement module containing the hot fix * 82bc14o2.aud a hot fix identifier file that will allow Technical Support to determine which fixes have been applied to a system * 82bc14o2.txt a copy of these installation instructions; this file is installed in !SASROOT\core\sasinst\hotfix IMPORTANT NOTES: 1. You must have Release 8.2 (TS2M0) installed on your system before applying this hot fix. 2. 82bc14o2.exe must be run from an OS2 command-line and must be launched from !SASROOT (the directory where Release 8.2 (TS2M0) is installed). AFTER DOWNLOADING: In this example, it is assumed that !SASROOT is: c:\sas STEP 1 Change to the !SASROOT directory, [c:\] cd c:\sas STEP 2 Move the downloaded executable to the !SASROOT directory. Assuming 82bc14o2.exe is downloaded to c:\myfiles, [c:\sas] move c:\myfiles\82bc14o2.exe \sas\82bc14o2.exe STEP 3 Back-up the original file(s), [c:\sas] ren c:\sas\core\sasexe\sasesql.dll sasesql.000 [c:\sas] ren c:\sas\core\sasexe\sassqlt.dll sassqlt.000 [c:\sas] ren c:\sas\core\sasexe\sassqpd.dll sassqpd.000 [c:\sas] ren c:\sas\core\sasexe\sassqxe.dll sassqxe.000 [c:\sas] ren c:\sas\core\sasexe\sassqxn.dll sassqxn.000 [c:\sas] ren c:\sas\core\sasexe\sassqxs.dll sassqxs.000 [c:\sas] ren c:\sas\core\sasexe\sassql.dll sassql.000 [c:\sas] ren c:\sas\core\sasexe\sassqlu.dll sassqlu.000 [c:\sas] ren c:\sas\core\sasexe\sassqxb.dll sassqxb.000 [c:\sas] ren c:\sas\core\sasexe\sassqxi.dll sassqxi.000 [c:\sas] ren c:\sas\core\sasexe\sassqxo.dll sassqxo.000 [c:\sas] ren c:\sas\core\sasexe\sassqxu.dll sassqxu.000 [c:\sas] ren c:\sas\core\sasexe\sassqlp.dll sassqlp.000 [c:\sas] ren c:\sas\core\sasexe\sassqp.dll sassqp.000 [c:\sas] ren c:\sas\core\sasexe\sassqxc.dll sassqxc.000 [c:\sas] ren c:\sas\core\sasexe\sassqxj.dll sassqxj.000 [c:\sas] ren c:\sas\core\sasexe\sassqxp.dll sassqxp.000 [c:\sas] ren c:\sas\core\sasexe\sassqz.dll sassqz.000 STEP 4 Assuming you are still in c:\sas, launch the executable. The "/directories" option is required to maintain the proper directory structure during file extraction, [c:\sas] 82bc14o2.exe /directories This completes the installation of hot fix 82BC14 on OS/2.