INSTALLATION INSTRUCTIONS FOR HOT FIX 82SH09 ON OS/390 BEFORE DOWNLOADING: The hot fix 82SH09 addresses the issue(s) in Release 8.2 (TS2M0) of SAS/SHARE software on OS/390 as documented in SAS Note(s): SN-004909 Cross-architecture catalog access fails to reflect updates by same architect clients in a SAS/SHARE environment SN-006581 Cross-architecture RLS catalog access fails to reflect updates by server side in a SAS/CONNECT environment SN-005507 Loop in SAS/SHARE server with Yielding to Wait messages SN-006053 Concurrent updates against shared data on a SAS/SHARE server might compromise data integrity SN-005185 "WZX: conversion buffer overflowed" error with SAS/CONNECT RLS SN-005745 Version 6 data set header corruption by Version 8 SAS/SHARE cross-architecture client SN-005694 VIEWTABLE, Table Viewer, and Data Table WHERE clauses might return incorrect results through SAS/CONNECT RLS SN-006387 Explicit locking against Version 6 SAS/SHARE server can compromise data integrity SN-005187 "WZX: conversion buffer overflowed" error with SAS/SHARE RLS SN-005697 VIEWTABLE, Table Viewer, and Data Table WHERE clauses might return incorrect results through SAS/SHARE RLS SN-007225 Using PROC FSEDIT with a WHERE statement in SAS/SHARE across platforms and releases generates error message SN-006337 Memory abends may occur when processing SAS data with a WHERE clause through remote library services. SN-009498 CLOSE function through REMOTE engine abends CONNECT server side SN-009371 KEY= value not found in SAS/SHARE cross-platform and cross-release environment SN-009499 CLOSE function through REMOTE engine abends SHARE server side SN-009549 "Library damaged" error message appears when reading large catalog entry through REMOTE engine SN-007490 PROC OPERATE and DISPLAY USER returning two rows of output to SAS/SHARE server SAS Log SN-010004 Creating new catalog via RLS (Remote Library Services) through SAS/CONNECT results in appending to existing catalog SN-010876 S0C4 in SAS/SHARE Server SN-011360 PROC SQL with SHARE via XMS produces incorrect results SN-014465 WARNING: Task is in hold-term SN-016778 server NOALLOC option is not completely honored in certain cases which may be reviewed at: http://support.sas.com/techsup/unotes/SN/004/004909.html http://support.sas.com/techsup/unotes/SN/006/006581.html http://support.sas.com/techsup/unotes/SN/005/005507.html http://support.sas.com/techsup/unotes/SN/006/006053.html http://support.sas.com/techsup/unotes/SN/005/005185.html http://support.sas.com/techsup/unotes/SN/005/005745.html http://support.sas.com/techsup/unotes/SN/005/005694.html http://support.sas.com/techsup/unotes/SN/006/006387.html http://support.sas.com/techsup/unotes/SN/005/005187.html http://support.sas.com/techsup/unotes/SN/005/005697.html http://support.sas.com/techsup/unotes/SN/007/007225.html http://support.sas.com/techsup/unotes/SN/006/006337.html http://support.sas.com/techsup/unotes/SN/009/009498.html http://support.sas.com/techsup/unotes/SN/009/009371.html http://support.sas.com/techsup/unotes/SN/009/009499.html http://support.sas.com/techsup/unotes/SN/009/009549.html http://support.sas.com/techsup/unotes/SN/007/007490.html http://support.sas.com/techsup/unotes/SN/010/010004.html http://support.sas.com/techsup/unotes/SN/010/010876.html http://support.sas.com/techsup/unotes/SN/011/011360.html http://support.sas.com/techsup/unotes/SN/014/014465.html http://support.sas.com/techsup/unotes/SN/016/016778.html The following file(s) will be installed: * 82sh09os.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\82sh09os 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 82sh09os.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/share/82sh09/mvs Issue the following commands where 'sas.hotfix.xmit' is the filename you created in step 1. binary get 82sh09os.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.HF82SH09.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.HF82SH09.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82SH09.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.HF82SH09.DBCS.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82SH09.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.HF82SH09.SASMSG'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation SASMSG library before replacing. * '&prefix.HF82SH09.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.HF82SH09.AUTOLIB'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation AUTOLIB library before replacing. * '&prefix.HF82SH09.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.HF82SH09.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.HF82SH09.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.HF82SH09.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 82SH09 on OS/390.