Installation Instructions for Hot Fix E53001

z/OS


Hot fix E53001 addresses the issue(s) in SAS OnDemand Scoring Engine 3.2 on z/OS.

See the Maintenance Installation Tool (MIT) documentation for more details
on the installation of hot fixes.


IMPORTANT NOTES

     1. You must have SAS OnDemand Scoring Engine 3.2 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.
     6. SAS Hot Fixes are installed into new datasets after which they can be
        promoted to your production libraries.  Several new datasets will be
        created in this process.
     7. The hotfix CLIST or PROC jcl will be customized with the concatenate hotfix
        datasets.


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 E53001os.bin TO A UNIX FILE SYSTEM DIRECTORY ON Z/OS

This can be done in one of three ways:

  Method 1) Download hot fix E53001os.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 E53001os.bin file
            to your working directory in USS by issuing the following commands:

            binary
            put E53001os.bin /uss_directory/E53001os.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/E/E53/E53001/xx/mvs

            Issue the following commands to place the BIN file in your
            working directory in USS:

            binary
            get E53001os.bin /uss_directory/E53001os.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/E/E53/E53001/xx/mvs
                  get E53001os.bin /uss_directory/E53001os.bin (repl
                  quit
                  /*


STEP 2: VERIFY EXECUTE PERMISSION ON THE INSTALLATION BINARY

   1. "cd" to the working directory in USS where you copied E53001os.bin

   2. Issue a ls -l to view the E53001os.bin permissions. If you do NOT see:
      -rwxr-xr-x    E53001os.bin
      then you will need to change the permissions.

   3. Use the chmod command to make E53001os.bin executable:

            chmod 755 E53001os.bin

   4. Issue a ls -l again to confirm that E53001os.bin has execute permission.
      You should now see:
      -rwxr-xr-x    E53001os.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: 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:

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. ./E53001os.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. ./E53001os.bin --keep -- -silent -nojobsubmit After you have manually submitted all the jobs you must re-launch the hot fix binary with the -finalizeinstall parameter: ./E53001os.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 ./E53001os.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 ./E53001os.bin --keep -- -nojobsubmit After you have manually submitted all the jobs you must re-launch the hot fix binary with the -finalizeinstall parameter: ./E53001os.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: raptor_3.2_M0_HFE53001_mvs_xx_Install_postexec.log raptor_3.2_M0_HFE53001_mvs_xx_Install_preexec.log STEP 5: PROMOTING HOT FIXES TO PRODUCTION There are several different types of files that the hot fix created. The following datasets are created for testing purposes only and should not be promoted to production unless instructed otherwise: &prefix.E53001.BAMISC &prefix.E53001.CLIST &prefix.E53001.CNTL &prefix.E53001.CNTL.PREEDIT &prefix.E53001.CNTL.UTILIB &prefix.E53001.CONFIG &prefix.E53001.PROCLIB &prefix.E53001.SASRX &prefix.E53001.SASRXCFG &prefix.E53001.TKMVSENV The following files should be promoted to production. '&prefix.E53001.OSE.LIBRARY' Replace the following modules in your current SAS 9.2 (9.2 TS2Mx) OSE installation library with the modules loaded to '&prefix.E53001.OSE.LIBRARY'. We suggest you rename the modules in the current SAS 9.2 (9.2 TS2Mx) OSE installation library before replacing, or make a backup copy of the original modules. RAPPQX30 RAPTPC01 This completes the installation of hot fix E53001 on z/OS.