Hi, have you tried the TSO DELETE, instead of IDCAMS DELETE? I usually do this task trying first online (in 3.4 list) and if it doesn't work, with JCL batch. I have done it many times, and it works even if you get the HSM error message, if you have a reasonable recent version of zOS
regards, *Gonzalo Cengotita* 2017-08-21 13:21 GMT+02:00 Rodatz, William J < william.rod...@labor.alabama.gov>: > Hi, > > I want to thank everyone who responded to my inquiry regarding the > deletion of migrated datasets. It looks like all of the responses have > suggested using IDCAMS with the DELETE and NOSCRATCH control statements. I > tried that last week. I ran the job again this morning. Below is the job > log and the control statements I used. As you can see, a call is made to > DFHSM to do a recall prior to deletion. > > DELETE - > EH.FP78.RESBHSFL - > NOSCRATCH - > NONVSAM > > > ICH70001I WR99900 LAST ACCESS AT 05:52:53 ON MONDAY, AUGUST 21, 2017 > $HASP373 IDCAMS1 STARTED - INIT D - CLASS Y - SYS 9121 > IEF403I IDCAMS1 - STARTED - TIME=05.57.52 > ARC0050A DFSMSHSM IS NOT ACTIVE - START DFSMSHSM > ARC0051A JOB IDCAMS1 WAITING FOR DFSMSHSM TO RECALL DSN=EH.FP78.RESBHSFL > *06 ARC0055A REPLY 'GO' OR 'CANCEL' > > Thanks again for the responses. > > Bill > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Rodatz, William J > > Sent: Friday, August 18, 2017 10:41 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Removing Catalog Entries for Datasets That Do Not Exist > > > > Hello Everyone, > > > > Recently I discovered some datasets with "MIGRAT" as the volser. These > datasets had been migrated with DFHSM many years ago. My organization is > no longer running the product. I am attempting to remove the dangling > catalog entries which appears to be challenging. The pubs say to use > IEHPROGM with the SCRATCH function if (1) the dataset is non-SMS managed > and (2) you know the dataset's volser prior to migration. I don't what the > original volser was and I don't know why it matters. The catalog entry has > only the dataset name and "MIGRAT" for the volser. > > > > When I execute IEHPROGM, I get messages denoting that DFHSM is not > active. I am unable to move past this point. > > > > Does anyone have an idea how the catalog entries can be removed? Any > input would be greatly appreciated. > > > > Thank you. > > > > Bill > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
