Hi Jack,
What will happen (with your proposed solution) if you have Dataset A.B
Cataloged to ABC123 and also present on ABC124, or, Dataset ABC
Cataloged to ABC123, but, present only on ABC124?
I do not want to sound like a broken record, but,. the VTOC Command
Processor (CBT File 112) can deal with both of these situations.
Regards,
David
On 2022-07-25 07:23, Jack Zukt wrote:
Hi all,
Thank you all for all of your suggestions so far.
After one weekend with everything working in the background I came up with
an idea for a new approach.
I have the DCOLLECT output with all the formatted data records or the file
treated by DFSORT with only the dataset names and a few extra tidbits. Now
I also have a file that is a result of a SORT over a LISTCAT of all the
user catalogs on the system, with all (and only) the cataloged dataset
names.
Now, can I use DFSORT with those two files as input to create a file with
only the dataset names that exist on the DCOLLECT file but do not exist on
the LISTCAT output?
Regards,
Jack
On Mon, 25 Jul 2022 at 09:23, Jack Zukt <jzuk...@gmail.com> wrote:
Hi,
Thank you for the suggestion.
At this point in time, I only have access to IBM software
Regards
Jack
On Mon, 25 Jul 2022 at 09:17, Alain Benvรฉniste <a.benveni...@free.fr>
wrote:
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
----------------------------------------------------------------------
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
