INSTALLATION INSTRUCTIONS FOR HOT FIX 82BC24 ON OS/390 BEFORE DOWNLOADING: The hot fix 82BC24 addresses the issue(s) in Release 8.2 (TS2M0) of Base SAS software on OS/390 as documented in SAS Note(s): SN-005048 Incorrect output results from PROC FORMAT with the MULTILABEL option SN-004316 WHERE returns incorrect number of observations SN-005243 CALL EXECUTE may truncate or repeat generated code SN-005374 Pull-down menus in SAS Display Manager on OS/390 may be affected by European locales SN-004992 Interrupting and cancelling a DATA step replaces exiting data set SN-005744 WHERE statement returns incorrect results SN-004633 "Error: The yieobtn function is not supported by the SASE7 engine" might appear when you examine remote SQL views via the SQL dictionary table SN-005975 ERROR: Macro variable name & must start with a letter or underscore SN-006109 Exiting SAS within a macro window causes an infinite loop SN-006963 Values within %SYSFUNC on a %DO loop are incorrectly uppercased SN-006566 SAS SHARE server abends with S0C4 in VSRACR1 SN-006847 COMPRESS=BINARY may cause problems SN-007001 Missing semicolon on a %LOCAL statement causes system specific errors SN-008106 Missing format on the SAS/SHARE server may cause S0C4 abend SN-008119 Error message generated when creating a V6 SAS data set from a DBMS table containing a character column greater than 200 bytes SN-004165 Catalog becomes corrupted leaving header information unreadable SN-008902 Segmentation Violation or other abend possible when running SAS macro code from within Risk Dimensions SN-008911 Macro causes errors when tokenizer reads past an end of line SN-008919 WHERE with user-written informat produces incorrect results SN-009349 Errors from EFI, PROC IMPORT, or PROC EXPORT following hot fix installation SN-009294 Long character value may not be visible in the FSVIEW window SN-009299 PROC UNIVARIATE may abend with the PLOTS option and BY statement SN-009625 PROC TRANSPOSE produces errors when VALIDVARNAME=V6 is specified and 82BX04 HotFix is applied SN-011148 PROC APPEND Abends with S0C4, U2096, Segmentation Violation, Stack Overflow or Read/Write Access Violations in Task Append SN-012376 SURVEYSELECT may produce incorrect results SN-012162 MODIFY Statement uses more I/O in Version 8 than in Version 6 SN-006334 Ending from Output window may return to Program Editor instead of the AF window SN-008832 SAS code in SUBMIT block may suspend execution SN-007336 Program Editor window may display on top of fullscreen window SN-013577 WHERE clause returns incorrect results with overlapping ranges SN-015882 A Japanese character that contains the hex value for a single or double quote may be misinterpreted by the SAS tokenizer SN-016283 A Japanese character that contains the hex value for a single or double quote may cause the Program Editor to have an incorrect color which may be reviewed at: http://support.sas.com/techsup/unotes/SN/005/005048.html http://support.sas.com/techsup/unotes/SN/004/004316.html http://support.sas.com/techsup/unotes/SN/005/005243.html http://support.sas.com/techsup/unotes/SN/005/005374.html http://support.sas.com/techsup/unotes/SN/004/004992.html http://support.sas.com/techsup/unotes/SN/005/005744.html http://support.sas.com/techsup/unotes/SN/004/004633.html http://support.sas.com/techsup/unotes/SN/005/005975.html http://support.sas.com/techsup/unotes/SN/006/006109.html http://support.sas.com/techsup/unotes/SN/006/006963.html http://support.sas.com/techsup/unotes/SN/006/006566.html http://support.sas.com/techsup/unotes/SN/006/006847.html http://support.sas.com/techsup/unotes/SN/007/007001.html http://support.sas.com/techsup/unotes/SN/008/008106.html http://support.sas.com/techsup/unotes/SN/008/008119.html http://support.sas.com/techsup/unotes/SN/004/004165.html http://support.sas.com/techsup/unotes/SN/008/008902.html http://support.sas.com/techsup/unotes/SN/008/008911.html http://support.sas.com/techsup/unotes/SN/008/008919.html http://support.sas.com/techsup/unotes/SN/009/009349.html http://support.sas.com/techsup/unotes/SN/009/009294.html http://support.sas.com/techsup/unotes/SN/009/009299.html http://support.sas.com/techsup/unotes/SN/009/009625.html http://support.sas.com/techsup/unotes/SN/011/011148.html http://support.sas.com/techsup/unotes/SN/012/012376.html http://support.sas.com/techsup/unotes/SN/012/012162.html http://support.sas.com/techsup/unotes/SN/006/006334.html http://support.sas.com/techsup/unotes/SN/008/008832.html http://support.sas.com/techsup/unotes/SN/007/007336.html http://support.sas.com/techsup/unotes/SN/013/013577.html http://support.sas.com/techsup/unotes/SN/015/015882.html http://support.sas.com/techsup/unotes/SN/016/016283.html The following file(s) will be installed: * 82bc24os.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\82bc24os 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 82bc24os.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/82bc24/mvs Issue the following commands where 'sas.hotfix.xmit' is the filename you created in step 1. binary get 82bc24os.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.HF82BC24.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.HF82BC24.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82BC24.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.HF82BC24.DBCS.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82BC24.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.HF82BC24.SASMSG'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation SASMSG library before replacing. * '&prefix.HF82BC24.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.HF82BC24.AUTOLIB'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation AUTOLIB library before replacing. * '&prefix.HF82BC24.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.HF82BC24.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.HF82BC24.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.HF82BC24.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 82BC24 on OS/390.