I already have the list of backups and I can create a million+ line JCL but 
would prefer not to. It would be best if HSM would simply delete the backups 
that are no longer valid once I change the Management class definition. I don't 
know about you, but that seems quite reasonable to me.

However, this is not the case. Removing the backup requirement from the 
Management class definition, I am still left with all the backups even after 
HSM Space Management and a run of EXPIREBV.

Is there really no better solution to this?



David G. Schlecht | Information Technology Professional
State of Nevada | Department of Administration | Enterprise IT Services
T:(775)684-4328 | F: (775) 684‐4324 | E:dschle...@admin.nv.gov <-- New Address


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mark Zelden
Sent: Wednesday, February 06, 2013 1:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Deleting old HSM backups

Even without CSI, as long as there is a list it can just be edited (chose your 
method, ISPF, rexx program, whatever) to have  DELETE '...name...' 
in a flat file and executed in TSO batch or used as input to IDCAMS
in batch.     Using ISPF 3.4 and saving the list would work.  May
have to do that in batch also if some pattern can be used to match millions at 
once (to possibly increase allocation amounts).

Running this would be quicker than ISPF 3.4 (modify "L" or pass the parm as 
needed for HLQ / pattern)

PROC 0 L(&SYSUID)  G(SAVE)                                           
 /*                                                         */       
 /* Quick ISPF save of data set names. This is much quicker */       
 /* than using OPT 3.4, because it does not do an obtain    */       
 /* for each data set in the list because of STATS(NO).     */       
 /* The dsn created will be USERID.SAVE.DATASETS            */       
 /*                                                         */       
 ISPEXEC CONTROL ERRORS RETURN                                       
 ISPEXEC LMDINIT LISTID(LISTID)  LEVEL(&L)                           
 ISPEXEC LMDLIST LISTID(&LISTID) OPTION(SAVE) STATS(NO) GROUP(&G)    
 WRITE COMPLETE!! RETURN CODE WAS &LASTCC                            
 ISPEXEC LMDFREE LISTID(&LISTID)                                     

--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS       
mailto:m...@mzelden.com                                        
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://expertanswercenter.techtarget.com/


On Wed, 6 Feb 2013 15:27:24 -0500, Don Williams <donb...@gmail.com> wrote:

>Many years ago, I wrote a REXX EXEC to mass delete migrated files. It calls
>IGGCSI00 with a wilcard search argument to build a list of matching data set
>names to be deleted.  I've deleted many thousands of migrated data sets with
>"one" command, but millions would probably exceed its capacity. However, you
>could modify IBM's SYS1.SAMPLIB(IGGICSRX) to delete them.
>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>> On Behalf Of David G. Schlecht
>> Sent: Tuesday, February 05, 2013 5:25 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Deleting old HSM backups
>>
>> We have been backing up millions of unnecessary datasets. I am changing
>> HSM to not back them up but would like a reasonably easy way to delete
>> the millions of backups that already exist.
>>
>> Is there anything short of generating millions of lines of JCL. Is
>> there any way to get HSM to delete these backups?
>>
>> David G. Schlecht | Information Technology Professional
>> State of Nevada | Department of Administration | Enterprise IT Services
>>
>>
>> ________________________________
>> This communication, including any attachments, may contain confidential
>> information and is intended only for the individual or entity to which
>> it is addressed. Any review, dissemination or copying of this
>> communication by anyone other than the intended recipient is strictly
>> prohibited. If you are not the intended recipient, please contact the
>> sender by reply e-mail and delete all copies of the original message.
>>
>> ----------------------------------------------------------------------
>> 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

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

Reply via email to