INSTALLATION INSTRUCTIONS FOR HOT FIX 82BA19 ON OS/390 BEFORE DOWNLOADING: The hot fix 82BA19 addresses the issue(s) in Release 8.2 (TS2M0) of Base SAS software on OS/390 as documented in SAS Note(s): SN-005868 New procedure CV2VIEW is available to assist in converting SAS/Access view descriptors to LIBNAME views which may be reviewed at: http://www.sas.com/service/techsup/unotes/SN/005/005868.html The following files will be installed: * 82ba19os.xmit the replacement load module(s) containing the hot fix in XMIT format (sascv2vi) * 82ba19os.xmitmsg the replacement message(s) containing the hot fix in XMIT format (dbicvt) * 82ba19os.rexx the REXX EXEC used to install the hot fix on your OS/390 system * 82ba19os.aud a hot fix identifier file that will allow Technical Support to determine which fixes have been applied to a system * 82ba19os.txt a copy of these installation instructions IMPORTANT NOTE(S): 1. You must have Release 8.2 (TS2M0) 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 82BA19". 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 82ba19os.exe. Launching the executable will extract the OS/390 files to the default location C:\os390\82ba19os 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 82ba19os.exe, contact your System Administrator for additional instructions. STEP 2: Once the contents of 82ba19os.exe have been extracted, the files must be moved via FTP from your PC to your OS/390 system. 1. Allocate two data sets on OS/390 with the following DCB characteristics. These are the locations where the files 82ba19os.xmit and 82ba19os.xmitmsg files MUST be FTP'ed. In this example these data sets will be called "sas.hotfix.xmit" and "sas.hotfix.xmitmsg". Organization . . . . . : PS Record format . . . . . : FB Record length . . . . . : 80 Block size . . . . . . : 3120 2. Open an MS-DOS (or NT Command Prompt) window and change to the directory where the contents of 82ba19os.exe were unzipped. C:\> cd \os390\82ba19os 3. FTP to your OS/390 system using the appropriate userid and password. C:\os390\82ba19os> ftp 4. Issue the following commands: ftp> binary ftp> put 82ba19os.xmit 'sas.hotfix.xmit' (rep <== VERIFY 'sas.hotfix.xmit' DSN ftp> put 82ba19os.xmitmsg 'sas.hotfix.xmitmsg' (rep <== VERIFY 'sas.hotfix.xmitmsg' DSN ftp> ascii ftp> put 82ba19os.rexx 'sas.hotfix.rexx' <== VERIFY 'sas.hotfix.rexx' DSN ftp> put 82ba19os.aud 'sas.hotfix.aud' <== VERIFY 'sas.hotfix.aud' DSN ftp> put 82ba19os.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 82ba19os.xmit and 82ba19os.xmitmsg MUST be transferred using the BINARY protocol, and 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.2 (TS2M0) SAS Installation Libraries as you will be prompted for this information. NOTE: We will not modify any of your Release 8.2 (TS2M0) libraries during this process. STEP 4: After completing this install using the REXX EXEC, you will need to replace the like-named modules in your current Release 8.2 (TS2M0) installation library with the modules loaded to '&prefix.HF82BA19.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. You also will need to replace the like-named members in your current Release 8.2 (TS2M0) SASMSG library with the members loaded to '&prefix.HF82BA19.SASMSG'. We suggest you rename the members in the current Release 8.2 (TS2M0) SASMSG library before replacing. This completes the installation of hot fix 82BA19 on OS/390. ----- ADDITIONAL OPTION FOR ACCESSING HOT FIX 82BA19 ----- 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: Allocate two data sets on OS/390 with the following DCB characteristics. These are the locations where the files 82ba19os.xmit and 82ba19os.xmitmsg MUST be FTP'ed. In this example these data sets will be called "sas.hotfix.xmit" and "sas.hotfix.xmitmsg". Organization . . . . . : PS Record format . . . . . : FB Record length . . . . . : 80 Block size . . . . . . : 3120 STEP 2: FTP to ftp.sas.com using: userid=anonymous and password=your.email@address STEP 3: Issue the following command: cd /techsup/download/hotfix/v82/base/82ba19/mvs STEP 4: If you are executing FTP directly from OS/390 you can issue the following commands, otherwise go to STEP 5: binary get 82ba19os.xmit 'sas.hotfix.xmit' (rep get 82ba19os.xmitmsg 'sas.hotfix.xmitmsg' (rep ascii get 82ba19os.rexx 'sas.hotfix.rexx' get 82ba19os.aud 'sas.hotfix.aud' get 82ba19os.txt 'sas.hotfix.txt' This will FTP the file 82ba19os.xmit to "sas.hotfix.xmit" and 82ba19os.xmitmsg to "sas.hotfix.xmitmsg" which you allocated in Step 1 above. Now skip to Step 6. STEP 5: If you are executing FTP from another host, you can issue the following commands: binary get 82ba19os.xmit "a_local_path_name" get 82ba19os.xmitmsg "a_local_path_name" ascii get 82ba19os.rexx "a_local_path_name" get 82ba19os.aud "a_local_path_name" get 82ba19os.txt "a_local_path_name" You will then need to take steps to FTP the file 82ba19os.xmit to "sas.hotfix.xmit" and 82ba19os.xmitmsg to "sas.hotfix.xmitmsg" which you created in STEP 1 above. The remaining three files must also be FTP'ed to your OS/390 system. STEP 6: 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.2 (TS2M0) SAS Installation Libraries as you will be prompted for this information. NOTE: We will not modify any of your Release 8.2 (TS2M0) libraries during this process. STEP 7: After completing this install using the REXX EXEC, you will need to replace the like-named modules in your current Release 8.2 (TS2M0) installation library with the modules loaded to '&prefix.HF82BA19.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. You also will need to replace the like-named members in your current Release 8.2 (TS2M0) SASMSG library with the members loaded to '&prefix.HF82BA19.SASMSG'. We suggest you rename the members in the current Release 8.2 (TS2M0) SASMSG library before replacing. This completes the installation of hot fix 82BA19 on OS/390.