Explanation
A request to DFSMShsm for a backup of data set
dsname failed.
The NEWNAME parameter or one of its associated keywords was specified
on the backup request. The reason for the failure is explained as
determined by the
retcode.
- Retcode
- Meaning
- 2
- DATE, TIME, SPHERE, or GENVSAMCOMPNAMES specified without NEWNAME.
- 3
- GENVSAMCOMPNAMES specified without required YES/NO parameter.
- 4
- TIME specified without DATE.
- 6
- NEWNAME specified with VOLUME and UNIT.
- 8
- Multiple data sets were specified for backup to the new name newdsname.
- 10
- Dsname and newdsname are
the same.
- 12
- Invalid date specified.
- 14
- Invalid time specified.
- 16
- Data set dsname is uncataloged.
- 18
- Data set dsname is migrated.
- 20
- Backup of data set dsname is not supported
with the NEWNAME parameter.
- 22
- DFSMShsm internal
error.
- 24
- Dsname is a VSAM data set, and newdsname is
uncataloged or migrated. DFSMShsm is unable to assign the proper
new names to the data and index components.
- 26
- Data set newdsname is uncataloged or has been
migrated outside of DFSMShsm, and data set dsname is
VSAM with associated AIX/PATH components. Therefore, DFSMShsm is
unable to determine the new names to assign to the AIX/PATH components.
If the data set is cataloged and was not migrated outside of DFSMShsm,
an error occurred while reading a cds record associated with data
set newdsname.
- 28
- Data sets dsname and newdsname do
not have the same number of AIXs, PATHs on the AIX®, and/or PATHs on the base cluster.
- 30
- Error occurred while reading a cds record associated with data
set newdsname.
- 32
- User not authorized to data set newdsname,
or error processing RACF® authority
check.
- 34
- Error processing data set newdsname.
- 36
- The maximum number of backup versions DFSMShsm is to maintain for
data set newdsname is zero. Either an (H)ALTERDS
command was issued for the data set, and the value specified for VERSIONS
is zero, or if never specified on an (H)ALTERDS command, the value
specified for VERSIONS on the SETSYS command is zero.
- 38
- Data set newdsname has a retired backup version.
- 40
- A backup version with the specified date and time already exists
for data set newdsname.
- 42
- Error occurred while invoking the ACS routines for data set newdsname.
- 44
- Error occurred while obtaining the management class definition
for data set newdsname.
- 46
- Management class attributes indicate that data set newdsname is
not eligible to back up. One of the following applies:
- A non-DFSMShsm-authorized user issued the command and management
class attribute ADMIN-OR-USER-COMMAND-BACKUP=BOTH is not indicated.
- A DFSMShsm-authorized user issued the command and management class
attribute ADMIN-OR-USER-COMMAND-BACKUP=NONE is indicated.
- 48
- Only one AIX and one PATH
can exist for the data set to back up as well as the data set specified
as the NEWNAME parameter.
- 50
- Data sets dsname and newdsname do
not have the same SMS-managed/non-SMS-managed status.
- 52
- A GETMAIN error occurred.
- 54
- Data sets dsname and newdsname do
not have the same data set organization.
- 56
- Data sets dsname and newdsname do
not have the same base cluster structure. One data set has an index
component, and the other does not.
- 58
- The date specified with the DATE keyword is prior to the date
of the oldest existing backup version of data set newdsname,
and the maximum number of backups of this data set has been reached.
Therefore, the version was rolled-off.
- 60
- RETAINDAYS was specified with NEWNAME and DATE.
Creating a new version with the specified date and retention period
would result in a backup copy that has already expired.
- 62
- RETAINDAYS was specified with NEWNAME and DATE,
and the specified date is earlier than the date when the most recent
retained backup copy was created. This would result in creating a
backup version within the set of existing retained copies, which is
not allowed.
System action
The backup request fails. DFSMShsm processing continues.
Programmer response
Review and resolve the cause of the problem
and reissue the backup request.
- Retcode
- Meaning
- 2
- Reissue the backup request with the NEWNAME keyword.
- 3
- Reissue the backup request with the proper GENVSAMCOMPNAMES parameter.
- 4
- Reissue the backup request with the DATE keyword, or remove the
TIME keyword and reissue the backup request.
- 6
- Reissue the backup request without the VOLUME and UNIT keywords.
- 8
- Reissue the backup request specifying a single, fully-qualified
data set name as the data set to be backed up.
- 10
- Reissue the backup request without the NEWNAME keyword, or correct
the NEWNAME parameter and reissue the command.
- 12
- Reissue the backup request and specify the date in the following
format: yyyy/mm/dd. Ensure that the date specified
is not beyond the current date.
- 14
- Reissue the backup request and specify the time if the following
format: hhmmss. If the current date is specified,
ensure the time is not beyond the current time.
- 16
- Determine if the correct data set name was specified. DFSMShsm only
supports the NEWNAME keyword for cataloged data sets.
- 18
- Recall the data set and then reissue the backup request.
- 20
- Some data set types, such as the following, are not supported
for backup with the NEWNAME parameter: User labeled sequential non-empty
data sets, ICF catalogs, unmoveable data sets with one extent, and
APF authorized libraries.
- 22
- Contact the IBM® Support
Center.
- 24
- Reissue the backup request with the GENVSAMCOMPNAMES(YES) parameter.
- 26
- If the data set is uncataloged or was migrated outside of DFSMShsm,
reissue the backup request with the SPHERE(NO) parameter. Otherwise,
contact the IBM Support Center.
- 28
- Reissue the backup request with the SPHERE(NO) parameter.
- 30
- Contact the IBM Support
Center.
- 32
- If RACF denied access,
there is an associated RACF message.
If the data set name and DSCB do not match, there is an associated
access method message. If an I/O error caused the reading of the JFCB
to fail, an associated error message can be found in the DFSMShsm job
log SYSMSG data set. Respond to the associated message.
- 34
- See the corresponding message ARC1356I for
further explanation of the error.
- 36
- Issue an (H)ALTERDS command for the data set and specify a positive
non-zero value for the VERSIONS parameter. Then reissue the backup
request.
- 38
- Determine if the retired version must be maintained. Issue the
BDELETE command to delete the retired version and then reissue the
backup request.
- 40
- Determine if the correct date and time were specified on the command.
If necessary, use the BDELETE command to delete the existing version
with the same timestamp. Then reissue the backup request.
- 42
- If SMS is active, contact the IBM Support
Center.
- 44
- If data set newdsname is cataloged, list the
catalog information for the data set to determine the management class
name. See message ARC0935I in
the command activity log for the specific failure. Define the management
class if it does not exist. If the management class exists, contact
the IBM Support Center.
- 46
- If the command failed 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 the command failed 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.
- 48
- Reissue the command with the SPHERE(NO) parameter.
Note: When DFSMShsm backs
up a data set with the SPHERE(NO) option, the user must rebuild any
associated AIXs/PATHs when the data set is recovered.
- 50
- Determine if the correct data set names were specified on the
command. If an incorrect data set name was specified, reissue the
backup request with the proper data set names.
- 52
- Contact the IBM Support
Center.
- 54
- Determine if the correct data set names were specified on the
command. If an incorrect data set name was specified, reissue the
backup request with the proper data set names.
- 56
- Determine if the correct data set names were specified on the
command. If an incorrect data set name was specified, reissue the
backup request with the proper data set names.
- 58
- Determine if any of the existing backup versions can be deleted
with the (H)BDELETE command. Then reissue the BACKDS NEWNAME DATE
command.
- 60
- Ensure that the specified DATE and RETAINDAYS parameters
are correct. If necessary, reissue the backup request with the proper
parameters.
- 62
- Ensure that the date specified on the backup request
is correct. If the specified date was correct, and this new version
must be created, either reissue the request specifying a date that
is after the date of the most recent retained backup copy, or use
the BDELETE command to delete all retained copies with dates after
the date specified on the command and then reissue the original request.
Issue the LIST DATASETNAMES command to obtain a list of all retained
backup copies and corresponding dates for this data set.