Before you begin
Decide how 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 only
be 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
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.
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 writeable by the 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 ("binary files") and runtime data on z/OS.Files |
Admin or group mode |
User mode |
Binary files |
/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.
- Create a user ID and group to own the Installation Manager.
This 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
- Read access to UNIXPRIV profile SUPERUSER.FILESYS.CHANGEPERMS
The user ID that creates the Installation Manager becomes
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 becomes the "owning group" for
the Installation Manager.
You can use an existing user ID if
it meets these requirements.
If you installed the Installation
Manager installation kit with SMP/E, you can use the Installation
Manager sample job GIN2ADMN in SGINJCL to create this user ID and
group as well as to assign appropriate permissions.
Tip: If
you are creating a group-mode Installation Manager, consider putting
the following line in a
.profile script in the
home directory for each user ID that invokes the Installation Manager:
umask 002
This command ensures
that all files created in the Installation Manager runtime data and
installed products are group writable. Otherwise, you might have to
issue
chmod 775 commands against these directories
whenever you use a different user ID to invoke the group-mode Installation
Manager.
- If the Installation Manager binary files and runtime data
does not reside in existing read/write file systems, create file systems
for the data and mount the file systems read/write.
The
file systems should be owned by the user ID and group that creates
the Installation Manager and have permissions 755 for an admin or
user-mode Installation Manager or 775 for a group-mode Installation
Manager.
If you installed the Installation Manager installation
kit with SMP/E, you can use the Installation Manager sample job GIN2CFS
in SGINJCL to allocate and mount a file system to hold the binary
files and runtime data.
The Installation Manager creation process
creates the binary files and runtime data directories if they do not
already exist.
- Log in to the UNIX system
services shell using the user ID for the Installation Manager, and
change the directory to the location of the Installation Manager installation
kit.
cd /usr/lpp/InstallationManager/V1R5
- Run the installc, userinstc,
or groupinstc command from the installation kit
to create the Installation Manager.
- To create an Installation Manager in admin mode, issue the following
command from the shell:
installc -acceptLicense
-installationDirectory binaries_location
-dataLocation appdata_location
- To create an Installation Manager in user mode, issue the following
command from the shell:
userinstc -acceptLicense
-installationDirectory binaries_location
-dataLocation appdata_location
- To create an Installation Manager in group mode, issue the following
command from the shell:
groupinstc -acceptLicense
-installationDirectory binaries_location
-dataLocation appdata_location
You can omit the -installationDirectory and -dataLocation parameters
if you use the default locations.
If you used SMP/E to install
the Installation Manager installation kit, you can use sample job
GIN2INST in SGINJCL to create an Installation Manager.
What to do next
You can verify that the Installation Manager is correctly
installed by logging in to the
UNIX System Services
shell using the user ID that created the Installation Manager and
running the Installation Manager imcl command from the
eclipse/tools subdirectory
of the Installation Manager's binary files location. For example:
cd /InstallationManager/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 and then connect them to the owning group for the Installation
Manager using the TSO CONNECT command:
CONNECT user2 GROUP(IMGROUP)
To create an additional Installation Manager, follow the
steps in the procedure, selecting a new user ID and group (if appropriate)
and new binary files and runtime data locations. Do not share binary
files or runtime data locations between separate Installation Managers.
Correcting
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 binary files 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 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.
Upgrading
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, change
directory to the new level of the installation kit and reissue the
same installc, userinstc, or groupinstc command
that you used to create the Installation Manager. This action updates
the Installation Manager's binary files from the new installation
kit.