Try this;
The DELETE data set name NOSCRATCH command can be used to uncatalog migrated
data sets. For this command to be used when RACF® protection is used for
DFSMShsm-owned data sets, two conditions must exist:
A RACF group of ARCCATGP must exist.
The user who issues the DELETE NOSCRATCH command must be authorized to
group ARCCATGP.
You'll need to run the batch job or logon using that specific group. It's not
enough to have your userid connected to it.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&[email protected]
------- Original Message -------
On Sunday, February 20th, 2022 at 12:32 PM, fred glenlake
<[email protected]> wrote:
> Hi List,
>
> I recently inherited DFHSM responsibilities at my account, previous person
> decided to take the money and run towards retirement. Just to see the lay of
> the land I ran an HSM AUDIT and it reported errors on a number of migrated
> datasets on both ML1 DASD and ML2 Tape. The Audit reported showed ERR 03
> errors such as:
>
> ERR or Userhlq.system.cntl NOT CATALOGED, HAS MIGRATION COPY +
>
> DFHSM.HHMIG.T290510.Userhlq.system.B2021
>
> I tried deleting the dataset using HDELETE and HSEND DELETE commands, did not
> seem to work. I also tried IDCAMS DELETE but did not work. I found a hit
> "https://bit.listserv.ibm-main.narkive.com/VxAz3kU0/dfhsm-uncatalog-migrated-dataset-how-to-fix";
> from many years ago that had a list of commands to do this. I followed the
> instructions and the entry in DFHSM still exists.
>
> DFHSM Uncatalog Migrated dataset - How to
> Fixhttps://bit.listserv.ibm-main.narkive.com/VxAz3kU0/dfhsm-uncatalog-migrated-dataset-how-to-fix
>
> Kenneth, 1) HSEND FIXCDS D dsn - will give you listing of the d record. You
> will see the ML1 volume(+000) and the funny name(+009C). 2) Do an ISPF 3.4
> for the ML1 volume found in 1
>
> bit.listserv.ibm-main.narkive.com
>
> 1) HSEND FIXCDS D dsn - will give you listing of the d record. You will
>
> see the ML1 volume(+000) and the funny name(+009C).
>
> 2) Do an ISPF 3.4 for the ML1 volume found in 1
>
> 3) Find the "funny" dataset name from 1
>
> 4) On the command line issue a delete of the dataset
>
> 5) Again on the command line issue HSEND FIXCDS A / DELETE
>
> 6) Issue HSEND FIXCDS D DSN DELETE using dsn from 1
>
> I am more than happy to continue with RTFM's but thus far nothing that
> addresses this situation.
>
> Any suggestions, recommendations would be greatly appreciated.
>
> Many thanks,
>
> Fred G.
>
> Sent from Outlookhttp://aka.ms/weboutlook
>
> ----------------------------------------------------------------------
>
> For IBM-MAIN subscribe / signoff / archive access instructions,
>
> send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
