|
- INFILE(ddname)|INDATASET(entryname)
- specifies the name of a DD statement or names the portable data
set that contains a copy of the cluster, alternate index, or user
catalog to be imported.
When importing into a nonexistent or an
existing nonempty data set or catalog, the names specified for management
class and storage class in the IMPORT command override the management
class and storage class names from the portable data set. The class
specifications and other attributes of the exported object are used
to determine the SMS class specifications. - INFILE(ddname)
- specifies the
name of a DD statement that identifies the portable copy of the cluster,
alternate index, or user catalog to be imported.
If a nonlabeled
tape or a direct access data set created by DOS/VS access method services
contains the copy, the following DCB parameters must be specified
on the referenced DD statement: - BLKSIZE. If you specified BLKSIZE when the cluster or alternate
index was exported, you must specify the same block size value for
IMPORT. If you did not specify a block size for EXPORT, a default
value of 2048 was used. Consequently, if you do not specify BLKSIZE
for IMPORT, IMPORT sets the block size to 2048.
- LRECL. LRECL is based on the maximum record size of the exported
VSAM data set. Maximum record size is determined by the value given
by the maximum subparameter of the RECORDSIZE parameter of the DEFINE
CLUSTER or DEFINE ALTERNATEINDEX command when the data set was defined.
- RECFM. Must be VBS.
Abbreviation: IFILE
- INDATASET(entryname)
- specifies
the name of the portable data set that contains a copy of the cluster,
alternate index, or user catalog to be imported.
If INDATASET
is specified, the portable data set is dynamically allocated. The
entryname must be cataloged in a catalog that is accessible by the
system into which the entry is to be imported.
Abbreviation:
IDS
- OUTFILE(ddname)|OUTDATASET(entryname)
- specifies the name of a DD statement or the name of a cluster,
alternate index, or user catalog to be imported.
When you use
OUTFILE or OUTDATASET to describe the data set, one of the following
conditions must be true: - The data set's entry is in the master catalog.
- The qualifiers in the data set's qualified name are the catalog's
name or alias.
- You are importing a non-SMS-managed catalog:
- When importing a cluster that was permanently exported, the OUTFILE
parameter should be used.
- If you are importing to a volume other than the original volume,
the OBJECTS(VOLUMES) parameter must also be specified.
- OUTFILE(ddname)
- specifies
the name of a DD statement that identifies the data set name and volumes
of the cluster, alternate index, or user catalog that is to be imported.
If the object was permanently exported or you are importing to
a volume other than the original volume, the DD statement specifies
the name of the cluster or alternate index as DSNAME, the volume serial
number, the device type, DISP=OLD, and AMP='AMORG'.
If the
object has its data and index components on different device types,
specify OUTDATASET instead of OUTFILE.
If the NEWNAME parameter
is specified for the cluster or alternate index entry, the data set
name on the DD statement must be the same as the new name. Failure
to do so will result in the deletion of the original cluster.
Abbreviation:
OFILE
- OUTDATASET(entryname)
- specifies
the name of the cluster, alternate index, or user catalog that is
to be imported. If you select OUTDATASET, the VSAM data set you identify
is dynamically allocated.
You can use concatenated
DD statements if the object was permanently exported and its data
and index components are on different device types. The first DD statement
specifies the name of the cluster or alternate index as the DSNAME,
the volume serial numbers and device type of the data component, DISP=OLD.
The second DD statement specifies the name of the index component
as the DSNAME, the volume serial numbers and device type of the index
component, DISP=OLD.
If NEWNAME is specified for the cluster
or alternate index entry, entryname must
be the same as the new name. Also, this should be the same name as
declared on the NEWNAME parameter. Failure to do so will result in
the deletion of the original cluster.
Abbreviation:
ODS
|