INSTALLATION INSTRUCTIONS FOR HOT FIX 82BB84 ON OS/390 BEFORE DOWNLOADING: The hot fix 82BB84 addresses the issue(s) in Release 8.2 (TS2M0) of Base SAS software on OS/390 as documented in SAS Note(s): SN-004574 Spanned headers in PROC REPORT may cause incorrect cellwidth when using ODS SN-004501 PROC TABULATE repeats statistics in all ODS destinations except listing and output data sets SN-005261 The CHARSET= and ENCODING= ODS options are ignored by the HTML and XML destinations SN-005850 DBCS characters may not display properly when using ODS RTF SN-005851 Certain DBCS characters prevent RTF files from being opened by Microsoft Word SN-005425 Invalid files generated for ODS printer destinations in Asian encodings SN-005950 ODS PDF does not render Latin1 (ISO 8859-1) encoding correctly SN-005951 ODS PDF and RTF can not produce double-byte encoded output SN-005949 ODS PDF will only use Times, Helvetica, and Courier as default font SN-005596 Output data set may not be generated when using the ODS OUTPUT statement SN-007190 Incorrect Japanese character appears in ODS RTF output on DBCS systems SN-007191 Generating ODS/RTF output using the ESCAPECHAR option causes errors on DBCS systems SN-009281 The OVERPRINT system option does not work correctly with the ODS PRINTER and PDF destinations SN-010318 User-defined format can not be updated when applied to a variable created with ODS OUTPUT SN-010411 Customized template may cause observations to not appear in ODS PRINTER output SN-005994 Using a PREIMAGE= specification and STARTPAGE= with ODS PRINTER causes errors SN-009366 ODS PRINTER does not close registry keys properly which may be reviewed at: http://support.sas.com/techsup/unotes/SN/004/004574.html http://support.sas.com/techsup/unotes/SN/004/004501.html http://support.sas.com/techsup/unotes/SN/005/005261.html http://support.sas.com/techsup/unotes/SN/005/005850.html http://support.sas.com/techsup/unotes/SN/005/005851.html http://support.sas.com/techsup/unotes/SN/005/005425.html http://support.sas.com/techsup/unotes/SN/005/005950.html http://support.sas.com/techsup/unotes/SN/005/005951.html http://support.sas.com/techsup/unotes/SN/005/005949.html http://support.sas.com/techsup/unotes/SN/005/005596.html http://support.sas.com/techsup/unotes/SN/007/007190.html http://support.sas.com/techsup/unotes/SN/007/007191.html http://support.sas.com/techsup/unotes/SN/009/009281.html http://support.sas.com/techsup/unotes/SN/010/010318.html http://support.sas.com/techsup/unotes/SN/010/010411.html http://support.sas.com/techsup/unotes/SN/005/005994.html http://support.sas.com/techsup/unotes/SN/009/009366.html The following file(s) will be installed: * 82bb84os.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\82bb84os 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 82bb84os.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/DBCS/v82/base/82bb84/mvs Issue the following commands where 'sas.hotfix.xmit' is the filename you created in step 1. binary get 82bb84os.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.HF82BB84.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.HF82BB84.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82BB84.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.HF82BB84.DBCS.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82BB84.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.HF82BB84.SASMSG'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation SASMSG library before replacing. * '&prefix.HF82BB84.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.HF82BB84.AUTOLIB'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation AUTOLIB library before replacing. * '&prefix.HF82BB84.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.HF82BB84.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.HF82BB84.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.HF82BB84.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 82BB84 on OS/390.