This topic lists various attributes that DFSMSdss can set or change for a given data set, and identifies where DFSMSdss gets the attribute information from.

Locate the data set attribute of interest in the first column of Table 1. The remaining columns indicate where and under which conditions DFSMSdss finds the attribute information. For example, the data set size is usually determined by the source data set, unless the preallocated target data set is larger. The ALLDATA(x) and ALLEXCP keywords have an effect on the data set size.

Table 1. Data Set Attributes and How They Are Determined.

Attribute	Is the Attribute Determined by…
	...the Source Data Set?	...the Pre-Allocated Target?	...a Keyword?	...another Factor?
Data set name	Yes, if no RENAME or RENAMEU	No	RENAME or RENAMEU	No
Data set size	Yes, unless the preallocated target data set is larger	Yes, if it is big enough	ALLDATA(x) or ALLEXCP	No
Volumes	Yes, if doing a RESTORE and no output volumes were specified, no target exists, and not SMS-managed	Yes	Yes, if not SMS, OUTDDNAME(x,...) or OUTDYNAM(x,...)	If SMS-managed, ACS routines and SMS allocation choose volumes with most available space; if not SMS-managed, DFSMSdss chooses volumes with most available space
Data set location on volume	Yes, if no target and either ABSTR, PSU, POU, or DAU	Yes	FORCE can override ABSTR, PSU, POU, and DAU	DFSMSdss locates wherever space is available; DEFRAG may move extents
PDS directory size (blocks)	Yes	No	No	No
PDSE directory size (blocks)	Yes	No	No	No
SMS Storage Class or Management Class	Yes, if no target and BYPASSACS is specified	Yes	Yes, if STORCLAS(x) or MGMTCLAS(x), or both, are specified with BYPASSACS	ACS routines if no target and BYPASSACS is not specified
SMS Data Class	Yes, if no target	Yes	No	No
BLKSZ	Yes, if REBLOCK is not specified and data set is not system reblockable	No	If REBLOCK keyword is specified, DFSMSdss chooses a new optimal blocksize	If system reblockable, DFSMSdss chooses a new optimal blocksize, or else the user can change blocksize with the installation reblock exit and can specify REBLOCK with the installation options exit
LRECL	Yes	No	No	No
RECFM	Yes	No	No	No
DSORG	Yes	No	No	No
Number of stripes	Yes, source must be striped	Yes for non-VSAM. No for VSAM	No	For nonguaranteed-space, determined by sustained data rate (SDR) in STORCLAS. For guaranteed-space, must have a nonzero SDR, then determined by number of output volumes supplied
Number of volumes (VOLCOUNT)	Yes	Yes	VOLCOUNT can make a single volume source into a multivolume target, or change the number of volumes for a multivolume data set	Yes (see the COPY and RESTORE command VOLCOUNT parameter descriptions for specific information)
Number of extents	Yes, for imbedded extended KSDSs during physical data set restore	Yes	No	DFSMSdss always tries to consolidate during COPY/RESTORE. RELEASE may reduce the number of extents
PDS/PDSE	Yes, if no target or if doing a RESTORE	Yes, if doing a COPY	CONVERT(PDS(x)) or CONVERT(PDSE(x))	No
Cataloged	Yes, if RECATALOG(*) is specified, no target, and the user is not doing a physical data set restore	Yes	RECATALOG(x), CATALOG, UNCATALOG (applies to source only)	If SMS or VSAM, cataloged by default; if physical data set restore, only single volume non-VSAM is cataloged (if CATALOG is specified)
Allocation unit	Yes, if no target and TGTALLOC (SOURCE) specified or defaulted	Yes	TGTALLOC(x)	No
Free space in VSAM	Yes, if going to like device, nonVALIDATE, no dummy blocks, and CI and CA sizes do not change	Yes, if doing VSAM I/O and uses values in target catalog entry	VALIDATE, NOVALIDATE, FREESPACE	No
Security (RACF®)	If no target and source was generic or discrete, and no applicable profile protecting new target, a new discrete will be defined	Yes	MENTITY, MVOLSER	Full RACF profile information (access lists) are not preserved
AIX® data sets on VSAM clusters	If SPHERE is specified during COPY or DUMP and RESTORE, sphere and connections are preserved	No	SPHERE	No
GDS state	Yes, if no target and TGTGDS (source) specified	Yes	TGTGDS(x)	No
RLS BWO field	Yes, if no preallocated target and no UIM input	Yes, if no UIM input	No	UIM can pass a value in Exit 22 during logical RESTORE
RLS timestamps	Yes, if not a logical restore	No	No	For logical restore, if dumped using RLS access, timestamps reflect the time of the dump; otherwise the timestamps are zero
RLS recovery required	Yes, if no UIM input	No	No	UIM can pass a value in Exit 22 during logical RESTORE
RLS log parameter	Yes, if no preallocated target and no UIM input	Yes, if no UIM input	No	UIM can pass a value in Exit 22 during logical RESTORE
RLS log stream ID	Yes, if no preallocated target and no UIM input	Yes, if no UIM input	No	UIM can pass a value in Exit 22 during logical RESTORE
BCS Quiesce enabled	Yes, unless preallocated	Yes	No	Only applies to logical restore
BCS lock or suspend	Yes, unless preallocated	Yes	No	Only applies to logical restore. BCSRECOVER(LOCK|SUSPEND) is ignored if not preallocated.
BCS RLS in use	No	No	No	Only applies to logical restore. BCSRECOVER(LOCK|SUSPEND) is ignored if not preallocated.
Class transition information	Yes, if no preallocated target	Yes, unless it is unusable and needs to be scratched and reallocated	No	No
LOGREPLICATE parameter	Yes, if no preallocated target and no UIM input	Yes, if no UIM input	No	UIM can pass a value in EXIT 22 during logical restore
extended format sequential version number	Yes, if no preallocated target	Yes, if target has to be scratched and reallocated, the target version type will be preserved	No	No, if the target data set does not exist the target will be allocated with the source version type