Hot fix D56001 addresses the issue(s) in SAS/IntrNet 9.21_M1 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/D56.html#D56001
See the Maintenance Installation Tool (MIT) documentation for more details
on the installation of hot fixes.
IMPORTANT NOTES
1. You must have SAS/IntrNet 9.21_M1 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 D56001os.bin TO A UNIX FILE SYSTEM DIRECTORY ON Z/OS
This can be done in one of three ways:
Method 1) Download hot fix D56001os.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 D56001os.bin file
to your working directory in USS by issuing the following commands:
binary
put D56001os.bin /uss_directory/D56001os.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/D/D56/D56001/xx/mvs
Issue the following commands to place the BIN file in your
working directory in USS:
binary
get D56001os.bin /uss_directory/D56001os.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/D/D56/D56001/xx/mvs
get D56001os.bin /u/sdcsas2/D56001os.bin (repl
quit
/*
STEP 2: VERIFY EXECUTE PERMISSION ON THE INSTALLATION BINARY
1. "cd" to the working directory in USS where you copied D56001os.bin
2. Issue a ls -l to view the D56001os.bin permissions. If you do NOT see:
-rwxr-xr-x D56001os.bin
then you will need to change the permissions.
3. Use the chmod command to make D56001os.bin executable:
chmod 755 D56001os.bin
4. Issue a ls -l again to confirm that D56001os.bin has execute permission.
You should now see:
-rwxr-xr-x D56001os.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:
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.
./D56001os.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.
./D56001os.bin --keep -- -silent -nojobsubmit
After you have manually submitted all the jobs you must re-launch the
hot fix binary with the -finalizeinstall parameter:
./D56001os.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
./D56001os.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
./D56001os.bin --keep -- -nojobsubmit
After you have manually submitted all the jobs you must re-launch the
hot fix binary with the -finalizeinstall parameter:
./D56001os.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:
intrnet_9.21_M1_HFD56001_mvs_xx_Install_postexec.log
intrnet_9.21_M1_HFD56001_mvs_xx_Install_preexec.log
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.D56001.BAMISC
&prefix.D56001.CLIST
&prefix.D56001.CNTL
&prefix.D56001.CNTL.PREEDIT
&prefix.D56001.CNTL.UTILIB
&prefix.D56001.CONFIG
&prefix.D56001.PROCLIB
&prefix.D56001.SASRX
&prefix.D56001.SASRXCFG
&prefix.D56001.TKMVSENV
If the following datasets were created:
* '&prefix.D56001.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.D56001.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.D56001.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.D56001.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.D56001.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.D56001.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.D56001.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.D56001.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.D56001.SASHELP'
then you will need to replace your current SAS 9.2 (9.2 TS2Mx)
installation SASHELP library with the
'&prefix.D56001.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.D56001.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.D56001.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 D56001 on z/OS.