Installing Installation Manager on z/OS
You can create one or more Installation Managers on your z/OS® system to install and maintain software products. You do not need to create an Installation Manager when working with Installation Manager portable installations on z/OS.
Before you begin
In order to install WebSphere Application Server Version 8.5, your Installation Manager must be at Version 1.5.2 or later. Installation Manager Version 1.9.0 or later is recommended.
- An Installation Manager install kit. See Obtaining an Installation Manager installation kit for installing the product on z/OS
- The Installation Manager sample jobs for z/OS. These jobs are shipped with the no-charge product 5655-IMZ (FMID HGIN140) in the SGINJCL library. You can also download a current version of the sample jobs here.
- user mode
- In user mode (also called nonAdmin mode), the Installation Manager can be invoked only by the user that installed it. There can only be 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. Group mode is recommended on z/OS.
The Installation Manager consists of two sets of files—a set of executable 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 write-able by the Installation Manager. You must select locations for both the executable and runtime data for each Installation Manager.
Files | Admin or group mode | User mode |
---|---|---|
Binaries | /InstallationManager/bin |
$HOME/InstallationManager/bin |
Runtime data (also called agent data) | /InstallationManager/appdata |
$HOME/InstallationManager/appdata |
Files | Admin or group mode | User mode |
---|---|---|
Binaries | /global/instmgr/bin |
$HOME/instmgr/bin |
Runtime data (also called agent data) | /global/instmgr/appdata |
$HOME/instmgr/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
What to do next
cd /global/instmgr/bin/eclipse/tools
imcl -version
You are now ready to install products 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 described previously and then connect them to the owning group for the Installation Manager using the TSO CONNECT command:
CONNECT user2 GROUP(IMGROUP)
To create an extra Installation Manager, follow the steps in the procedure described previously. Select 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 Managers.
- Correct file ownership or permission problems.If you accidentally invoke an Installation Manager from the wrong user ID, some files might end up with ownerships that prevent normal use of the Installation Manager. 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:
If the users of a group-mode Installation Manager do not havechown IMADMIN:IMGROUP /global/instmgr/bin chmod 775 /global/instmgr/bin chown IMADMIN:IMGROUP /global/instmgr/appdata chmod 775 /global/instmgr/appdata
umask
set to allow group-write permission on created files, you might also have to perform this step when switching 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. - Upgrade the Installation Manager.
To upgrade an Installation Manager to a new level of the Installation Manager product, download or install the new level of the IBM Installation Manager installation kit and mount it on your system. Then, resubmit GIN2INST sample job with the same values that you used to create the Installation Manager. This resubmission updates the Installation Manager binaries from the new installation kit.