Installation instructions for hot fix B25210 on z/OS

Installation Instructions for Hot Fix B25210

z/OS

Hot fix B25210 addresses the issue(s) in Base SAS 9.21_M3 on z/OS as documented in the Issue(s) Addressed section of the hot fix download page: http://ftp.sas.com/techsup/download/hotfix/HF2/B25.html#B25210 See the Maintenance Installation Tool (MIT) documentation for more details on the installation of hot fixes. IMPORTANT NOTES 1. You must have Base SAS 9.21_M3 installed on your system before applying this hot fix. Refer to SN-35968 for instructions on how to determine which product releases you have installed. 2. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix. 3. This hot fix must be installed using the same userid which performed the initial software installation. 4. The hot fix installer has a graphical user interface that requires the use of an X11 server. If an X11 server is not available at your site, the silent installation process described below may be used. 5. Before proceeding with the execution of the hot fix binary, ensure that there are no SAS 9.2 jobs 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 hot fix file, moving the files to Unix System Services (USS) on your z/OS system and installing the hot fix from USS. STEP 1: FTP B25210os.bin TO A UNIX FILE SYSTEM DIRECTORY ON Z/OS This can be done in one of three ways: Method 1) Download hot fix B25210os.bin to your PC. When downloading a SAS 9.2 hot fix, you must choose to "save" the hot fix. **Note: Selecting "find a program online to open it" will result in an error. After downloading the file to the PC, FTP the B25210os.bin file to your working directory in USS by issuing the following commands: binary put B25210os.bin /uss_directory/B25210os.bin quit Method 2) From z/OS, FTP to ftp.sas.com using userid=anonymous and password=your.email@address Once you are logged on, "cd" to the following directory: /techsup/download/hotfix/HF2/B/B25/B25210/xx/mvs Issue the following commands to place the BIN file in your working directory in USS: binary get B25210os.bin /uss_directory/B25210os.bin quit Method 3) From z/OS, sumbit a batch job to FTP to ftp.sas.com using using userid=anonymous and password=your.email@address See sample JCL: //FTPFIX EXEC PGM=FTP //SYSPRINT DD SYSOUT=D //FTPOUT DD SYSOUT=D //SYSIN DD * ftp.sas.com (exit anonymous your.email@address binary cd /techsup/download/hotfix/HF2/B/B25/B25210/xx/mvs get B25210os.bin /uss_directory/B25210os.bin (repl quit /* STEP 2: VERIFY EXECUTE PERMISSION ON THE INSTALLATION BINARY 1. "cd" to the working directory in USS where you copied B25210os.bin 2. Issue a ls -l to view the B25210os.bin permissions. If you do NOT see: -rwxr-xr-x B25210os.bin then you will need to change the permissions. 3. Use the chmod command to make B25210os.bin executable: chmod 755 B25210os.bin 4. Issue a ls -l again to confirm that B25210os.bin has execute permission. You should now see: -rwxr-xr-x B25210os.bin STEP 3: LOCATE SASHOME AND BACK UP THE DEPLOYMENT REGISTRY During the hot fix installation you will need to provide the <SASHOME> location to be updated. You should provide the path to the top level SAS directory where the deploymntreg directory exists. It is recommended that you back up the deploymntreg directory prior to executing the hot fix binary. You can "cd" to your <SASHOME> and issue a command: cp -rf deploymntreg <backup_file_name> STEP 4: BACK UP FILES TO BE UPDATED IN USS This hot fix includes updates to files installed in USS, including <SASHOME>/SASFoundation/9.2/picklist/base/infomaps.txt <SASHOME>/SASVersionedJarRepository/9.2/eclipse/plugins/sas.iquery.services.nls_902300.0.0.20111209113500_v920m3f/sas.iquery.services.nls.jar <SASHOME>/SASVersionedJarRepository/9.2/eclipse/plugins/sas.iquery.services.nls_902300.0.0.20111209113500_v920m3f/META-INF/MANIFEST.MF <SASHOME>/SASVersionedJarRepository/9.2/eclipse/plugins/sas.iquery.services_902300.14.0.20120501074518_v920m3f/sas.iquery.services.jar <SASHOME>/SASVersionedJarRepository/9.2/eclipse/plugins/sas.iquery.services_902300.14.0.20120501074518_v920m3f/META-INF/MANIFEST.MF <SASHOME>/SASVersionedJarRepository/9.2/eclipse/plugins/sas.report.config_902300.1.0.20110225121800_v920m3f/sas.report.config.jar <SASHOME>/SASVersionedJarRepository/9.2/eclipse/plugins/sas.report.config_902300.1.0.20110225121800_v920m3f/META-INF/MANIFEST.MF Before installing this hot fix, you should make a back up copy of the infomaps.txt file. STEP 5: EXECUTE THE HOT FIX BINARY There are four methods for executing the hot fix binary. Select the method appropriate for your environment to install this hot fix.

Note: Method B and Method D use -nojobsubmit. Below are some of the reasons for using the -nojobsubmit command line option which will allow you to edit and submit the batch jobs yourself:

Your site uses JES3 (not JES2), or
Your FTP server is configured for JESINTERFACELEVEL=2, or
The SAS installer ID is not authorized to use FTP, or
You need to make site-specific changes to the JCL or wish to review the JCL before submission, or
The FTP JES interface’s requirement that the jobname be the user ID performing the install suffixed with a single letter or digit is incompatible with your site’s jobname requirements

If any of these conditions apply at your site, you must use the -nojobsubmit command line option.
If the initial SAS 9.2 installation is performed using the -nojobsubmit option either Method B or Method D, using the -nojobsubmit option, must be used to successfully apply hot fixes. See Usage Note 42460 for the error reported if the -nojobsubmit option is not used.

Method A) Line mode, Installation jobs submitted automatically Invoke the hot fix installation using the -silent option. The hot fix jobs will be automatically submitted for execution. ./B25210os.bin -- -silent Note: -- (represents two dashes) Method B) Line mode, Installation jobs submitted manually Invoke the hot fix installation using -silent mode and manually submit the hot fix jobs. ./B25210os.bin --keep -- -silent -nojobsubmit After you have manually submitted all the jobs you must re-launch the hot fix binary with the -finalizeinstall parameter: ./B25210os.bin -- -finalizeinstall NOTE (1): The installation job "Hotfix0" will automatically submit the MKSASINS job. When this job is completed, you can submit the next job which is "Hotfix1". NOTE (2): Only one hot fix can be installed at a time. You must install the hot fix, manually submit the install jobs and execute the -finalizeinstall step for one hot fix before beginning the installation of another hot fix. NOTE (3): This method creates a temporary directory XX_V1 in your working directory in USS. Once you have verified the hotfix, you can remove this directory to free up space. Method C) Graphical User Interface (GUI) mode, Installation jobs submitted automatically Invoke the hot fix installation. The hot fix jobs will be automatically submitted for execution. This method requires the use of an X11 server. An installation wizard will be initiated and will guide you through the hot fix installation process. Set your DISPLAY environment variable export DISPLAY=<your_node_name>:0 Execute the hot fix package ./B25210os.bin Method D) Graphical User Interface (GUI) mode, Installation jobs submitted manually Invoke the hot fix installation and manually submit the hot fix jobs. This method requires the use of an X11 server. An installation wizard will be initiated and will guide you through the hot fix installation process. Set your DISPLAY environment variable export DISPLAY=<your_node_name>:0 Execute the hot fix package ./B25210os.bin --keep -- -nojobsubmit After you have manually submitted all the jobs you must re-launch the hot fix binary with the -finalizeinstall parameter: ./B25210os.bin -- -finalizeinstall NOTE (1): The installation job "Hotfix0" will automatically submit the MKSASINS job. When this job is completed, you can submit the next job which is "Hotfix1". NOTE (2): Only one hot fix can be installed at a time. You must install the hot fix, manually submit the install jobs and execute the -finalizeinstall step for one hot fix before beginning the installation of another hot fix. NOTE (3): This method creates a temporary directory XX_V1 in your working directory in USS. Once you have verified the hotfix, you can remove this directory to free up space. A hot fix installation log will be created in the following location: <!SASHOME>/InstallMisc/InstallLogs/Maintenance/MIT_date-and-time-stamp.log Note: Each attempt to install a hot fix results in the creation of a new log file giving detailed information regarding the installation process. A preexec and postexec log is created during the hot fix installation process. The prexec log is created prior to installing the updates in the hot fix and identifies the files included in the hot fix that should be updated during the hot fix installation. The postexec log is created after the installation is completed and identifies the files that were updated. Both logs are written in the <!SASHOME>/InstallMisc/InstallLogs/Maintenance directory and include the hot fix id in the name of the file, for example: base_9.21_M3_HFB25210_mvs_xx_Install_postexec.log base_9.21_M3_HFB25210_mvs_xx_Install_preexec.log This completes the installation of hot fix B25210 on z/OS.