Installation Instructions for Hot Fix B99010

z/OS


Hot fix B99010 addresses the issue(s) in SAS/CONNECT 9.21_M2 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/B99.html#B99010


This hot fix contains updates to the following software components:

Base SAS 9.21_M3
SAS/CONNECT 9.21_M2

Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The software components and release numbers should match the list of software components updated by the individual hot fix installers.


IMPORTANT NOTES

  1. You must have SAS/CONNECT 9.21_M2 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

  1. The B99010os.exe hot fix download package is a self-extracting zip file that contains individual hot fix installation binaries. Copy this file to your location of choice and extract the contents. Extracting the zip file will produce the following hot fix installers:
    B25162os.bin
    B99009os.bin
  2. To install each individual hot fix, follow the installation instructions below
    For each product installed, click the link to be redirected to post-installation instructions.
    B25162os.bin for Base SAS 9.21_M3
    B99009os.bin for SAS/CONNECT 9.21_M2


    B25162os.bin for Base SAS 9.21_M3

    STEP 1: FTP B25162os.bin TO A UNIX FILE SYSTEM DIRECTORY ON Z/OS

After extracting the contents of B99010os.exe on your PC, FTP the B25162os.bin file to your working directory in USS by issuing the following commands:

            binary
            put B25162os.bin /uss_directory/B25162os.bin
            quit




STEP 2: VERIFY EXECUTE PERMISSION ON THE INSTALLATION BINARY

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

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

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

            chmod 755 B25162os.bin

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

      

    •  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.


    

  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.

            ./B25162os.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.

            ./B25162os.bin --keep --  -silent -nojobsubmit

            After you have manually submitted all the jobs you must re-launch the
            hot fix binary with the -finalizeinstall parameter:

            ./B25162os.bin -- -finalizeinstall

            NOTE: 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

                    ./B25162os.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

                   ./B25162os.bin --keep -- -nojobsubmit

            After you have manually submitted all the jobs you must re-launch the
            hot fix binary with the -finalizeinstall parameter:

            ./B25162os.bin -- -finalizeinstall

            NOTE: 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.


STEP 5: PROMOTING HOT FIXES TO PRODUCTION

There are several different types of files that the hot fix may
have created.

The following datasets are created for testing purposes only and
should not be promoted to production unless instructed otherwise:

       &prefix.B25162.BAMISC
       &prefix.B25162.CLIST
       &prefix.B25162.CNTL
       &prefix.B25162.CNTL.PREEDIT
       &prefix.B25162.CNTL.UTILIB
       &prefix.B25162.CONFIG
       &prefix.B25162.PROCLIB
       &prefix.B25162.SASRX
       &prefix.B25162.SASRXCFG
       &prefix.B25162.TKMVSENV

If the following datasets were created:

    * '&prefix.B25162.LIBRARY'
         then you will need to replace the like-named modules in
         your current SAS 9.2 (9.2 TS2Mx) installation library
         with the modules loaded to '&prefix.B25162.LIBRARY'.
         We suggest you rename the modules in the current SAS 9.2
         (9.2 TS2Mx) installation library before replacing, or
         make a backup copy of the original modules.

    * '&prefix.B25162.DBCS.LIBRARY'
         then you will need to replace the like-named modules in
         your current SAS 9.2 (9.2 TS2Mx) installation DBCS
         library with the modules loaded to
         '&prefix.B25162.DBCS.LIBRARY'.  We suggest you rename
         the modules in the current SAS 9.2 (9.2 TS2Mx)
         installation library before replacing, or make a backup
         copy of the original modules.

    * '&prefix.B25162.SASMSG'
         then you will need to replace the like-named members in
         your current SAS 9.2 (9.2 TS2Mx) installation SASMSG
         library with the members loaded to
         '&prefix.B25162.SASMSG'.  We suggest you rename the
         members in the current SAS 9.2 (9.2 TS2Mx) installation
         SASMSG library before replacing, or make a backup copy
         of the original members.

    * '&prefix.B25162.AUTOLIB'
         then you will need to replace the like-named members in
         your current SAS 9.2 (9.2 TS2Mx) installation AUTOLIB
         library with the members loaded to
         '&prefix.B25162.AUTOLIB'.  We suggest you rename the
         members in the current SAS 9.2 (9.2 TS2Mx) installation
         AUTOLIB library before replacing, or make a backup copy
         of the original members.

    * '&prefix.B25162.SASHELP'
         then you will need to replace your current SAS 9.2 (9.2 TS2Mx)
         installation SASHELP library with the
         '&prefix.B25162.SASHELP'.  We suggest you rename the
         the current SAS 9.2 (9.2 TS2Mx) installation
         SASHELP library before replacing, or make a backup copy
         of the original library.



ADDITIONAL NOTES:

  * If the hot fix installation created '&prefix.B25162.LIBRARY'
    and it 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 hot fix installation created a '&prefix.B25162.LIBRARY'
    and you run with an entry point of SASLPA 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 and refresh LPA.

    In the configuration guide, the modules recommended for
    installation in the LPA are:

                    SASXAL
                    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 SAS 9.2 Foundation Into The
    LPA/ELPA" in the "Configuration Guide for SAS 9.2 Foundation
    for z/OS".


This completes the installation of hot fix B25162 on z/OS.


    B99009os.bin for SAS/CONNECT 9.21_M2

    STEP 1: FTP B99009os.bin TO A UNIX FILE SYSTEM DIRECTORY ON Z/OS

After extracting the contents of B99010os.exe on your PC, FTP the B99009os.bin file to your working directory in USS by issuing the following commands:

            binary
            put B99009os.bin /uss_directory/B99009os.bin
            quit




STEP 2: VERIFY EXECUTE PERMISSION ON THE INSTALLATION BINARY

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

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

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

            chmod 755 B99009os.bin

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

      

    •  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.


    

  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.

            ./B99009os.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.

            ./B99009os.bin --keep --  -silent -nojobsubmit

            After you have manually submitted all the jobs you must re-launch the
            hot fix binary with the -finalizeinstall parameter:

            ./B99009os.bin -- -finalizeinstall

            NOTE: 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

                    ./B99009os.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

                   ./B99009os.bin --keep -- -nojobsubmit

            After you have manually submitted all the jobs you must re-launch the
            hot fix binary with the -finalizeinstall parameter:

            ./B99009os.bin -- -finalizeinstall

            NOTE: 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.


STEP 5: PROMOTING HOT FIXES TO PRODUCTION

There are several different types of files that the hot fix may
have created.

The following datasets are created for testing purposes only and
should not be promoted to production unless instructed otherwise:

       &prefix.B99009.BAMISC
       &prefix.B99009.CLIST
       &prefix.B99009.CNTL
       &prefix.B99009.CNTL.PREEDIT
       &prefix.B99009.CNTL.UTILIB
       &prefix.B99009.CONFIG
       &prefix.B99009.PROCLIB
       &prefix.B99009.SASRX
       &prefix.B99009.SASRXCFG
       &prefix.B99009.TKMVSENV

If the following datasets were created:

    * '&prefix.B99009.LIBRARY'
         then you will need to replace the like-named modules in
         your current SAS 9.2 (9.2 TS2Mx) installation library
         with the modules loaded to '&prefix.B99009.LIBRARY'.
         We suggest you rename the modules in the current SAS 9.2
         (9.2 TS2Mx) installation library before replacing, or
         make a backup copy of the original modules.

    * '&prefix.B99009.DBCS.LIBRARY'
         then you will need to replace the like-named modules in
         your current SAS 9.2 (9.2 TS2Mx) installation DBCS
         library with the modules loaded to
         '&prefix.B99009.DBCS.LIBRARY'.  We suggest you rename
         the modules in the current SAS 9.2 (9.2 TS2Mx)
         installation library before replacing, or make a backup
         copy of the original modules.

    * '&prefix.B99009.SASMSG'
         then you will need to replace the like-named members in
         your current SAS 9.2 (9.2 TS2Mx) installation SASMSG
         library with the members loaded to
         '&prefix.B99009.SASMSG'.  We suggest you rename the
         members in the current SAS 9.2 (9.2 TS2Mx) installation
         SASMSG library before replacing, or make a backup copy
         of the original members.

    * '&prefix.B99009.AUTOLIB'
         then you will need to replace the like-named members in
         your current SAS 9.2 (9.2 TS2Mx) installation AUTOLIB
         library with the members loaded to
         '&prefix.B99009.AUTOLIB'.  We suggest you rename the
         members in the current SAS 9.2 (9.2 TS2Mx) installation
         AUTOLIB library before replacing, or make a backup copy
         of the original members.

    * '&prefix.B99009.SASHELP'
         then you will need to replace your current SAS 9.2 (9.2 TS2Mx)
         installation SASHELP library with the
         '&prefix.B99009.SASHELP'.  We suggest you rename the
         the current SAS 9.2 (9.2 TS2Mx) installation
         SASHELP library before replacing, or make a backup copy
         of the original library.



ADDITIONAL NOTES:

  * If the hot fix installation created '&prefix.B99009.LIBRARY'
    and it 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 hot fix installation created a '&prefix.B99009.LIBRARY'
    and you run with an entry point of SASLPA 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 and refresh LPA.

    In the configuration guide, the modules recommended for
    installation in the LPA are:

                    SASXAL
                    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 SAS 9.2 Foundation Into The
    LPA/ELPA" in the "Configuration Guide for SAS 9.2 Foundation
    for z/OS".


This completes the installation of hot fix B99009 on z/OS.


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

This completes the installation of hot fix B99010 on z/OS.