Data Links File Manager uses a DB2 instance to track files that are under its control. An instance-owning user is assigned when creating the instance. DB2 logs on with this user name to perform all Data Links File Manager functions.
Every DB2 instance has one instance-owning user that is assigned when the instance is created. DB2 logs on with this user name to perform all instance functions. One user name can be used for only one instance.
Each instance owner must have a unique home directory. All of the files necessary to run the instance are created in the home directory of the Data Links user. If the Data Links user name is removed from the system, you can lose files associated with the instance and lose access to data stored in this instance. It is recommended that you dedicate a Data Links user exclusively to run the Data Links instance.
The primary group of the Data Links user automatically becomes the system administration group for the instance and gains SYSADM authority over the instance. SYSADM is the highest level of administrative authority. Users with SYSADM authority can run utilities, issue database and database manager commands, and access the data in any table in any database within the database manager instance.
Each member of the primary group of the instance owner also gains this level of authority. To control access, you can assign the instance-owning user to a primary group that is reserved for instance administration. If you have a group that you want to make the system administration group for the instance, you can assign this group as the primary group when you create the instance-owning user. If you want to create a new group, enter a new name.
To separate SYSADM authority between instances, ensure that each instance-owning user uses a different primary group. If you choose to have a common SYSADM authority over multiple instances, you can use the same primary group for all the instance owners.
In a Network Information Services (NIS) environment, users and groups are remotely managed from an NIS server. Users and groups that you want to use with DB2 must exist on the NIS server prior to installation. The DB2 Setup wizard cannot create users or groups in an NIS environment.
To create a new user, click New user and provide the required information for the instance-owning user.
The User name you specify must be a valid DB2 user ID.
The Group name you type can be an existing group you have defined, or a new group that will be created if it does not exist. The group must be the primary group of the user.
Type the UID if you want a specific UID to be used. Otherwise, select Use default UID to use a system-generated UID.
Enter the GID if you are creating a new group and you want a specific GID to be used. Select Use default GID to use a system-generated or already-existing GID.
The Password you specify:
The Home directory is used to store all files used by the database instance. You cannot change the location of the directory once it is created. In a partitioned database environment, the instance directory is shared among all partitions that belong to the instance. Therefore, it must be created on an NFS mountable drive that all computers in the instance can access.
The directory can be any valid new or existing directory, although permission problems may arise if an existing directory is used.
Click Existing user to use an existing user ID.
Enter a valid existing user name in the User name field or click [...] to select from a list of existing names.
The DB2 Setup wizard will verify that the user name follows the naming rules and that no instance currently exists in the user's home directory.
The DB2 Setup wizard will check the user ID, home directory and password for validity. The user ID and password are stored in the operating system security files.