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),
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:
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
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
