Datasets Allocation Considerations
The first step of the installation process creates IMAGE files from which the Connector files are loaded by the later steps.
Ensure that you select different prefix + version combinations to the IMAGE files (%instpref% in the Installation Upload and IMAGE Datasets Parameters table below) and to the Connector files (xPREFx + xVERx in the Connector for RACF Datasets Allocation Parameters table). Otherwise the installation fails due to duplicate datasets.
When selecting high level qualifiers for the files, ensure the product installer has ALTER authority for these files.
Some of the parameters are the unit name and volume serial number to be used for product datasets allocation. If the datasets must be SMS managed, leave these parameters empty (except for SPCVOL which must be *). If the datasets must not be SMS managed, specify the values for unit and volume serial number to ensure proper handling of the file.
Installation Upload and IMAGE Datasets Parameters
Parameter |
Description |
Value |
Upload dataset name |
The name of the dataset into which the product would be transferred using FTP. |
|
%xmitlib% |
Name of the library into which the Connector for RACF uploaded file would be uncompressed. |
|
%instpref% |
Prefix selected for Connector for RACF installation IMAGE datasets that are later used to install Connector for RACF. |
|
%UNIT% |
For non-SMS managed datasets specify UNIT(unitname) where unitname is the name of DASD unit where the Connector for RACF Installation IMAGE datasets would be placed. For SMS-managed datasets, specify null |
|
%VOLUME% |
For non-SMS managed datasets specify VOLUME(volser) where volser is the volume serial number on which Connector for RACF Installation IMAGE datasets would be placed. For SMS-managed datasets, specify null. |
|