Are you licensed for DFDSS? You can use it to clean up uncatalogued DASD
resident datasets. The JCL would look something like:

//JS010    EXEC  PGM=ADRDSSU,
//             REGION=0M
//INVOL    DD  DISP=SHR,
//             UNIT=SYSDA,
//             VOL=SER=......
//DUMMY    DD  DUMMY
//SYSPRINT DD  SYSOUT=*
//SYSUDUMP DD  SYSOUT=*
//ABNLIGNR DD  DUMMY
//SYSIN    DD  *
 COPY -
      DS( -
         BY((CATLG,EQ,NO))  -
         EXCLUDE(SYS1.**, -
                 CATALOG.** -
                ) -
         )  -
      SPHERE -
      PURGE -
      LIDD(INVOL)
      DELETE -
      FORCE -
      OUTDD(DUMMY)
/*

You might need to change the DSNs listed in the EXCLUDE list. Instead of
DD DUMMY, you might want to actually dump them to a tape for backup
purposes.

On Mon, 2011-05-09 at 23:22 -0700, Mohamed Juma wrote:
> What I mean that the data sets are not in catalog, but they are in VTOC of 
> the volume.
>  
> Mohamed Juma
> 
> --- On Mon, 5/9/11, Schwarz, Barry A <[email protected]> wrote:
> 
> 
> From: Schwarz, Barry A <[email protected]>
> Subject: Re: Removing entries of non-existing data sets from SMS volumes
> To: [email protected]
> Date: Monday, May 9, 2011, 2:58 PM
> 
> 
> Start by explaining what you mean by "a non-existent dataset."
> 
> Do you mean a catalog entry for which there is no corresponding dataset on 
> the indicated volume?  If that is the case, then there is no need to remove 
> it from the volume (since it is not there anyway).  But you do want to remove 
> it from the catalog.  The DELETE NOSCRATCH command as described in the Access 
> Method Services is the usual tool of choice.
> 
> For datasets erroneously catalogued on SMS volumes, the LISTCAT ALL command 
> will generate errors when it cannot extract information from the VVDS.  You 
> can list an entire catalog, hold the output, and use SDSF to search for the 
> errors.
> 
> If you know the volumes in question, the DCOLLECT, DIAGNOSE CATALOG, and 
> DIAGNOSE VVDS commands ((all from Access Method Services) may provide useful 
> information.  If you don't know the volumes, the DSMON program from the RACF 
> Auditor's Guide may provide useful information.
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
> Of Mohamed Juma
> Sent: Saturday, May 07, 2011 10:44 PM
> To: [email protected]
> Subject: Removing entries of non-existing data sets from SMS volumes
> 
> We are facing a problem to remove entries of non-existing data sets from SMS 
> volume,
> first how to check all volumes in that SMS group for the data sets which not 
> existing, second how to delete their entries.
> 
> ----------------------------------------------------------------------
> 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
> 
> ----------------------------------------------------------------------
> 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
-- 
John McKown
Maranatha! <><

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

Reply via email to