INSTALLATION INSTRUCTIONS
STEP 1: VERIFY EXECUTE PERMISSION ON THE INSTALLATION BINARY
1. "cd" to the working directory in UNIX File System where the D49002 subdirectory was extracted
2. Issue a ls -l to view the D54002os.bin permissions. If you do NOT see:
-rwxr-xr-x D54002os.bin
then you will need to change the permissions.
3. Use the chmod command to make D54002os.bin executable:
chmod 755 D54002os.bin
4. Issue a ls -l again to confirm that D54002os.bin has execute permission.
You should now see:
-rwxr-xr-x D54002os.bin
STEP 2: 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 3: BACK UP FILES TO BE UPDATED IN UNIX File System
This hot fix includes updates to load modules installed in MVS libraries and to files
installed in UNIX File System.
Before installing this hot fix, you should make a back up copy of the /SASFoundation/9.2/picklist/itmsmvadata/batchapi.txt file.
These are the updated files that will be installed in UNIX File System after the hot fix is installed:
/SASFoundation/9.2/picklist/itmsmvadata/batchapi.txt
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.hpovpa.nls_302001.0.0.20110518102523_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.hpovpa_302001.0.0.20110518102523_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.hpovrep_302001.0.0.20110518102524_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.mxg_302001.0.0.20110518102524_f0rm32/sas.solutions.itms.adapter.mxg.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.mxg_302001.0.0.20110518102524_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.ntsmf_302001.0.0.20110518102524_f0rm32/sas.solutions.itms.adapter.ntsmf.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.ntsmf_302001.0.0.20110518102524_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.patrol_302001.0.0.20110518102524_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.snmp_302001.0.0.20110518102523_f0rm32/sas.solutions.itms.adapter.snmp.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.snmp_302001.0.0.20110518102523_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.adapter.vmware_302001.0.0.20110518102524_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.deploy.nls_302001.0.0.20110518102603_f0rm32/sas.solutions.itms.deploy.nls.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.deploy.nls_302001.0.0.20110518102603_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.deploy_302001.0.0.20110518102603_f0rm32/sas.solutions.itms.deploy.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.deploy_302001.0.0.20110518102603_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.models.nls_302001.0.0.20110518102336_f0rm32/sas.solutions.itms.models.nls.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.models.nls_302001.0.0.20110518102336_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.models_302001.0.0.20110518102336_f0rm32/sas.solutions.itms.models.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.models_302001.0.0.20110518102336_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.visuals.nls_302001.0.0.20110518102428_f0rm32/sas.solutions.itms.visuals.nls.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.visuals.nls_302001.0.0.20110518102428_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.visuals_302001.0.0.20110518102428_f0rm32/sas.solutions.itms.visuals.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itms.visuals_302001.0.0.20110518102428_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.hpovpa_302001.0.0.20110518102336_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.hpovrep_302001.0.0.20110518102336_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.mxg_302001.0.0.20110518102336_f0rm32/sas.solutions.itrm.adapter.mxg.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.mxg_302001.0.0.20110518102336_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.ntsmf_302001.0.0.20110518102336_f0rm32/sas.solutions.itrm.adapter.ntsmf.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.ntsmf_302001.0.0.20110518102336_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.patrol_302001.0.0.20110518102336_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.sar_302001.0.0.20110518102336_f0rm32/sas.solutions.itrm.adapter.sar.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.sar_302001.0.0.20110518102336_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.scom_302001.0.0.20110518102337_f0rm32/sas.solutions.itrm.adapter.scom.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.scom_302001.0.0.20110518102337_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.snmp_302001.0.0.20110518102337_f0rm32/sas.solutions.itrm.adapter.snmp.jar
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.snmp_302001.0.0.20110518102337_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.vmware_302001.0.0.20110518102337_f0rm32/META-INF/MANIFEST.MF
/SASVersionedJarRepository/9.2/eclipse/plugins/sas.solutions.itrm.adapter.weblog_302001.0.0.20110518102336_f0rm32/META-INF/MANIFEST.MF
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.
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.
./D54002os.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.
./D54002os.bin --keep -- -silent -nojobsubmit
After you have manually submitted all the jobs you must re-launch the
hot fix binary with the -finalizeinstall parameter:
./D54002os.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 UNIX File System. 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
./D54002os.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
./D54002os.bin --keep -- -nojobsubmit
After you have manually submitted all the jobs you must re-launch the
hot fix binary with the -finalizeinstall parameter:
./D54002os.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 UNIX File System. 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: SASHELP Updates
Notes:
&prefix is the prefix specified at the time of your install.
ll is the code for the language of your installation.
Wn is the encoding for your installation.
This hot fix includes updates to the SASHELP.ITMS and SASHELP.SASMACR catalogs, and the
SASHELP.ITMS_SMF_LSPRDATA dataset in &prefix.D54002.llWn.SASHELP.
To test these updates prior to promoting them to production, concatenate the &prefix.D54002.llWn.SASHELP
library in front of the production SASHELP library. To do so, update your SAS configuration file
&prefix.CONFIG(llWn) as follows:
SASHELP=('MVS:&prefix.D54002.llWn.SASHELP'
'MVS:&prefix.llWn.SASHELP')
Sample names for the configuration file, and SASHELP libraries are:
USERID.CONFIG(ENW0)
USERID.ENW0.SASHELP
USERID.D54002.ENW0.SASHELP
STEP 6: PROMOTING HOT FIXES TO PRODUCTION
Notes:
&prefix is the prefix specified at the time of your install.
ll is the code for the language of your installation.
Wn is the encoding for your installation.
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.D54002.BAMISC
&prefix.D54002.CLIST
&prefix.D54002.CNTL
&prefix.D54002.CNTL.PREEDIT
&prefix.D54002.CNTL.UTILIB
&prefix.D54002.CONFIG
&prefix.D54002.PROCLIB
&prefix.D54002.SASRX
&prefix.D54002.SASRXCFG
&prefix.D54002.TKMVSENV
If the following datasets were created:
* '&prefix.D54002.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.D54002.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.D54002.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.D54002.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.D54002.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.D54002.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.D54002.<encoding>.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.D54002.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.D54002.ITRM.CPMISC
then you will need to replace the like-named members in
your current SAS 9.2 (9.2 TS2Mx) installation CPMISC
library with the members loaded to
'&prefix.D54002.ITRM.CPMISC'. We suggest you rename the
members in the current SAS 9.2 (9.2 TS2Mx) installation
CPMISC library before replacing, or make a backup copy
of the original members.
* '&prefix.D54002.<encoding>.SASHELP
Before promoting the updated catalogs you should first make a
backup copy of the production SASHELP dataset.
To promote the updated SASMACR catalog to production, submit the
following SAS job:
//jobname JOB
//STEP1 EXEC SAS92,OPTIONS=’SASHELP=SASHELP’
//SASHELP DD DSN=&prefix.llWn.SASHELP,DISP=OLD
//SYSIN DD *
libname hflib '&prefix.D54002.llWn.SASHELP' DISP=SHR;
proc catalog cat=hflib.SASMACR force;
copy out=SASHELP.SASMACR;
quit;
run;
For more information about the LSPR table, updating its values, or
backing up and restoring the default table after applying hot fix D49002,
please refer to SAS Note 40936.
To promote the updated ITMS catalog and
ITMS_SMF_LSPRDATA dataset to production, submit the following SAS code:
//jobname JOB
//STEP1 EXEC SAS92,OPTIONS=’SASHELP=SASHELP’
//SASHELP DD DSN=&prefix.llWn.SASHELP,DISP=OLD
//SYSIN DD *
libname hflib '&prefix.D54002.llWn.SASHELP' DISP=SHR;
proc copy in=hflib out=SASHELP;
select ITMS ITMS_SMF_LSPRDATA;
run;
ADDITIONAL NOTES:
* If the hot fix installation created '&prefix.D54002.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.D54002.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 D54002 on z/OS.
Return to the D49002 install instructions.