ADR380E

MIGRAT

Explanation
 The data set was not copied, restored, converted,
or released. The reason codes (reason_code or reason_code-xxx)
are: 0
An unmovable/ABSTR data set was not pre-allocated. Either the
system does not support allocation of these data sets, or you are
attempting physical restore of a nonpre-allocated unmovable/ABSTR
data set. 
1
REPLACE or REPLACEUNCONDITIONAL was not specified for
the unmovable data set.
2
There were unmatched extents on input and output for an unmovable/ABSTR
data set. The extents of the source unmovable data set are printed.
3-xxx
DADSM was unable to allocate a data set. The xxx indicates
DADSM (SVC 32) return codes. See z/OS DFSMSdfp Diagnosis information for
more information.
3-004
The dsname of request already exists on this
volume; initial allocation was not possible under the given name.
3-008
No room was available in the VTOC.
3-012
A permanent I/O error or an error returned by CVAF was encountered.
3-016
Direct access to the absolute track was unavailable.
3-020
The requested quantity was unavailable.
3-024
The average record length is greater than 65535 bytes.
3-048
The parameter list was invalid.
3-052
The JFCB was invalid or a partial DSCB pointer was specified.
3-072
The DOS VTOC cannot be converted to an OS VTOC.
3-076
No space parameter was given for a new data set, or zero space
was requested at absolute track zero.
3-100
CYL and CONTIG requests conflict.
3-104
The space subparameter was invalid.
3-116
User labels were not supported.
3-120
DSSIZE=0 and minimum allocation unit is greater than 0.
3-124
DSSIZE is not a multiple of the minimum allocation unit.
3-128
During a PDS space allocation request, a directory size request
was larger than the entire allocation request.
3-132
Space request must be ABSTR for a DOS volume.
3-148
Overlapping extents were in the VTOC.
3-152
Overlapping DOS split-cylinder extents were in the VTOC.
3-156
DADSM allocation ended because of possible VTOC errors.
3-164
Allocation ended because of DOS stacked pack format.
3-168
RACDEF failed; data already was defined.
3-172
The user was not authorized to define the data set.
3-176
The installation-wide exit rejected the request with a return
code of 8.
3-180
The installation-wide exit rejected the request with a return
code of 4.
3-184
RACF® was defined with modeling
specified; the model was not found.
4
The authorization check failed.
5
The block sizes of the target and source data sets do not match.
This can be caused by attempting to move a data set created in an
N*512 environment to a non-N*512 environment, or vice versa.
6
The volume sequence number does not match.
7
DSORG did not match.
8
There was an error in the rename filter.
9
The movable data set on the receiving volume is not the same size
as the data set on the source volume. The data set is in use and cannot
be scratched and reallocated. This might be caused by the initiator
holding serialization for the data set because the data set is referenced
in a subsequent job step.
10
The movable data set on the receiving volume is smaller than the
data set on the source volume. Failure occurred in the scratch; the
data set cannot be scratched and reallocated.
11-xx
The VVDS calls failed. See return code 50 under message IDC3009I.
12
The extents mapped by the VTOC and VVDS on DASD do not match the
VVDS on the input logical volume.
13-xxxx
Retrieving the extents from the VTOC failed. xxxx is
the obtain error code. See z/OS DFSMSdfp Diagnosis for
these codes.
14
Component names do not match. Either the component was redefined
since the data set was backed up; or it is a multivolume data set,
and the input and output volumes are different volumes of a multivolume
data set.
15
The number of components differs on input and output. Either the
component was redefined since the data set was backed up; or it is
a multivolume data set, and input and output volumes are different
volumes of a multivolume data set.
16
The beginning RBA for the components does not match on input and
output. The input and output volumes are different volumes of a multivolume
data set.
17
Primary/secondary indicators do not match on input and output.
The input and output volumes are different volumes of a multivolume
data set.
18
For physical data set processing: the REPLACE, RENAME,
or RENAMEUNCONDITIONAL keywords were not specified for the movable
non-VSAM data set, or REPLACE was not specified for a VSAM data set.For
logical data set processing, the REPLACE, REPLACEUNCONDITIONAL, RENAME,
or RENAMEUNCONDITIONAL keywords were not specified for the data set.

19
The extents mapped by the VTOC do not match the VVDS on the output
volume.
20-xxxx,yyyy
The data set on the output volume is smaller than on the input
logical volume. xxxx = data component size in tracks
(hexadecimal). yyyy = index component size in tracks
(hexadecimal).
21
The VVDS, BCS, or VTOCIX cannot be restored or copied to a different
volume. 
22
The location of where the unmovable data set is to be allocated
is not free, and FORCE is not specified.
23
The indicated data set is a duplicate data set and exists on more
than one input volume.
24
The pre-allocated target data set was defined with a larger control
area (CA) size than the source data set.
25
DFSMSdss cannot
restore data sets with a volume serial of MIGRAT.
26
CVOL cannot be replaced.
27
Input/output block cannot be built because one or more of the
following conditions exists: Ddname is not found.
Ddname is a SYSIN or SYSPRINT.
Device is not DASD.
Device is not supported.
Incorrect ranges are specified for DASD.

28
The catalog return code was unexpected.
29
No output volumes were available because one of the following
conditions exists: There are no volumes in the output volume list that fulfill the
requirements of the target volumes (that is, same or like device type).
Not all volumes of a pre-allocated multivolume data set are included
in the output volume list.
An attempt is made to restore an unmovable data set while output
volumes are specified without at least as much space as is required
by each corresponding source volume.
The volumes on which the pre-allocated VSAM clusters reside do
not match the volumes listed in the catalog entry for the cluster.
This can happen, for example, if the pre-allocated cluster is cataloged
outside the standard order of search or is not cataloged at all, while
another cluster with the same name is cataloged in the standard order
of search.
A VSAM data set was pre-allocated on the target volumes, but no
catalog entry was found.

30
The volume serials of the pre-allocated, cataloged multivolume
data set do not match those of the first volume.
31
The VSAM data set was pre-allocated on source volumes, but the
catalog entry was not found.
32
Space on the output volumes was insufficient to restore the data
set.
33
Allocation errors were unexpected.
34
Data set not processed. Catalog entry for an SMS-managed data
set was found but there was no corresponding VTOC entry.
35
The VSAM define failed.
36
Processing of an integrated catalog facility user catalog is not
supported when input volumes are specified (using one of the INDDNAME,
INDYNAM, LOGINDDNAME, or LOGINDYNAM keywords).
37
The new name specified with RENAME or RENAMEUNCONDITIONAL
already exists on the volume and the REPLACEUNCONDITIONAL keyword
was not specified. The REPLACE keyword cannot be used to replace a
data set that is being renamed.
38
The VVR for a component of the data set was found, but no corresponding
DSCB was found.
39
RENAME or RENAMEUNCONDITIONAL is not supported for unmovable data
sets.
40
A nonexistent catalog is specified in the RECATALOG parameter,
but the target data set is not SMS-managed.
41
During physical restore or copy, the target volume is not SMS-managed,
but one of the following situations occurs: The ACS routine returned an SMS storage class.  
The user specified BYPASSACS with STORCLAS.  
The user specified BYPASSACS without STORCLAS, but the source
data set was SMS-managed.  
The data set is only supported in an SMS environment.

42
The NOPACKING keyword was specified for the data set, but the
pre-allocated target was on an unlike device.
43
During physical restore or copy, the target volume is SMS-managed,
but one of the following situations occurs: The ACS routine returned NULL storage class.  
The user specified BYPASSACS with NULLSTORCLAS.  
The user specified BYPASSACS without NULLSTORCLAS, but the source
data set was not SMS-managed.  
The data set is not supported by SMS. 

44
The source component is multivolume, and the pre-allocated target
is either a different size or is now single volume.
45
The number of tracks on the pre-allocated target does not match
the number of source tracks, and it is not the first part of a multivolume
data set.
46
Allocation of resource failed because DFSMSdss used a utility to perform
data movement. Processing ends.
47
Locate failed for a component of the VSAM cluster that was named
in the message as the data set that was not processed (dsname). 
48
The data set must be copied with a utility, but DFSMSdss is unable to use utilities. 
50
DFSMSdss is
unable to determine the number of blocks per track for the target
device because of an invalid source data set block size.
51
The stripe number of the source and target extended format VSAM
data sets do not match.
52
The primary VVR of the target data set does not contain extended
format information. The pre-allocated target data set cannot be used.
53
The primary VVR of the source data set does not contain extended
format information.
56
The requested data set is a PDSE, but SMSX is not currently available
or the PDSE cannot be allocated and accessed at this time.
58
The requested data set is an extended sequential data set, but
the target volume selected is not SMS-managed. An extended sequential
data set can reside only on SMS-managed volumes.
59
The source data set for the operation is SMS-managed and has extended
attributes. Allocation has selected a target volume that is not SMS-managed.
Since the data set is not renamed, the requested operation would cause
the attributes to be lost.
60
The requested data set is a PDSE, HFS or an extended sequential
data set, but there is a pre-allocated target data set that is a different
type or has different attributes.
61
The requested data set is a physical sequential data set or partitioned
data set (PDS), but there is a pre-allocated target that is an extended
sequential data set or a partitioned data set extended (PDSE).
62
An attempt was made to restore an extended sequential data set
either to a non-ESCON attached device or to a device whose controller
does not support extended sequential data sets.
63
The source data set for the operation is SMS-managed and has extended
attributes, and the target data set has the same name as the source
but is not SMS-managed. The requested operation would cause the extended
attributes to be lost. The pre-allocated data set cannot be used.
64
The source data set has extended attributes, but the target data
set does not have extended attributes. The pre-allocated data set
cannot be used.
65
The target data set has extended attributes, but the source data
set does not have extended attributes. The pre-allocated target cannot
be used.
67
The pre-allocated target for the restore of a keyrange data set
(KRDS) is currently defined with a different number of keyranges than
the source dump.
68
During a restore, one or more keyranges of the pre-allocated target
of a KRDS have extents on the overflow volumes.
69
For a pre-allocated KRDS, the VTOC entry was not found on the
volume indicated by the catalog entry for the data set.
70
Dynamic allocation failed for DFSMSdss export data set.
71
The SMS indicator in the VTOC entry is off, showing that the data
set is not SMS, but the volume is SMS-managed.
72
DFSMSdss does
not provide support to perform a logical copy on hierarchical file
system (HFS) data sets.
73
Hierarchical file system (HFS) data sets cannot be restored to
non-SMS-managed volumes.
74
An attempt was made to restore a compressed data set to a device
whose controller does not support compressed data sets. 
75
All volumes of a multivolume data set were not included in the
input volume list and SELECTMULTI was not specified. A list of volumes
associated with the data set  be printed after this message as additional
information to assist the user. 
76
All components of a VSAM data set could not be selected. The missing
component and a list of volumes associated with the missing component
 be printed after this message as additional information to assist
the user.
77
The data set would be unusable after a restore because of the
relationship between the high allocated RBA of the VSAM source data
set and the target data set.
78
The catalog entry for the data set indicates that the data set
is NONVSAM, but the F1 DSCB indicates that the data set is VSAM.
80
The pre-allocated data set was unusable because of one of the
following conditions: The attributes of the pre-allocated target do not match those
of the source data set. The target data set is single volume, and
the source data set is multivolume, or vice-versa.
The target data set is not cataloged and has never been opened.
Therefore, DFSMSdss cannot
determine if it is single volume or multivolume.
The pre-allocated target VSAM data set is multivolume
and the output volumes specified do not include all of the volumes
on which the components reside.

82
An error occurred during CVAF VTOC access for the data set. Message
ADR246E  accompany this message and provide more information.
83
An error was detected while attempting to process the sequence
set VVR of a VSAM KSDS with an imbedded index. 
84
The data set is pre-allocated on an SMS-managed volume that is
disabled.
85
The current release does not support Large Format Physical Sequential
data sets.
86
The source and target volsers are the same. While
processing during a physical data set copy renaming of the source
data set was not performed and data sets with the same name cannot
reside on the same volume.
88
Renaming of a VSAM Alternate Index (AIX®)
was requested and cannot be performed.

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

Operator response
None.

System programmer response
On a RESTORE, dump the VTOC track
records on the input that are at the beginning of the file. 

Programmer response
Take the following action, depending on
the reason code (reason_code): 0
pre-allocate the data set with the size and location of the extents
to match those on the source volume, or specify FORCE. Rerun the job.
1
Specify REPLACE or REPLACEUNCONDITIONAL and rerun the
job.
2
Copy/Restore of unmovable/ABSTR data sets is allowed only if the
size and location of the extents match and the data set is pre-allocated.
Initialize a new DASD volume with the VTOC extent matching the input
logical volume, do a TRACKS COPY/RESTORE to copy the VTOC and TRACK
0, and do a data set COPY/RESTORE of the failing data set. Use the
appropriate utility for the type of data set to move the data set
from the scratch volume to the failing volume.
3
Take appropriate action according to the DADSM return code.
4
Acquire adequate authorization (RACF or
password). If it is a checkpoint/restart or system data set, instruct
the operator to allow the function to continue. You can also change
the user authorization exit routine to allow access to the data set.
Rerun the job.
5
Copy or restore the data set in the same environment in which
it was created.
6
For a multivolume non-VSAM data set, the volume sequence number
must match. For a VSAM data set, the beginning RBA of the data set
on the volume must match.
7
If it is the same data set, use AMASPZAP to modify the DSORG field
in VTOC entry. Rerun the job.
8
Correct the RENAME filter specification. Rerun the job.
9
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. 
10
Scratch the data set and rerun the job.
11
See return code 50 under message IDC3009.
12
Use a different backup copy to restore the data set.
13
Contact your system programmer.
14
If it is not a multivolume data set, delete the data set on DASD
and resubmit the job. If it is a multivolume data set and a RESTORE
in which the data set is not restored from the correct input logical
volume, resubmit the job to restore from the proper logical volume.
If it is a COPY, pass the proper input or output volumes and rerun
the job.
15
See reason code number 14.
16
See reason code number 14.
17
See reason code number 14.
18
For physical data set processing: specify REPLACE, RENAME,
or RENAMEUNCONDITIONAL if it is a non-VSAM data set. Specify REPLACE
if it is a VSAM data set. For logical data set processing, specify
REPLACE, REPLACEUNCONDITIONAL, RENAME (RESTORE only), or RENAMEUNCONDITIONAL.

19
Run the DIAGNOSE command of access method services to determine
the error.
20
Delete the data set and redefine it.
21
For non-SMS-managed data sets, restore to the correct DASD volume,
or use the LVOL parameter to restore from the correct logical volume.
For an SMS-managed user catalog, specify the correct DASD volume in
the OUTDD/OUTDY parameter, and ensure that the volume is in a Storage
Class with the guaranteed space attribute.
22
Specify FORCE or free the corresponding location on the target
volume, and rerun the job.
23
If it is a multivolume data set, correct the last volume indicator and the
volume sequence number fields in the VTOC, or catalog the data
set in the proper sequence in the appropriate catalog. Rerun the job.
24
Specify RENAME or RENAMEUNCONDITIONAL or delete the pre-allocated
target data set, and then rerun the job. For physical data set COPY,
delete or pre-allocate the target data set with the appropriate sized
CA.
25
Recall the data set and retry the restore operation.
26
Delete the CVOL from the target volume, then rerun the job.
27
Take one or more of the appropriate actions listed below, then
rerun the job: Ensure that a DDNAME statement is present in job step.
Ensure that the DDNAME is not that of a SYSIN or SYSPRINT.
Ensure that the device specified is a DASD.
Ensure that the device is supported on the system.
Ensure that the correct ranges are specified for DASD.

28
See message ADR497E, printed before this message, and take the
appropriate action.
29
Take one of the actions listed below; then rerun the job: Supply a new choice of output volumes.
Ensure that the data set is cataloged and the catalog volumes
and output volumes on which it is pre-allocated match.
Restore as a movable data set by specifying the FORCE keyword.
Supply the name of the catalog in which the pre-allocated cluster
resides, by using the RECATALOG keyword. If the pre-allocated target
cluster is not cataloged in any catalog, then either catalog it or
delete it.
Ensure that the pre-allocated target data set is cataloged in
the standard order of search.

30
Ensure that the correct target volumes for the multivolume data
set are specified in the output DD statements, then rerun the job.
31
Ensure that the catalog containing this data set
is in the standard order of search.
32
Provide a different choice of output volumes, then rerun the job.
33
Provide a different choice of output volumes, then rerun the job.
34
Delete the catalog entry for the failing data set. Full volume
dump/restore does not allocate data sets. However, it does restore
all of the data tracks as well as the VTOC. Thus, full volume restore
can be used to restore cataloged SMS-managed data sets with no corresponding
VTOC entries.
35
Ensure that the new name specified with RENAME or RENAMEUNCONDITIONAL
does not already exist on the volume. If the new name already exists,
specify REPLACEUNCONDITIONAL or delete the name and specify a new
name before retrying the command. REPLACE is ignored if RENAME or
RENAMEUNCONDITIONAL is used.
36
Do not specify input volumes, then rerun the job.
37
Ensure that the new data set name specified with RENAME
or RENAMEUNCONDITIONAL does not already exist on the volume. Specify
REPLACEUNCONDITIONAL to replace data set names that match the rename
criteria of the RENAME or RENAMEUNCONDITIONAL keywords. REPLACE is
ignored if RENAME or RENAMEUNCONDITIONAL is used.
38
Delete the VVR for the failing component, and rerun the job.
39
Specify REPLACE or REPLACEUNCONDITIONAL to replace the
unmovable data set name under the old name, and rerun the job. 
40
Ensure that the catalog name is correct and available if the target
data set is not SMS-managed, and rerun the job.
41
Specify either an SMS target or a NULLSTORCLAS. 
42
Delete and reallocate the target partitioned data set on a like
device, or rerun the job without specifying NOPACKING for the data
set. 
43
Specify a non-SMS target.
44
Delete the data set on DASD, and resubmit the job.
45
Delete the data set on DASD, and resubmit the job.
46
Rerun the job when the data set is not in use.
47
Identify components of the VSAM cluster and ensure that they are
named and cataloged correctly.
48
See preceding error messages (for example ADR476E) for information
as to why DFSMSdss is
unable to use utilities. Take appropriate action as described for
those messages. 
50
Ensure that the source data set has a valid block size or pre-allocate
a target data set with a valid block size. Specify the REPLACE or
REPLACEUNCONDITIONAL keyword.
51
Delete the pre-allocated target data set and rerun the restore
job.
52
See the previously issued ADR432E message. Delete the pre-allocated
target data set and allow DFSMSdss to allocate the target data set.
53
See the previously issued ADR432E message. You might need to use
a previous backup copy to restore the data set.
56
Ensure that SMSX is available and that the PDSE can be allocated
and accessed on the system. Rerun the job.
58
Ensure that the target volume for the PDSE or extended sequential
data set is SMS-managed, or do not select the PDSE or extended sequential
data set.
59
Either rename the data set and allow the operation to proceed
against the non-SMS-managed volume or modify ACS filtering in such
a way as to cause the target data set to reside on SMS volumes.
60
Process the PDSE, HFS, or extended sequential data set using the
RENAME or RENAMEUNCONDITIONAL keywords, or rename the pre-allocated
target data set, or delete the pre-allocated target data set.
61
Process the physical sequential data set or PDS using the RENAME/RENAMEUNCONDITIONAL
keywords, or rename the pre-allocated target data set, or delete the
pre-allocated target data set.
62
Change the target volume for the restore to a device that is both
ESCON-attached and the controller of which supports extended sequential
data sets.
63
Data sets with extended attributes cannot reside on non-SMS managed
volumes. Either delete the pre-allocated target or restore with RENAME
to a new data set.
64
Either delete the pre-allocated target and allow the data set
to be allocated by DFSMSdss,
or restore with RENAME to a new data set.
65
Either delete the pre-allocated target and allow the data set
to be allocated by DFSMSdss,
or restore with RENAME to a new data set.
67
Take one of the following actions: Delete and redefine the data set with the proper number of keyranges.
Delete the pre-allocated target and let DFSMSdss determine the number
of keyranges.

68
Take one of the following actions: Delete and redefine the data set. A candidate volume is acceptable
in the redefine, but can be retained only if the new definition has
a primary extent sufficient to contain the primary and secondary extents,
including those on the overflow volumes.
Delete the pre-allocated target. DFSMSdss restores the data set to the volumes
from which it was dumped.

69
Take one of the following actions: Delete and redefine the data set to ensure that the catalog and
VTOC entries match.
Delete the pre-allocated target and let DFSMSdss restore the data set
to the volumes from which it was dumped.

70
Determine the condition that caused the allocation to fail (for
example, authorization failure, and so on), correct the error condition,
and rerun the job. To bypass the problem, the user must define a generic
profile with "HLQ.*"
71
Correct the VTOC entry and rerun the job. 
72
Use a data set dump and restore or a full volume tracks physical
copy to move a hierarchical file system (HFS) data set. 
73
Ensure that the target volume for the HFS data set is SMS-managed,
or do not select the HFS data set. 
74
Change the target volume for the restore to a device whose controller
supports compressed data sets. 
75
Specify all of the volumes for the data set or specify SELECTMULTI(ANY)
and resubmit the job. 
76
Specify all of the volumes for the data set and resubmit the job. 
77
Delete the pre-allocated target, rerun the job, and issue an IDCAMS
DEFINE RECATALOG to get the restarted data set cataloged.
78
Correct the catalog or the F 1 DSCB to correctly indicate the
data set is VSAM or NONVSAM.
80
Take the appropriate action listed below, and rerun the job: Ensure that the attributes of the source and the pre-allocated
target match.
Either catalog the pre-allocated target, or open/close the pre-allocated
target so that DFSMSdss can
determine whether it is single volume or multivolume.
Specify all the output volumes where the pre-allocated
target data set resides and run the job again.

82
Contact your system programmer. 
83
Contact your system programmer. 
84
Use the VARY SMS,VOLUME(xxxxxx),ENABLE command
to enable the volume that contains the pre-allocated data set.
85
Process the Large Format Physical Sequential data set using level z/OS® V1R7 or higher.
86
For VSAM data sets, specify an output volser that is different
from the output volser of the input volume. For non-VSAM, specify
appropriate RENAMEUNCONDITIONAL criteria or specify an output volser
that is different from the input volume's.
87
The data set is a catalog open for use with RLS access.
88
Correct the RENAMEUNCONDITIONAL filter specification by not including
VSAM Alternate Indexes and rerun the job.

Source
DFSMSdss