TSM processes administrator commands in the foreground or in the background. When administrative commands are processed, you receive a message indicating:
TSM sends a confirmation message when commands are issued that affect the availability of the server or data managed by the server. TSM does not send a confirmation message if the command is issued from the server console or from an administrative client with the NOCONFIRM option specified.
TSM formats the output processed from commands according to your screen or window width. If the width of your screen or window is not wide enough to display the output horizontally, TSM arranges and displays the information vertically.
Foreground processing specifies that each command issued must complete before another command is issued. Commands processed in the foreground can be canceled from the server console or another administrative client session.
When you issue a QUERY command from the administrative client, multiple screens of output may be generated. If this occurs and additional output is not needed, you can cancel the display of output to the client workstation. While canceling does not end the processing of the command, it ends any further display of command output.
For some commands, you can specify whether to wait for TSM to complete
processing the command in the foreground before you issue other
commands. By including the WAIT parameter, you can specify whether TSM
processes the following commands in the foreground:
|
|
Background processing specifies that you can enter commands while the server is processing a previously issued command. When you enter a command that creates a background process, TSM submits a request to the server to perform the task identified in the command. Each background process is assigned a process number. Use the CANCEL PROCESS command to cancel commands that generate background processes.
Use the QUERY PROCESS command to obtain the status and process number of a background process. If a background process is active when you cancel it, the server stops the process. Any changes that are uncommitted are rolled back, however, changes that are committed are not rolled back.
The following is a list of commands that can generate background
processes:
|
|