Contribute in GitHub:
Open doc issue|Edit online
Planning Considerations
The installation of UKO includes the following installation steps:
| Area | Details | Installation skills required |
|---|---|---|
| z/OS network definitions | The connection between UKO and the UKO Agent program is based on the TCP/IP protocol. A raw IP socket interface is used. | z/OS TCP/IP |
| Db2 definitions and customization | The UKO installation provides sample Db2 definitions. The sample must be customized for the installation. | z/OS Db2 administrator |
| ICSF software | Integrated Cryptographic Service Facility (ICSF) must be installed and configured. | z/OS system programmer |
| RACF definitions and customization | UKO requires new RACF profiles to be defined. Also, access to the ICSF callable services, keys, and Db2 must be permitted. Note: This documentation refers to the RACF Security Server, but other authorization systems can be used as well. |
RACF administrator |
| Agent installation | The UKO installation delivers load modules for the execution of the UKO Agent. The load modules must be distributed and installed on each of the LPARs where a UKO Agent has to run. Special attention should be given to the UKO APF authorized modules. These modules should be reviewed and installed according to the procedures normally used for APF authorized programs. | z/OS application developer and z/OS system programmer |