You can use defaults for processing options or you can tailor the processing options to meet specific needs. This chapter:
As a quick reference, this chapter includes instructions for the following
tasks:
During the installation of TSM, you are provided with a sample Preferences file called TSM Backup Preferences-Sample located in the system folder's preference folder. This file contains processing options that are categorized as follows:
By default, TSM will create a TSM Backup Preferences file in the Tivoli Storage Manager folder in the system's preferences folder. With the Setup Assistant, you can import the sample preferences file, or any other ADSM/TSM preferences file.
To view or modify the Preferences file, select the Edit menu> Preferences item on the backup-archive GUI. The graphical options editor updates the client configuration Preferences file, if any options have changed.
The graphical options editor groups the options in the following categories:
Options are processed in the following order (precedence):
You use communication options to specify how your client node communicates with a TSM server. TSM for Apple Macintosh uses the TCP/IP communication protocol.
Use the commmethod option to specify the communication protocol. For more information, see Commmethod. Ask your TSM administrator for assistance in setting your communication options.
To use the TCP/IP communication protocol, you must include the
tcpserveraddress option in your Preferences file. The other
TCP/IP options have default values which you can modify only if you want to
change the default value.
Option | Description | Page |
---|---|---|
tcpbuffsize | Specifies the size, in kilobytes, of the TSM internal TCP/IP communication buffer. | Tcpbuffsize |
tcpport | Specifies the TCP/IP port address for a TSM server. | Tcpport |
tcpserveraddress | Specifies the TCP/IP address for a TSM server. | Tcpserveraddress |
tcpwindowsize | Specifies the size, in kilobytes, of the TCP/IP sliding window for your client node. | Tcpwindowsize |
You can use the following option to specify the client node for which you
want to request backup-archive services.
Table 10. Server and Node Options
Option | Description | Page |
---|---|---|
nodename | Specifies one of the following:
| Nodename |
You can use the following options to control some aspects of backup and
archive processing.
Table 11. Backup and Archive Processing Options
Option | Description | Page |
---|---|---|
changingretries | Specifies the number of retries when attempting to back up or archive a file that is in use. | Changingretries |
compressalways | Whether to compress files or send them if compression causes them to grow. | Compressalways |
compression | Specifies whether to compress files before sending them to the TSM server. | Compression |
dirmc | Specifies the management class to use for directories. If not specified, TSM uses the management class with the longest retention period. | Dirmc |
domain | Specifies the volumes to include in your default client domain for an incremental backup. | Domain |
exclude | Excludes a file or group of files from backup services. Any file in your client domain that is not specifically excluded with this option is considered for backup. | Exclude Options |
exclude.archive | Excludes a file or group of files from archive services. | Exclude Options |
exclude.backup | Excludes a file or a group of files from backup services only. | Exclude Options |
exclude.dir | Excludes the specified directory, its files, and all its subdirectories and their files are excluded from backup services. | Exclude Options |
exclude.file | Excludes files, but not directories, that match a pattern. | Exclude Options |
exclude.file.backup | Excludes a file from normal backup services. | Exclude Options |
guitreeviewafterbackup | Specifies whether the client is returned to the Backup, Restore, Archive, or Retrieve window after a successful operation completes. | Guitreeviewafterbackup |
include | Includes files or management classes for backup or archive processing. | Include Options |
include.file | Includes a file for backup services, or assigns a management class to a file. | Include Options |
memoryefficientbackup | Specifies a memory-saving backup algorithm for incremental backups for use with the incremental command. | Memoryefficientbackup |
tapeprompt | Specifies whether you want TSM to wait for a tape required for a backup or archive to be mounted, or to prompt you for your choice. | Tapeprompt |
The following options relate to restore and retrieve processing.
Table 12. Restore and Retrieve Processing Options
Option | Description | Page |
---|---|---|
guitreeviewafterbackup | Specifies whether the client is returned to the Backup, Restore, Archive, or Retrieve window after a successful operation completes. | Guitreeviewafterbackup |
tapeprompt | Specifies whether you want TSM to wait for a tape required for a restore or retrieve to be mounted, or to prompt you for your choice. | Tapeprompt |
You can use the following options to regulate central scheduling.
TSM uses scheduling options only when the Scheduler is running.
Option | Description | Page |
---|---|---|
maxcmdretries | Specifies the maximum number of times the client scheduler attempts to process a scheduled command that fails. | Maxcmdretries |
postschedulecmd, postnschedulecmd | Specifies a command to process after running a schedule. | Postschedulecmd/Postnschedulecmd |
preschedulecmd, prenschedulecmd | Specifies a command to process before running a schedule. | Preschedulecmd/Prenschedulecmd |
queryschedperiod | Specifies the number of hours the client scheduler waits between unsuccessful attempts to contact the TSM server for scheduled work. | Queryschedperiod |
retryperiod | Specifies the number of minutes the client scheduler waits between attempts to process a scheduled command that fails or between unsuccessful attempts to report results to the server. | Retryperiod |
schedcompleteaction | Specifies an action to take after a schedule has been completed. | Schedcompleteaction |
schedlogname | Specifies the name of the file where schedule log information is stored. | Schedlogname |
schedlogretention | Specifies the number of days to keep log file entries in the schedule log, and whether to save pruned entries. | Schedlogretention |
You can use the following options to select different formats for date,
time, numbers, and different languages if you have the appropriate client
installed for that language.
Table 14. Format and Language Options
Option | Description | Page |
---|---|---|
dateformat | Specifies the format for displaying dates. | Dateformat |
language | Specifies the language used for messages. | Language |
numberformat | Specifies the format for displaying numbers. | Numberformat |
timeformat | Specifies the format for displaying times. | Timeformat |
The following options apply only when you use certain TSM commands.
Table 15. Command Processing Options
Option | Description | Page |
---|---|---|
guitreeviewafterbackup | Specifies whether the client is returned to the Backup, Restore, Archive, or Retrieve window after a successful operation completes. | Guitreeviewafterbackup |
matchallchar | Specifies the character to use as a match-all wildcard character. | Matchallchar |
matchonechar | Specifies the character to use as a match-one-character wildcard character. | Matchonechar |
quiet | Specifies that processing information does not display on your screen. This option can be overidden by the TSM server. | Quiet |
verbose | Specifies that processing information should display on your screen. The alternative is quiet. This option can be overridden by the TSM server. | Verbose |
These options control access to a TSM server.
Table 16. Authorization Options
Option | Description | Reference |
---|---|---|
password | A TSM password. | Password |
passwordaccess | How TSM handles a password if one is required for your workstation. | Passwordaccess |
passworddir | The directory in which you want TSM to store an automatically generated password for your client node. | Passworddir |
These options specify the name of the error log file and how TSM treats the
entries in the log file.
Table 17. Error Processing Options
Option | Description | Page |
---|---|---|
errorlogname | Specifies the path and name of the error log. | Errorlogname |
errorlogretention | Specifies the number of days to keep log file entries in the error log, and whether to save pruned entries. | Errorlogretention |
These options control how TSM processes transactions between the client and
server.
Table 18. Transaction Processing Option
Option | Description | Page |
---|---|---|
commrestartduration | Specifies the maximum number of minutes you want the TSM client to try to reconnect to a TSM server after a communication error occurs. | Commrestartduration |
commrestartinterval | Specifies the number of seconds you want the TSM client to wait between attempts to reconnect to a TSM server after a communication error occurs. | Commrestartinterval |
largecommbuffers | Specifies whether the client will use increased buffers to transfer large amounts of data between the client and the server. | Largecommbuffers |
resourceutilization | Specifies the number of sessions opened between the TSM server and client during processing. | Resourceutilization |
This section describes how to set options in your Preferences file.
To view or modify the Preferences file, select the Edit menu> Preferences item on the backup-archive GUI. The graphical options editor updates the client configuration Preferences file, if any options have changed.
Use SimpleText or some other Macintosh text editor to tailor the Preferences file.
To set an option in your Preferences file, enter the option name, followed by one or more blank spaces, followed by the option value. For example:
compression yes nodename client_a
Some options consist of only the option name, such as verbose and quiet. You can enter the entire option name, or its abbreviation. For example, you can specify the verbose option as either of the following:
verbose ve
Follow these additional rules when entering options in your Preferences file:
domain "La Pomme" "Macintosh HD"
If you update the Preferences file while a GUI session is active, you must restart the session to pick up the changes.
Some tasks require changes to the Preferences file. For example, suppose you want to back up your files to one server and archive them to another. Or, suppose you want to retrieve files to a different workstation. Instead of editing your Preferences file each time you want to connect to a different server or use a different workstation, you can create multiple Preferences files. Depending on what you want to do, you can launch TSM with a different Preferences file that suits your needs.
Suppose you have two servers named Alpha and Bravo. Simply create two Preferences files named, for example, Prefs Alpha and Prefs Bravo. When you want to connect to Bravo, locate Prefs Bravo on your desktop and drop it onto the TSM icon. TSM starts using all options specified in Prefs Bravo, including the server address.
Note: | Remember to make duplicates of your original Preferences file and modify the duplicates. Always keep the original TSM Backup Preferences-Sample intact. |
The following sections contain detailed information about each of the TSM processing options. These options are arranged in alphabetical order. Information for each option includes:
Note: | For options with a yes parameter, acceptable alternatives are 1, true, and on. For options with a no parameter, acceptable alternatives are 0, false, and off. |
The changingretries option specifies how many additional times you want the TSM client program to attempt to back up or archive a file that is in use.
This option is used only when serialization, an attribute in a management class copy group, is shared static or shared dynamic.
With shared static serialization, if a file is in use during the first backup or archive attempt, the operation is attempted again the number of times you specified. If the file is in use during each attempt, the operation does not complete.
With shared dynamic serialization, if a file is in use during the first backup or archive attempt, the operation is attempted again the number of times you specified. The backup or archive operation occurs during the last attempt whether the file is in use or not.
Note: | This option can also be defined on the server. |
Syntax
.-----------------. V | >>-CHAngingretries----numberretries--+-------------------------><
Parameters
Examples
The commmethod option specifies the communication method you use to provide connectivity for client-server communication.
Syntax
>>-COMMMethod--- TCPip-----------------------------------------><
Parameters
Examples
The commrestartduration option specifies the maximum number of minutes you want the client to spend in an attempt to reconnect with a server after a communication error occurs.
Note: | When a schedule is running, the connection and schedule fail if a communication failure occurs and the client cannot reconnect with the server before the startup window for the schedule ends. |
You can use the commrestartduration option and the commrestartinterval in busy or unstable network environments to decrease connection failures.
Syntax
>>-COMMRESTARTDuration- minutes--------------------------------><
Parameters
Examples
The commrestartinterval option specifies the number of seconds you want the client to wait between attempts to reconnect with a server after a communication error occurs.
Note: | This option is used only when commrestartduration is set to a value greater than zero. |
You can use the commrestartduration option and the commrestartinterval in busy or unstable network environments to decrease connection failures.
Syntax
>>-COMMRESTARTInterval- seconds--------------------------------><
Parameters
Examples
The compressalways option specifies whether to continue compressing an object if it grows during compression, or resend the object, uncompressed. This option is used with the compression option.
Note: | This option can also be defined on the server. |
Syntax
.-Yes--. >>-COMPRESSAlways-+------+------------------------------------->< '-No---'
Parameters
Examples
The compression option compresses files before you send them to the server. Compressing your files reduces data storage that is required to store backup versions and archive copies of your files. It can, however, affect TSM throughput. A fast processor on a slow network connection benefits from compression, but a slow processor on a fast network connection does not.
If compressalways yes (the default) is specified, files continue compression even if the file size increases. To stop compression if the file size grows, and resend the file, uncompressed, specify compressalways No.
This option controls compression only if your administrator specifies that your client node determines the selection.
Note: | This option can also be defined on the server. |
Syntax
.-No--. >>-COMPRESSIon-+-----+----------------------------------------->< '-Yes-'
Parameters
Examples
The dateformat option selects the format you want to use to display dates.
Note: | When the date format is changed and the schedlogretention option is used to prune the schedule log, all entries in the schedule log with a different date format are removed when the log is pruned. When the date format is changed and the errorlogretention option is used to prune the error log, then all entries in the error log with a different date are removed when the log is pruned. When changing the date format, copy the schedule log and error log if you wish to preserve log entries that contain a different date format. |
Syntax
>>-DATEformat- format_number-----------------------------------><
Parameters
Examples
The dirmc option specifies the management class you want to use for directories. If you do not specify this option to associate a management class with directories, the client program uses the management class in the active policy set of your policy domain with the longest retention period. Select a management class for individual directories that retains directories at least as long as it retains the files associated with them.
The dirmc option specifies the management class of directories being backed up, and does not effect archived directories. Archived directories are always bound to the default management class.
Note: | This option can also be defined on the server. |
Syntax
>>-DIRMc- mgmtclassname----------------------------------------><
Parameters
Examples
The domain option specifies the volumes that you want to include for incremental backup in your client domain. This option can also be defined on the server.
When used in your Preferences file , the domain option defines your default client domain. TSM uses your default client domain when your administrator defines a schedule to run an incremental backup for you, but does not specify which volumes to process.
If you do not use the domain option to specify volumes in your client options file, the all-local parameter default is used.
Note: | The Linux and OS/390 UNIX clients are not enabled for automounter support. |
Syntax
.- ----------------. V .-all-local--. | >>-DOMain-----+------------+--+-------------------------------->< '-domain-----'
Parameters
A volume name must be enclosed in quotes if it includes any spaces.
Examples
The errorlogname option specifies the fully-qualified path and file name of the file where you want to store information about errors that occur during processing.
Syntax
>>-ERRORLOGName- filespec--------------------------------------><
Parameters
The default file name is TSM Error Log; it is placed in your TSM application folder.
Examples
The errorlogretention option specifies how many days to maintain error log entries before pruning, and whether to save the pruned entries. The error log is pruned when the first error is written to the log after a TSM session is started. If the only session you run is the client scheduler, and you run it twenty-four hours a day, the error log might not be pruned according to your expectations. Stop the session and start it again to prune the error log when the next error is written.
Syntax
.-N----. .-D--. >>-ERRORLOGRetention--+------+---+----+------------------------>< '-days-' '-S--'
Parameters
The pruned entries are copied from the error log to TSM Error Pruned Log.
Examples
The exclude options exclude objects from backup, or archive services. For example, you might want to exclude all temporary files, any local caches of network files, all files that contain compiled object code that you can easily reproduce using other methods, or your operating system files.
Exclude any system files that could corrupt the operating system when recovered. The client directory where TSM is stored should be excluded, also.
Note: | If you change your include-exclude list so that a previously included file is now excluded, any pre-existing backup versions of that file become inactive the next time an incremental backup is run. |
Use wildcard characters to exclude a broad range of files. See "Including and Excluding Groups of Files" for a list of wildcard characters that you can use. Then, if necessary, use the include option to make exceptions.
Syntax
.- -----------------. V | >>----options pattern--+---------------------------------------><
If a matching directory is found, that directory, its files, and all its subdirectories and their files are excluded from backup services. When you exclude a directory, you can still back up specific files within that directory, using selective backup.
The exclude.dir option works only if the excluded directory is a subdirectory.
Parameters
If the pattern begins with a single or double quote or contains any embedded blanks or equal signs, you must surround the value in either single (') or double (") quotation marks. The opening and closing quotation marks must be the same type of quotation marks.
You cannot use the match-all character (or any wildcard character) when specifying the high-level qualifier of an object, only use it for the low-level qualifier.
Examples
exclude "...:Desktop DB" exclude ":Norton FileSaver Data" exclude.archive "...:Desktop DF"
The guitreeviewafterbackup option specifies whether the client returns to the Backup, Restore, Archive, or Retrieve window after a successful operation completes.
Syntax
.-No--. >>-GUITREEViewafterbackup-+-----+------------------------------>< '-Yes-'
Parameters
Examples
The include options specify one of the following:
If you do not assign a specific management class to objects, the default management class in the active policy set of your policy domain is used.
Note: | You cannot use the include option to override an exclude.dir option. |
See Chapter 7, "Creating an Include-Exclude List" for more information.
Syntax
.- ------------------------------------. V | >>----options pattern-+----------------+--+-------------------->< '- mgmtclassname-'
Parameters
If the pattern begins with a single or double quote or contains any embedded blanks or equal signs, you must surround the value in either single (') or double (") quotation marks. The opening and closing quotation marks must be the same type of quotation marks.
Examples
include "...:Data:Test:Test*" include "...:System:...:*" mgmtcls1 include "...:*" managall
The language option specifies the national language in which to present client messages.
You can use American English (AMENG) with all clients. Currently, you can use American English (AMENG) only.
Syntax
>>-LANGuage- language------------------------------------------><
Parameters
Examples
The largecommbuffers option specifies whether the client uses increased buffers to transfer large amounts of data between the client and the server. You can disable this option when your machine is running low on memory.
Syntax
.-No--. >>-LARGECOMmbuffers-+-----+------------------------------------>< '-Yes-'
Parameters
Examples
The matchallchar option specifies the character to use as a match-all wildcard character. For example, File* matches File1, FileA1, and File. Place this option in the Preferences file before any include or exclude statements.
Syntax
>>-MATCHAllchar character--------------------------------------><
Parameters
Examples
The matchonechar option specifies the character to use as a match-one wildcard character. For example, File? matches File1, but it does not match File or File10. Place this option in the Preferences file before any include or exclude statements.
Syntax
>>-MATCHOnechar character--------------------------------------><
Parameters
Examples
The maxcmdretries option specifies the maximum number of times the client scheduler (on your workstation) attempts to process a scheduled command that fails. The command retry starts only if the client scheduler has not yet backed up a file, never connected to the server, or failed before backing up a file. This option is used only when the scheduler is running.
Your administrator can also set this option. If your administrator specifies a value for this option, that value overrides what you specify in the Preferences file after your client node successfully contacts the server.
Note: | This option can also be defined on the server. |
Syntax
>>-MAXCMDRetries- maxcmdretries--------------------------------><
Parameters
Examples
The memoryefficientbackup option specifies a memory conserving algorithm for processing incremental backups, that backs up one directory at a time, using less memory. Use this option when your machine is memory constrained.
Note: | This option can also be defined on the server. |
Syntax
.-Yes--. >>-MEMORYEFficientbackup-+------+------------------------------>< '-No---'
Parameters
Examples
The nodename option identifies your workstation to the server. You can use different node names to identify multiple systems on your workstation.
You can also use the nodename option if you want to restore or retrieve files from the server while you are working from a different workstation. When you use the nodename option, you are prompted for the TSM password assigned to the node you specify, if a password is required.
If you do not specify this option in the Preferences file, TSM prompts you for the node name when it starts.
Syntax
>>-NODename- nodename------------------------------------------><
Parameters
Examples
The numberformat option specifies the format you want to use to display numbers.
Syntax
>>-NUMberformat- number----------------------------------------><
Parameters
Examples
The password option specifies a TSM password. If this option is not used and your administrator has set authentication to On, you are prompted for a password when you start a TSM session.
Note: | If you are prompted for a password, it is not displayed as you enter it. However, if you use the password option, your password is displayed when you enter it. |
The password option is ignored when the passwordaccess option is set to generate.
Syntax
>>-PASsword- password------------------------------------------><
Parameters
Examples
The passwordaccess option specifies whether you want your TSM password generated automatically, or set as a user prompt. A password is required for your client node only when your administrator enables the authentication feature. Check with your administrator to verify that a password is required for your client node.
If a password is required, you can choose to:
Use the passworddir option in your Preferences file to specify the directory location in which to store the encrypted password file. The default directory location depends on how the client was installed.
When the passwordaccess option is set to generate and you specify the password option, the password option is ignored.
Syntax
.-prompt---. >>-PASSWORDAccess-+----------+--------------------------------->< '-generate-'
Parameters
A password prompt displays when registering a workstation with a server using open registration, or if your password was changed manually by the administrator.
Examples
The passworddir option forces the directory location in which to store an encrypted password file. The default directory location depends upon how the client was installed.
Syntax
>>-PASSWORDDIR- directoryname----------------------------------><
Parameters
Examples
The postschedulecmd option specifies a command that the client program processes after it runs a schedule. The client program waits for the command to complete before it continues with other processing.
If you do not want to wait, specify postnschedulecmd.
Note: | The postschedulecmd option (and the postnschedulecmd option) can be defined on the server. |
Syntax
>>-+-POSTSchedulecmd--+--- "cmdstring"------------------------->< '-POSTNschedulecmd-'
Parameters
Use a blank, or null string for cmdstring if you want to prevent any commands from running that the administrator uses for postschedulecmd or preschedulecmd. If you specify a blank, or null string on either option, it prevents the administrator from using a command on both options.
If your administrator uses a blank, or null string on the postschedulecmd option, you cannot run a post-schedule command.
If the command string contains blanks, enclose it in double quotes. If you have double quotes within the command string, use single quotes to enclose them.
The command string should specify an AppleScript to launch. If it is only a file name, such as "Database Script", the client program searches for this file in the Scripts folder inside the TSM folder. Otherwise, the command string should contain the full path of the file, such as:
"La Pomme:Scripting:Database Script"
Examples
The command string is a valid command for restarting your database.
The preschedulecmd option specifies a command that the client program processes before it runs a schedule. The client program waits for the command to complete before it starts the schedule.
If you do not want it to wait, specify prenschedulecmd.
Note: | The preschedulecmd option (and the prenschedulecmd option) can also be defined on the server. |
Syntax
>>-+-PRESchedulecmd--+--- "cmdstring"-------------------------->< '-PRENSchedulecmd-'
Parameters
Use a blank, or null string for cmdstring if you want to prevent any commands from running that the administrator uses for postschedulecmd and preschedulecmd. If you specify a blank, or null string on either option, it prevents the administrator from using a command on both options.
If your administrator uses a blank, or null string on the preschedulecmd option, you cannot run a pre-schedule command.
If the command string contains blanks, enclose it in double quotes. If you placed double quotes within the command string, use single quotes to enclose them.
The command string should specify an AppleScript to launch. If it is only a file name, such as "Database Script", the client program searches for this file in the Scripts folder inside the TSM folder. Otherwise, the command string should contain the full path of the file, such as:
"La Pomme:Scripting:Database Script"
Examples
The command string is a valid command for quiescing your database.
The queryschedperiod option specifies the number of hours you want the client scheduler to wait between attempts to contact the server for scheduled work. This option applies only when you set the schedmode option to polling. This option is used only when the scheduler is running.
Your administrator can also set this option. If your administrator specifies a value for this option, that value overrides the value set in your Preferences file after your client node successfully contacts the server.
Note: | This option can also be defined on the server. |
Syntax
>>-QUERYSCHedperiod- hours-------------------------------------><
Parameters
Examples
The quiet option prevents messages from displaying on your screen during processing.
When you use the quiet option, some error information still displays on your screen, and messages are written to log files. If you do not specify quiet, the default option, verbose is used.
Note: | Quiet can also be defined on the server and overrides the client setting. |
Syntax
>>-QUIET-------------------------------------------------------><
Examples
The resourceutilization option regulates the level of resources the TSM server and client can use during processing.
When a backup or archive operation is requested, the TSM client may use more than one session to the TSM server. The default is to use a maximum of two sessions; one to query the server, and one to send file data. The client is restricted to a single server session when a resourceutilization setting of 1 is specified..
A TSM client can be permitted to use more than the default number of sessions when connecting to a TSM server that is Version 3.7 or higher. For example, resourceutilization=10 permits up to eight sessions with the server. Multiple sessions may be used for querying the server and sending file data.
The following factors may affect the throughput of multiple sessions:
You should also consider potentially undesirable aspects of running multiple sessions, such as the following:
Note: | This option can also be defined on the server. |
Syntax
>>-RESOURceutilization- number---------------------------------><
Parameters
Examples
The retryperiod option specifies the number of minutes the client scheduler waits between attempts to process a scheduled command that fails, or between unsuccessful attempts to report results to the server. This option is used only when the scheduler is running.
Your administrator can also set this option. If your administrator specifies a value for this option, that value overrides the value specified in your Preferences file after your client node successfully contacts the server.
Note: | This option can also be defined on the server. |
Syntax
>>-RETRYPeriod- minutes----------------------------------------><
Parameters
Examples
The schedcompleteaction option specifies an action to take when a schedule completes. This option is used only when the scheduler is running.
Syntax
>>-SCHEDCOMpleteaction----+- Quit-----+------------------------>< '- SHUTdown-'
Parameters
Examples
The schedlogname option specifies the path and file name where you want to store schedule log information. This option applies when the scheduler is running.
Syntax
>>-SCHEDLOGName- filespec--------------------------------------><
Parameters
If you specify a file name only, the file is stored in your default folder. The default is the TSM application folder and a file name of TSM Schedule Log.
Examples
schedlogn "SupDrive:David Sched Log"
The schedlogretention option specifies the number of days to keep entries in the schedule log, and whether to save the pruned entries. The schedule log is pruned after a scheduled event completes.
Syntax
.-N----. .-D--. >>-SCHEDLOGRetention----+------+---+----+---------------------->< '-days-' '-S--'
Parameters
TSM copies the entries pruned from the log to TSM Sched Pruned Log.
Examples
The tapeprompt option specifies whether you want to wait for a tape to mount if it is required for a backup, archive, restore, or retrieve process, or to be prompted for a choice.
Tape prompting does not occur during a scheduled operation regardless of the setting for the tapeprompt option.
Note: | This option can also be defined on the server. |
Syntax
.-No--. >>-TAPEPrompt-+-----+------------------------------------------>< '-Yes-'
Parameters
Examples
The tcpbuffsize option specifies the size of the internal TCP/IP communication buffer. Although it uses more memory, a larger buffer can improve communication performance.
Syntax
>>-TCPBuffsize- size-------------------------------------------><
Parameters
Depending on the operating system communication settings, your system might not accept all values in the range of one through 512.
Examples
The tcpport option specifies a TCP/IP port address for a server. You can obtain this address from your administrator. This option is required in your Preferences file.
Syntax
>>-TCPPort- port_address---------------------------------------><
Parameters
Examples
The tcpserveraddress option specifies the TCP/IP address for a server. You can obtain this port address from your administrator. This option is required in your Preferences file.
Syntax
>>-TCPServeraddress- server_address----------------------------><
Parameters
Examples
The tcpwindowsize option specifies the amount of data in kilobytes that is buffered when receiving data on a TCP/IP connection. To improve backup or archive performance, increase the tcpwindowsize on the TSM server. To improve restore or retrieve performance, increase the tcpwindowsize on the TSM client. For more information about improving communication performance, see the ADSM Performance Tuning Guide at URL: http://www.tivoli.com/storage.
Syntax
>>-TCPWindowsize- window_size----------------------------------><
Parameters
The range of values is one through 128; the default is 16.
Note: | Depending on the operating system communication settings, your system might not accept all values in the range of values. |
Examples
The timeformat option specifies the format in which you want system time displayed.
Syntax
>>-TIMEformat- format_number-----------------------------------><
Parameters
Examples
The verbose option specifies that you want processing information to display on your screen. This is the default.
The information appears on your screen in the Scheduler Status window. This option only applies when you are running the Scheduler and TSM is performing scheduled work.
Note: | This option can also be defined on the server and overrides the client setting. |
Syntax
>>-VErbose-----------------------------------------------------><
Parameters
There are no parameters for this option.
Examples