Troubleshooting
Problem
Include/Exclude statements in dsm.opt don't seam to work
Cause
Conflicting Include/Exclude statements defined in a client option set get processed before the Include/Exclude statements defined in dsm.opt.
Resolving The Problem
Client Include/Exclude statements could be defined in the client dsm.opt file. The TSM client, when processing the dsm.opt file, reads the file from the bottom up, processing the Include/Exclude statements in the same order.
Include/Exclude statements could also be defined in a client option set on the TSM server. The Include/Exclude statements in the client option set will be processed in the order based on the sequence number defined for each statement.
The resultant Include/Exclude statements (combining both defined in the client dsm.opt, and the client option set) could be reviewed using the TSM client query: Q INCLEXCL issued from the client command line dsmc.
The output of the query, displays the Include/Exclude statements defined in the client option set first, and then those defined in the client dsm.opt.
The TSM client will process the Include/Exclude statements from TOP to BOTTOM as shown by the output of the query.
If an Include statement defined in the client dsm.opt conflicts with an Exclude statement defined in the client option set, the Exclude statement will be processed first and the Include statement will be ignored,
Note: the option "Override" in the client option set has no effect on the Include/Exclude processing and is ignored.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21251085