An SMS-managed
generation
data set (GDS) can be in one of three states:
- ACTIVE
- DEFERRED
- ROLLED-OFF
When
copying a GDS to an SMS-managed volume and the data set is
not preallocated, DFSMSdss allocates the target GDS as follows:
- If DELETE is specified and RENAMEUNCONDITIONAL is
not specified, the target GDS is allocated with the same state as
the source GDS.
- If the TGTGDS keyword is specified, the appropriate
status is
assigned to the data set. The requested target status must not violate
rules of the generation data group.
- When the source is an
SMS-managed GDS and the target has the same
name (that is, DELETE without RENAME), the target status is the same
as the source status.
- When the source is a non-SMS-managed
GDS and the target has the
same name (that is, DELETE without RENAMEUNCONDITIONAL),
the default target status is ACTIVE when the source is cataloged.
When the source is not cataloged, the default target status is DEFERRED.
- In all other cases, the default target status is DEFERRED.
- You
can use the TGTGDS keyword to alter the target status except
when the source is an SMS-managed GDS and the target has the same
name.
Table 1 describes
the default situation for DFSMSdss
to allocate the SMS-managed GDG data set (MOVE refers to COPY command
with the DELETE keyword specified):
Table 1. Default Situation for DFSMSdss to Allocate the SMS-Managed
GDG
Data SetTarget
Environment |
Source Environment |
Source
Status
|
DFSMSdss
Function |
TGTGDS
Default
|
---|
SMS |
Non-SMS |
Cataloged |
COPY |
DEFERRED |
MOVE |
ACTIVE |
Not Cataloged |
COPY |
DEFERRED |
MOVE |
DEFERRED |
SMS |
ACTIVE |
COPY |
DEFERRED |
MOVE |
ACTIVE |
DEFERRED |
COPY |
DEFERRED |
MOVE |
DEFERRED |
ROLLED-OFF |
COPY |
DEFERRED |
MOVE |
ROLLED-OFF |
If the data set is preallocated,
the state of the target GDS is
not altered.