If I remember well RSVP from Broadcom did that. If you have it ?

Resiliency Services on Z Mainframe
alain.benveni...@kyndryl.com 

> Le 25 juil. 2022 ร  10:13, Jack Zukt <jzuk...@gmail.com> a รฉcrit :
> 
> ๏ปฟHi,
> Thank you for your input. Using DFDSS like that would be an option.
> However, there are over eight thousand volumes in this system and that
> would be a lot of JOBs. I thought about submitting one JOB for each Storage
> Group but that would mean too many DD for most of the JOBs.
> Regards
> Jack
> 
>> On Sun, 24 Jul 2022 at 22:48, Nigel Morton <nigelamor...@gmail.com> wrote:
>> 
>> This is what I'd use, shown for a single volume:
>> 
>> //UNCAT EXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN'
>> //SYSPRINT DD SYSOUT=*
>> //SYSIN    DD *
>> COPY -
>>   DATASET( INCLUDE (**)) -
>>   LOGINDYNAM(volser) -
>>   BY (CATLG,EQ,NO) -
>>   DELETE
>> /*
>> The parm setting lets you see what it would do if you unleash it.  One
>> tool, standard, no need for own code.
>> 
>> DCOLLECT won't cut it because it doesn't look at catalogs.
>> 
>> On Sun, 24 Jul 2022 at 22:24, John McKown <john.archie.mck...@gmail.com>
>> wrote:
>> 
>>> Sorry, I should have double checked. It's been years since I've had to do
>>> it. And it's Sunday. Yes COPY DELETE is correct.
>>> 
>>> On Sun, Jul 24, 2022 at 4:18 PM David Spiegel <dspiegel...@hotmail.com>
>>> wrote:
>>> 
>>>> Hi John,
>>>> "...ADRDSSU MOVE..." There is no such verb.
>>>> Maybe you mean COPY ... DELETE?
>>>> 
>>>> Regards,
>>>> David
>>>> 
>>>> On 2022-07-24 17:03, John McKown wrote:
>>>>> ADRDSSU MOVE can scan volumes for uncatalogued datasets and MOVE the
>>> to a
>>>>> sequential dataset, or just DD DUMMY. It doesn't care what the DSN
>> is,
>>>> even
>>>>> if it has abnormal byte values in the name.
>>>>> 
>>>>> On Sat, Jul 23, 2022, 14:29 David Staudacher <dlstaudac...@gmail.com
>>> 
>>>> wrote:
>>>>> 
>>>>>> Jack Zukt wrote: "I would prefer a more standard approach if I could
>>>> find
>>>>>> one".
>>>>>> 
>>>>>> What you need is something that can dig out all the DSCBs from every
>>>> VTOC
>>>>>> of every online DASD device and sum these into a Data Set list.
>>>>>> I happen to have an Assembler program which does just that, if you'd
>>>> like
>>>>>> to try it out.
>>>>>> Assuming you have the required MACLIBs (SYS1.MACLIB and SYS1.MODGEN
>> or
>>>>>> SYS1.AMODGEN) it's very easy to Assemble and run it yourself.
>>>>>> Use a Catalog Search to find uncataloged data sets is of course
>>> useless
>>>>>> for obvious reasons.
>>>>>> My program outputs a record for each DSCB. These are then summed to
>>>> create
>>>>>> a report listing every Data Set on every online DASD device.
>>>>>> The report gives VOLSER, DSORG, RECFM, LRECL, BLKSIZE, # of Tracks,
>> %
>>>>>> Used, # of Extents, Create Date and Date Last Referenced.
>>>>>> It rivals DCOLLECT in what it can do but requires no special
>>>>>> Authorization.
>>>>>> A recent enhancement to calculate space utilization for PDSEs slowed
>>> it
>>>>>> down quite a bit, but otherwise it's *very* fast.
>>>>>> The report is also handy for contractors who want to quickly learn
>> the
>>>>>> "filescape" of any new site to which they're assigned.
>>>>>> Next enhancement I have in mind is to calculate total *available*
>> DASD
>>>>>> space, which *could* be very easy (or not). Just haven't gotten
>> around
>>>> to
>>>>>> figuring it out yet.
>>>>>> Let me know if you'd like a copy of the source I have so far, and
>> JCL
>>> to
>>>>>> run it, and I'll send it to you.
>>>>>> So far, it's worked everywhere it's been tried.
>>>>>> If there are any cases where it *doesn't* work, that would be nice
>> to
>>>> know
>>>>>> too.
>>>>>> David Staudacher
>>>>>> LinkedIn Mainframe Groups Manager
>>>>>> => linkedin.com/groups/910927   ๐Œ๐š๐ข๐ง๐Ÿ๐ซ๐š๐ฆ๐ž (๐‚๐Ž๐๐Ž๐‹,
>>> ๐ž๐ญ๐œ)
>>>>>> ๐„๐ฑ๐ฉ๐ž๐ซ๐ญ๐ฌ
>>>>>> => linkedin.com/groups/2915689 ๐Œ๐š๐ข๐ง๐Ÿ๐ซ๐š๐ฆ๐ž ๐๐ซ๐จ๐๐ฎ๐œ๐ญ๐ฌ
>>>> ๐š๐ง๐
>>>>>> ๐’๐ž๐ซ๐ฏ๐ข๐œ๐ž๐ฌ
>>>>>> => linkedin.com/groups/12307358 ๐Œ๐š๐ข๐ง๐Ÿ๐ซ๐š๐ฆ๐ž ๐‰๐จ๐›๐ฌ /
>>>>>> ๐‚๐š๐ซ๐ž๐ž๐ซ๐ฌ
>>>>>> => linkedin.com/groups/8979270 ๐Œ๐š๐ข๐ง๐Ÿ๐ซ๐š๐ฆ๐ž
>> ๐€๐ฌ๐ฌ๐ž๐ฆ๐›๐ฅ๐ž๐ซ
>>>>>> ๐ƒ๐ž๐ฏ๐ž๐ฅ๐จ๐ฉ๐ž๐ซ๐ฌ
>>>>>> => linkedin.com/groups/155723   ๐’๐ฒ๐ฌ๐ญ๐ž๐ฆ ๐ณ ๐€๐๐ฏ๐จ๐œ๐š๐ญ๐ž๐ฌ
>>>>>> => linkedin.com/groups/2085030 ๐ณ/๐•๐’๐„
>>>>>> 
>>>>>> 
>> ----------------------------------------------------------------------
>>>>>> 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
>>> 
>> 
>> ----------------------------------------------------------------------
>> 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