Hot fix B4C001 addresses the issue(s) in SAS IT Resource Management 3.8 on z/OS as documented
in the following SAS Note:
http://http://support.sas.com/kb/60977
IMPORTANT NOTES
1. This hot fix should only be applied to a SAS System running 9.4 TS1M5. Use
the special install instructions provided in the INSTALLATION INSTRUCTIONS
section below to install this hot fix.
2. You must have SAS IT Resource Management 3.8 installed on your system before
applying this hot fix. Refer to Usage Note 35968 for instructions
on how to determine which product releases you have installed.
3. All currently active SAS sessions, daemons, spawners and servers must
be terminated before applying this hot fix.
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. 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.
DOWNLOAD INSTRUCTIONS
FTP B4C001os.zip to a UNIX file system directory on z/OS. This can be
done in one of three ways:
Option 1) Download hot fix B4C001os.zip to your PC. When downloading a
SAS 9.4 hot fix, you must choose to "save" the hot fix. After
downloading the file to the PC, FTP the B4C001os.zip file to
your working directory in USS by issuing the following commands:
NOTE: It is recommended to FTP the file(s) to the default USS
directory <SASHOME>/InstallMisc/HotFixes/New. If this
USS directory does not exist on your system, you should create
it before beginning the FTP process.
binary
put B4C001os.zip /<your_uss_directory>/B4C001os.zip
quit
Option 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/B4C/B4C001/xx/mvs
Issue the following commands to place the ZIP file in your working
directory in USS:
binary
get B4C001os.zip /<your_uss_directory>/B4C001os.zip
quit
Option 3) From z/OS, submit 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/B4C/B4C001/xx/mvs
get B4C001os.zip /<your_uss_directory>/B4C001os.zip (repl
quit
/*
INSTALLATION INSTRUCTIONS
The B4C001 hot fix for SAS IT Resource Management Data 3.8 will be installed using the SAS Deployment
Manager. By default, the SAS Deployment Manager will search in the <SASHOME>/InstallMisc/HotFixes/New
directory for hot fixes to be applied, but will also prompt for a location if you have
downloaded hot fixes to a different directory.
After downloading B4C001os.zip, follow the instructions for applying hot fixes in the
SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.
IMPORTANT NOTE: Do not specify the –jobsubmit option when starting the SAS Deployment Manager
for this hot fix and follow the important instructions below before running any jobs that the
SAS Deployment Manager creates.
The SASHELP dataset that is used to receive the content of the hot fix must be created before running
any jobs associated with the hot fix. Look for the allocation details of your existing SASHELP dataset,
typically called:
<hlq>.ENW0.SASHELP
where hlq is the high-level qualifier of your existing SAS System installation.
Using the same DCB attributes and SPACE allocation, create another dataset with the following name:
<hlq>.B4C001.ENW0.SASHELP
The “B4C001” qualifier is important because it designates the name of the hot fix to which this
dataset will be associated.
Run the jobs HOTFIX01 thru HOTFIX07 and PROMOT01 and PROMOT02. The default action is for each HOTFIX
job to submit the next one in sequence, on the condition that no errors are encountered. Similarly,
PROMOT01 will submit PROMOT02.
If you do not pre-allocate the B4C001.ENW0.SASHELP dataset, the second job, HOTFIX02, might abend with
a B37. In which case you should create the SASHELP dataset according to the instructions above and rerun
the HOTFIX02 job.
ITRM will not execute correctly using staged hot fix libraries, so you should run the PROMOT01 and PROMOT02
jobs following the HOTFIX07 job.
This completes the installation of hot fix B4C001 on z/OS.