Removeoperandlimit
The removeoperandlimit option specifies that the client removes the 20-operand limit.
If you specify the removeoperandlimit option with the incremental, selective, or archive commands, the 20-operand limit is not enforced and is restricted only by available resources or other operating system limits.
The removeoperandlimit option
can be useful if you generate scripts which can invoke the command-line
client with a large number of operands. For example, you can prescan
a directory tree looking for files to back up. As each eligible file
is discovered, it is added to the operand list of a selective command.
Later, this selective command is submitted by a
controlling script. In this case, specifying the removeoperandlimit option
removes the 20-operand limit.
Note:
- The removeoperandlimit option must be placed immediately after the incremental, selective, or archive command before any file specifications.
- This option does not accept a value. If this option is specified on a command, the 20-operand limit is removed.
- Because it adversely affects performance to allow the shell to expand wild cards, use the removeoperandlimit option in backup or archive operations in which wild cards are not used.
- The removeoperandlimit option is valid only on the incremental, selective, or archive commands in batch mode. It is not valid in the client options file (dsm.opt) or dsm.sys file.
Supported Clients
This option is valid for all UNIX and Linux clients.
Parameters
There are no parameters for this option.
Examples
- Command line:
- -removeoperandlimit