How To
Summary
When trying to delete catalog entries that have the volser of MIGRAT but are not found in HSM, an ARC1102I error message will be encountered due to the automatic recall of the data set.
To delete these catalog entries, use the ARCCATGP group and the IDCAMS DELETE 'dsname' NOSCRATCH command to bypass the automatic recall of the data set and remove the catalog entry.
Objective
To delete catalog entries with volser of MIGRAT and are not known to HSM.
Environment
Storage administrators who are responsible for migrated data sets and backup versions can be authorized to process catalogs without recalling the migrated data sets and backup versions.
In processing units with both DFSMShsm and RACF® active, issuing the UNCATALOG, RECATALOG, or DELETE/NOSCRATCH command against a migrated data set causes DFSMShsm to recall the data set before the operation is performed unless you take action.
In processing units with both DFSMShsm and RACF® active, issuing the UNCATALOG, RECATALOG, or DELETE/NOSCRATCH command against a migrated data set causes DFSMShsm to recall the data set before the operation is performed unless you take action.
There has been a specific scenario that can cause this type of issue where there is a catalog entry showing MIGRAT but with no MCD record for the data set, resulting in an ARC1102I on a RECALL or DELETE.
In this scenario, suppose there is an environment that has multiple systems sharing HSM CDS's but does not have all aliases defined pointing to the same shared catalogs. For example, HLQ hlq1 is defined as an alias on SYS1 pointing to catalog CATALOG1. However on SYS2, there is no alias for this HLQ defined. Data set hlq1.TEST is cataloged in the master catalog for SYS2 with a volser of MIGRAT and is not cataloged at all on SYS1.
When HSM expiration processing runs on SYS1, HSM will scan the MCDS and for any MCD records that exist. It will verify whether the data set is still cataloged. Since this data set is not cataloged, HSM will expire it based on either the expiration date, retention limit or management class definitions. Once HSM expires the data set, any attempt to recall the data set on SYS2 will fail.
The catalog entry in the master catalog on SYS2 will need to be deleted using IDCAMS DELETE 'dsname' NOSCRATCH which will require the user to be logged on to TSO with ARCCATGP group, or a batch job with GROUP=ARCCATGP on the job card can be submitted.
Steps
ARCCATGP procedure:
- Create a RACF group called ARCCATGP (if it is not already defined).
- Connect the userid to this group with AUTHORITY(USE).
- Logon to TSO specifying ARCCATGP group on the logon.
- Go to ISPF 3.4 and display the data set.
- Issue a DELETE NOSCRATCH to remove the catalog entry or from option 6 of TSO, DELETE 'dsn' NOSCRATCH.
Recommendation:
Ensure that all aliases defined are the same on all systems that share HSM CDS's so that data sets do not get deleted prematurely.
Ensure that all aliases defined are the same on all systems that share HSM CDS's so that data sets do not get deleted prematurely.
Related Information
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB56","label":"Z HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG90","label":"z\/OS"},"ARM Category":[{"code":"a8m0z0000000AK3AAM","label":"DFSMS-\u003EHSM-\u003ERecall"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.10.0;1.11.0;1.12.0;1.9.0;2.3.0;2.4.0;2.5.0;3.1.0;3.2.0"}]
Was this topic helpful?
Document Information
Modified date:
05 June 2025
UID
ibm17235097