I confess to not having digested every post in this thread, but some additional (or restated) observations:
1. For 'a long time now', simple 'd' on a DSLIST is converted automatically to HDELETE for migrated data sets. And nothing gets recalled in the process. I just tested this. 'del' is not converted because that's a TSO command, not a DSLIST operative. 2. Once sorted by VOLUME, VSAM clusters and their data/index components are segregated in the list with *VSAM* at the top, components below by volser. So first 'd' the cluster names, then refresh the list to remove the now-deleted components. 3. Block commands are your friend. For a group of data sets to delete, type '//d' on the first one, '//' on the last. Didn't test this time, but I believe that you can scroll down many screens before the '//', so when you hit <Enter>, all commands will be processed before the list is redisplayed. 4. Once the block command is issued, you get a chance to 'bypass further prompting'. If you've set it up right, do so. If not, oops. 5. Not the best time for a coffee break in any case because, for a lengthy list, you'll get back a 'data set deleted' message for every one, requiring you to periodically hit <Enter> to clear the screen. Good task for your intern. I haven't played with this much, but in a recent release, we now have wild card capabilities in IDCAMS. Very efficient if coded right. If not, oops. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Neil Duffee <[email protected]> To: [email protected], Date: 02/21/2014 03:23 PM Subject: Re: Deleting multiple data sets Sent by: IBM Mainframe Discussion List <[email protected]> Again, daily digest delay caveat insert... Gil: once in DsList, use sort on any two columns ie. SORT DSORG VOLUME. Then you can move to your grouped clusters (Vol= *VSAM*) for D line commands followed by the Migrate Volumes (Vol=Migrat*) for HDelete. Unfortunately, (in v1.12 anyway), it appears EXCLUDE ALL & FIND ALL only work on the names. (tho' X ALL '.DATA ' & X ALL '.INDEX ' might reduce the displayed information in the DsOrg=VS section) [No, it *still* doesn't operate in parallel.] Another thought... you wouldn't be lucky enough to use the same number of levels in your test naming scheme ie. HLQ.LV1.LV2.LV3.LLQ[.DATA|.INDEX]? If so, removing "Include Additional Qualifiers" would drop all the .DATA & .INDEX entries. "Do you feel lucky, punk? Do ya? Go ahead, make my day." *grin* Well, even if you have just, say, 3 & 5, it could be done in two lists to ease your burden. Even something like HLQ.**.TST0221.*.* could be viable. --------> signature = 6 lines follows <-------- Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada telephone:1 613 562 5800 x4585 fax:1 613 562 5161 mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee “How *do* you plan for something like that?” Guardian Bob, Reboot “For every action, there is an equal and opposite criticism.” “Systems Programming: Guilty, until proven innocent” John Norgauer 2004 -----Original Message----- From: Paul Gilmartin [mailto:[email protected]] Sent: February 20, 2014 21:29 Subject: Re: Deleting multiple data sets On Thu, 20 Feb 2014 20:17:46 -0600, Mike Schwab wrote: >HDEL in front of each dataset name, instead of D. >Type HDEL on the first one, = on the rest. > Some of them aren't migrated. But I could go back and get them later. Actually, I think DSLIST is smart enough to DTRT if I just type D. (But I must type DEL rather than D in front of the clusters, else I hang on a prompt. And that fills up my screen so my coffee break is again interrupted, by the "***".) SORT VOL helps a lot. (Is there any way to get DSLIST to show only the PS and PO data sets and the clusters, and omit the .INDEX and .DATA components? I know some people like to see them; to me they're just a distraction.) And it doesn't operate in parallel. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
