Are you not yet using SMS-managed volumes and forcing all non-system
DASD datasets to be SMS-managed? If not, you should be.
SMS datasets are forced to be cataloged, even if the end-user out of
ignorance doesn't specify it properly in his JCL, and if some rare
system failure were to allow one to be uncataloged, running periodic
DIAGNOSEs against catalogs and VVDSs will catch that as an inconsistency.
Pre-SMS we used to worry about this kind of thing and run daily/weekly
cleanup of uncataloged datasets, but the problem completely disappeared
over a decade ago when we converted all application DASD datasets to SMS
and enforced this restriction via naming conventions, ACS routines, and
RACF.
I haven't seen an uncataloged DASD dataset for years, except for ones
Technical Support deliberately creates as part of system cloning on
non-SMS volumes.
Uncataloged datasets introduce a myriad of problems in dataset
management, tracking, and cleanup, not to mention that 99.9% of the time
when an end-user or application programmer creates one, they can't find
it, just think it was deleted somehow, and try to create another copy
somewhere else. Uncataloged DASD datasets should be disallowed by
installation standards and enforcement mechanisms like SMS & RACF should
be in place to prevent accidental creation in the first place.
Sivakumar, Manikandan wrote:
Folks,
I would like to know information how to list the uncatalog datasets. I
would like to know whether we can use IDCAMS utility or any other
utility. Thanks.
Regards, Mani
...
--
Joel C. Ewing, Fort Smith, AR [EMAIL PROTECTED]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
