ARC1866I

Explanation
 A FRRECOV DSNAME command for data set dsname ended
before normal termination of the function.  If the request was initiated
from TSO, dsname equals '***'. See the corresponding
ARC1000I or ARC1001I message for the data set name. The reason for
the failure is explained as determined by the retcode.
 Retcode
Meaning
2
Invalid data set type.  The following data set types are not supported
by Fast Replication Data Set Recovery: User catalog, VVDS, VTOC Index,
and VSAM Key-ranged.
4
Invalid data set. The specified data set is a data, index or path
component of a VSAM data set, or is a GDG base.
6
No data sets were found that match the fully or partially qualified
data set name dsname.
8
A catalog error occurred. 
10
The FRRECOV command or an associated data set restore work element
was canceled.
12
A multi-volume data set was not fully recovered from one or more
volumes.
14
Data set dsname has been migrated.
16
Multi-volume VSAM data sets with AIXs cannot be recovered.
18
The  backup copy does not exist.
20
The copy pool name was not specified for this data set and it
resides on a volume that belongs to more than one copy pool.
22
A CDS I/O error occurred.
24
The data set was determined to be on a volume that is not part
of a copypool.
28
Another DFSMShsm function was processing the copy
pool cpname.
30
RACF® failure.
32
The version determined to be the version requested, is not of
the format (dump copy/fast replication copy) requested.
34
The dump volume is not a copy pool dump volume. 
36
The dump volume  is not for the source volume that the data set
 is being recovered to.
38
The dump class specified is not associated with the
copy pool version being recovered, or DUMPCLASS was not specified
and all dump classes associated with this copy pool were designated
as 'AVAILABLEFORMOUNT(NO)' by the dump class definition.
40
The dump volume does not contain a valid copy.  
42
While preparing for the recovery of the data set, the state of
the version to be recovered changed from valid to invalid.
44
Data set is currently in use. 
46
Data set is no longer cataloged to the volume it resided on at
the time of the backup. 
48
The REPLACE keyword was not specified on the FRRECOV command.
50
The FROMCOPYPOOL keyword was not specified for a data set that
is not currently cataloged.
54
SMS was not active in the system when DFSMShsm attempted to retrieve
the SMS copy pool definition.
56
Copy pool not found.
58
An error occurred while retrieving a copy pool definition from
SMS.
60
The REPLACE keyword was not specified on the FRRECOV command when
NEWNAME(newdsname) was specified.
62
An enqueue or dequeue failure occurred.
98
An internal error occurred.

System action
 The data set recovery ends for data set dsname.
If a partially qualified data set name was specified on the FRRECOV
command, other data set recoveries may continue processing.  DFSMShsm processing
continues.

Programmer response
 Review and resolve the cause of the problem,
and reissue the command for data set dsname.
 Retcode
Meaning
2
None.
4
For a VSAM data set, determine the cluster name which corresponds
to the specified dsname.  Reissue the command with the base cluster
name.  For a GDG data set, determine the GDG generation to be recovered.
Reissue the command with the data set name for that generation. 

6
Uncataloged data sets are not supported.  
8
If the data set was not currently cataloged at the
time of recover and it is a GDS, verify that the GDG base exists.
If the GDG base does not exist, allocate it and retry the data set
recovery.
10
None.
12
Determine the cause of the error and reissue the command.
14
Migrated data sets are not supported by FRRECOV DSNAME recovery.
16
Delete all existing AIXs for the VSAM data set and re-try the
Fast Replication data set recovery. Re-build the AIXs after the recovery
has successfully completed. See z/OS DFSMS Using Data Sets for
information on rebuilding AIXs.
18
Issue the LIST COPYPOOL(cpname) command to
obtain a list of valid versions for the copy pool. If necessary, reissue
the FRRECOV DSNAME command specifying a valid existing version, generation,
date, or token. If the data set is not currently
cataloged and does not appear in the list of backed up data sets acquired
using the LIST COPYPOOL(cpname) DATASETS() command, some catalog information
might not be captured. Issue LIST COPYPOOL(cpname) to determine if
the catalog information was partially captured during the creation
of the backup.
20
Determine which volume(s) the data set resides on. Issue LIST
PVOL(volser) BCDS for one of the volumes that the
data set resides on. LIST PVOL will return which copy pools the data
set resides in.  From the available copy pools, determine which copy
pool backup version should be used for the recovery.  Reissue the
FRRECOV command  with the FROMCOPYPOOL keyword to specify the selected
copy pool name.
22
See the corresponding ARC0184I message for additional information.
24
This data set cannot be recovered using the FRRECOV DSNAME command.
You will need to recover this data set with the RECOVER command.
28
Wait for processing of the copy pool identified
in the message to complete, then attempt the operation against the
copy pool again if necessary.
30
The user that issued the FRRECOV command was not RACF authorized to the command.  See the associated
ARC1710E message for additional information regarding this error.
 Determine if the user requires this access and authorize the user
to the command.  Reissue the command.
32
Issue the LIST COPYPOOL(cpname) command to
view the valid versions and media formats associated with this copy
pool. Reissue the FRRECOV DSNAME  command using an existing valid
version for this copy pool.
34
Issue the LIST COPYPOOL(cpname) command, to
view the dump volumes associated with this copy pool.  Reissue the
FRRECOV DSNAME command using the dump volume for the source volume
to which the data set is being recovered.
36
Issue the LIST COPYPOOL(cpname) command, to view the dump volumes
associated with this copy pool. Reissue the FRRECOV DSNAME command
using the dump volume for the source volume to which the data set
is being recovered. When recovering a multivolume
data set, the DUMPVOLUME keyword can only be specified when all the
source volumes that the data set resided on at the time of the backup
are stacked onto the same dump tape. Reissue the FRRECOV DSNAME command
using VERSION and DCLASS to select the appropriate dump copy. 

38
Issue the LIST COPYPOOL(cpname) command to view the dump classes
associated with the copy pool you are attempting to recover from.
Determine the dump class you want to recover from, then reissue the
FRRECOV DSNAME command using a valid dump class for this copy pool.
40
Issue the LIST COPYPOOL(cpname) command, to
view the dump volumes associated with this copy pool.  Reissue the
FRRECOV DSNAME command using the dump volume for the source volume
to which the data set is being recovered.
42
Reissue the FRRECOV DSNAME command.
44
The data set must be closed and unallocated before it can be recovered.  For
Generation Data Group data sets, only one generation can be recovered
at a time because the GDG base is serialized.

46
Determine which version of the data set is required.  To recover
this data set it will need to be cataloged on the volume(s) that it
resided on at the time of the backup before it can be successfully
recovered.
48
The data set, dsname, exists and can be replaced
only with the use of the REPLACE keyword on the FRRECOV command.
50
A fully qualified data set that was not cataloged was specified
on the FRRECOV command.  The FROMCOPYPOOL keyword is required to be
specified on the FRRECOV command.
54
Bring up SMS and run the command again.
56
Correct the copy pool name, if needed, and issue the command for
this copy pool.
58
See the preceding ARC0935I message in the command activity log
for the specific failing code from the subsystem interface (SSI) of
SMS. Return code 2 is issued when SMS is installed but not started
in the IEFSSNxx member. An SMS lock token error occurs if DFSMShsm
attempts to issue an SMS service when the IGDSSIIN program is not
specified to start SMS.

60
The new data set name, newdsname, exists and
can be replaced only with the use of the REPLACE keyword.
62
Contact IBM® support.
98
Contact IBM support.

Source
 DFSMShsm