Copy and data set profiles

If a data set is protected by a generic or discrete profile when it is copied, DFSMSdss tries to ensure that the target data is also protected (see Table 1). To do so, DFSMSdss uses the RACF DEFINE function or the catalog ALTER function. You need authority to define or rename discrete profiles, even if you are acting as a DFSMSdss-authorized storage administrator.

Table 1. DFSMSdss COPY Command and RACF Profiles. This table summarizes how DFSMSdss defines discrete profiles to protect the target set.
COPY with:		Source Data Set Protected?	RACF Profile:
RENAME	DELETE	Source Data Set Protected?	Source	Target
NO	NO	NO	None	As predefined
NO	NO	GENERIC	No change	As predefined
NO	NO	DISCRETE	No change	DEFINE
NO	YES	NO	None	As predefined
NO	YES	GENERIC	No change	As predefined
NO	YES	DISCRETE	DELETE	DEFINE
YES	NO	NO	None	As predefined
YES	NO	GENERIC	No change	MENTITY
YES	NO	DISCRETE	No change	DEFINE
YES	YES	NO	None	As predefined
YES	YES	GENERIC	No change	MENTITY
YES	YES	DISCRETE	DELETE	DEFINE
Terms defined: None The data set remains unprotected. As predefined DFSMSdss does not ensure that the target data set is RACF-protected. If a covering data set profile is not already predefined, the data set may be unprotected. No change The data set profile that is protecting the source data set remains unchanged. DEFINE A discrete profile is defined by DFSMSdss. DELETE The data set and the discrete profile are deleted. MENTITY If the target data set is not RACF-protected by a generic or discrete profile and MENTITY is specified, DFSMSdss defines a discrete profile. Otherwise, no profile is defined.