Re: Removing Catalog Entries for Datasets That Do Not Exist

[Toni Cecil]

Hi Bill,
have you tried login with ARCCATGP and do a DELETE NSCR ??

HTH, A.Cecilio

2017-08-21 12:21 GMT+01: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

Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not Exist

[John Eells]

Tom Marchant wrote:

On Mon, 21 Aug 2017 12:40:50 -0400, John Eells wrote:


IEFBR14 won't allocate a migrated data set to delete it in a batch job
when IEFBR14_DELMIGDS(NORECALL) is specified in an active ALLOCxx member
of parmlib.  Instead, Allocation will call DFSMShsm to (effectively)
HDELETE the data set.

However, LEGACY is the default, and the data set will be allocated if
LEGACY is in effect.


And that doesn't help the OP who no longer has DFSMShsm.



Entirely true.  I just posted so people would realize NORECALL (and thus 
no allocation) is *not* the default.  Others got him going with DEL 
NOSCR, though.


--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not Exist

[Tom Marchant]

On Mon, 21 Aug 2017 12:40:50 -0400, John Eells wrote:

>IEFBR14 won't allocate a migrated data set to delete it in a batch job
>when IEFBR14_DELMIGDS(NORECALL) is specified in an active ALLOCxx member
>of parmlib.  Instead, Allocation will call DFSMShsm to (effectively)
>HDELETE the data set.
>
>However, LEGACY is the default, and the data set will be allocated if
>LEGACY is in effect.

And that doesn't help the OP who no longer has DFSMShsm.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not Exist

[John Eells]

IEFBR14 won't allocate a migrated data set to delete it in a batch job 
when IEFBR14_DELMIGDS(NORECALL) is specified in an active ALLOCxx member 
of parmlib.  Instead, Allocation will call DFSMShsm to (effectively) 
HDELETE the data set.


However, LEGACY is the default, and the data set will be allocated if 
LEGACY is in effect.


Allan Staller wrote:

The key is that if the dataset is allocated, HSM will be invoked.

DEL dsn NSCR does not allocate the dataset
IEFBR14 (optional) does not allocate the dataset. This was introduce w/zOS 2.1 
IIRC.
Iehprogm uncatlg will not allocate the dataset.




--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not Exist

[Allan Staller]

The key is that if the dataset is allocated, HSM will be invoked.

DEL dsn NSCR does not allocate the dataset
IEFBR14 (optional) does not allocate the dataset. This was introduce w/zOS 2.1 
IIRC.
Iehprogm uncatlg will not allocate the dataset. 

HTH,


It's been a few years since I worked in a shop with DFHSM but I do recall that 
IEHPROGM didn't require a recall but that may have been in the last decade (or 
millennium).

--

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, August 21, 2017 9:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not 
Exist

Typically for these types of cases, the problem is not the utility being used, 
but that the Entry MIGRAT(1/2) will force a recall.

Only way to get around it is to use the ARCCATGP.  Then IDCAMS, IEHPROGM, etc. 
will work.  You can do the delete noscratch easily then.

So batch job with GROUP=ARCCATGP on the JOBCARD or at TSO LOGON enter ARCCATGP 
in the GROUP field of the logon panel.




::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not Exist

[Dyck, Lionel B. (TRA)]

It's been a few years since I worked in a shop with DFHSM but I do recall that 
IEHPROGM didn't require a recall but that may have been in the last decade (or 
millennium).

--
Lionel B. Dyck 
Mainframe Systems Programmer - TRA

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, August 21, 2017 9:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not 
Exist

Typically for these types of cases, the problem is not the utility being used, 
but that the Entry MIGRAT(1/2) will force a recall.

Only way to get around it is to use the ARCCATGP.  Then IDCAMS, IEHPROGM, etc. 
will work.  You can do the delete noscratch easily then.

So batch job with GROUP=ARCCATGP on the JOBCARD or at TSO LOGON enter ARCCATGP 
in the GROUP field of the logon panel.


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Dyck, Lionel B. (TRA)
> Sent: Monday, August 21, 2017 7:50 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That 
> Do Not Exist
> 
> Wouldn't IEHPROGM be easier?
> 
> 
> --
> 
> Lionel B. Dyck
> Mainframe Systems Programmer - TRA
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of R.S.
> Sent: Monday, August 21, 2017 9:44 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do 
> Not Exist
> 
> To complement: ARCCATGP is *tricky*.
> It is NOT enough to be connected to the group. One has to logon with 
> ARCCATGP as current connect group.
> For TSO one has to provide his userid, password and the ARCCATGP as 
> the group.
> 
> HTH
> 
> --
> Radoslaw Skorupka
> Lodz, Poland
> 
> 
> 
> 
> 
> 
> 
> W dniu 2017-08-21 o 16:36, Allan Staller pisze:
> > My bad, it is *JUST* a group.
> >
> > Lizette provided the info in a later post. Thanks Lizette
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Elardus Engelbrecht
> > Sent: Monday, August 21, 2017 8:41 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist
> >
> > Allan Staller wrote:
> >
> >> See if you or your job has access to ARCCATGP in (IIRC) the RACF 
> >> facility class,
> > Sorry, but could you be kind to say what profile in that RACF 
> > FACILITY
> Class?
> >
> > AFAIK, ARCCATGP has no access to any profiles in RACF. (I have 
> > checked that
> in zSecure), I believe, just being a member, you get all the HSM goodies.
> >
> > Thanks in advance.
> >
> > Groete / Greetings
> > Elardus Engelbrecht
> >

--
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

Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not Exist

[Lizette Koehler]

Typically for these types of cases, the problem is not the utility being used, 
but that the Entry MIGRAT(1/2) will force a recall.

Only way to get around it is to use the ARCCATGP.  Then IDCAMS, IEHPROGM, etc. 
will work.  You can do the delete noscratch easily then.

So batch job with GROUP=ARCCATGP on the JOBCARD or at TSO LOGON enter ARCCATGP 
in the GROUP field of the logon panel.


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Dyck, Lionel B. (TRA)
> Sent: Monday, August 21, 2017 7:50 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not
> Exist
> 
> Wouldn't IEHPROGM be easier?
> 
> 
> --
> Lionel B. Dyck
> Mainframe Systems Programmer - TRA
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of R.S.
> Sent: Monday, August 21, 2017 9:44 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not
> Exist
> 
> To complement: ARCCATGP is *tricky*.
> It is NOT enough to be connected to the group. One has to logon with ARCCATGP
> as current connect group.
> For TSO one has to provide his userid, password and the ARCCATGP as the
> group.
> 
> HTH
> 
> --
> Radoslaw Skorupka
> Lodz, Poland
> 
> 
> 
> 
> 
> 
> 
> W dniu 2017-08-21 o 16:36, Allan Staller pisze:
> > My bad, it is *JUST* a group.
> >
> > Lizette provided the info in a later post. Thanks Lizette
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Elardus Engelbrecht
> > Sent: Monday, August 21, 2017 8:41 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist
> >
> > Allan Staller wrote:
> >
> >> See if you or your job has access to ARCCATGP in (IIRC) the RACF
> >> facility class,
> > Sorry, but could you be kind to say what profile in that RACF FACILITY
> Class?
> >
> > AFAIK, ARCCATGP has no access to any profiles in RACF. (I have checked that
> in zSecure), I believe, just being a member, you get all the HSM goodies.
> >
> > Thanks in advance.
> >
> > Groete / Greetings
> > Elardus Engelbrecht
> >

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not Exist

[Dyck, Lionel B. (TRA)]

Wouldn't IEHPROGM be easier?


--
Lionel B. Dyck 
Mainframe Systems Programmer - TRA


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: Monday, August 21, 2017 9:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Removing Catalog Entries for Datasets That Do Not Exist

To complement: ARCCATGP is *tricky*.
It is NOT enough to be connected to the group. One has to logon with ARCCATGP 
as current connect group.
For TSO one has to provide his userid, password and the ARCCATGP as the group.

HTH

--
Radoslaw Skorupka
Lodz, Poland







W dniu 2017-08-21 o 16:36, Allan Staller pisze:
> My bad, it is *JUST* a group.
>
> Lizette provided the info in a later post. Thanks Lizette
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Elardus Engelbrecht
> Sent: Monday, August 21, 2017 8:41 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist
>
> Allan Staller wrote:
>
>> See if you or your job has access to ARCCATGP in (IIRC) the RACF
>> facility class,
> Sorry, but could you be kind to say what profile in that RACF FACILITY Class?
>
> AFAIK, ARCCATGP has no access to any profiles in RACF. (I have checked that 
> in zSecure), I believe, just being a member, you get all the HSM goodies.
>
> Thanks in advance.
>
> Groete / Greetings
> Elardus Engelbrecht
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> ::DISCLAIMER::
> 
>
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only.
> E-mail transmission is not guaranteed to be secure or error-free as 
> information could be intercepted, corrupted,
> lost, destroyed, arrive late or incomplete, or may contain viruses in 
> transmission. The e mail and its contents
> (with or without referred errors) shall therefore not attach any liability on 
> the originator or HCL or its affiliates.
> Views or opinions, if any, presented in this email are solely those of the 
> author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction, 
> dissemination, copying, disclosure, modification,
> distribution and / or publication of this message without the prior written 
> consent of authorized representative of
> HCL is strictly prohibited. If you have received this email in error please 
> delete it and notify the sender immediately.
> Before opening any email and/or attachments, please check them for viruses 
> and other defects.
>
> 
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



==


--
 Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

 This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

 mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII 
Wydział Gospodarczy 

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Lizette Koehler]

I am glad to help

I am also glad IBM gave at least a way to do this.  But I would have preferred 
a Facility in the ARC stuff.  Easier to remember and see.  The use of a GROUP 
do to this seems a little kludgy


Lizette

;-D


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Allan Staller
> Sent: Monday, August 21, 2017 7:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist
> 
> My bad, it is *JUST* a group.
> 
> Lizette provided the info in a later post. Thanks Lizette
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Elardus Engelbrecht
> Sent: Monday, August 21, 2017 8:41 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist
> 
> Allan Staller wrote:
> 
> >See if you or your job has access to ARCCATGP in (IIRC) the RACF
> >facility class,
> 
> Sorry, but could you be kind to say what profile in that RACF FACILITY Class?
> 
> AFAIK, ARCCATGP has no access to any profiles in RACF. (I have checked that
> in zSecure), I believe, just being a member, you get all the HSM goodies.
> 
> Thanks in advance.
> 
> Groete / Greetings
> Elardus Engelbrecht
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist

[R.S.]

To complement: ARCCATGP is *tricky*.
It is NOT enough to be connected to the group. One has to logon with 
ARCCATGP as current connect group.
For TSO one has to provide his userid, password and the ARCCATGP as the 
group.


HTH

--
Radoslaw Skorupka
Lodz, Poland







W dniu 2017-08-21 o 16:36, Allan Staller pisze:

My bad, it is *JUST* a group.

Lizette provided the info in a later post. Thanks Lizette

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Monday, August 21, 2017 8:41 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist

Allan Staller wrote:


See if you or your job has access to ARCCATGP in (IIRC) the RACF
facility class,

Sorry, but could you be kind to say what profile in that RACF FACILITY Class?

AFAIK, ARCCATGP has no access to any profiles in RACF. (I have checked that in 
zSecure), I believe, just being a member, you get all the HSM goodies.

Thanks in advance.

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN




==


   --
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII 
Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców 
KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał 
zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych.
   


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Allan Staller]

My bad, it is *JUST* a group.

Lizette provided the info in a later post. Thanks Lizette

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Monday, August 21, 2017 8:41 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist

Allan Staller wrote:

>See if you or your job has access to ARCCATGP in (IIRC) the RACF 
>facility class,

Sorry, but could you be kind to say what profile in that RACF FACILITY Class?

AFAIK, ARCCATGP has no access to any profiles in RACF. (I have checked that in 
zSecure), I believe, just being a member, you get all the HSM goodies.

Thanks in advance.

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Lizette Koehler]

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.arci000/racf.htm




z/OS DFSMS
z/OS DFSMShsm Implementation and Customization Guide
Implementing DFSMShsm
Authorizing and protecting DFSMShsm commands and resources



DFSMShsm to recall the data set before the operation is performed unless you 
take action.

To allow certain authorized users to perform these operations on migrated data 
sets without recalling them, perform the following steps.

Define a RACF catalog maintenance group named ARCCATGP.

Example: ADDGROUP (ARCCATGP)
Connect the desired users to that group.
If you specify . . .Then . . .
CONNECT (userid1,. . .,useridn ) GROUP(ARCCATGP) AUTHORITY(USE) Each 
user (userid1,. . .,useridn) is authorized to bypass automatic recall for 
catalog operations.

Only when such a user is logged on under group ARCCATGP does DFSMShsm bypass 
the automatic recall for UNCATALOG, RECATALOG, and DELETE/NOSCRATCH requests 
for migrated data sets.
Example: The following LOGON command demonstrates starting a TSO session under 
ARCCATGP:

   LOGON userid | password GROUP(ARCCATGP)



Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Elardus Engelbrecht
> Sent: Monday, August 21, 2017 6:41 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist
> 
> Allan Staller wrote:
> 
> >See if you or your job has access to ARCCATGP in (IIRC) the RACF
> >facility class,
> 
> Sorry, but could you be kind to say what profile in that RACF FACILITY Class?
> 
> AFAIK, ARCCATGP has no access to any profiles in RACF. (I have checked that
> in zSecure), I believe, just being a member, you get all the HSM goodies.
> 
> Thanks in advance.
> 
> Groete / Greetings
> Elardus Engelbrecht
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Elardus Engelbrecht]

Allan Staller wrote:

>See if you or your job has access to ARCCATGP in (IIRC) the RACF facility 
>class,

Sorry, but could you be kind to say what profile in that RACF FACILITY Class?

AFAIK, ARCCATGP has no access to any profiles in RACF. (I have checked that in 
zSecure), I believe, just being a member, you get all the HSM goodies.

Thanks in advance.

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Allan Staller]

See if you or your job has access to ARCCATGP in (IIRC) the RACF facility class,

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rodatz, William J
Sent: Monday, August 21, 2017 6:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Removing Catalog Entries for Datasets That Do Not Exist

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


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Elardus Engelbrecht]

Rodatz, William J wrote:

>I wanted to let everyone that I have been able to remove the migrated dataset 
>names from the catalog.  Lizette Koehler suggested that try using ARCCATGP 
>which is a RACF group.

Excellent! I am glad for your part.

I did a little RTFM and came across this snippet in "DFSMShsm Storage 
Administration":

"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."

I totally forgot about this group, looking it up in my RACF I see I did created 
it in year 2006 to resolve a similar problem for my HSM gurus... ;-)

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Rodatz, William J]

I wanted to let everyone that I have been able to remove the migrated dataset 
names from the catalog.  Lizette Koehler suggested that try using ARCCATGP 
which is a RACF group.  If you are connected to this group  you can delete 
migrated datasets without first recalling them.  I issued the RACF command:

CONNECT WR99900 GROUP(ARCCATGP) AUTHORITY(USE)

I then added GROUP=ARCCATGP to my job card and executed IDCAMS with the DELETE 
and NOSCRATCH control statements and got RC=0.  I'm glad to resolve this.

My thanks to everyone who responded to my posting.

William Rodatz



-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

Re: Removing Catalog Entries for Datasets That Do Not Exist [Public Information]

[Styles, Andy (ITS zPlatform Services)]

Classification: Public
I imagine that a vendor product like CIM or TACM could surgically zap the 
catalog to remove the entries.

I checked with one of our storage folks, he suggested that the catalog entry 
actually has MIGRAT (I've checked that on one of my own migrated datasets with 
LISTC), and it's actually the listing that adds the "1" or "2" depending on the 
device type of the catalog entry. He suggests:

"As far as I can remember, the actual entry for a migrated entry is MIGRAT (as 
that is a 6 char VOLSER entry). It is the listing of it that adds the suffix 1 
or 2 depending on the catalog device type (either disk or tape) - but - to get 
rid of the entries, you need to connect to the ARCCATGP RACF group. That will 
cause allocation to just delete it rather than drive a recall attempt."

Sure enough that appears to be a valid group - whether you still need DFHSM to 
be active, though..

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.arci000/endus.htm

Not really my area, so I'm hoping some of this will help!

Andy Styles
z/Series Systems Programmer


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Dawes
Sent: 21 August 2017 12:50
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist [Public 
Information]

-- This email has reached the Bank via an external source --
 

Bill,I checked some of our migrated dsns.  They have the catalog entry as 
MIGRAT1 or MIGRAT2.  The status of MIGRAT (folks at FDR please correct me if I 
am wrong) indicates that the dsn was archived by FDR.

  From: "Usher, Darrold" <014f796d148d-dmarc-requ...@listserv.ua.edu>
 To: IBM-MAIN@LISTSERV.UA.EDU
 Sent: Friday, 18 August 2017, 11:58
 Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist [Public 
Information]
   
Did your try DEL 'dsname' NSCR?

Classification: Public Information


-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: EXTERNAL: 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

   

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. 
Registered in Scotland no. SC95000. Telephone: 0131 225 4555. Lloyds Bank plc. 
Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England 
and Wales no. 2065. Telephone 0207626 1500. Bank of Scotland plc. Registered 
Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. 
Telephone: 03457 801 801. Cheltenham & Gloucester plc. Registered Office: 
Barnett Way, Gloucester GL4 3RL. Registered in England and Wales 2299428. 
Telephone: 0345 603 1637

Lloyds Bank plc, Bank of Scotland plc are authorised by the Prudential 
Regulation Authority and regulated by the Financial Conduct Authority and 
Prudential Regulation Authority.

Cheltenham & Gloucester plc is authorised and regulated by the Financial 
Conduct Authority.

Halifax is a division of Bank of Scotland plc. Cheltenham & Gloucester Savings 
is a division of Lloyds Bank plc.

HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in 
Scotland no. SC218813.

This e-mail (including any attachments) is private and confidential and may 
contain privileged material. If you have received this e-mail in error, please 
notify the sender and delete it (including any attachments) immediately. You 
must not copy, 

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Gonzalo Cengotita]

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

Re: Removing Catalog Entries for Datasets That Do Not Exist [Public Information]

[John Dawes]

Bill,I checked some of our migrated dsns.  They have the catalog entry as 
MIGRAT1 or MIGRAT2.  The status of MIGRAT (folks at FDR please correct me if I 
am wrong) indicates that the dsn was archived by FDR.

  From: "Usher, Darrold" <014f796d148d-dmarc-requ...@listserv.ua.edu>
 To: IBM-MAIN@LISTSERV.UA.EDU 
 Sent: Friday, 18 August 2017, 11:58
 Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist [Public 
Information]
   
Did your try DEL 'dsname' NSCR?

Classification: Public Information


-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: EXTERNAL: 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

   

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist

[van der Grijn, Bart (B)]

Bill, not all the replies were to use DELETE NOSCRATCH. I suggested using the 
following sequence: 
- Create a new catalog (a throw-away catalog used just for this cleanup)
- REPRO MERGECAT your entries to this new catalog
- Delete the catalog (with RECOVERY)

As far as I know the above steps will not try to interact with HSM. I use this 
same approach when we have orphaned catalog entries of old archived datasets. 

Bart

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rodatz, William J
Sent: Monday, August 21, 2017 7:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Removing Catalog Entries for Datasets That Do Not Exist

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

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Dyck, Lionel B. (TRA)]

Why not use IEHPROGM to do the uncatalog

//UNCAT  EXEC PGM=IEHPROGM
//SYSPRINT  DD SYSOUT=*
//SYSIN DD *
  UNCATLG DSNAME=name
/*

--
Lionel B. Dyck 
Mainframe Systems Programmer - TRA

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rodatz, William J
Sent: Monday, August 21, 2017 6:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Removing Catalog Entries for Datasets That Do Not Exist

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

Removing Catalog Entries for Datasets That Do Not Exist

[Rodatz, William J]

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

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Lizette Koehler]

If you have access to ARCCATGP then you can do a DEL namehere NOSCRATCH

If you do not, then a RECALL Will be attempted.

See if your security product has ARCCATGP defined and that you can use it.

Then either LOGON to TSO with GROUP ARCCATGP or use a batch job with
GROUP=ARCCATGP


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Rodatz, William J
> Sent: Friday, August 18, 2017 8: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

Re: Removing Catalog Entries for Datasets That Do Not Exist

[van der Grijn, Bart (B)]

IIRC, the approach I use is: 
- Create a new catalog
- REPRO MERGECAT the entries you want to delete to the new catalog
- Delete the catalog with RECOVERY

Bart

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rodatz, William J
Sent: Friday, August 18, 2017 11: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

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Allan Staller]

As others have said, DEL 'dsname' NSCR will fix you up.

However, I am aware of at least one other product that also uses this 
convention.
Be careful!

-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


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist [Public Information]

[Longabaugh, Robert E]

If you are not running DFHSM are you running any other product that could cause 
MIGRAT entries?   When CA Disk archives data sets, they are recataloged to 
MIGRAT with DEVT(C4C9E2D2).  In that case the catalog entry is legitimate.

Bob Longabaugh
CA Technologies 
Storage Management

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Usher, Darrold
Sent: Friday, August 18, 2017 10:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist [Public 
Information]

CAUTION: This email originated from outside of CA. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.


Did your try DEL 'dsname' NSCR?

Classification: Public Information


-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: EXTERNAL: 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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist [Public Information]

[Usher, Darrold]

Did your try DEL 'dsname' NSCR?

Classification: Public Information


-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: EXTERNAL: 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

Re: Removing Catalog Entries for Datasets That Do Not Exist

[Burrell, Todd]

Wouldn't a simple IDCAMS DELETE NSCR work?  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rodatz, William J
Sent: Friday, August 18, 2017 11: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



This email transmission and any accompanying attachments may contain CSX 
privileged and confidential information intended only for the use of the 
intended addressee. Any dissemination, distribution, copying or action taken in 
reliance on the contents of this email by anyone other than the intended 
recipient is strictly prohibited. If you have received this email in error 
please immediately delete it and notify sender at the above CSX email address. 
Sender and CSX accept no liability for any damage caused directly or indirectly 
by receipt of this email.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Removing Catalog Entries for Datasets That Do Not Exist

[Rodatz, William J]

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