Task | Required Privilege Class |
---|---|
Start, halt, and restart the server | System or operator |
The following events occur when the TSM server is started:
You can start the server in console mode, in background mode, or specify other modes as part of the dsmserv command.
To start the server from the console, complete the following steps:
Enter:
cd /opt/adsmserv/bin
Enter:
./dsmserv
TSM displays the following information when the server is started:
If TSM detects an invalid system date and time, the server is disabled, and expiration, migration, reclamation, and volume history deletion operations are not allowed. An error message (ANR0110E) is displayed and you may either change the system date if it is in error, or issue the ACCEPT DATE command to force the server to accept the current system date as valid. After the system date is resolved, you must issue the ENABLE SESSIONS command to re-enable the server for client sessions.
The date and time check occur when the server is started and once each hour thereafter. An invalid date is one that is:
You may choose to run the server in the background. When the server runs in the background, you control the server through your administrative client.
Attention: | Before you run the server in the background, ensure the following
conditions exist:
If you do not follow these steps, you cannot control the server. When this occurs, you can only stop the server by canceling the process, using the process number displayed at startup. You may not be able to take down the server cleanly without this process number. |
To start the server running in the background, enter the following:
nohup dsmserv -quiet &
You can check your directory for the output created in the nohup.out file to determine if the server has started. This file can grow considerably over time.
The following TSM command options specify how you can start the server in other modes as part of the dsmserv command. For example:
dsmserv option
Where option can be any one of the following:
Note: | Before issuing this command, you must have an administrative client registered and authorized with system authority. The administrative client must be started. Otherwise, the server will run in the quiet mode and you will not be able to access the server. |
If you want to run the TSM server from a directory other than the default directory or to run multiple servers, you may have to define environment variables.
An environment variable describes the operating environment of a process, such as the home directory or the terminal in use. It provides the path that the server requires to find and create files.
For example, to define the DSMSERV_DIR environment variable to point to the directory so that the server can find various files, such as dsmreg.lic or the message file (dsmameng.txt) enter:
export DSMSERV_DIR=/opt/adsmserv/bin
You can also define an environment variable to point to the server options file. For example, to define the DSMSERV_CONFIG environment variable to point to the server options file, enter:
export DSMSERV_CONFIG=/users/myserver/filename.opt
where filename is the name you assigned your server options file (dsmserv.opt).
To have multiple servers running on a single machine, issue the DSMSERV FORMAT command from different directories to create multiple pairs of recovery log and database files. Do not attempt to install the server executable files in more than one directory.
Note: | Each TSM server requires approximately 100 kernel semaphores. If you wish to run more than one TSM server, you may need to increase the number of semaphores in the kernel configuration parameter semmns. You may increase this parameter by using System Administration Manager (SAM), and selecting the Kernel Configuration option. Refer to Quick Start for more information. |
The following example shows how you can set up an additional TSM server:
cd /users/myserver
cp /opt/adsmserv/bin/dsmserv.opt dsmserv.opt
Note: | Ensure that the TCPPORT option in the dsmserv.opt file is unique from all other TSM servers. |
DSMSERV_DIR=/opt/adsmserv/bin export DSMSERV_DIR
DSMSERV_CONFIG=/users/myserver/dsmserv.opt export DSMSERV_CONFIG
/opt/adsmserv/bin/dsmfmt -m -db dbvol2 5 /opt/adsmserv/bin/dsmfmt -m -log logvol2 9
/opt/adsmserv/bin/dsmserv format 1 logvol2 1 dbvol2
dsmserv
Notes:
dsmserv -options filename
where filename is the name of the server options file.
You can halt the server without warning if an unplanned operating system problem requires the server to be stopped.
When you halt the server, all processes are abruptly stopped and client sessions are canceled, even if they are not completed. Any in-progress transactions are rolled back when the server is restarted. When the server is halted, administrator activity is not possible.
If possible, halt the server only after current administrative and client node sessions have completed or canceled. To shut down the server without severely impacting administrative and client node activity with the server, you must:
Note: | The QUIESCE option on the HALT command is recommended only if you plan to do a database dump by using the DSMSERV DUMPDB command immediately after halting. Because TSM supports online database backup (BACKUP DB command), the DSMSERV DUMPDB command should be rarely, if ever, needed. |
To start the server after it has been halted, follow the instructions in Starting the Server.
When you restart the server after it has been halted, TSM rolls back any operations that had been in process to ensure that the database remains in a consistent state.