ADRDSSU Introduction
ADRDSSU Introduction
ADRDSSU Introduction
Introduction
I. Introduction
1.1 Purpose
This is a short-term course that discusses the usage about ADRDSSU. It aims to equip
participants with techniques they need to learn the ways they can use ADRDSSU utility
to dump, restore and copy-with-rename the datasets.
1.2 Objectives
1.3 Outline
I. Introduction
I. Overview
2.1 What is ADRDSSU?
2.2 Usage of ADRDSSU
2.3 Types of Operation
2.4 Invoke ADRDSSU with JCL
2
ADRDSSU Introduction
II. Overview
Copy and move datasets between volumes of like and unlike device types
Convert data sets and volumes to and from storage management subsystem
(SMS) management
Logical Processing:
o Treat each dataset and its associated information as a logical entity,
and processes an entire dataset before beginning the next one.
o Specify the DATASET keyword with the COPY command. A data set
copy is always a logical operation, regardless of how or whether you
specify input volumes.
o Specify the DATASET keyword with the DUMP command, and either
no input volume is specified, or LOGINDDNAME, LOGINDYNAM, or
STORGRP is used to specify input volumes.
3
ADRDSSU Introduction
Physical processing:
o Only target devices with track sizes equal to those of the source
device are supported.
o Operates on volumes, ranges of tracks, or data sets. For data sets, it
relies only on volume information (in the VTOC and VVDS) for data
set selection, and processes only that part of a data set residing on
the specified input volumes.
You can use the JCL statements to invoke ADRDSSU and to define the
datasets used and created by it.
The JCL defines the ADRDSSU commands that specify and control tasks.
The JCL statements you need for most jobs are described below:
//STEPLIB DD
o If ADRDSSU is not in a library known to the system, the //STEPLIB
DD statement defines the library containing the ADRDSSU program
//SYSPRINT DD
o Defines a sequential message dataset.
//SYSIN DD
o Defines a command dataset containing your ADRDSSU commands. It
usually resides in the input stream.
o It can be defined as a blocked or unblocked sequential data set or as
a member of a partitioned data set. Records must be fixed format,
LRECL=80.
input DD
o Defines the input dataset. The ddname will be referred to by the
ADRDSSU commands. This DD statement is not required for some
operations.
output DD
o Defines the output dataset. The ddname will be referred to by the
ADRDSSU commands. This DD statement is not required for some
operations.
filter DD
4
ADRDSSU Introduction
Example:
//SAMP1 JOB ATST,REGION=1024K
//STEP1 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=A
//TAPE DD UNIT=3480,VOL=SER=TAPE01,
//
LABEL=(1,SL),DISP=(OLD,KEEP),DSNAME=MYDATSET.BACKUP
//DASD DD UNIT=3380,VOL=(PRIVATE,SER=111111),DISP=OLD
//SYSIN DD *
RESTORE DATASET(INCLUDE(MYDATSET)) -
INDDNAME(TAPE) OUTDDNAME(DASD) REPLACE
/*
5
ADRDSSU Introduction
Each command must take up only one line, unless a continuation character
is used to indicate continuation of the command on the next line.
Continuation of a command is specified by a hyphen (-)
Example:
DUMP FULL INDD(INF1) –
OUTDD(OUTF1);
6
ADRDSSU Introduction
Using the INCLUDE or EXCLUDE keyword, you can filter on fully qualified or
partially qualified dataset names.
A fully qualified data set name is one in which all qualifiers are completely
spelled out.
A partially qualified data set name is one in which asterisks (*) or percent
signs (%) are used to represent qualifiers or parts of qualifiers.
The single asterisk (*) is used in place of one qualifier or only part of a
qualifier. While the double asterisk (**) indicates, either the nonexistence of
leading, trailing, or middle qualifiers, or the fact that they play no role in the
selection process.
Examples:
(INCLUDE(SERS.*.SRC))
(INCLUDE(SERS*.**.SRC))
(INCLUDE(**.SRC))
(INCLUDE(*.SRC))
(INCLUDE(*ER*.SRC))
The percent sign (%) acts as a place holder for a single character during
data set name filtering.
Examples:
(INCLUDE(S%RS.SRC))
(INCLUDE(S%%S.SRC))
(INCLUDE(S%*S.**.SRC))
(INCLUDE(S%RS.%%.SRC))
7
ADRDSSU Introduction
Syntax:
BY ((characteristic, operator, (arg1,arg2,…)), (…)…)
8
ADRDSSU Introduction
Examples:
BY (ALLOC, EQ, CYL)
BY ((ALLOC, EQ, TRK) ( CATLG, EQ, YES))
BY (DSORG, EQ, (PDS, PDSE))
With the DUMP command, you can dump DASD data to a sequential
dataset. The storage medium for the sequential dataset can be a tape or
DASD. You can dump datasets, an entire volume, or ranges of tracks.
The following special considerations apply when you are performing a dump
operation:
o A logical data set dump cannot be performed on the following data
sets:
VSAM datasets not cataloged in an integrated catalog facility
catalog
Page, swap, and SYS1.STGINDEX data sets
VSAM Volume DataSets (VVDS)
Partitioned data sets containing location-dependent information
that does not reside in note lists or in the directory
o A physical data set dump cannot be performed on the following data
sets:
KSDSs with key ranges. Use logical processing for this type of
data set.
VSAM datasets not cataloged in an integrated catalog facility
catalog.
Page, swap, and SYS1.STGINDEX datasets.
Example:
//STEP1 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//TAPE1 DD DSN=TEST1.DATA.BACKUP,
// UNIT=(3490, ,DEFER),
// LABEL=EXPDT=99000
// VOL=(,,,15),
// DISP=(,CATLG,DELETE)
//SYSIN DD *
DUMP DATASET(INCLUDE(TEST1.DATA.**)) -
OUTDDNAME(TAPE1) -
OPTIMIZE (4) -
SPHERE -
ALLDATA(*) -
ALLEXCP -
9
ADRDSSU Introduction
SHARE
/*
SPHERE is an option for a logical dataset dump. SPHERE specifies that for
any VSAM cluster dumped ADRDSSU must also dump all associated AIX
clusters and paths. Individual sphere components need not be specified,
only the base cluster name.
You can also use LOGINDYNAM to specify that volumes that contain the
datasets to be dumped using logical processing are to be dynamically
allocated.
With the RESTORE command, you can restore data to DASD volumes from
ADRDSSU-produced dump volumes.
You can restore datasets, an entire volume, or ranges of tracks. You can
restore to unlike devices from a logical dump tape.
10
ADRDSSU Introduction
Example:
//STEP1 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//TAPE1 DD DSN=TEST1.DATA.BACKUP, DISP=SHR
//SYSIN DD *
RESTORE DATASET(INCLUDE(**)) -
INDDNAME(TAPE1) -
CATALOG -
TOL(ENQF) -
SHARE
/*
INDDNAME specifies the name of the DD statement that identifies the (input)
dump dataset. This dataset can be on a tape or DASD volume.
You can also use RENAME to specify that, if a dataset with the old name
exists on the output DASD volume, ADRDSSU is to allocate a new dataset
with the new name and restore the dataset.
o pfx Specifies the prefix used to replace the first-level qualifier of the
data set name. It is optional, but if specified, must be the first
parameter in the list of subkeywords. The prefix is used only if the
(on,nn) parameters are not specified or the old name filters do not
match the data set name.
o on Specifies the old name to be used as a filtering criterion to check if
it matches the data set name.
o nn Specifies the new name to be used to derive the new data set
name when the data set name matches the corresponding old name
filtering criterion.
11
ADRDSSU Introduction
Example:
//STEP1 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
COPY DATASET( -
INCLUDE(USER1.**)) -
OUTDYNAM((338001),(338002),(338003)) -
DELETE -
RENAMEU(USER2) -
RECATALOG(USERCAT2)
DELETE
PURGE
/*
DELETE specifies that for a dataset copy ADRDSSU deletes VSAM and
non-VSAM datasets from the source volume after a successful copy. This
moves, in effect, a dataset from one volume to another. The datasets are
scratched and uncataloged.
PURGE specifies that unexpired data sets, which reside on the target
volume, can be overlaid for a full or track copy operation. If you do not
specify PURGE and unexpired datasets exist on the target volume, the copy
operation fails. For dataset copy operations, PURGE specifies that unexpired
source datasets can be deleted after they have been successfully copied.
PURGE is only valid with the DELETE keyword.
RENAMEU specifies that the dataset must be copied with the new name,
regardless of whether the dataset exists on DASD with the old name. If the
data set exists on the target volume with the new name and the
12
ADRDSSU Introduction
RENAME and RENAMEU are mutually exclusive; you cannot specify these
keywords together. RENAMEU is not supported for physical restore of VSAM
data sets, and, if specified, the datasets will not be restored.
13