Hot fix E18001 addresses the issue(s) in SAS Deployment Tester - Server 1.3_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/E18.html#E18001
See the Maintenance Installation Tool (MIT) documentation for more details
on the installation of hot fixes.
IMPORTANT NOTES
1. You must have SAS Deployment Tester - Server 1.3_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.
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 E18001os.bin TO A UNIX FILE SYSTEM DIRECTORY ON Z/OS
This can be done in one of three ways:
Method 1) Download hot fix E18001os.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 E18001os.bin file
to your working directory in USS by issuing the following commands:
binary
put E18001os.bin /uss_directory/E18001os.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/E18/E18001/xx/mvs
Issue the following commands to place the BIN file in your
working directory in USS:
binary
get E18001os.bin /uss_directory/E18001os.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/E18/E18001/xx/mvs
get E18001os.bin /uss_directory/E18001os.bin (repl
quit
/*
STEP 2: VERIFY EXECUTE PERMISSION ON THE INSTALLATION BINARY
1. "cd" to the working directory in USS where you copied E18001os.bin
2. Issue a ls -l to view the E18001os.bin permissions. If you do NOT see:
-rwxr-xr-x E18001os.bin
then you will need to change the permissions.
3. Use the chmod command to make E18001os.bin executable:
chmod 755 E18001os.bin
4. Issue a ls -l again to confirm that E18001os.bin has execute permission.
You should now see:
-rwxr-xr-x E18001os.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 two methods for executing the hot fix binary. Select the method
appropriate for your environment to install this hot fix.
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.
./E18001os.bin -- -silent
Note: -- (represents two dashes)
Method B) 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
./E18001os.bin
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:
dproserver_1.3_M2_HFE18001_mvs_xx_Install_postexec.log
dproserver_1.3_M2_HFE18001_mvs_xx_Install_preexec.log
This completes the installation of hot fix E18001 on z/OS.