|
To invoke inline backup, perform the following tasks:
- Include a step at the correct place in the job to execute a program
called ARCINBAK. The PARM parameter allows you to specify the options
TARGET and CC, from which you can target data set backups and concurrent
copy support, respectively. These TARGET and CC parameter values apply
to all backups in this job step.
- For each data set to be backed up, specify the name of the data
set to be processed by including a valid DD statement with a DDNAME
of BACKxxxx (where xxxx is 1–4 characters).
Note: - Only cataloged data sets and SMS-managed open VSAM data sets are
supported for inline backup. If volume and unit information is specified
on the DD statement, an uncataloged data set is assumed, and the data
set is not processed.
- ARCINBAK does not support data sets allocated with any of the
following three dynamic allocation options: XTIOT, UCB NOCAPTURE,
and DSAB above the line, except when the calling program supplies
an open DCB.
Any form of the data set name is acceptable to ARCINBAK.
Specification of a relative generation number for a GDG or a reference
to a DDNAME in a previous step is acceptable. You can also specify
a VSAM cluster, or data or index components, or both.
- A DD statement with a DDNAME of ARCPRINT can be optionally included
in the ARCINBAK program job step. This DD statement defines a SYSOUT
data set to contain messages about data sets for which a backup has
been attempted.
The possible messages are as follows:
BACKUP FOR (DSNAME) SUCCESSFUL
DDNAME (DDNAME) NOT BACKED UP, UNABLE TO GET ASSOCIATED JFCB
BACKUP FOR (DSNAME) FAILED, DATA SET NOT CATALOGED
BACKUP FOR (DSNAME) FAILED, RC = (RETURN CODE), REAS = (REASON CODE)
At the completion of the ARCINBAK module job step,
you will receive a return code as shown in Table 1
Table 1. ARCINBAK Return CodesCC= |
Explanation |
---|
CC=0 |
All backups were successful. |
CC=4 |
No DDNAMEs prefixed with BACK were found or
the JFCB associated with a DDNAME could not be found. |
CC=8 |
Backup of an uncataloged data set was attempted.
Uncataloged data sets are not supported by inline backup. |
CC=12 |
Backup of a data set failed. If the return code
equals:
- RC=0100
- DFSMShsm is
not active; request rejected.
- RC=0001-0099
- For message return codes and reason codes, see message ARCnnnnI
using the REAS field, where nnnn is the return code.
For
RC=0004, see message ARCnnnnI or ARCnnnnE where nnnn is
the reason code.
|
CC=16 |
Parameter error. |
CC=806 |
Link error. |
- You can specify the RETAINDAYS keyword with the ARCINBAK program.
RETAINDAYS specifies a number of days to retain a specific backup
copy of a data set. A single RETAINDAYS value applies to all of the
data sets that are backed up under this job step. RETAINDAYS specifies
a minimum number of days (0–50000) that DFSMShsm retains the
backup copy. If you specify 99999, the data set backup version never
expires. Any value greater than 50000 (and other than 99999) causes
failure. A retain days value of 0 indicates, that:
- The backup version might expire within the same day that it was
created if EXPIREBV processing takes place,
- The backup version is kept as an active copy before roll-off
occurs,
- The backup version is not managed as a retained copy.
- A DD statement with a DDNAME of ARCSNAP can be included in the
ARCINBAK program job step. This DD statement defines a SYSOUT data
set for the output from a SNAP macro. The following storage areas
are dumped to the SNAPDCB data set when the inline backup fails for
any reason:
- MWE storage can be dumped when an error occurs in issuing the
service call.
- A complete image of the task storage can be dumped when no DDNAMEs
or data sets are processed.
Figure 1 shows a job stream example of data sets that
can or cannot be backed up by ARCINBAK in a batch environment. In
this example, each data set backup is targeted to tape, and each data
set will be backed up using the specified concurrent copy and
RETAINDAYS options. For a description of the TARGET options,
see TARGET: Specifying the media target of the backup data set. For a description of the CC options, see CC: Tailoring concurrent copy backups for SMS and non-SMS data sets.
Figure 1. Example of Inline Backup Job Stream//JOBNAME JOB . . . ,USER=USERID,PASSWORD=USERPSWD
//STEP1 EXEC PGM=USERPGM
//SYSPRINT DD SYSOUT=A
//DSET1 DD DSN=USERID.N03.GDG(-1),DISP=OLD
//DSET2 DD DSN=USERID.N03.PSFB,DISP=OLD
//DSET3 DD DSN=USERID.N04.PSFB,DISP=OLD
//DSET4 DD DSN=USERID.N03.KSDS,DISP=OLD
/*
//STEP2 EXEC PGM=ARCINBAK,PARM=('RETAINDAYS(00365),
// TARGET(TAPE),CC=(PREFERRED,PHYSICALEND)')
//ARCPRINT DD SYSOUT=A
//ARCSNAP DD SYSOUT=A
//* ----------------------------------------------------------------
//* BACKUP OF GDG DATA SET SHOULD BE SUCCESSFUL.
//* ----------------------------------------------------------------
//BACK01 DD DSN=*.STEP1.DSET1,DISP=SHR
//* ----------------------------------------------------------------
//* BACKUP OF NON-VSAM DATA SET SHOULD BE SUCCESSFUL.
//* ----------------------------------------------------------------
//BACK02 DD DSN=*.STEP1.DSET2,DISP=SHR
//* ----------------------------------------------------------------
//* BACKUP OF VSAM DATA SET SHOULD BE SUCCESSFUL.
//* ----------------------------------------------------------------
//BACK03 DD DSN=*.STEP1.DSET4,DISP=SHR
//* ----------------------------------------------------------------
//* BACKUP OF GDG DATA SET SHOULD BE SUCCESSFUL.
//* ----------------------------------------------------------------
//BACK04 DD DSN=USERID.N01.GDG.G0001V00,DISP=SHR
//* ----------------------------------------------------------------
//* BACKUP OF NON-VSAM DATA SET SHOULD BE SUCCESSFUL.
//* ----------------------------------------------------------------
//BACK05 DD DSN=USERID.N01.PSFB,DISP=SHR
//* ----------------------------------------------------------------
//* BACKUP OF UNCATALOGED DATA SET SHOULD FAIL.
//* ----------------------------------------------------------------
//BACK06 DD DSN=USERID.N02.UNCAT,VOL=SER=VOL003,UNIT=3390,DISP=SHR
//* ----------------------------------------------------------------
//* BACKUP OF VSAM DATA SET SHOULD BE SUCCESSFUL.
//* ----------------------------------------------------------------
//BACK07 DD DSN=USERID.N01.KSDS,DISP=SHR
//* ----------------------------------------------------------------
//* BACKUP OF OPEN IN-USE VSAM DATA SET SHOULD FAIL.
//* ----------------------------------------------------------------
//BACK08 DD DSN=USERID.N02.KSDS,DISP=SHR
//* ----------------------------------------------------------------
//* BACKUP OF RACF PROTECTED NON-VSAM DATA SET
//* BY AN UNAUTHORIZED USER SHOULD FAIL.
//* ----------------------------------------------------------------
//BACK09 DD DSN=USERXX.N02.PSFB,DISP=SHR
//* ----------------------------------------------------------------
//* DDNAME PREFIX OTHER THAN BACK IS NOT PROCESSED.
//* ----------------------------------------------------------------
//BAK01 DD DSN=*.STEP1.DSET3,DISP=SHR
//* ----------------------------------------------------------------
//* DDNAME PREFIX OTHER THAN BACK IS NOT PROCESSED
//* ----------------------------------------------------------------
//BAK02 DD DSN=USERID.N02.PSFB,DISP=SHR
/*
The return code from processing the inline backup job stream example
of the ARCINBAK program is 12, and the resulting messages for each
DDNAME prefixed with BACK are described in Figure 2.
Figure 2. Example of Messages Resulting from Inline Backup Job StreamBACKUP FOR USERID.N03.GDG.G0001V00 SUCCESSFUL
BACKUP FOR USERID.N03.PSFB SUCCESSFUL
BACKUP FOR USERID.N03.KSDS SUCCESSFUL
BACKUP FOR USERID.N01.GDG.G0001V00 SUCCESSFUL
BACKUP FOR USERID.N01.PSFB SUCCESSFUL
BACKUP FOR USERID.N02.UNCAT FAILED, DATA SET NOT CATALOGED
BACKUP FOR USERID.N01.KSDS SUCCESSFUL
BACKUP FOR USERID.N02.KSDS FAILED, RC = 056, REAS = 016
BACKUP FOR USERXX.N02.PSFB FAILED, RC = 039, REAS = 008
|