The syntax of the BACKUP command is as follows:
BACKUP RETPD=,EXPDT=,ACCESS=,RPT=CIA,CIAOPT=,NORESET,DEFER,NEWNAME=,NEWHLQ=
MEMBER=,SELTYPE=,MODE=,FAST=
Plus the following parameters honored for PRIMARY2 processing only:RETPD2=,EXPDT2= Parameters Honored with the PRIMARY2 Parameter of SET
Specify a one- to five-digit number indicating the number of days the selected data sets is to be retained in the CA Disk archives. The date calculated from this retention period cannot exceed the year 2155. For more information, see the section Year 2000 Considerations in the chapter "General Information" and the sysparm description of EXPDTUSEn in the Systems Guide.
If multiple BACKUP (and ARCHIVE) commands are entered, each can have a different RETPD2= or EXPDT2= value. You cannot specify both the RETPD2 and EXPDT2 parameters
Specify a date constant in any acceptable CA Disk format. For a list of valid dates, see the section Date Formats in the chapter "General Information." For more information, see the sysparm description of EXPDTUSEn in the Systems Guide.
CA Disk treats DSNINDEX Julian expiration dates 99000 (except as described in the next paragraph), 99365, 99366 and 99999 as never scratch dates. That is, data sets whose ARCHVOLS or DSNINDEX records use these dates as expiration dates will not be deleted automatically as expired by the CA Disk function IXMAINT. For more information, see the section Year 2000 Considerations in the chapter "General Information."
By default, CA Disk treats Julian expiration date 99000 as a never scratch date. But if you set sysparm UNCATDEL to a value of Y, CA Disk treats Julian expiration date 99000 as a catalog control date. That is, data sets backed up or archived with an expiration date of 99000 are deleted automatically by the CA Disk function IXMAINT when the data sets become uncatalogued. What this means is, if your catalog goes bad or someone uncatalogs some data sets, all backups and archives of these data sets will be deleted on the next IXMAINT run. Although you can use EXPDT2=99000 for any purpose, it was intended for use with archiving generation data groups (GDGs), the generations of which are managed by the catalog. For example, to archive all GDG generations, leaving the two most recent on disk, deleting generations that roll off of the catalog, specify sysparm UNCATDEL with a value of Y and:
SCAN REALVOLS SELECT CRITERIA=(GDGGEN,LE,- 2) ARCHIVE DISP=RECAT,EXPDT2=99000
If multiple BACKUP (and ARCHIVE) commands are entered, each can have a different RETPD2= or EXPDT2= value.
You cannot specify both the RETPD2 and EXPDT2 parameters.
By default, data sets are assigned a retention period equal to the value of sysparm RETRETPD. To override the default, specify a one- to five-digit number indicating the number of days the selected data sets are to be retained in the CA Disk archives. The date calculated from this retention period cannot exceed the year 2155. For more information, see the section Year 2000 Considerations in the chapter "General Information" and the sysparm description of EXPDTUSEn in the Systems Guide.
If multiple BACKUP (and ARCHIVE) commands are entered, each can have a different RETPD= or EXPDT= value. You cannot specify both the RETPD and EXPDT parameters.
By default, data sets are assigned a retention period equal to the value of sysparm RETRETPD. To override the default, specify a date constant in any acceptable CA Disk format. For a list of valid dates, see the section Date Formats in the chapter "General Information." For more information, see the sysparm description of EXPDTUSEn in the Systems Guide.
CA Disk treats DSNINDEX Julian expiration dates 99000 (except as described in the next paragraph), "99365", 99366 and 99999 as never scratch dates. That is, data sets whose ARCHVOLS or DSNINDEX records use these dates as expiration dates will not be deleted automatically as expired by the CA Disk function IXMAINT. For more information, see the section Year 2000 Considerations in the chapter "General Information."
By default, CA Disk treats Julian expiration date 99000 as a never scratch date. But if you set sysparm UNCATDEL to a value of Y, CA Disk treats Julian expiration date 99000 as a catalog control date. That is, data sets backed up or archived with an expiration date of 99000 are deleted automatically by the CA Disk function IXMAINT when the data sets become uncataloged. What this means is, if your catalog goes bad or someone uncatalogs some data sets, all backups and archives of these data sets are deleted on the next IXMAINT run. Although you can use EXPDT=99000 for any purpose, it was intended for use with archiving generation data groups (GDGs), the generations of which are managed by the catalog. For example, to archive all GDG generations, leaving the two most recent on disk, deleting generations that roll off of the catalog, specify sysparm UNCATDEL with a value of Y and:
SCAN REALVOLS SELECT CRITERIA=(GDGGEN,LE,- 2) ARCHIVE DISP=RECAT,EXPDT=99000
If multiple BACKUP (and ARCHIVE) commands are entered, each can have a different RETPD= or EXPDT= value.
You cannot specify both the RETPD and EXPDT parameters.
You can override the value of sysparm VSACCESS for this BACKUP command by specifying ACCESS= with a value of C for Control Interval (CI-level) access, or L for logical-level access.
This option allows the Cluster Internal Analysis (CIA) report to be produced as a by-product of live mode backup of VSAM clusters. The CIA report will not be produced during simulate runs. See the section CIARPT – Cluster Internal Analysis Report in the chapter "Reports" for further information.
If the RPT=CIA parameter is specified, this parameter can be used to specify which options are to be used. See the section CIAOPT = (CATLG, DETAIL, DUMP) in the chapter "Reports" for further information.
If a data set is backed up, normal processing resets (to zero) the change bit DS1IND02 in the format-1 DSCB. Specification of this parameter will cause processing to bypass updating the change bit. This feature would be useful for full-volume backup runs for off-site storage, where you do not want to prevent the data set from being processed by the next incremental backups.
An alternative data set name to be assigned to the DSNINDEX record for the backed up data set (a relative GDG name is also permitted). The backed up version is indexed under this name, which can be up to 44 characters in length.
This parameter can be specified on the BACKUP command to indicate that the request is to be queued for later processing. For an overview of this function, see Deferred Requests.
An alternative high level qualifier can be assigned to each data set selected for backup (a relative GDG name is also permitted). The backed up version is indexed in the FILES under this name, which can be up to 44 characters in length.
To back up a subset of a partitioned data set, this parameter is used to specify one or more member and/or pattern names to constitute the backed up version of the data set. A valid pattern for member level processing is any character followed by the '/' pattern character. This is the only valid pattern character available for this parameter. As an example:
MEMBER=(A/,GEN/)
For detailed information on the '/' pattern character, see Slash (/) Pattern in DSN= in the section Data Set Names and Parameters in the chapter "General Information."
A maximum of 25 entries is supported and is only valid when an immediate backup is being done (not a deferred backup).
For an overview of this function, see Member Level Backup.
This is for CA—Select customers only. See SELTYPE= for a description of this parameter.
This is for CA—Select customers only. See MODE= for a description of this parameter.
Specify YES or NO to indicate whether the data sets selected for processing should use the Fast Archive path.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|