ARC1245I

Explanation
 A space management operation has been requested
for a data set that is not eligible for space management processing.
In the preceding ARC1001I message or in the ARC0734I message, the
values for reascodeand its meaning are: 
 Reascode
Meaning
1
The data set is a system data set, a VSAM catalog, or an integrated
catalog facility (ICF) catalog. Either the first four characters of
the data set name are HSM, or the first five characters of the data
set name are SYS1, or the data set name is SYSCTLG.
2
The SETMIG command restricts the data set by initial characters
of the data set name.
3
The SETMIG command restricts the data set by the full data set
name.
4
The data set has been temporarily prevented from migrating because
a JES3 job plans to use it. The end date of this restriction is in
the MCD record for the data set.
5
The management class attribute COMMAND-OR-AUTO-MIGRATE=COMMAND
restricts migration of this SMS-managed data set.
6
The management class attribute COMMAND-OR-AUTO-MIGRATE=NONE restricts
migration of this SMS-managed data set.
7
The setting of the backup-while-open bits restricts migration
of this SMS-managed data set.  Note: Reason codes 90 and higher are
not produced unless you have installed a patch titled "Getting an
ARC0734I Message Issued with the Appropriate Reason Code for Data
Sets Not Selected during Volume Migration or Backup". For more
information about this patch, refer to z/OS DFSMShsm Diagnosis topic, "PATCH: Changing Storage in the Address Space of DFSMShsm" under topic, "DFSMShsm Maintenance
Commands". 

8
The SMS-managed data set is not eligible for migration because
it is checkpointed and the minimum number of days since the date last
referenced has not elapsed.  Note: Reason codes below 90 are not produced
during interval migration regardless of the patch described above.

90
The SMS-managed data set is not eligible for migration by space
management because it is checkpointed and the minimum number of days
since the date last referenced has not elapsed.
91
The SMS-managed data set is not eligible for migration because
it has not gone unused for the number of days specified in the management
class definition for PRIMARY DAYS NON USAGE.
92
The return code passed back from the data set migration exit (ARCMDEXT),
indicates the data set should not be migrated.
93
The data set is not eligible for migration because it does not
have a current backup copy and it is being directed to tape.
94
The data set is not eligible for partial release because it is
a multivolume data set.
95
The data set is not eligible for migration because it has more
than one AIX®, more than one
path on the base cluster, or more than one path on the AIX.
96
The data set is not eligible for migration because the date last
referred to in the data set VTOC entry is 0.
97
The return code passed back from the space management exit (ARCSAEXT)
indicates the data set should not be processed.
98
The data set is not eligible for space management because the
data set’s age is less than the DFSMShsm integrity age. (For SMS temporary
data sets under JES3, this is always 2 days regardless of USERDATASETSERIALIZATION.)
99
For VSAM data sets, this reason code is issued when the data set
VTOC entry is not for the base data object of a VSAM data set, or
is the secondary piece of a key range data set.  For non-VSAM data
sets, this reason code is issued when the data set sequence number
is not 1. This indicates that the data set is part of a multivolume
data set, but is not the first segment of that data set.

 Attention: The data set will not be reconnected, but remains
eligible for normal migration for Reason Codes 100 through 114.
 100
Catalog reconnectable flag is off.
101
Either the data set has changed since the last recall, or DFSMShsm cannot
determine whether the data set has changed. You may receive this error
for the following reasons: the Format1 DSCB change flag is set to
on, the creation date of the data set does not match the creation
date stored in the MCD, or the MCB record could not be read to verify
backup dates.
102
Either:  SETSYS TAPEMIGRATION(RECONNECT(NONE))
 or
 DFHSMDATASETSERIALIZATION
 specified.
103
CONVERT parameter specified on MIGRATE VOLUME command.
104
Forced to ML1 by option on HMIGRATE ISMF panel or FORCML1=YES
parameter on ARCHMIG macro.
105
The ARCMDEXT installation exit set issues return code 44 for the
data set.
106
The SETSYS TAPEMIGRATION (RECONNECT (ML2DIRECTEDONLY)) option
is in effect and the DFSMShsm target is ML1 with no override
from the ARCMDEXT installation exit.
107
The data set cannot be serialized.
108
The ML2 volume cannot be serialized.
109
There is an error reading the MCD record.
110
There is an error updating or creating CDS record.
111
There is an error deleting or recataloging original data set.
112
There is an error obtaining VTOC data set entry for original data
set.
113
There is a Getmain/Freemain error.
114
There is an error cataloging data set to MIGRAT.
115
The return code passed back from the second level migration data
set exit (ARCMMEXT) indicates that the data set should not be migrated.
116
The ESTAE setup for the data set migration exit (ARCMDEXT) failed.
201
A data set eligible for migration from cylinder-managed space
is skipped, because high volume threshold is not exceeded and the
data set has the 1st three extents allocated in the cylinder-managed
space.
202
A data set is not eligible for migration, because the low volume
threshold is already reached and the data set has the 1st three extents
allocated in the cylinder-managed space.

System action
 If reascode is other than
100–111, the space management operation of the data set ends. For reascode 100–111,
the data set will not be reconnected, but remains eligible for normal
migration. An additional ARC0734I message will be issued when the
normal migration of the data set is attempted. DFSMShsm processing continues.

Programmer response
 Perform the action that has been assigned
to the reascode you have received. 
 Reascode
Action
1
There is no response needed.
2, 3
Contact the storage administrator.
4
Reenter the request after the JES3 prevent-migration date (MCDJDATE)
has expired. To determine this date, use the FIXCDS command to display
the MCD record.
5, 6
This data set will only be migrated if the management class definition
is changed to allow migration, or the management class associated
with the data set is changed to one that allows migration.
7
This data set can only be migrated if the data base administrator
removes it as a candidate for backup-while-open processing.
8
The default minimum number of days that must have elapsed since
the date last referenced is 5. This value may be modified with a patch
command documented in the z/OS DFSMShsm Implementation and Customization Guide. 
90
The default minimum number of days that must have elapsed since
the date last referenced is five. This value may be modified with
a patch command documented in the z/OS DFSMShsm Implementation and Customization Guide. 
91
The data set will be eligible for migration after it has gone
unused for the number of days specified in the management class definition
for PRIMARY DAYS NON USAGE.  If the data set should be considered
eligible for migration sooner, it needs to be associated with a management
class whose definition of PRIMARY DAYS NON USAGE is smaller than the
value specified in the management class currently associated with
the data set.

92
If the data set should be considered eligible for migration, the
data set migration exit (ARCMDEXT) must be updated so that it does
not exclude the data set from migration.
93
To migrate the data set directly to tape, perform one of the following:
 Create a backup copy of the data set. This can be done by automatic
backup or by issuing a data set backup command (HBACKDS or BACKDS).
Ensure that no current backup copy exists before the data set
can be migrated to tape. This can be done by specifying AUTO BACKUP=N
in the management class definition associated with the data set.

94
No response required. The only way to release the unused allocated
space for a multivolume data set through DFSMShsm is to migrate the data
set and then recall it.
95
The data set can only be migrated by a data set migration command
(HMIGRATE or MIGRATE).
96
No response required. DFSMShsm resets the date last referred to
in the DFCB to the current date. The next time volume space management
is performed, migration eligibility will be done using this date.
97
If the data set should be considered eligible for migration, the
space management exit (ARCSAEXT) needs to be updated to not exclude
the data set from migration.
98
No response required. The data set is not eligible for migration
because the data set’s age is less than the DFSMShsm integrity age. For
a discussion of integrity age, refer to z/OS DFSMShsm Storage Administration.  
99
No response required. DFSMShsm processes a VSAM data set when
it encounters the data set VTOC entry of the base data object. For
a key range data set, the data set VTOC entry must be for the first
segment of the data set.  For a non-VSAM data set, processing occurs
when the volume with a data set sequence number of 1 is encountered.

100
No action required. The data set is ineligible for reconnection
until migrated and recalled again.
101
No action required. The data set is ineligible for reconnection
until migrated and recalled again.
102
No action required. Reconnection not permitted by the storage
administrator.
103
No action required. MIGRATE CONVERT does not use reconnection
because an immediate RECALL is scheduled.
104
Remove the option forcing migration to ML1 if reconnection to
an ML2 copy is desired.
105
No action required. ARCMDEXT installation exit has disallowed
reconnection.
106
No action required. The SETSYS TAPEMIGRATION (RECONNECT(ML2DIRECTONLY))
command was not overridden by the ARCMDEXT installation exit.
107
No action required. The data set remains eligible for reconnection
when the volume it resides on is next space managed.
108
No action required. The data set remains eligible for reconnection
when the volume it resides on is next space managed.
109
Increase the reconnectdays value on SETSYS
MIGRATIONCLEANUP command if an excessive number of data sets fail
reconnection for this reason.
110
No action required. The data set remains eligible for reconnection
when the volume it resides on is next space managed.
111
No action required. The data set remains eligible for reconnection
when the volume it resides on is next space managed.
112
No action required. The data set will be retried for normal migration.
If obtain error persists, see associated messages.
113
No action required. The data set remains eligible for reconnection
when the volume it resides on is next space managed.
114
No action required for a non-VSAM data set, which remains eligible
for reconnection when the volume it resides on is next space managed.
For a VSAM data set, see associated message ARC0512I for information
on which components could not be cataloged to MIGRAT.
115
If the data set should be considered eligible for migration, the
second level migration data set exit (ARCMMEXT) must be updated so
that it does not exclude the data set from migration.
116
Contact the IBM® Support
Center.
201, 202
No response is needed.

Source
 DFSMShsm