AUTODS console command
The AUTODS command is used to initiate solutions against data sets in a:
- Pool
- Storage group
- SMS pool
- Policy
- Application on a list of volumes
- Volume within a pool

In the command parameters, the POOL, GROUP, SUBPOOL, VOL, APPL, POLICY, and SOL keywords can include variables. Multiple variables can be used as long as they are separated by a comma.
AUTODS processes the data sets that are associated with the specified resource (pool, application, volume, and so on).
These data sets, or a subset of these data sets, compose the result group that is manipulated by the SET keywords of AUTODS RLST.
AUTODS requests cause collection to occur for all data sets in the indicated resource. For large resources, this collection could be CPU-intensive and time-intensive.
The following examples show how to use AUTODS keywords:
/-SVOS AUTODS,VOL=BAB200,SOLUTION=RLSESPAC
The following table describes valid keywords for the AUTODS command.
AUTODS command keywords
Keyword | Description |
|---|---|
APPL=(applName,applName,applName...) | Specifies one or more application names, name masks, or one or more variable names defined in the SMVARS member |
DATA=HIST | REAL | Indicates whether the AUTODS command should use data from the VTOC Scan master-collection data set or collect data set information in real time (optional). DATA=HIST indicates that the data to be run through the AUTODS solution should come from the VTOC Scan master collection data set. To avoid the overhead associated with scanning all data sets in a pool or on a volume, this parameter can be used when testing new AUTODS solutions. |
POOL=(pool,pool,pool...) GROUP=(group,group,group,...) SUBPOOL=(subpool,subpool,subpool...) POLICY=(policy,policy,policy...) | Specifies one or more pool, SMS storage group, BMC AMI Storage-defined SMS pool, or policy on which to perform the AUTODS command. Mask values and variables names defined in the SMVARS member can be used here. If a list of group, pool, policy, or subpool masks is specified, volumes within all of the listed resources are used in the AUTO command. Any volumes that exist in more than one specified resource are processed only once. If these parameters are used in conjunction with the VOL parameter, these parameters must specify a single pool, group, or subpool. The VOL parameter in conjunction with the POOL, GROUP, or SUBPOOL parameters is used only when performing multiple level automation (MLA). Specifying the VOL parameter in addition to one of the these parameters causes only the volumes specified in the VOL keyword to be associated with the pool rather than every volume in the pool, group, or subpool. In this situation variable names cannot be used. |
SOLUTION=(solution,solution,solution...) or SOL=(solution,solution,solution...) | Specifies names of one or more solution separated by commas or one or more variable names defined in the SMVARS member (optional). You can specify as many solution names as will fit on the command line. Any value, up to 8 characters, can be specified. Each volume is run against each solution in the list, regardless of the outcome of each individual solution. The order of the solutions does not matter. This value is used in the SOLUTION parameter on the SET statement in the AUTO function RLST member. This value associates the request with a particular SET statement in the AUTODS RLST member. If this keyword is not specified, each resource in the request is checked against all RLST SET statements and the first match is processed. You cannot edit this command input field. BMC Software recommends specifying a solution value for every request. This solution value should match a value specified in an AUTODS RLST SET statement. |
VOL=(volser,volser,volser...) | Specifies one or more volume serial numbers or one or more variable names defined in the SMVARS member. VOL can be specified by itself to initiate an AUTODS solution against a list of volumes or volume masks. VOL can be used with the POOL keyword to indicate a volume in a pool. This specification is for multilevel automation (MLA) usage, where the AUTODS solution is being initiated on multiple volumes in a pool, each on a separate AUTODS command. In this scenario, each request is associated with the pool. |
Related topic