INSTALLATION INSTRUCTIONS FOR HOT FIX 82BC10 ON OS/390 BEFORE DOWNLOADING: The hot fix 82BC10 addresses the issue(s) in Release 8.2 (TS2M0) of Base SAS software on OS/390 as documented in SAS Note(s): SN-004436 Assert Data error message after hiding statistic labels and expanding a webEIS report SN-005262 Column order may change after performing an Analysis Sort SN-005259 Error displaying a hierarchy level when all values are hidden SN-005260 Computed columns calculated from restricted analysis variables are visible SN-005265 MDDB Table Exception invalid dimension error running with Middleware Server SN-005263 HOLAP Data Group Values marked SHOW in Access Control not found SN-004934 Holap data sources may not always be correctly joined SN-005668 Modifying column colors or fonts may not work and could generate errors SN-005670 Formats on Computed Values are not honored using a Bookmark in WebEIS SN-003072 Values for a class variable that have been restricted in Access Control may display in Subset by Dimension window. SN-005669 Java exception received when accessing Bookmarks using Access Control SN-005671 ERROR: Invalid list item index message received in WebEIS using NUNIQUE and ACL SN-005196 Cannot register an MDDB if SAS/MDDB Server common products not licensed SN-005264 Informat not honored in WHERE statement of PROC SQL when using a Star Schema SN-007171 Olap reports may fail when using user-defined display formats and no informats SN-007174 Mixed case variable names could generate error on _GET_UNIQUE_VALUES_ SN-007163 Columns Database not used when synchronizing MDDB metadata SN-007176 Only the computed values on current level of report get saved SN-007177 Drilling back up after applying a subset may not display correct report SN-007169 Metabase sort order not honored for registered MDDB tables SN-007179 Mixed case analysis variable used in a computed value may generate errors SN-007168 Unable to programatically register computed columns with long names SN-007178 Computed values may not appear when level is expanded and subset applied SN-007180 Subset specified on a drill variable may not be applied SN-007181 Computed columns defined with mixed case analysis variable names may not display SN-007042 Program halt in SASHELP.MDDB.TRANSLATE.SCL when EIS catalog not available SN-010373 ASSERT DATA and segmentation violation in task SASAZF errors when sorting MDDB column SN-013296 Analysis Variable sort is extremely slow which may be reviewed at: http://support.sas.com/techsup/unotes/SN/004/004436.html http://support.sas.com/techsup/unotes/SN/005/005262.html http://support.sas.com/techsup/unotes/SN/005/005259.html http://support.sas.com/techsup/unotes/SN/005/005260.html http://support.sas.com/techsup/unotes/SN/005/005265.html http://support.sas.com/techsup/unotes/SN/005/005263.html http://support.sas.com/techsup/unotes/SN/004/004934.html http://support.sas.com/techsup/unotes/SN/005/005668.html http://support.sas.com/techsup/unotes/SN/005/005670.html http://support.sas.com/techsup/unotes/SN/003/003072.html http://support.sas.com/techsup/unotes/SN/005/005669.html http://support.sas.com/techsup/unotes/SN/005/005671.html http://support.sas.com/techsup/unotes/SN/005/005196.html http://support.sas.com/techsup/unotes/SN/005/005264.html http://support.sas.com/techsup/unotes/SN/007/007171.html http://support.sas.com/techsup/unotes/SN/007/007174.html http://support.sas.com/techsup/unotes/SN/007/007163.html http://support.sas.com/techsup/unotes/SN/007/007176.html http://support.sas.com/techsup/unotes/SN/007/007177.html http://support.sas.com/techsup/unotes/SN/007/007169.html http://support.sas.com/techsup/unotes/SN/007/007179.html http://support.sas.com/techsup/unotes/SN/007/007168.html http://support.sas.com/techsup/unotes/SN/007/007178.html http://support.sas.com/techsup/unotes/SN/007/007180.html http://support.sas.com/techsup/unotes/SN/007/007181.html http://support.sas.com/techsup/unotes/SN/007/007042.html http://support.sas.com/techsup/unotes/SN/010/010373.html http://support.sas.com/techsup/unotes/SN/013/013296.html The following file(s) will be installed: * 82bc10os.xmit CNTL PDS in XMIT format. It contains all of the XMIT code necessary to apply the hotfix. IMPORTANT NOTE(S): 1. You must have Release 8.2 (TS2M0) installed on your system before applying this hot fix. 2. Before proceeding with STEP 5 of the INSTALLATION INSTRUCTIONS, insure no Version 8.2 SAS jobs are running because this step requires exclusive access to the SASHELP library. INSTALLATION INSTRUCTIONS: The following instructions describe the steps for extracting the contents of the downloaded file, moving the files to your OS/390 system and installing the hot fix. Please be sure to read the 'ADDITIONAL NOTES' section for situations where additional actions may be required. STEP 1: PRE-ALLOCATE THE XMIT FILE ON MVS Pre-allocate a file on MVS with the following DCB. Be sure to check the space requirement on the download page: Organization : PS Record format : FB Record length : 80 Block size : 3120 STEP 2: FTP THE XMIT FILE TO MVS FTP the XMIT file into this newly created file. This can be done in one of 2 ways: Method 1) Download the packaged hot fix to your PC. The packaged hot fix is a is a self extracting executable. Launching the executable will extract the OS/390 files to a default location example: C:\os390\82bc10os You will be prompted during the extraction process to accept or overwrite the default unzip location. The remaining steps in these installation instructions assume that you have unzipped the files to the default location After extracting the file, FTP the 82bc10os.xmit file to your MVS system doing a BINARY upload into the preallocated file created in step 1. Method 2) From MVS, FTP to ftp.sas.com using userid=anonymous and password=your.email@address Once you're logged on, cd into the following directory: /techsup/download/hotfix/v82/base/82bc10/mvs Issue the following commands where 'sas.hotfix.xmit' is the filename you created in step 1. binary get 82bc10os.xmit 'sas.hotfix.xmit' (rep STEP 3: RECEIVE THE XMIT FILE TO CREATE THE CNTL PDS On MVS do a RECEIVE command on the uploaded XMIT file as follows where 'sas.hotfix.xmit' is the preallocated file in step 1. receive indataset('sas.hotfix.xmit') After doing this you will be prompted with something similar to the following: INMR901I Dataset DATA.SET.NAME from USERID on ???????? INMR906A Enter restore parameters or 'DELETE' or 'END' + at this prompt you sould enter: DA('sas.hotfix.cntl') ... where sas.hotfix.cntl will be a new PDS that contains all of the parts necessary to apply this hot fix. STEP 4: EXECUTE THE REXX EXEC In your new CNTL data set is a REXX exec that will, if applicable, create any new load libraries and, if applicable, generate any JCL required to modify SAS catalogs in your SAS system. Execute this REXX exec from ISPF prompt: ex 'sas.hotfix.cntl(rexx)' STEP 5: RUN ANY GENERATED JCL If the REXX exec generated any JCLxxxxx members in your CNTL dataset you will need to edit the JCL to make any site specific modifications and then run the JCL. Note that the output data sets in this JCL requires DISP=OLD, so you will have to run it at a time when this would be possible. STEP 6: MERGE GENERATED LIBRARIES WITH SAS If the REXX exec created: * '&prefix.HF82BC10.LIBRARY' then you will need to replace the like-named modules in your current Release 8.2 (TS2M0) installation library with the modules loaded to '&prefix.HF82BC10.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82BC10.DBCS.LIBRARY' then you will need to replace the like-named modules in your current Release 8.2 (TS2M0) installation DBCS library with the modules loaded to '&prefix.HF82BC10.DBCS.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82BC10.SASMSG' then you will need to replace the like-named members in your current Release 8.2 (TS2M0) installation SASMSG library with the members loaded to '&prefix.HF82BC10.SASMSG'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation SASMSG library before replacing. * '&prefix.HF82BC10.AUTOLIB' then you will need to replace the like-named members in your current Release 8.2 (TS2M0) installation AUTOLIB library with the members loaded to '&prefix.HF82BC10.AUTOLIB'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation AUTOLIB library before replacing. * '&prefix.HF82BC10.ITSV.CPMISC' then you will need to replace the like-named members in your current Release 8.2 (TS2M0) installation CPMISC library with the members loaded to '&prefix.HF82BC10.ITSV.CPMISC'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation CPMISC library before replacing. ADDITIONAL NOTES: * If the REXX exec created a '&prefix.HF82BC10.LIBRARY' that contains a SASHOST, SASXAL, or SASXA1 module, and if you set SAS System options by assembling the DEFAULT OPTIONS TABLE using the BAOPTS1 member of the original CNTL data set, then you must re-assemble this table after applying this hot fix. To re-assemble this table do the following: 1) Edit the BAOPTS1 member in the original CNTL data set. 2) Change the SYSLMOD DD in all three LINK EDIT steps to point to the new HLQ.LIBRARY 3) rerun BAOPTS1. * If the REXX exec created a '&prefix.HF82BC10.LIBRARY' and you run with an entry point of SASXAL then you will need to look in the unloaded library to see if any of the new modules are installed in your LPA. If so, then you will need to replace them with the new modules. In the installation guide, the modules recommended for installation in the LPA are SASXAL SASXAL2 SABXSPL SABXDML SABDS SABSCLL SABDBGM SABZPLH SABXGPH Please note that if you use the BNDLSUFX option, you will have to rename the modules appropriately in your LPA. For more information about the LPA bundled configuration and information about using the BNDLSUFX option, please refer to the section entitled "Installing The SAS System Into The LPA" in the "Installation Instructions and System Manager's Guide" appropriate to the Version and maintenance level for your SAS System. This completes the installation of hot fix 82BC10 on OS/390.