Use the DSMSERV FORMAT utility to initialize a server instance. No other server activity is allowed while initializing the database and recovery log.
After you set up server communications, you are ready to initialize the database. Ensure that you log in by using the instance user ID. Do not place the directories on file systems that might run out of space. If certain directories (for example, the archive log) become unavailable or full, the server stops.
For optimal performance and to facilitate I/O, specify at least two equally sized containers or Logical Unit Numbers (LUNs) for the database. See IBM Tivoli Storage Manager Optimizing Performance for more information about the configuration of directories for the database. In addition, each active log and archive log should have its own container or LUN.
Important: The installation program creates
a set of registry keys. One of these keys points to the directory
where a default server, named SERVER1, is created. To install an additional
server, create a directory and use the DSMSERV FORMAT utility,
with the -k parameter, from that directory. That
directory becomes the location of the server. The registry tracks
the installed servers.Initializing a server instance
dsmserv -k server2 format dbdir=d:\tsm\db001 activelogsize=8192
activelogdirectory=e:\tsm\activelog archlogdirectory=f:\tsm\archlog
archfailoverlogdirectory=g:\tsm\archfaillog mirrorlogdirectory=h:\tsm\mirrorlog