When you are ready to have your data sets backed up, you can issue the ABACKUP command and specify the EXECUTE parameter. After successful data set verification processing, your data sets are backed up.
The following topics describe in more detail what occurs when you issue the ABACKUP command with the VERIFY or EXECUTE parameter.
The agname and EXECUTE | VERIFY parameters are required on the ABACKUP command.
For agname, specify the name of the aggregate group you defined earlier. See Defining an aggregate group.
The VERIFY parameter lists all input tape volumes that are required at the aggregate backup site if a subsequent ABACKUP EXECUTE command is submitted. It also performs verification processing of both migrated and nonmigrated data sets, detecting validation errors before data movement actually takes place.
For unittype in UNIT(unittype), specify the tape unit type to be allocated for the aggregate backup data, control, and instruction/activity log files.
If a user has comprehensive RACF command authority and issues the ABACKUP command with the MOVE parameter, no RACF checking of individual data sets is required.
The optional FILTEROUTPUTDATASET(dsname) parameter allows DFSMShsm to direct a fully-qualified list of data set names from the filtering criteria from the INCLUDE/EXCLUDE lists, as well as the names of ACCOMPANY, ACCOMPANYEXCLUDE, ALLOCATE, and ALLOCATEEXCLUDE data sets, to a separate output data set. If the user has restricted ABACKUP command authority, then that user must have a minimum of update authority to append to the existing RACF-protected filter output data set or allocation authority to create a new filter output data set. For dsname, substitute a data set name of up to 44 characters. FILTEROUTPUTDATASET can be abbreviated FODS.
When the FILTEROUTPUTDATASET parameter is specified along with the PROCESSONLY parameter, the filter output data set contains the data sets that pass the filtering criteria and also match the category designated in the PROCESSONLY parameter.
When you use the optional OPTIMIZE(option) parameter with an ABACKUP command it overrides the value specified by the SETSYS ABARSOPTIMIZE command. The OPTIMIZE parameter allows you to specify the performance level used by DFSMSdss during dump processing of level 0 DASD data sets. You can specify that DFSMSdss read one, two, or five tracks at time, or one cylinder at a time.
The optional PROCESSONLY parameter directs DFSMShsm to process only the specified categories. You can specify one or more of the categories L0, ML1, ML2, and USERTAPE. The categories can be specified in any order. Specification of all categories will be accepted and is equivalent to not specifying the PROCESSONLY parameter.
The optional, and mutually exclusive, STACK and NOSTACK parameters allow you to override the specified SETSYS ABARSTAPES value, or its default value of STACK. The STACK option causes ABACKUP to place the ABACKUP output files on a minimum number of tape cartridges. The STACK option only applies to output being directed to tape. Using the STACK option and attempting to direct the ABACKUP output files to DASD causes ABACKUP to fail.
The SKIP option causes DFSMShsm to skip data sets on volumes that are protected by PPRC or XRC. That is, these data sets are not backed up.
For more information about the commands listed in this topic, see DFSMShsm Storage Administration Reference.