Explanation
DFSMShsm attempted to create a backup version
of a data set. The reason code in message ARC1001I indicated the conditions
encountered and the reason the backup version was not created.
In
message ARC1001I, the values for
reason-code are:
- Reascode
- Meaning
- 1
- The data set is extended format, but DFSMSdss is not specified as
the datamover for extended format data sets. DFSMShsm datamover cannot move
extended format data sets.
- 2
- The data set is extended format, but it is not SMS-managed. Only
SMS-managed extended format data sets can be backed up.
- 3
- The data set is large format sequential, but DFSMSdss is not specified as
the datamover for large format sequential data sets. DFSMShsm datamover
cannot move large format sequential data sets.
- 4
- A BACKDS or HBACKDS command was issued to back up the non-SMS-managed
data set identified in the message ARC1001I. The backup version was
not created because the maximum number of backup versions DFSMShsm is
to maintain is 0. Either an ALTERDS or HALTERDS command was issued
for the data set, and the value specified for VERSIONS is 0, or if
never specified on an ALTERDS or HALTERDS command, the value specified
for VERSIONS on the SETSYS command is 0.
- 5
- The current level of DFSMShsm cannot backup an extended format
data set (sequential striped or compressed). A minimum of DFSMShsm 1.1.0
is required for sequential striped data sets, and a minimum of DFSMShsm 1.2.0
is required for extended format compressed data sets.
- 6
- The installation attempted to backup a Large Format Sequential
Data Set. This level of DFSMS/DFSMShsm does not support backing up
large format sequential data sets.
- 8
- A backup version was not created for an SMS-managed data set because
the management class attribute ADMIN-OR-USER-COMMAND-BACKUP indicates
the data set should not be backed up.
For a BACKDS or HBACKDS
command, one of the following applies:
- The management class attribute ADMIN-OR-USER-COMMAND-BACKUP =
BOTH is not indicated.
- A management class attribute of ADMIN-OR-USER-COMMAND-BACKUP =
ADMIN is indicated, and the user is not DFSMShsm-authorized to back
up the data set.
For a data set processed during volume backup, ADMIN-OR-USER-COMMAND-BACKUP
= NONE is specified.
- 12
- The backup-while-open candidate data set is not available to be
backed up at the time of the request.
- 14
- The data set is eligible for backup-while-open processing, but DFSMShsm is
the datamover.
Note: Reason codes 90 and higher are not produced
unless you have installed a problem determination patch for volume
backup. For information about this patch, see the
topic on
"Determining
Why SMS-Managed Data Sets Are Not Processed" in Appendix C of
z/OS DFSMShsm Diagnosis.
- 16
- An abend or error occurred and cleanup was not completed before
continuing. A backup version should be successfully created during
the next backup.
- 17
- An abend or error occurred and cleanup was not completed before
starting a new source volume. A backup version should be successfully
created during the next backup.
- 18
- Backup of this data set was bypassed because of a previous error.
A backup version should be successfully created during the next backup.
- 19
- An internal error occurred.
- 20
- A backup version was not created because it would cause an existing
version with a non-expired RETAINDAYS value to roll-off.
- 90
- The management class attribute AUTO BACKUP = N prevents backup
of the data set.
- 91
- The backup installation-wide exit (ARCSAEXT) indicates the data
set should not be processed.
- 92
- The data set VTOC entry is not for the first segment of a key
range data set, or the data set VTOC entry is for the index component
of a key range data set.
- 93
- 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.
For
non-VSAM data sets, this reason code is issued when the data set sequence
number is not 1. This indicates the data set is part of a multivolume
data set, but is not the first segment of that data set.
- 94
- A backup version was not created because the data set was not
changed since the last time a backup version was made and this:
SETSYS INCREMENTALBACKUP(CHANGEDONLY)
was
specified.
- 95
- A backup version was not created because the data set was not
changed since the last time a backup version was made. SETSYS INCREMENTALBACKUP(ORIGINAL)
was specified and the existence of a backup version is based on the
last backup date in the catalog entry record.
- 96
- A backup version was not created because the data set was not
changed since the last time a backup version was made. SETSYS INCREMENTALBACKUP(ORIGINAL)
was specified and the existence of a backup version is based on the
last backup date in the MCB record.
- 97
- The number of days specified in the management class attribute
BACKUP FREQUENCY has not elapsed. The existence of a backup version
is based on the last backup date in the catalog
entry record.
- 98
- The number of days specified in the management class attribute
BACKUP FREQUENCY has not elapsed. The existence of a backup version
is based on the last backup date in the MCB
record.
System action
The BACKUP command processing of
the indicated data set ends. DFSMShsm processing continues.
Programmer response
Perform the action which corresponds to
the reason code you received. The values for reason-code are:
- Reascode
- Action
- 1
- Specify DFSMSdss as
the datamover for extended format data sets.
- 3
- Contact IBM® Support and
indicate to them that your installation has HSM as the default data
mover for backup of Large Format Data sets and that needs to be changed.
- 2
- See the system administrator to bring the data set under SMS management.
- 4
- Issue an ALTERDS or HALTERDS command for the data set and specify
a positive nonzero value for the VERSIONS parameter. Then reissue
the BACKDS or HBACKDS command.
- 5
- It may be possible to back up the data set from a different processing
unit in a multiple processing unit environment. Otherwise, a sufficient
level of DFSMShsm must
be installed on the system.
- 6
- Re-try backup on a level of DFSMS/DFSMShsm that does support large
format sequential data sets.
- 8
- If a BACKDS or HBACKDS command is failing
because the user is not authorized, perform one of the following:
- Issue the command from a DFSMShsm-authorized user.
- Associate the data set with a management class that does not require
the user to be DFSMShsm-authorized.
- If a data set is not backed up because ADMIN-OR-USER-COMMAND-BACKUP=NONE,
associate the data set with a management class that does not specify
ADMIN-OR-USER-COMMAND-BACKUP=NONE.
- 12
- Retry the backup operation when the data set is available, for
example, when the reorganization of a data set completes.
- 14
- Specify the DFSMSdss parameter
on the SETSYS DATAMOVER command.
- 16
- To pursue the source of this problem, save at least two hours
of PDA trace prior to the REAS16 failure and contact DFSMShsm Level
2 service.
- 17
- To pursue the source of this problem, save at least two hours
of PDA trace prior to the REAS17 failure and contact DFSMShsm Level
2 service.
- 18
- None.
- 19
- Contact IBM Support.
- 20
- Reissue the backup request on a z/OS® V1R11
or later system.
- 90
- If the data set should be considered eligible for backup, it needs
to be associated with a management class defined with AUTO BACKUP
= Y.
- 91
- If the data set should be considered eligible for backup, the
backup exit (ARCSAEXT) needs to be updated to not exclude the data
set from backup.
- 92
- No response required. DFSMShsm processes the key range data set
when it encounters the data set VTOC entry for the first segment of
the data set.
- 93
- No response required. DFSMShsm processes the VSAM data set when
it encounters the data set VTOC entry for the base data object.
For
a non-VSAM data set, processing occurs when the volume with a data
set sequence number of 1 is encountered.
- 94
- No response required. A current backup version exists.
- 95
- No response required. A current backup version exists.
- 96
- No response required. A current backup version exists.
- 97
- If a backup version was created before the BACKUP FREQUENCY defined
for the management class elapsed, perform one of the following:
- Issue the BACKDS or HBACKDS command to cause a backup version
to be created.
- Associate the data set with a management class whose definition
of BACKUP FREQUENCY is small enough to satisfy the data set’s backup
requirements.
- 98
- If a backup version was created before the BACKUP FREQUENCY defined
for the management class elapsed, perform one of the following:
- Issue the BACKDS or HBACKDS command to cause a backup version
to be created.
- Associate the data set with a management class whose definition
of BACKUP FREQUENCY is small enough to satisfy the data set’s backup
requirements.