[z/OS]

Installing Installation Manager on z/OS

To install and maintain software products, you can create one or more Installation Managers on your z/OS® system.

Before you begin

IBM® Installation Manager Version 1.8.5 or later is required to install the product.

  • Obtain the installation files for IBM Installation Manager as described in Obtaining an Installation Manager installation kit for installing IBM HTTP Server for z/OS.

    The sample jobs assume that the Installation Manager installation kit is mounted as read-only at /usr/lpp/InstallationManager/V1R4.

  • Decide in which of the following modes you want to run the Installation Manager:
    admin mode
    In admin mode, the Installation Manager is installed from a superuser ID (uid=0) and can be invoked from any superuser ID. There can be only one admin-mode Installation Manager on a system.
    user mode
    In user mode (also called nonAdmin mode), the Installation Manager can be invoked only by the user that installed it. There can be only one user-mode Installation Manager for a user.
    group mode
    In group mode, the Installation Manager can be invoked by any user ID that is connected to the owning group for the Installation Manager (the default group of the user ID that creates it). There is no limit to the number of group-mode Installation Managers that you can have on a system.
  • Choose locations for the Installation Manager executable binary files and runtime data locations.

    An Installation Manager consists of two sets of files: a set of executable binary files that are copied or updated from the installation kit, and a set of runtime data files that describe the products installed by this Installation Manager. Both sets of files must be writable by Installation Manager. You must select locations for both the executable and runtime data for each Installation Manager.

    Table 1. Default locations for Installation Manager files. The following table shows the default locations for the Installation Manager executable files (binaries) and runtime data on z/OS.
    Files Admin or group mode User mode
    Binaries /InstallationManager/bin $HOME/InstallationManager/bin
    Runtime data (also called agent data) /InstallationManager/appdata $HOME/InstallationManager/appdata

    These locations are assumed in the Installation Manager documentation and sample jobs. If these names are not appropriate for your system or if you choose to have several Installation Managers, you can choose different names and specify them when you create the Installation Manager.

Procedure

  1. Create a SAF group and user ID to own the Installation Manager by editing and submitting the GIN2ADMN sample job.

    If you installed the Installation Manager files with SMP/E, the Installation Manager sample jobs are in the GIN.SGINJCL data set. If you downloaded the files from the IBM website, they are the partitioned data set that you chose when you installed them.

    The user ID must have the following attributes:
    • Read/write home directory
    • Read access to FACILITY profile BPX.FILEATTR.APF
    • Read access to FACILITY profile BPX.FILEATTR.PROGCTL
    • Read access to FACILITY profile BPX.FILEATTR.SHARELIB
    • Read access to UNIXPRIV profile SUPERUSER.FILESYS.CHOWN or CHOWN.UNRESTRICTED
    • Read access to UNIXPRIV profile SUPERUSER.FILESYS.CHANGEPERMS

    The user ID that creates the Installation Manager is the initial (possibly only) user ID that can invoke that particular Installation Manager. If you create an Installation Manager in group mode, the default group for this user is the owning group for the Installation Manager. This user ID must have a read/write home directory.

  2. Edit and submit the GIN2CFS sample job to create a UNIX System Services file system and mount it at /InstallationManager.

    Before you run the job, you might have to create the /InstallationManager directory if it does not already exist.

  3. Install Installation Manager by editing and submitting the GIN2INST sample job.

What to do next

You can verify that Installation Manager is correctly installed by editing and submitting the GIN2CMD sample job. Alternatively, you can log in to the UNIX System Services shell under the user ID that created Installation Manager, and run the Installation Manager imcl command from the eclipse/tools subdirectory of the Installation Manager binaries location. For example:
cd /InstallationManager/bin/eclipse/tools

imcl -version

You are now ready to install products by using IBM Installation Manager.

Authorizing additional users to a group-mode Installation Manager: To allow additional users to access a group-mode Installation Manager, make sure that they meet the requirements listed in the first step of the procedure, and then connect them to the owning group for the Installation Manager by using the TSO CONNECT command:
CONNECT user2 GROUP(IMGROUP)
To install another Installation Manager, follow the steps in the procedure, selecting a new user ID and group (if appropriate) and new binaries and runtime data locations. Do not share binaries or runtime data locations between separate Installation Manager installations.
Correcting file ownership or permission problems: If you accidentally invoke Installation Manager from the wrong user ID, some files might end up with ownerships that prevent normal use of that Installation Manager instance. To correct this problem, log on to a super user or other privileged user ID and reset the file ownership and permissions for the Installation Manager binaries and runtime data. For example:
chown IMADMIN:IMGROUP /InstallationManager/bin
chmod 775 /InstallationManager/bin

chown IMADMIN:IMGROUP /InstallationManager/appdata
chmod 775 /InstallationManager/appdata
If the users of a group-mode Installation Manager do not have umask set to allow group-write permission on created files, you might also have to perform this step when you switch from one user ID to another. You might also need to set permissions and owners for the product files that you install with the Installation Manager to ensure that maintenance can be performed from other user IDs in the group.

Upgrading the Installation Manager: To upgrade an Installation Manager to a new level of the Installation Manager product, update your Installation Manager installation kit and sample jobs by following the instructions in Obtaining an Installation Manager installation kit for installing IBM HTTP Server for z/OS. Then re-run your GIN2INST job, specifying the same parameters that you used when you created the Installation Manager. Running the job updates the Installation Manager binaries to the level of the Installation Manager installation kit.


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 23, 2018 0:23
File name: tihs_installation_zos_im.html