A possible RYO would be to write a rexx exec to: 1. issue operator command using sdsf rexx d u,dasd,online,,9999 2. parse the results for each volser 3. invoke iehlist - listvtoc for each and capture the results 4. issue listdsi for each dataset - if not cataloged then you have them - if the sysvolume is not the same as the iehlist volser then you have a mismatch
This will take awhile so run it in batch. Lionel B. Dyck <>< Website: https://www.lbdsoftware.com Github: https://github.com/lbdyck โWorry more about your character than your reputation. Character is what you are, reputation merely what others think you are.โ - - - John Wooden -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jack Zukt Sent: Monday, July 25, 2022 8:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Finding uncatalogued datasets Hi, In this SYSPLEX all user catalog and all its aliases are shared. There is a daily process that emits an alert for any ALIAS that is not defined on all systems. On Mon, 25 Jul 2022 at 13:59, Seymour J Metz <sme...@gmu.edu> wrote: > How does it deal with user catalogs? If FOO is a catalog alias in one > master catalog but not in another, could FOO.** datasets be > incorrectly treated as uncataloged? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > behalf of John McKown [john.archie.mck...@gmail.com] > Sent: Sunday, July 24, 2022 5:03 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Finding uncatalogued datasets > > 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
