ADR878E

Explanation
 REASON: rc,mmmmm(yy),[volser],[reason]
           {[,catlg func,catlg rsn code,catlg mod id,
           parmlist rsn code,catlg service id] |
           [,VVR func,VVDS manager rsn code] |
           [,SMPM CFPurge rc, SMPM CFPurge rsn code]}
 AIX:      aix name rc,[volser],[reason]
           {[,catlg func,catlg rsn code,catlg mod id,
           parmlist rsn code,catlg service id] |
           [,VVR func,VVDS manager rsn code]}
 PATH: path name rc
           [,catlg func,catlg rsncode,catlg mod id,
           parmlist rsncode,catlg service id]

The listed data set (or its associated AIX® or PATH) failed
conversion either to or from SMS management, where rc is the reason code for the
data set failing. If the data set is multivolume and the error occurred on a volume other than the
one being processed by CONVERTV at that time, then the volume serial number of this other volume is
printed. If a multivolume data set fails conversion because one of the other volumes that the data
set is on is ineligible for SMS processing, then this reason is printed after the volume serial
number. If the error occurred in a catalog call, then the catalog function code, catalog reason
code, catalog module ID, and parmlist reason code are printed. See IDC3009I for an explanation of
the error, where: IDC3009I return_code = ADR878E catalog_reason_code IDC3009I reason_code =
ADR878E parmlist_reason_code IDC3009I module_ID = ADR878E catlg module_ID
 If the error occurred
in a VVR REQUEST function call, then the VVR function code that failed and the VVDS manager reason
code are printed. See message IDC3009I under return code 50 for an explanation of the VVDS manager
reason code.

If the error occurred in an SMPM CFPurge function invocation, then the SMPM CFPurge return codes
and reason codes are printed. See the z/OS DFSMSdfp Diagnosis for explanations of the return and reason
codes.

The reason codes are: 02
The data set is not supported in an SMS environment (ABSTR, unmovable, model DSCB,
CVOL, nonintegrated catalog facility VSAM catalog, or nonintegrated catalog facility VSAM data
set).
03
The data set is not supported in a non-SMS environment (PDSE, HFS or extended format data
set).
04
The data set is an uncataloged GDS.
05
The data set has extended attributes. Data sets with extended attributes cannot reside on
non-SMS volumes.
06
The data set is a cataloged GDS, but it is not cataloged in the standard order of search.
08
The data set is a GDS with nonspecific volumes.
10
The data set is a GDS with candidate volumes.
12
ACS routines did not return SMS constructs for the data set.
14
A null storage class was returned for the data set.
16
The storage class definition cannot be retrieved for the data set.
18
The data set is multivolume, extents for the data set exist on volume volser,
volume volser was not specified in the volume list, and SELECTMULTI(ALL) was
specified (or defaulted to).
20
The data set is multivolume, volume volser is the first volume of the data
set (for VSAM, volume volser is the first volume of the data component), volume
volser was not specified in the volume list, and SELECTMULTI(FIRST) was
specified.
22
The data set is multivolume and has extents on volumes volume_serial_number
that are in different storage groups.
24
The data set has candidate volumes volume_serial_number that are in different
storage groups.
26
The data set is multivolume and has extents on volumes volume_serial_number
that are ineligible for conversion for the reasons given. (See message ADR874E for volume reason
code.)
28
The data set has candidate volumes volume_serial_number that are ineligible
for conversion for the reasons given. (See message ADR874E for volume reason code.)
30
The data set is multivolume and is not cataloged.
32
The data set is not cataloged in the standard search order, and the CATALOG keyword was not
specified.
34
The data set is not cataloged in the standard search order, and a duplicate entry was found in
another catalog.
36
The data set is not cataloged in the standard search order, and a duplicate entry was found in a
standard order of search catalog.
38
The VSAM base cluster is in a sphere where all data sets are not convertible to SMS
management.
40
The catalog to which the AIX’s sphere is directed is
different from the catalog to which the AIX’s related
base cluster is directed. All components must be in the same catalog.
42
The catalog to which the path’s sphere is directed is different from the catalog to which
the path’s related base cluster is directed. All components must be in the same catalog.
44
ALTER failed during an attempt to update the catalog entry for the data set.
46
DELETE NOSCRATCH failed during an attempt to delete the catalog entry for the data set.
48
DEFINE RECATALOG failed during an attempt to recatalog the data set.
49
DEFINE ALIAS failed during an attempt to define the aliases for the data set.
50
DEFINE CATALOG failed during an attempt to catalog the data set.
52
CATALOG NAME LOCATE failed during an attempt to determine where the data set should be cataloged
according to standard order of search.
54
DEFINE PATH failed during an attempt to define a path.
56
LOCATE failed.
58
The VSAM base cluster is in a sphere that includes data sets with catalog errors.
60
Read non-VSAM volume record (NVR) failed in the VVDS manager.
62
Get for update of non-VSAM volume record (NVR) failed in the VVDS manager.
64
Put for update of non-VSAM volume record (NVR) failed in the VVDS manager.
66
Delete of non-VSAM volume record (NVR) failed in the VVDS manager.
68
Insert of non-VSAM volume record (NVR) failed in the VVDS manager.
70
Read VSAM volume record (VVR) failed in the VVDS manager.
72
Get for update of VSAM volume record (VVR) failed in the VVDS manager.
74
Put of VSAM volume record (VVR) failed in the VVDS manager.
76
The VSAM base cluster is in a sphere that includes data sets with VVR errors.
78
Read of the VTOC failed during an attempt to update the SMS indicator for the data set.
80
Rewrite of the VTOC failed during an attempt to update the SMS indicator for the data set.
82
The VSAM base cluster is in a sphere that includes data sets with VTOC entry update errors.
84
The VSAM component does not have a corresponding VTOC entry.
86
The non-VSAM data set is SMS-managed, but its NVR cannot be found.
88
Storage class authorization for the data set failed.
90
Management class authorization for the data set failed.
92
Both storage class and management class authorization for the data set failed.
93
DFSMSdss invoked the SMPM CFPurge
function to purge the data in the coupling facility caches for the data set. The SMPM CFPurge
function returned the listed return and reason codes.
94
Unable to get extent information from the VTOC.
95
Data set is HFS file.
96
The data set failed enqueue.
98
The data set is an extended sequential data set (SAM striped).
99
Extended format VSAM data set.
100
Extended addressable non-extended format VSAM Linear data set.
101
The data set has RLS information associated with it, and therefore is not supported in this
release.
102
The data set is marked as checkpointed.
103
A component of the VSAM base cluster or alternate index has more than 255 extents, which
requires System Managed Storage (SMS).

System action
Processing continues with the next data set. The volume will not be successfully converted to or
from SMS management. The return code is 8.

Operator response
None.

Programmer response
02-10
Move or delete the data set from the volume.
12
Update ACS routines to return SMS constructs for the data set.
14-16
Verify ACS routines to ensure that the data set is defined to a storage class.
18
Take one of the following actions and rerun the job: Specify SELECTMULTI(FIRST) and include the first volume of the data set in the input volume
list. For VSAM data sets, you must include the first volume of the data component in the input
volume list.
Specify SELECTMULTI(ALL) (this is the default if you do not specify SELECTMULTI) and include all
volumes of the data set in the input volume list.
Specify SELECTMULTI(ANY) and include at least one primary or candidate-with-space volume of the
data set in the input volume list.
Move or delete the data set off the volume you are trying to convert.

20
Take one of the following actions and rerun the job: Specify SELECTMULTI(FIRST) and include the first volume of the data set in the input volume
list. For VSAM data sets, you must include the first volume of the data component in the input
volume list.
Specify SELECTMULTI(ALL)(this is the default if you do not specify SELECTMULTI) and include all
volumes of the data set in the input volume list.
Specify SELECTMULTI(ANY) and include at least one primary or candidate-with-space volume of the
data set in the input volume list.
Move or delete the data set off the volume you are trying to convert.

22
Change your active control data set so that all the volumes that the data set resides on are
defined to the same storage group.
24
(1) Delete the candidate volumes from the data set’s catalog entry, or (2) change your
ACDS so that all the candidate volumes are defined to the same storage group as the volumes on which
the data set resides.
26-28
See message ADR874E for required action.
30
(1) Catalog the data set, or (2) move or delete the data set from the volumes that you are
trying to convert.
32
(1) Specify the CATALOG keyword, or (2) recatalog the data set into the standard order of
search.
34
(1) Catalog the data set into the standard order of search, or (2) rename the data set, or (3)
move or delete the data set from the volumes that you are trying to convert.
36
(1) Rename the data set, or (2) move or delete the data set from the volumes that you are trying
to convert.
38-42
(1) Rename the base cluster, the data or index component, AIX, AIX data or index component, or PATH to be directed
to the same catalog as the VSAM base cluster, or (2) delete or add catalog aliases so all parts of
the sphere are alias-directed to the same catalog.
44-86
Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.
88-92
(1) Make sure that the RESOWNER of the data set is authorized to use the storage or management
class derived for the data set, or (2) update the ACS routines to select a different storage or
management class for the data set.
93
See the z/OS DFSMSdfp Diagnosis for an explanation of the listed return and reason
codes.
94
See previous error message associated with the data set for specific action.
95
Move the data set to another SMS volume.
96
Ensure that no other jobs are accessing data sets on volumes to be converted, and then rerun the
CONVERTV job.
98
Move or delete the data set from the volume
99
Move the data set to another SMS volume.
100
Move the data set to another non-SMS volume.
101
Rerun the job on a system running DFSMS/MVS Version 1 Release 3 or higher.
102
Confirm that the checkpointed data set is no longer required for a restart, specify FORCECP with
the appropriate days parameter and rerun the job.
103
Move the data set to another SMS volume.
Delete the data set from the volumes that you are trying to convert.

Source
DFSMSdss