Creating the user ID and directories for the server instance

Create the user ID for the IBM Storage Protect server instance and create the directories that the server instance needs for database and recovery logs.

1. Create the user ID that will own the server instance.
   You use this user ID when you create the server instance in a later step.

   

   Create a user ID and group that will be the owner of the server instance.

   1. The following commands can be run from an administrative user ID that will set up the user and group. Create the user ID and group in the home directory of the user.
      Restriction: In the user ID, only lowercase letters (a-z), numerals (0-9), and the underscore character ( _ ) can be used. The user ID and group name must comply with the following rules:

      • The length must be 8 characters or less.
      • The user ID and group name cannot start with ibm, sql, sys, or a numeral.
      • The user ID and group name cannot be user, admin, guest, public, local, or any SQL reserved word.

      For example, create user ID tsminst1 in group tsmsrvrs. The following examples show how to create this user ID and group using operating system commands.

      

      mkgroup id=1001 tsmsrvrs
      mkuser id=1002 pgrp=tsmsrvrs home=/home/tsminst1 tsminst1
      passwd tsminst1

      

      groupadd tsmsrvrs -g 1111
      useradd -d /home/tsminst1 -u 2222 -g 1111 -s /bin/bash tsminst1
      passwd tsminst1

      Restriction: IBM Db2 does not support direct operating system user authentication through LDAP.
   2. Log off, then log in to your system. Change to the user account that you just created. Use an interactive login program, such as telnet, so that you are prompted for the password and can change it if necessary.

   

   Create a user ID that will be the owner of the IBM Storage Protect server instance. A user ID can own more than one IBM Storage Protect server instance. Identify the user account that will own the server instance.

   When the server is started as a Windows service, this account is the one that the service will log on to. The user account must have administrative authority on the system. One user account can own more than one server instance.

   If you have multiple servers on one system and want to run each server with a different user account, create a new user account in this step.

   Create the user ID.

   Restriction: The user ID must comply with the following rule:

   In the user ID, only lowercase letters (a-z), numerals (0-9), and the underscore character ( _ ) can be used. The user ID must be 30 characters or less, and cannot start with ibm, sql, sys, or a numeral. The user ID and group name cannot be user, admin, guest, public, local, or any SQL reserved word.

   1. Use the following operating system command to create the user ID:

      net user user_ID * /add

      You are prompted to create and verify a password for the new user ID.
   2. Issue the following operating system commands to add the new user ID to the Administrators groups:

      net localgroup Administrators user_ID /add
      net localgroup DB2ADMNS user_ID /add

2. Create directories that the server requires.
   Create empty directories for each item in the table and ensure that the directories are owned by the new user ID you just created. Mount the associated storage to each directory for the active log, archive log, and database directories.

   Item	Example commands for creating the directories	Your directories
   The instance directory for the server, which is a directory that will contain files specifically for this server instance (the server options file and other server-specific files)	mkdir /tsminst1
   The database directories	mkdir /tsmdb001 mkdir /tsmdb002 mkdir /tsmdb003 mkdir /tsmdb004
   Active log directory	mkdir /tsmlog
   Archive log directory	mkdir /tsmarchlog
   Optional: Directory for the log mirror for the active log	mkdir /tsmlogmirror
   Optional: Secondary archive log directory (failover location for archive log)	mkdir /tsmarchlogfailover

   Create empty directories for each item in the table and ensure that the new user ID you just created has read/write permission to the directories. The database, archive log, and active log must reside on different physical volumes.

   Item	Example commands for creating the directories	Your directories
   The instance directory for the server, which is a directory that will contain files specifically for this server instance (the server options file and other server-specific files)	mkdir d:\tsm\server1
   The database directories	mkdir d:\tsm\db001 mkdir e:\tsm\db002 mkdir f:\tsm\db003 mkdir g:\tsm\db004
   Active log directory	mkdir h:\tsm\log
   Archive log directory	mkdir i:\tsm\archlog
   Optional: Directory for the log mirror for the active log	mkdir j:\tsm\logmirror
   Optional: Secondary archive log directory (failover location for archive log)	mkdir k:\tsm\archlogfailover

   When a server is initially created by using the DSMSERV FORMAT utility or the configuration wizard, a server database and recovery log are created. In addition, files are created to hold database information that is used by the database manager.

3. Log off the new user ID.