ABCs of z/OS System Programming Volume 3 - IBM Redbooks

4.50 Data set separation syntax
Data set separation function syntax:
Earlier syntax supports only PCU separation
{SEPARATIONGROUP | SEP}
{FAILLEVEL | FAIL}({PCU|NONE})
Figure 4-61 Defining separation profiles and syntax
Data set profile for separation
To use data set separation, you must create a data set separation profile and specify the
name of the profile to the base configuration. During allocation, SMS attempts to separate the
data sets listed in the profile.
A data set separation profile contains at least one data set separation group. Each data set
separation group specifies whether separation is at the PCU or volume level and whether it is
required or preferred. It also includes a list of data set names to be separated from each other
during allocation.
Restriction: You cannot use data set separation when allocating non-SMS-managed data
sets or during use of full volume copy utilities such as PPRC.
Separation profile
The syntax for the data set separation profiles is defined as follows:
SEPARATIONGROUP(PCU) This indicates that separation is on the PCU level.
SEPARATIONGROUP(VOLUME) This indicates that separation is on the volume level.
VOLUME may be abbreviated as VOL.
TYPE(REQUIRED) This indicates that separation is required. SMS fails the
allocation if the specified data set or data sets cannot be
separated from other data sets on the specified level
188 ABCs of z/OS System Programming Volume 3
{DSNLIST | DSNS | DSN}(data set name[,data set name,....}
New syntax supports both PCU and Volume separation
{SEPARATIONGROUP | SEP}({PCU | VOL})
TYPE({REQ | PREF})
{DSNLIST | DSNS | DSN}(data set name[,data set name,...}
Wildcard characters (* and %) are supported for DSN at
the third level qualifier (for example, A.B.*)
Earlier syntax for PCU separation continues to function
Both earlier and new syntax can coexist in the same separation
profile