ADR439E

Explanation
DFSMSdss found
a pre-allocated data set but determined that it was unusable for the
following reason, (reason_code): 04
The pre-allocated cluster type does not match the source cluster
type. Either the organization (indexed, numbered, linear) of the clusters,
or one of the following cluster attributes, does not match: Extended format
Compressible
Extended addressable
Source is not striped and the pre-allocated target is striped

08
An alternate index (AIX®)
is defined over the pre-allocated cluster.
12
The source data RECORDSIZE is incompatible with the target CISIZE
and control area (CA) size attributes.
16
The pre-allocated target relative key position or key length is
not equal to the source cluster values.
20
The pre-allocated keyed VSAM cluster is not empty or REUSABLE.
24
The pre-allocated KSDS KEYRANGES do not match those of the source
cluster.
28
The index component of the pre-allocated target cluster does not
have sufficient allocated space for the source index component.
32
At least one data component of the pre-allocated target cluster
does not have sufficient allocated space for the corresponding source
data component.
40
At least one component of the pre-allocated target cluster spans
volumes.
44
An update of the target VTOC entry failed. The target must be
updated to make the target data set look empty if a utility does the
data transfer.
48
The VSAM data set must be copied with utilities, which requires
that both the source and the target data sets be cataloged in the
standard order of search. However, because they both have the same
name, this is not possible.
52
The pre-allocated, unmovable data set is not on the same or a
like device type as the source data set.
56
The pre-allocated DSORG is not equal to the target DSORG.
60
The pre-allocated data set space is insufficient. This  occur
when a nonpre-allocated partitioned-organized (PO) data set is copied
without the ALLDATA keyword, and a second copy is attempted to the
data set pre-allocated by the previous copy.
64
The pre-allocated PDS has an insufficient number of directory
blocks to contain the source directory.
68
The pre-allocated data set checking could not be completed.
72
The pre-allocated data set extents do not match the source data
set extents, and the source is an unmovable data set.
76
The direct data set cannot be pre-allocated to an unlike device
type.
80
The pre-allocated data set has no SUL extent.
84
The pre-allocated SUL data set has only one extent.
87
The data set is a Catalog open for use with RLS access.
88
An I/O error was encountered on the directory of the pre-allocated
partitioned data set.
92
The data set being restored is a PDS with no directory blocks
and cannot be restored to a pre-allocated data set.
95
There is a mismatch between the components of the source data
set and the target data set. For example, the source data set only
has a data component on the source volume being processed and the
target data set has a data and index component or only an index component
on its volume, or vice versa.  
96
The pre-allocated sphere does not match the source sphere.
97
The stripe attributes of the target and source data sets do not
match.
98
The data set is an extended sequential data set (SAM striped).
100
The pre-allocated data set is unusable because the source block
size is greater than the target device track capacity.
104
The NOPACKING keyword was specified for the data set, but the
pre-allocated target was on an unlike device.
108
The high-used page value (HURPN) of the pre-allocated PDSE cannot
be retrieved. DFSMSdss needs
the HURPN to calculate the size of the pre-allocated target data set
to ensure that it is usable.
112
The control interval size of the target data component is not
equal to the source data set
116
Either the source data set has extended attributes and the target
data set does not, or the target data set has extended attributes
and the source data set does not.
120
The first extent of the pre-allocated PDS was too small to contain
the source directory.
124
pre-allocated data set is either a tape or migrated data set.
128
The pre-allocated data set is marked as SMS checkpointed and cannot
be replaced unless the appropriate FORCECP keyword is specified.
132
The pre-allocated data set is one of many possible target data
sets and DFSMSdss is
unable to determine which target data set to copy to.
136
The pre-allocated data set is too small and in use. DFSMSdss is
unable to scratch and reallocate the target data set.
140
The pre-allocated data set has a format-8 DSCB that is not supported
in this release.
142
A VSAM data set that is a catalog or VVDS with a format-8 DSCB
is not supported in this release.
144
The preallocated integrated catalog facility user catalog was
found but is not locked or suspended
146
The source data set was compressed with zEDC services but the
target is not a VERSION 2.

System action
The specified data set is not processed. The return
code is 8.

Operator response
None.

Programmer response
If the system does not require use of a
pre-allocated data set, delete the pre-allocated target. If the system
requires use of the pre-allocated data set, correct the problem as
indicated by the reason code (reason_code) and
rerun the job.04
Delete and redefine the target cluster, ensuring that the cluster
types are the same.
08
Delete any AIX and PATH
associations defined over the target cluster.
12
Delete and redefine the target cluster using the source cluster
RECORDSIZE attributes.
16
Either delete and redefine the target cluster using the source
cluster KEY attributes, or ALTER the target cluster KEY attributes
to equal the source.
20
Delete and redefine the target cluster. If the target is to be
copied to repeatedly and is not a key range cluster, specify the REUSE
attribute on the DEFINE.
24
Delete and redefine the target cluster, ensuring that the KEYRANGES(lowkey
highkey) for target cluster are equal to the KEYRANGES(lowkey highkey)
for the source cluster.
28
Delete and redefine the target cluster with at least as much primary
index space as the source index has, or force the target cluster index
to extend to at least as much space as the source index.
32
Delete and redefine the target cluster with at least as much primary
data space as the largest source data component, or force the target
cluster data components to extend to at least as much space as the
source data components.
40
Delete and redefine the target cluster, ensuring that no components
span volumes (CANDIDATE volumes excepted).
44
One of the following actions should be taken: delete the target
and rerun DFSMSdss,
allowing it to perform the allocation; delete the existing target
and reallocate a new one, leaving it empty; or use AMASPZAP to alter
the target data set VTOC entry to make the data set appear empty.
48
Do not pre-allocate the data set.
52
Allocate an unmovable target data set on the same or a like device
type, or specify the FORCE keyword.
56
Ensure that the pre-allocated DSORG is equal to the source DSORG.
60
Ensure that the amount of space allocated for the pre-allocated
data set is sufficient to contain the source data set. If the error
is the result of successive copies of a PO data set without the ALLDATA
keyword, delete the pre-allocated data set and rerun all copy steps
specifying ALLDATA.
64
Ensure that the number of directory blocks defined for the pre-allocated
PDS is sufficient to contain the source directory blocks.
68
See the previous DFSMSdss message for the probable reason.
72
Ensure that the pre-allocated data set extents match the source
data set extents.
76
Ensure that the RELBLOCKADDRESS keyword was specified and that
the source: Is not a standard user label data set
Has a RECFM of fixed or fixed block.

 Or scratch and reallocate the target on the same device as the
source or on a like device.
80
Allocate a pre-allocated data set with standard user labels.
84
Allocate a standard user label data set with more than just the
standard user label extent.
87
Process the RLS Catalog on a system at the z/OS® V2R1 level or higher.
88
Scratch and reallocate the target partitioned data set to either
a different location on the target volume or a different target volume.
92
Scratch the target data set and allow DFSMSdss to allocate it during
the restore operation.
95
Check that the correct input and output volumes were specified
for the data set which you intended to copy. If the input and output
volumes are correct, delete the data set and let DSS allocate the
target data set or pre-allocated the target with the appropriate components
on its volumes in the same manner as they exist for the source data
set.
96
Ensure that the pre-allocated sphere’s AIX names, number of AIXs, number of paths, and
path names match the source sphere’s AIX names, number of AIXs, number of paths, and
path names.
97
Delete the pre-allocated target data set, and rerun the restore
operation.
98
Move or delete the data set from the volume.
100
Either reblock the data set or specify a target device that is
large enough for the source block size.
104
Delete and reallocate the target partitioned data set on a like
device, or rerun the job without specifying NOPACKING for the data
set.
108
Ensure that the pre-allocated PDSE is usable and accessible.
112
Delete and redefine the target cluster using the CISIZE attributes
of the source cluster.
116
Rename one of the data sets and retry the operation.
120
Ensure that the first extent of the pre-allocated PDS is large
enough to contain the source directory.
124
If pre-allocated data set is migrated, issue RECALL and rerun
the job. Tape data sets are not supported.
128
If the pre-allocated data set should be replaced, specify FORCECP
with the appropriate days parameter.
132
Either delete the pre-allocated target data sets with that name
until only one data set with that name exists, or narrow your specification
of output volumes as to exclude the duplicate target data sets.
136
Either delete the pre-allocated target data set and reallocate
it the appropriate size, or rerun the job when the data set is not
in use, or do not reference the data set in the same job as the DFSMSdss step.
140
Either delete the pre-allocated target data set and reallocate
it without a format-8 DSCB, or scratch the target data set and allow
DFSMSdss to allocate it.
142
Delete and reallocate the target data set. At the unsupported
level, the data set will get allocated in manner that is supported.
144  
When restoring a data set to a preallocated user catalog, it must
be locked or suspended prior to invoking DFSMSdss.  You do this by
either specifying the F CATALOG,RECOVER command or the RESTORE command
BCSRECOVER(SUSPEND|LOCK) parameter.
146
Delete the preallocated target data set or re-define it as a VERSION
2 data set.

Source
DFSMSdss