![]() |
![]() |
Task | Required Privilege Class |
---|---|
Start, halt, and restart the server | System or operator |
A region size of 256MB (REGION=256M) is recommended for starting the Tivoli Storage Manager server. However, this value can be decreased or increased based on server workload. To determine the optimum value for your installation, monitor server operation and set the region size according to the results.
If the specified region is too small, server performance can be significantly impacted, especially during periods of high server activity. For example, the operating system GETMAIN and FREEMAIN processing can have a major impact on the performance of transaction-oriented applications such as Tivoli Storage Manager. To eliminate or minimize GETMAIN and FREEMAIN calls, the server uses its own method for satisfying storage requests. The ability of the server to avoid calls to the GETMAIN and FREEMAIN procedures is highly dependent on adequate region size for the workload.
When increasing the region size, use 128MB increments until the desired performance is achieved, or until it is clear that the additional storage is yielding improved performance. Once this occurs, you can reduce the region size in small increments (for example, 32 MB), to determine the optimum region size for your workload. It is important that performance be monitored for a period of time and over periods of high activity.
If the desired performance is not achieved after adjusting the region size, consult the Tivoli Storage Manager documentation and Redbooks for performance-related options and suggestions.
A region size of 0M (REGION=0M) is not recommeded. Specifying 0M will result in poor server performance.
To start the server, edit and run the ANRSTART job from ASAMPLIB dataset.
The parameters you must update before running this job are the following:
The following figure is a sample ANRSTART job with the job statement parameters added.
This job starts the server as a batch job. When the startup completes, the system console displays the following message:
ANR0993I Tivoli Storage Manager server initialization complete.
This message is followed by the server prompt. The server is now up and running.
If the server 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 can be one of the following:
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 complete. Any in-progress transactions are rolled back when the server is restarted. 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: