INSTALLATION INSTRUCTIONS FOR HOT FIX 81BA47 ON OS/390 BEFORE DOWNLOADING: The hot fix 81BA47 addresses the issue(s) in Release 8.1 (TS1M0) of Base SAS software on OS/390 as documented in SAS Note(s): SN-003613 Performance enhancements made to the EIS Data model class SN-003612 Performance enhancements made to the MDDB Report Viewer SN-003810 Libref assigned to a Repository Manager may be ignored SN-003974 Memory not deallocated appropriately for Open Olap Server applications SN-003899 ERROR: Cannot Open SASHELP.EIS.UNIQUE.SCL SN-003072 Values for a class variable that have been restricted in Access Control may display in Subset by Dimension window. SN-004375 Filters may not work when you specify a label for the class variable SN-004378 Detail data not subsetted correctly when class variable value has an "=" character SN-004379 Detail data may not be subsetted correctly after changing filter by values SN-004377 All variables may not be displayed when reaching through to the detail data SN-004376 Download to spreadsheet may not work when class variable value contains an "&" character SN-004436 Assert Data error message after hiding statistic labels and expanding a webEIS report SN-004437 Reach Through to detail data in MDDB Report Viewer returns ERROR: Calling function DELLIST SN-004934 Holap data sources may not always be correctly joined SN-005196 Cannot register an MDDB if SAS/MDDB Server common products not licensed which may be reviewed at: http://www.sas.com/service/techsup/unotes/SN/003/003613.html http://www.sas.com/service/techsup/unotes/SN/003/003612.html http://www.sas.com/service/techsup/unotes/SN/003/003810.html http://www.sas.com/service/techsup/unotes/SN/003/003974.html http://www.sas.com/service/techsup/unotes/SN/003/003899.html http://www.sas.com/service/techsup/unotes/SN/003/003072.html http://www.sas.com/service/techsup/unotes/SN/004/004375.html http://www.sas.com/service/techsup/unotes/SN/004/004378.html http://www.sas.com/service/techsup/unotes/SN/004/004379.html http://www.sas.com/service/techsup/unotes/SN/004/004377.html http://www.sas.com/service/techsup/unotes/SN/004/004376.html http://www.sas.com/service/techsup/unotes/SN/004/004436.html http://www.sas.com/service/techsup/unotes/SN/004/004437.html http://www.sas.com/service/techsup/unotes/SN/004/004934.html http://www.sas.com/service/techsup/unotes/SN/005/005196.html The following files will be installed: * 81ba47os.xmit the replacement load module(s) containing the hot fix in XMIT format (sasomdbi) * 81ba47os.xpt the replacement catalog(s) containing the hot fix in XPT format (mb.sas7bcat, eissrv.sas7bcat, mddb.sas7bcat, webeis.sas7bcat) * 81ba47os.rexx the REXX EXEC used to install the hot fix on your OS/390 system * 81ba47os.aud a hot fix identifier file that will allow Technical Support to determine which fixes have been applied to a system * 81ba47os.txt a copy of these installation instructions IMPORTANT NOTE(S): 1. You must have Release 8.1 (TS1M0) installed on your system before applying this hot fix. 2. This hot fix must be downloaded to a PC running a Windows system (Windows 95/98/2000/NT or higher) for file extraction. If Web download on a PC is not available at your site, but FTP to external sites is available, instructions for an alternative process are documented below. See section titled "ADDITIONAL OPTION FOR ACCESSING HOT FIX 81BA47". 3. Before proceeding with STEP 5 of the INSTALLATION INSTRUCTIONS, insure no Version 8.1 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. STEP 1: The hot fix package downloaded is a self extracting executable named 81ba47os.exe. Launching the executable will extract the OS/390 files to the default location C:\os390\81ba47os 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. If you are unable to run 81ba47os.exe, contact your System Administrator for additional instructions. STEP 2: Once the contents of 81ba47os.exe have been extracted, the files must be moved via FTP from your PC to your OS/390 system. 1. XMIT file allocation: Allocate a data set on OS/390 with the following DCB characteristics. This is the location where the file 81ba47os.xmit MUST be FTP'ed. In this example the data set will be called "sas.hotfix.xmit". Organization . . . . . : PS Record format . . . . . : FB Record length . . . . . : 80 Block size . . . . . . : 3120 2. XPT file allocation: Allocate a data set on OS/390 with the following DCB characteristics. This is the location where the file 81ba47os.xpt MUST be FTP'ed. In this example the data set will be called "sas.hotfix.xpt". Organization . . . . . : PS Record format . . . . . : FB Record length . . . . . : 80 Block size . . . . . . : 8000 3. Open an MS-DOS (or NT Command Prompt) window and change to the directory where the contents of 81ba47os.exe were unzipped. C:\> cd \os390\81ba47os 4. FTP to your OS/390 system using the appropriate userid and password. C:\os390\81ba47os> ftp 5. Issue the following commands: ftp> binary ftp> put 81ba47os.xmit 'sas.hotfix.xmit' (rep <== VERIFY 'sas.hotfix.xmit' DSN ftp> put 81ba47os.xpt 'sas.hotfix.xpt' (rep <== VERIFY 'sas.hotfix.xpt' DSN ftp> ascii ftp> put 81ba47os.rexx 'sas.hotfix.rexx' <== VERIFY 'sas.hotfix.rexx' DSN ftp> put 81ba47os.aud 'sas.hotfix.aud' <== VERIFY 'sas.hotfix.aud' DSN ftp> put 81ba47os.txt 'sas.hotfix.txt' <== VERIFY 'sas.hotfix.txt' DSN ftp> quit Other methods for moving files between your PC systems and OS/390 systems that are available at your site may be used to transfer these files. However, the files 81ba47os.xmit and 81ba47os.xpt MUST be transferred using the BINARY protocol. The .rexx, .aud, and .txt files must be transferred using ASCII protocol. STEP 3: After you have completed the FTP, you should run the REXX EXEC from either native TSO or ISPF using the following command: EXEC 'sas.hotfix.rexx' where 'sas.hotfix.rexx' is the DSN you FTP'ed to as instructed above. You should follow the prompts of the REXX EXEC, typing in responses as directed. NOTE: You should know the high level qualifer, or prefix, of your Release 8.1 (TS1M0) SAS Installation Libraries as you will be prompted for this information. NOTE: We will not modify any of your Release 8.1 (TS1M0) libraries during this process. STEP 4: After completing the execution of the REXX EXEC, you will need to replace the like-named modules in your current Release 8.1 (TS1M0) installation library with the modules loaded to '&prefix.HF81BA47.LIBRARY'. We suggest you rename the modules in the current Release 8.1 (TS1M0) installation library before replacing. STEP 5: NOTE: Before proceeding with this step, insure no Version 8.1 SAS jobs are running because this step requires exclusive access to the SASHELP library. To complete the installation of this hot fix, the transport data set "sas.hotfix.xpt" must be cimported to the SASHELP library. The SASHELP library must be accessed with a DISP=OLD. To do this the following job must be run in batch mode: //CIMPORT JOB your jobcard <=== VERIFY INFO //STEP1 EXEC SAS8 <=== VERIFY PROC NAME //SASHELP DD DISP=OLD,DSN=sas.v81prod.sashelp <=== VERIFY DSN //SYSIN DD * /* Back up production catalogs */ proc datasets lib=sashelp memtype=catalog; change mb=mb_6; change eissrv=eissrv_6; change mddb=mddb_6; change webeis=webeis_6; quit; /* Cimport transport dataset */ proc cimport infile='sas.hotfix.xpt' lib=sashelp; /* VERIFY infile= */ This completes the installation of hot fix 81BA47 on OS/390. ----- ADDITIONAL OPTION FOR ACCESSING HOT FIX 81BA47 ----- If Web download and PC access are not available at your site, but FTP to external sites is available, you may use the following process to access this hot fix. These instructions explain accessing this hot fix through anonymous FTP. STEP 1: XMIT file allocation: Allocate a data set on OS/390 with the following DCB characteristics. This is the location where the file 81ba47os.xmit MUST be FTP'ed. In this example the data set will be called "sas.hotfix.xmit". Organization . . . . . : PS Record format . . . . . : FB Record length . . . . . : 80 Block size . . . . . . : 3120 STEP 2: XPT file allocation: Allocate a data set on OS/390 with the following DCB characteristics. This is the location where the file 81ba47os.xpt MUST be FTP'ed. In this example the data set will be called "sas.hotfix.xpt". Organization . . . . . : PS Record format . . . . . : FB Record length . . . . . : 80 Block size . . . . . . : 8000 STEP 3: FTP to ftp.sas.com using: userid=anonymous and password=your.email@address STEP 4: Issue the following command: cd /techsup/download/hotfix/v81/base/81ba47/mvs STEP 5: If you are executing FTP directly from OS/390 you can issue the following commands, otherwise go to STEP 6: binary get 81ba47os.xmit 'sas.hotfix.xmit' (rep get 81ba47os.xpt 'sas.hotfix.xpt' (rep ascii get 81ba47os.rexx 'sas.hotfix.rexx' get 81ba47os.aud 'sas.hotfix.aud' get 81ba47os.txt 'sas.hotfix.txt' This will FTP the file 81ba47os.xmit to "sas.hotfix.xmit" which you allocated in Step 1 and the file 81ba47os.xpt to "sas.hotfix.xpt" which you allocated in Step 2 above. Now skip to STEP 7. STEP 6: If you are executing FTP from another host, you can issue the following commands: binary get 81ba47os.xmit "a_local_path_name" get 81ba47os.xpt "a_local_path_name" ascii get 81ba47os.rexx "a_local_path_name" get 81ba47os.aud "a_local_path_name" get 81ba47os.txt "a_local_path_name" You will then need to take steps to FTP the file 81ba47os.xmit to "sas.hotfix.xmit" which you created in STEP 1 above, and FTP the file 81ba47os.xpt to "sas.hotfix.xpt" which you created in STEP 2. The remaining three files must also be FTP'ed to your OS/390 system. STEP 7: After you have completed the FTP, you should run the REXX EXEC from either native TSO or ISPF using the following command: EXEC 'sas.hotfix.rexx' where 'sas.hotfix.rexx' is the DSN you FTP'ed to as instructed above. You should follow the prompts of the REXX EXEC, typing in responses as directed. NOTE: You should know the high level qualifer, or prefix, of your Release 8.1 (TS1M0) SAS Installation Libraries as you will be prompted for this information. NOTE: We will not modify any of your Release 8.1 (TS1M0) libraries during this process. STEP 8: After completing the execution of the REXX EXEC, you will need to replace the like-named modules in your current Release 8.1 (TS1M0) installation library with the modules loaded to '&prefix.HF81BA47.LIBRARY'. We suggest you rename the modules in the current Release 8.1 (TS1M0) installation library before replacing. STEP 9: NOTE: Before proceeding with this step, insure no Version 8.1 SAS jobs are running because this step requires exclusive access to the SASHELP library. To complete the installation of this hot fix, the transport data set "sas.hotfix.xpt" must be cimported to the SASHELP library. The SASHELP library must be accessed with a DISP=OLD. To do this the following job must be run in batch mode: //CIMPORT JOB your jobcard <=== VERIFY INFO //STEP1 EXEC SAS8 <=== VERIFY PROC NAME //SASHELP DD DISP=OLD,DSN=sas.v81prod.sashelp <=== VERIFY DSN //SYSIN DD * /* Back up production catalogs */ proc datasets lib=sashelp memtype = catalog; change mb=mb_6; change eissrv=eissrv_6; change mddb=mddb_6; change webeis=webeis_6; quit; /* Cimport transport dataset */ proc cimport infile='sas.hotfix.xpt' lib=sashelp; /* VERIFY infile= */ This completes the installation of hot fix 81BA47 on OS/390.