INSTALLATION INSTRUCTIONS FOR HOT FIX 82BC14 ON HP-UX BEFORE DOWNLOADING: The hot fix 82BC14 addresses the issue(s) in Release 8.2 (TS2M0) of Base SAS software on HP-UX 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-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/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 that is downloaded is in compressed tar format. The name of the tar file is 82bc14h8.tar.Z, and it contains the following files: * sasesql.82bc14 the replacement executable containing the hot fix * sasesql a link to sasesql.82bc14 * sassqlt.82bc14 the replacement executable containing the hot fix * sassqlt a link to sassqlt.82bc14 * sassqpd.82bc14 the replacement executable containing the hot fix * sassqpd a link to sassqpd.82bc14 * sassqxe.82bc14 the replacement executable containing the hot fix * sassqxe a link to sassqxe.82bc14 * sassqxn.82bc14 the replacement executable containing the hot fix * sassqxn a link to sassqxn.82bc14 * sassqxs.82bc14 the replacement executable containing the hot fix * sassqxs a link to sassqxs.82bc14 * sassql.82bc14 the replacement executable containing the hot fix * sassql a link to sassql.82bc14 * sassqlu.82bc14 the replacement executable containing the hot fix * sassqlu a link to sassqlu.82bc14 * sassqxb.82bc14 the replacement executable containing the hot fix * sassqxb a link to sassqxb.82bc14 * sassqxi.82bc14 the replacement executable containing the hot fix * sassqxi a link to sassqxi.82bc14 * sassqxo.82bc14 the replacement executable containing the hot fix * sassqxo a link to sassqxo.82bc14 * sassqxu.82bc14 the replacement executable containing the hot fix * sassqxu a link to sassqxu.82bc14 * sassqlp.82bc14 the replacement executable containing the hot fix * sassqlp a link to sassqlp.82bc14 * sassqp.82bc14 the replacement executable containing the hot fix * sassqp a link to sassqp.82bc14 * sassqxc.82bc14 the replacement executable containing the hot fix * sassqxc a link to sassqxc.82bc14 * sassqxj.82bc14 the replacement executable containing the hot fix * sassqxj a link to sassqxj.82bc14 * sassqxp.82bc14 the replacement executable containing the hot fix * sassqxp a link to sassqxp.82bc14 * sassqz.82bc14 the replacement executable containing the hot fix * sassqz a link to sassqz.82bc14 * 82bc14h8.aud a hot fix identifier file that will allow Technical Support to determine which fixes have been applied to a system * 82bc14h8.txt a copy of these installation instructions; this file is installed in !SASROOT/hotfix/doc IMPORTANT NOTE(S): 1. You must have Release 8.2 (TS2M0) installed on your system before applying this hot fix. AFTER DOWNLOADING: The following instructions describe the steps for installing the files listed above. In this example, !SASROOT, the directory where Release 8.2 (TS2M0) is installed, is: /usr/lib/sas8 STEP 1: Assuming the tar file is downloaded to the user's HOME directory, follow these procedures to install the package. $> cd /usr/lib/sas8 $> uncompress -c $HOME/82bc14h8.tar | tar -xf - STEP 2: Once the tar command is complete, the following lines must be added as the first lines of the !SASROOT/dbcs/sasv8.cfg file: -path !SASROOT/hotfix/sasexe -path !SASROOT/../hotfix/sasexe Also, the following line must be added as the first line of the !SASROOT/sasv8.cfg: -path !SASROOT/hotfix/sasexe Do not modify any existing -PATH options in the !SASROOT/dbcs/sasv8.cfg or !SASROOT/sasv8.cfg files. STEP 3: Change the ownership (using the chown command) and permissions (using the chmod command) on the files in the !SASROOT/dbcs/hotfix/sasexe directory to match the ownership and permissions on the files in the !SASROOT/dbcs/sasexe directory. Also, change the ownership and permissions on the files in the !SASROOT/hotfix/sasexe directory to match the ownership and permissions on the files in the !SASROOT/sasexe directory. This completes the installation of hot fix 82BC14 on HP-UX.