ARC1115I

Explanation
 A delete request for a migrated data set was received
by DFSMShsm.
The request specified a VSAM component name or cluster name, or the
migration copy data set name. If the request came from the SVC 29
intercept or from the SMS subsystem delete intercept, DFSMShsm does
not support deletion of migrated data sets using any of these names.
For any other delete request source, DFSMShsm will only delete a VSAM data set
if the base cluster name is used on the request, and will only delete
a non-VSAM data set if the original data set name is used on the request.
 The
data set name is given in the preceding ARC1001I message, along with
a reascode. The reascode indicates
the type data set name used, and has the following meanings:  Reascode
Meaning
01
The name used on the request was a data component name.
02
The name used on the request was an index component name.
03
The name used on the request was a path name.
04
The name used on the request was an alternate index (AIX®) cluster name.
05
The name used on the request was a base cluster name from either
the SVC 29 or SMS subsystem delete intercept.
06
The name used on the request was the migration copy data set name.

System action
 The delete request fails. If the request was
processed through SVC 26 and an alternate index cluster name was specified,
the data set will be recalled and the delete request for the AIX will be processed by catalog
management. DFSMShsm processing
continues.

Programmer response
 A request through SVC 29 or the SMS Subsystem
should not be made with a VSAM cluster or component name. You should
modify the job or program to issue the AMS DELETE command, specifying
the name of the cluster that you want to delete. If you want to delete
an alternate cluster, you should recall the data set first, then issue
the AMS DELETE command for the AIX.

Source
 DFSMShsm