Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-16 Thread Seymour J Metz 
That's part of the issue REXX essentially supports only what is in the CMS 
stack, not the features of the TSO stack written specifically for CLIST.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
Jesse 1 Robinson 
Sent: Thursday, August 15, 2019 4:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

One CLIST feature I miss in REXX is the ability to run in subcommand mode. With 
CLIST, you can execute for example TSO TEST and supply in-line subcommands that 
execute in sequence from within the CLIST. With REXX, you have to QUEUE the 
subcommands before issuing TEST, after which REXX is no longer in control.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Thursday, August 15, 2019 12:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

DATA and DATA PROMPT come to mind, as does the parsing of keyword parameters. 
I've tried to avoid CLIST since TSO/E V2, but there really re things that it 
does better than REXX.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
Dana Mitchell 
Sent: Thursday, August 15, 2019 3:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

What would be one of those cases?  I can't really think of anyting, maybe its 
been so long since I've written a clist that I'm don't remember what I'm 
missing.  If you want a trip into the early 80's, try writing an IBMi  CL 
program ;)

Dana

On Thu, 15 Aug 2019 16:41:15 +, Seymour J Metz  wrote:
>
>Seriously, there are actually cases where CLIST still makes sense. I just wish 
>that they'd enhance REXX to have the same capability.
>

--
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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Russell Witt 
Lizette is absolutely correct with regard to CA 1. We have a utility (TMSOSCAT) 
that will give you a list of all MVS/Catalog tape entries for which there is no 
actual record in the TMC for. A great way to eliminate obsolete catalog entries.

Russell Witt
CA 1 Architect
Broadcom

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Thursday, August 15, 2019 9:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

I think this is still valid.  But you would need to check with CA Broadcom to 
be certain

If you have any CA products like, CA1, PDSMAN, DISK, ALLOCATE, and so forth

Then you should be able to download and install GMI which could also be called 
Vantage Lite or SRM Lite

It will do what you want.


Or if you have SRM/Vantage, it will do what you want.


So is the problem you are trying to solve preventing JCL errors due to datasets 
coded in JCL but not existing?  

Or is this due to using NON SMS Volumes where there is only a catalog entry and 
not a physical dataset?


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List  On 
> Behalf Of esmie moo
> Sent: Thursday, August 15, 2019 5:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY
> 
>  Ricks,
> Thanks for the example.  I will try it out.
> On Wednesday, August 14, 2019, 12:10:39 a.m. GMT-4, Rick J. Valles 
> <026801af9474-dmarc-requ...@listserv.ua.edu> wrote:
> 
>  This is what we use (from my friend, John C. Miller @ jmit.com
> <http://jmit.com/>):
> 
> 
> //S1  EXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN'
> //SYSPRINT DD  SYSOUT=*
> //TAPEDD  DUMMY
> //SYSINDD  *
>  DUMP DS(INC(**) BY(CATLG EQ NO)) OUTDD(TAPE) LOGINDYNAM(SYC500)
> 
> 
> r
> 
> > On Aug 13, 2019, at 9:00 AM, John McKown 
> > 
> wrote:
> >
> > On Tue, Aug 13, 2019 at 9:37 AM esmie moo < 
> > 012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
> >
> >> Gentle Readers,
> >> Is there a way of weeding out dsns with cataloged entries only.  I 
> >>tried  DFDSS logical backup with NORUN option but it did not give me 
> >>the desired  results.  I coded the VOLSER of the disk to no avail.  
> >>I am doing this  exercise in preparation of removing old dasd but 
> >>experiences of the past  jobs failed because the dsn is not 
> >>accessible Any suggestions would be helpful and welcomed.Here is an example 
> >>of my jcl:
> >> //NORUN  EXEC PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
> >>  //*DFDSS1  EXEC PGM=ADRDSSU,REGION=4096K,TIME=1440
> >>  //DASD1DD UNIT=SYSALLDA,VOL=SER=PROD91,DISP=SHR
> >>  //TAPE1  DD DSN=SYS2.CLOGR1.CLOGR2.LOGICAL,DISP=(,CATLG,DELETE),
> >>//
> >>  UNIT=3490,TRTCH=COMP,LABEL=(1,SL) //SYSPRINT  DD  SYSOUT=* 
> >>//SYSMAP  DD
> >> SYSOUT=*  //SYSINDD
> >>*
> >>  DUMP
> >> DATASET(INCLUDE(SYS2.ORDMS.FILES.PROD))  - SPHERE
> >>-
> >> SELECTMULTI(FIRST)  -
> >> LOGINDDNAME(DASD1)  -
> >> OUTDD(TAPE1) OPT(4) ALLDATA(*) ALLEXCP -
> >> TOL(ENQF)  /*
> >>
> >>
> >>
> > Do you mean DSNs in a catalog that don't exist on some volume (I am 
> > guessing DASD in particular)? ADRDSSU won't address that. T-REX has 
> > a SCRUB command which will do it. We use that at disaster recovery. 
> > I am not aware of any z/OS "built in" facility to do that.
> >
> > --
> > A sine curve goes off to infinity, or at least the end of the blackboard.
> > -- Prof. Steiner
> >
> > Maranatha! <><
> > John McKown
> >
> > 
> > -- 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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Rick J. Valles 



Matthew,


GREAT utility!


...
...
...
LISTICAT 2.1.5 -- MESSAGES
CATALOG ENTRY BUT NO DATASET FOR DSN: HS1.QASYST.HSCD002K.EXCPTRPT.G0431V00
CATALOG ENTRY BUT NO DATASET FOR DSN: HS1.QASYST.HSCD002K.EXCPTRPT.G0432V00
CATALOG ENTRY BUT NO DATASET FOR DSN: HS1.QASYST.HSCD002K.EXCPTRPT.G0433V00
CATALOG ENTRY BUT NO DATASET FOR DSN: HS1.QASYST.HSCD002K.EXCPTRPT.G0434V00
CATALOG ENTRY BUT NO DATASET FOR DSN: HS1.QASYST.HSCD002K.EXCPTRPT.G0435V00
...
...
...


Thank You,


r

On August 15, 2019 at 11:10 AM, "Rick J. Valles" 
<026801af9474-dmarc-requ...@listserv.ua.edu> wrote:


Thanks, Matthew. I just downloaded and received FILE527.XMI and will checkout 
LISTICAT and the other programs.


Great Author!    :)


r

On August 15, 2019 at 10:50 AM, Matthew Stitt  wrote:


Program LISTICAT on the CBT tape, file 527 will give you the list of datasets 
in a catalog, but not in a VTOC. That's in the error listing.

Matthew

--
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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Jesse 1 Robinson 
One CLIST feature I miss in REXX is the ability to run in subcommand mode. With 
CLIST, you can execute for example TSO TEST and supply in-line subcommands that 
execute in sequence from within the CLIST. With REXX, you have to QUEUE the 
subcommands before issuing TEST, after which REXX is no longer in control.  

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Thursday, August 15, 2019 12:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

DATA and DATA PROMPT come to mind, as does the parsing of keyword parameters. 
I've tried to avoid CLIST since TSO/E V2, but there really re things that it 
does better than REXX.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
Dana Mitchell 
Sent: Thursday, August 15, 2019 3:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

What would be one of those cases?  I can't really think of anyting, maybe its 
been so long since I've written a clist that I'm don't remember what I'm 
missing.  If you want a trip into the early 80's, try writing an IBMi  CL 
program ;)

Dana

On Thu, 15 Aug 2019 16:41:15 +, Seymour J Metz  wrote:
>
>Seriously, there are actually cases where CLIST still makes sense. I just wish 
>that they'd enhance REXX to have the same capability.
>

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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Seymour J Metz 
DATA and DATA PROMPT come to mind, as does the parsing of keyword parameters. 
I've tried to avoid CLIST since TSO/E V2, but there really re things that it 
does better than REXX.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
Dana Mitchell 
Sent: Thursday, August 15, 2019 3:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

What would be one of those cases?  I can't really think of anyting, maybe its 
been so long since I've written a clist that I'm don't remember what I'm 
missing.  If you want a trip into the early 80's, try writing an IBMi  CL 
program ;)

Dana

On Thu, 15 Aug 2019 16:41:15 +, Seymour J Metz  wrote:
>
>Seriously, there are actually cases where CLIST still makes sense. I just wish 
>that they'd enhance REXX to have the same capability.
>

--
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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Dana Mitchell 
What would be one of those cases?  I can't really think of anyting, maybe its 
been so long since I've written a clist that I'm don't remember what I'm 
missing.  If you want a trip into the early 80's, try writing an IBMi  CL 
program ;)

Dana

On Thu, 15 Aug 2019 16:41:15 +, Seymour J Metz  wrote:
>
>Seriously, there are actually cases where CLIST still makes sense. I just wish 
>that they'd enhance REXX to have the same capability.
>

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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Rick J. Valles 

Thanks, Matthew. I just downloaded and received FILE527.XMI and will checkout 
LISTICAT and the other programs.


Great Author!    :)


r

On August 15, 2019 at 10:50 AM, Matthew Stitt  wrote:


Program LISTICAT on the CBT tape, file 527 will give you the list of datasets 
in a catalog, but not in a VTOC. That's in the error listing.

Matthew

--
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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Matthew Stitt 
Program LISTICAT on the CBT tape, file 527 will give you the list of datasets 
in a catalog, but not in a VTOC.  That's in the error listing.

Matthew

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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Seymour J Metz 
Well, there's LIST .

Seriously, there are actually cases where CLIST still makes sense. I just wish 
that they'd enhance REXX to have the same capability.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
Kirk Wolf 
Sent: Thursday, August 15, 2019 10:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

As an opportunity to show that REXX isn't the only way to script something
on z/OS, here is an example of using a z/OS Unix shell script in a batch
job to do this.

The COZBATCH utility is our alternative to BPXBATCH that simplifies batch
shell scripts.
"catsearch" is a little Unix shell command that produces output like ISPF
3.4 - it uses IGGCSI00 for searching the catalog and then it gathers the
DSCBs to get label information.   Combining this with the z/OS Unix "awk"
scripting program allows you to filter the output and print and format
lines for the DSN and VOLUME of uncataloged datasets.

//UNIX EXEC PGM=COZBATCH# a better BPXBATCH
//STEPLIB DD DISP=SHR,DSN=DOVETAIL.COZ.LOADLIB
//STDIN   DD *
# This is just a z/OS Unix shell script:
# Search the catalog and print those entries not found on the volume
catsearch -l "*.**" |
  awk '$2 == "??" { printf("%-44s %s\n",$3,$1); }'
/*
//STDOUT  DD DISP=(,PASS),DSN=&&OUT1,DCB=(RECFM=FB,LRECL=80)
//

It would be trivial to have awk generate IDCAMS commands to delete
uncataloged entries.

Kirk Wolf
Dovetailed Technologies
http://secure-web.cisco.com/1bx9oM1LpoLUkcEMUGPQqAgvrd4MwoNQF-ZdQUbvjeu7kTOBtXsBAo5h4v5OC35u0w7HaY3KPg8fJlZZWAJYGgmRjJG1PQhw7VLXqlkRgYEEGVEj1f27P5v2JrZuK6D88YoJndf_swqQti3YYqbpSq48pczlPZ0yqGg0RZhuvosFBHd39NLUKOdqIxwU61qcIk96K4-9Z3aRUccK2urGFnXEikF0-LrA1lwEJM8pe81AP7yvN4yEJ9ChqMulN-DVpU_q9mHq0Fh3v_oIdINnYvHikS1mznHyrL63j85bqMlCp3N6zOXI8ahgCLvshyCdXQd7cOUjuWtabrB_fHiYHCy6iRzRed0pS9BZs4sas7Dhgl2FIrCuFB1RThR1-AS2YFrPYMuV3HJToXHP8QdbVzuvkg6qyqsYGJ4LuDE-bxgE3Zx9XIMt_X8VBdDtuy855/http%3A%2F%2Fdovetail.com

PS> Co:Z can be downloaded and used free under our Community License:
http://secure-web.cisco.com/1w1NYPRqZ3vq1L1aoisGhYxOhP8CqcJE74kCp-jRwhdIIvYl-qqsxF8vBjd3Qtwpqh5h-ehbwO2lJecsY4SWKobOxVqeZv6-ytuCC2TIoLZft3XPmXDqHE03_iCUwKAR6ddZTc6XtFA6GoWayFRR-4eQyuLbSAY7kmdhKvcD8KwLe7JD6pSTOEL1e-YHOrdyA5iV8yI-q4KS4oBOYc-r0aWRzBq-GGWZ9Fjbkexq9q8WyNBXrjsSOTw3UKPx2omwq2xlUIUN6BrShGx6VYAwCrSiqQVpwy8L_PGpTuJ-08j6arRRMHzh7vfc2Cs_jxH_X6-mpZ8jQlm8X_WtWI6fr-9eVHLLaox3-mexmOsF_jVPM-DLfXzzgelMLPwD9f3OwmyXjiPCn7bEHHkJij4hhCw6OHkv_OMjE8prchmvvxuqpghmTFjeHyfKhtAafiShT/http%3A%2F%2Fdovetail.com%2Fsupport.html
For more info on:
catsearch command
https://secure-web.cisco.com/1G0_5oLlmmGTPB_0FIFHhVI3CcK7fN-9SR-AXkZOdYycOb4qdi9MwydtcaVyR99uetSoClur_W8my-JsQYafpkcuzW2b28HXP1roWHC4vmPhPBxa58eRC5fCVKzPGkGsBbTRZ58shFpQpejJbhg7HSiDiRIvgGQjPChUkUiW9MTXH6quiO5qxsKEJiQygYOsCfr2SJPxNOeX9lazSX_8A6zqByO6of7HQz2Iru7XlqfGJ6vo-yieTVN2HKld3l21pEMG_EtEy6S_BY1KWcZd-j09u7eFndj-eoP1gN4VV4O08sFj0CbqhvoJcEifbGQoVRP-ldGwXmtXhpBD5rLeluOSDO5XdCp_bweeTLV1bB7MVVtU79lASKkXz3VPsH2iF--RfwcGuEtL7ICOj0geRbNEJXhJToNnLHV0bJ8X2HyC06nv1Ktji40dfFrcBNvRM/https%3A%2F%2Fdovetail.com%2Fdocs%2Fdspipes%2Fdsp-ref_catsearch.html
COZBATCH 
https://secure-web.cisco.com/1N8QOuOLNQYsfKtGpUt8zvD-zkE5uZyyijyGQ1WuWuEuLEJ-9GWPixIkdhmcVAYUwrXtxJuRuRg2egaV9HIPiFxYycRY8W3ZpGojHmJGPm_yhwJ-6l7wW2r9HILr5oGjqsB7Nyw4hLYaPhaJCUJBtiiRIVQs2p1kZJ485oUnEZ8TMX__lR9_XF1s2AzgoFQNYWhB01UIMFNM09ShdfpmgTb3kxB10gleJn9srHvrtEj5ctT_WHA-RzCcRaXr0weFTRVNtQ6BhKh7ppuieTfRJtSoM2kYwP8VtK5BPN_fV6AHd5w-SrtOtJPvifURLyaO-jKW7h7j49YpxpTh56ZJZUTlKeJDZxT8UjXrbieKwZ1WA_4n6z2bDxdWSH2BkiiZ1YRXNS3VHS1QSUV90vWHUwPZV4WZuPkGG8psUywojNUNS46SZd-8vH9h2Eu1w89UH/https%3A%2F%2Fdovetail.com%2Fproducts%2Fcozbatch.html




On Thu, Aug 15, 2019 at 8:10 AM Pew, Curtis G 
wrote:

> On Aug 15, 2019, at 7:00 AM, esmie moo <
> 012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > Yes.  I am trying to find any dsns that exist in the catalog but don't
> exist on the disk.  I know that we have some ancient applications which
> refer to procs that have dsns which are cataloged but do not exist on the
> disk.
>
> I’m going to recommend Rocket Mainstar Catalog RecoveryPlus for this. It
> won’t just identify the DSNs, it will generate the IDCAMS statements needed
> to clean everything up. It can also find and fix more serious problems with
> your catalogs.
>
> This is one of those products you don’t need often but saves a lot of time
> and effort when you do need it.
>
>
> --
> Pew, Curtis G
> curtis@austin.utexas.edu
>
>
>
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

---

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread John McKown 
On Thu, Aug 15, 2019 at 9:58 AM Kirk Wolf  wrote:

> I should point out that this doesn't deal with the issue of unmounted
> volumes :-)
>

Is that a 3330-11 I see in your pocket



>
> Kirk Wolf
> Dovetailed Technologies
> http://dovetail.com
>
>
-- 
I find television very educational. The minute somebody turns it on, I go
into the library and read a good book
-- Groucho Marx

Maranatha! <><
John McKown

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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Kirk Wolf 
I should point out that this doesn't deal with the issue of unmounted
volumes :-)

Kirk Wolf
Dovetailed Technologies
http://dovetail.com


On Thu, Aug 15, 2019 at 9:38 AM Kirk Wolf  wrote:

> As an opportunity to show that REXX isn't the only way to script something
> on z/OS, here is an example of using a z/OS Unix shell script in a batch
> job to do this.
>
> The COZBATCH utility is our alternative to BPXBATCH that simplifies batch
> shell scripts.
> "catsearch" is a little Unix shell command that produces output like ISPF
> 3.4 - it uses IGGCSI00 for searching the catalog and then it gathers the
> DSCBs to get label information.   Combining this with the z/OS Unix "awk"
> scripting program allows you to filter the output and print and format
> lines for the DSN and VOLUME of uncataloged datasets.
>
> //UNIX EXEC PGM=COZBATCH# a better BPXBATCH
> //STEPLIB DD DISP=SHR,DSN=DOVETAIL.COZ.LOADLIB
> //STDIN   DD *
> # This is just a z/OS Unix shell script:
> # Search the catalog and print those entries not found on the volume
> catsearch -l "*.**" |
>   awk '$2 == "??" { printf("%-44s %s\n",$3,$1); }'
> /*
> //STDOUT  DD DISP=(,PASS),DSN=&&OUT1,DCB=(RECFM=FB,LRECL=80)
> //
>
> It would be trivial to have awk generate IDCAMS commands to delete
> uncataloged entries.
>
> Kirk Wolf
> Dovetailed Technologies
> http://dovetail.com
>
> PS> Co:Z can be downloaded and used free under our Community License:
> http://dovetail.com/support.html
> For more info on:
> catsearch command
> https://dovetail.com/docs/dspipes/dsp-ref_catsearch.html
> COZBATCH https://dovetail.com/products/cozbatch.html
>
>
>
>
> On Thu, Aug 15, 2019 at 8:10 AM Pew, Curtis G <
> curtis@austin.utexas.edu> wrote:
>
>> On Aug 15, 2019, at 7:00 AM, esmie moo <
>> 012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
>> >
>> > Yes.  I am trying to find any dsns that exist in the catalog but don't
>> exist on the disk.  I know that we have some ancient applications which
>> refer to procs that have dsns which are cataloged but do not exist on the
>> disk.
>>
>> I’m going to recommend Rocket Mainstar Catalog RecoveryPlus for this. It
>> won’t just identify the DSNs, it will generate the IDCAMS statements needed
>> to clean everything up. It can also find and fix more serious problems with
>> your catalogs.
>>
>> This is one of those products you don’t need often but saves a lot of
>> time and effort when you do need it.
>>
>>
>> --
>> Pew, Curtis G
>> curtis@austin.utexas.edu
>>
>>
>>
>>
>>
>>
>> --
>> 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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Kirk Wolf 
As an opportunity to show that REXX isn't the only way to script something
on z/OS, here is an example of using a z/OS Unix shell script in a batch
job to do this.

The COZBATCH utility is our alternative to BPXBATCH that simplifies batch
shell scripts.
"catsearch" is a little Unix shell command that produces output like ISPF
3.4 - it uses IGGCSI00 for searching the catalog and then it gathers the
DSCBs to get label information.   Combining this with the z/OS Unix "awk"
scripting program allows you to filter the output and print and format
lines for the DSN and VOLUME of uncataloged datasets.

//UNIX EXEC PGM=COZBATCH# a better BPXBATCH
//STEPLIB DD DISP=SHR,DSN=DOVETAIL.COZ.LOADLIB
//STDIN   DD *
# This is just a z/OS Unix shell script:
# Search the catalog and print those entries not found on the volume
catsearch -l "*.**" |
  awk '$2 == "??" { printf("%-44s %s\n",$3,$1); }'
/*
//STDOUT  DD DISP=(,PASS),DSN=&&OUT1,DCB=(RECFM=FB,LRECL=80)
//

It would be trivial to have awk generate IDCAMS commands to delete
uncataloged entries.

Kirk Wolf
Dovetailed Technologies
http://dovetail.com

PS> Co:Z can be downloaded and used free under our Community License:
http://dovetail.com/support.html
For more info on:
catsearch command
https://dovetail.com/docs/dspipes/dsp-ref_catsearch.html
COZBATCH https://dovetail.com/products/cozbatch.html




On Thu, Aug 15, 2019 at 8:10 AM Pew, Curtis G 
wrote:

> On Aug 15, 2019, at 7:00 AM, esmie moo <
> 012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > Yes.  I am trying to find any dsns that exist in the catalog but don't
> exist on the disk.  I know that we have some ancient applications which
> refer to procs that have dsns which are cataloged but do not exist on the
> disk.
>
> I’m going to recommend Rocket Mainstar Catalog RecoveryPlus for this. It
> won’t just identify the DSNs, it will generate the IDCAMS statements needed
> to clean everything up. It can also find and fix more serious problems with
> your catalogs.
>
> This is one of those products you don’t need often but saves a lot of time
> and effort when you do need it.
>
>
> --
> Pew, Curtis G
> curtis@austin.utexas.edu
>
>
>
>
>
>
> --
> 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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Rick J. Valles 

Esmie,


I misunderstood your need for a listing of data sets in a catalog, but not on 
disk.


This DFDSS job lists data sets found in a VTOC, but not catalogued.


r

On August 15, 2019 at 6:01 AM, esmie moo 
<012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:


Ricks,
Thanks for the example.  I will try it out. 
On Wednesday, August 14, 2019, 12:10:39 a.m. GMT-4, Rick J. Valles 
<026801af9474-dmarc-requ...@listserv.ua.edu> wrote:

This is what we use (from my friend, John C. Miller @ jmit.com 
):


//S1      EXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN'
//SYSPRINT DD  SYSOUT=*
//TAPE    DD  DUMMY
//SYSIN    DD  *
DUMP DS(INC(**) BY(CATLG EQ NO)) OUTDD(TAPE) LOGINDYNAM(SYC500)


r


On Aug 13, 2019, at 9:00 AM, John McKown  wrote:


On Tue, Aug 13, 2019 at 9:37 AM esmie moo <
012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:


Gentle Readers,
Is there a way of weeding out dsns with cataloged entries only.  I tried
DFDSS logical backup with NORUN option but it did not give me the desired
results.  I coded the VOLSER of the disk to no avail.  I am doing this
exercise in preparation of removing old dasd but experiences of the past
jobs failed because the dsn is not accessible
Any suggestions would be helpful and welcomed.Here is an example of my jcl:
//NORUN  EXEC PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
  //*DFDSS1  EXEC PGM=ADRDSSU,REGION=4096K,TIME=1440
  //DASD1    DD UNIT=SYSALLDA,VOL=SER=PROD91,DISP=SHR
  //TAPE1  DD DSN=SYS2.CLOGR1.CLOGR2.LOGICAL,DISP=(,CATLG,DELETE),    //
          UNIT=3490,TRTCH=COMP,LABEL=(1,SL)                    //SYSPRINT
DD  SYSOUT=*                                              //SYSMAP  DD
SYSOUT=*                                              //SYSIN    DD  *
                                                  DUMP
DATASET(INCLUDE(SYS2.ORDMS.FILES.PROD))  -                          SPHERE
                                    -
SELECTMULTI(FIRST)                          -
LOGINDDNAME(DASD1)                          -
OUTDD(TAPE1) OPT(4) ALLDATA(*) ALLEXCP -
TOL(ENQF)                                                      /*






Do you mean DSNs in a catalog that don't exist on some volume (I am
guessing DASD in particular)? ADRDSSU won't address that. T-REX has a SCRUB
command which will do it. We use that at disaster recovery. I am not aware
of any z/OS "built in" facility to do that.


--
A sine curve goes off to infinity, or at least the end of the blackboard.
-- Prof. Steiner


Maranatha! <><
John McKown


--
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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Lizette Koehler 
I think this is still valid.  But you would need to check with CA Broadcom to 
be certain

If you have any CA products like, CA1, PDSMAN, DISK, ALLOCATE, and so forth

Then you should be able to download and install GMI which could also be called 
Vantage Lite or SRM Lite

It will do what you want.


Or if you have SRM/Vantage, it will do what you want.


So is the problem you are trying to solve preventing JCL errors due to datasets 
coded in JCL but not existing?  

Or is this due to using NON SMS Volumes where there is only a catalog entry and 
not a physical dataset?


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of
> esmie moo
> Sent: Thursday, August 15, 2019 5:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY
> 
>  Ricks,
> Thanks for the example.  I will try it out.
> On Wednesday, August 14, 2019, 12:10:39 a.m. GMT-4, Rick J. Valles
> <026801af9474-dmarc-requ...@listserv.ua.edu> wrote:
> 
>  This is what we use (from my friend, John C. Miller @ jmit.com
> <http://jmit.com/>):
> 
> 
> //S1  EXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN'
> //SYSPRINT DD  SYSOUT=*
> //TAPEDD  DUMMY
> //SYSINDD  *
>  DUMP DS(INC(**) BY(CATLG EQ NO)) OUTDD(TAPE) LOGINDYNAM(SYC500)
> 
> 
> r
> 
> > On Aug 13, 2019, at 9:00 AM, John McKown 
> wrote:
> >
> > On Tue, Aug 13, 2019 at 9:37 AM esmie moo <
> > 012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
> >
> >> Gentle Readers,
> >> Is there a way of weeding out dsns with cataloged entries only.  I
> >>tried  DFDSS logical backup with NORUN option but it did not give me
> >>the desired  results.  I coded the VOLSER of the disk to no avail.  I
> >>am doing this  exercise in preparation of removing old dasd but
> >>experiences of the past  jobs failed because the dsn is not accessible
> >>Any suggestions would be helpful and welcomed.Here is an example of my jcl:
> >> //NORUN  EXEC PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
> >>  //*DFDSS1  EXEC PGM=ADRDSSU,REGION=4096K,TIME=1440
> >>  //DASD1DD UNIT=SYSALLDA,VOL=SER=PROD91,DISP=SHR
> >>  //TAPE1  DD DSN=SYS2.CLOGR1.CLOGR2.LOGICAL,DISP=(,CATLG,DELETE),
> >>//
> >>  UNIT=3490,TRTCH=COMP,LABEL=(1,SL)
> >>//SYSPRINT  DD  SYSOUT=*
> >>//SYSMAP  DD
> >> SYSOUT=*  //SYSINDD
> >>*
> >>  DUMP
> >> DATASET(INCLUDE(SYS2.ORDMS.FILES.PROD))  -
> >>SPHERE
> >>-
> >> SELECTMULTI(FIRST)  -
> >> LOGINDDNAME(DASD1)  -
> >> OUTDD(TAPE1) OPT(4) ALLDATA(*) ALLEXCP -
> >> TOL(ENQF)  /*
> >>
> >>
> >>
> > Do you mean DSNs in a catalog that don't exist on some volume (I am
> > guessing DASD in particular)? ADRDSSU won't address that. T-REX has a
> > SCRUB command which will do it. We use that at disaster recovery. I am
> > not aware of any z/OS "built in" facility to do that.
> >
> > --
> > A sine curve goes off to infinity, or at least the end of the blackboard.
> > -- Prof. Steiner
> >
> > Maranatha! <><
> > John McKown
> >
> > --
> > 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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread Pew, Curtis G 
On Aug 15, 2019, at 7:00 AM, esmie moo 
<012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
> 
> Yes.  I am trying to find any dsns that exist in the catalog but don't exist 
> on the disk.  I know that we have some ancient applications which refer to 
> procs that have dsns which are cataloged but do not exist on the disk.

I’m going to recommend Rocket Mainstar Catalog RecoveryPlus for this. It won’t 
just identify the DSNs, it will generate the IDCAMS statements needed to clean 
everything up. It can also find and fix more serious problems with your 
catalogs.

This is one of those products you don’t need often but saves a lot of time and 
effort when you do need it.


-- 
Pew, Curtis G
curtis@austin.utexas.edu






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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread esmie moo 
 Ricks,
Thanks for the example.  I will try it out. 
On Wednesday, August 14, 2019, 12:10:39 a.m. GMT-4, Rick J. Valles 
<026801af9474-dmarc-requ...@listserv.ua.edu> wrote:  
 
 This is what we use (from my friend, John C. Miller @ jmit.com 
):


//S1      EXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN'
//SYSPRINT DD  SYSOUT=*
//TAPE    DD  DUMMY
//SYSIN    DD  *
 DUMP DS(INC(**) BY(CATLG EQ NO)) OUTDD(TAPE) LOGINDYNAM(SYC500)


r

> On Aug 13, 2019, at 9:00 AM, John McKown  wrote:
> 
> On Tue, Aug 13, 2019 at 9:37 AM esmie moo <
> 012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
> 
>> Gentle Readers,
>> Is there a way of weeding out dsns with cataloged entries only.  I tried
>> DFDSS logical backup with NORUN option but it did not give me the desired
>> results.  I coded the VOLSER of the disk to no avail.  I am doing this
>> exercise in preparation of removing old dasd but experiences of the past
>> jobs failed because the dsn is not accessible
>> Any suggestions would be helpful and welcomed.Here is an example of my jcl:
>> //NORUN  EXEC PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>>  //*DFDSS1  EXEC PGM=ADRDSSU,REGION=4096K,TIME=1440
>>  //DASD1    DD UNIT=SYSALLDA,VOL=SER=PROD91,DISP=SHR
>>  //TAPE1  DD DSN=SYS2.CLOGR1.CLOGR2.LOGICAL,DISP=(,CATLG,DELETE),    //
>>          UNIT=3490,TRTCH=COMP,LABEL=(1,SL)                    //SYSPRINT
>> DD  SYSOUT=*                                              //SYSMAP  DD
>> SYSOUT=*                                              //SYSIN    DD  *
>>                                                  DUMP
>> DATASET(INCLUDE(SYS2.ORDMS.FILES.PROD))  -                          SPHERE
>>                                    -
>> SELECTMULTI(FIRST)                          -
>> LOGINDDNAME(DASD1)                          -
>> OUTDD(TAPE1) OPT(4) ALLDATA(*) ALLEXCP -
>> TOL(ENQF)                                                      /*
>> 
>> 
>> 
> Do you mean DSNs in a catalog that don't exist on some volume (I am
> guessing DASD in particular)? ADRDSSU won't address that. T-REX has a SCRUB
> command which will do it. We use that at disaster recovery. I am not aware
> of any z/OS "built in" facility to do that.
> 
> -- 
> A sine curve goes off to infinity, or at least the end of the blackboard.
> -- Prof. Steiner
> 
> Maranatha! <><
> John McKown
> 
> --
> 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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-15 Thread esmie moo 
 John,
Yes.  I am trying to find any dsns that exist in the catalog but don't exist on 
the disk.  I know that we have some ancient applications which refer to procs 
that have dsns which are cataloged but do not exist on the disk.
On Wednesday, August 14, 2019, 12:35:39 a.m. GMT-4, John McKown 
 wrote:  
 
 On Tue, Aug 13, 2019 at 9:37 AM esmie moo <
012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:

> Gentle Readers,
> Is there a way of weeding out dsns with cataloged entries only.  I tried
> DFDSS logical backup with NORUN option but it did not give me the desired
> results.  I coded the VOLSER of the disk to no avail.  I am doing this
> exercise in preparation of removing old dasd but experiences of the past
> jobs failed because the dsn is not accessible
> Any suggestions would be helpful and welcomed.Here is an example of my jcl:
> //NORUN  EXEC PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>  //*DFDSS1  EXEC PGM=ADRDSSU,REGION=4096K,TIME=1440
>  //DASD1    DD UNIT=SYSALLDA,VOL=SER=PROD91,DISP=SHR
>  //TAPE1  DD DSN=SYS2.CLOGR1.CLOGR2.LOGICAL,DISP=(,CATLG,DELETE),    //
>            UNIT=3490,TRTCH=COMP,LABEL=(1,SL)                    //SYSPRINT
> DD  SYSOUT=*                                              //SYSMAP  DD
> SYSOUT=*                                              //SYSIN    DD  *
>                                                    DUMP
> DATASET(INCLUDE(SYS2.ORDMS.FILES.PROD))  -                          SPHERE
>                                      -
> SELECTMULTI(FIRST)                          -
> LOGINDDNAME(DASD1)                          -
> OUTDD(TAPE1) OPT(4) ALLDATA(*) ALLEXCP -
> TOL(ENQF)                                                      /*
>
>
>
Do you mean DSNs in a catalog that don't exist on some volume (I am
guessing DASD in particular)? ADRDSSU won't address that. T-REX has a SCRUB
command which will do it. We use that at disaster recovery. I am not aware
of any z/OS "built in" facility to do that.

-- 
A sine curve goes off to infinity, or at least the end of the blackboard.
-- Prof. Steiner

Maranatha! <><
John McKown

--
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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-13 Thread retired mainframer 
I think you are looking for the DIAGNOSE command found in the AMS manual.  It 
will compare the BCS and VVDS and identify mismatches in either direction.

> -Original Message-
> From: IBM Mainframe Discussion List  On
> Behalf Of esmie moo
> Sent: Tuesday, August 13, 2019 7:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY
> 
> Gentle Readers,
> Is there a way of weeding out dsns with cataloged entries only.  I tried 
> DFDSS logical
> backup with NORUN option but it did not give me the desired results.  I coded 
> the
> VOLSER of the disk to no avail.  I am doing this exercise in preparation of 
> removing
> old dasd but experiences of the past jobs failed because the dsn is not 
> accessible
> Any suggestions would be helpful and welcomed.Here is an example of my jcl:
> //NORUN   EXEC
> PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'  //*DFDSS1   E
> XEC PGM=ADRDSSU,REGION=4096K,TIME=1440  //DASD1DD
> UNIT=SYSALLDA,VOL=SER=PROD91,DISP=SHR  //TAPE1  DD
> DSN=SYS2.CLOGR1.CLOGR2.LOGICAL,DISP=(,CATLG,DELETE), // U
> NIT=3490,TRTCH=COMP,LABEL=(1,SL) //SYSPRINT
> DD  SYSOUT=*  //SYSMAP   DD
> SYSOUT=*   //SYSINDD  *
>DUMP DATASET(INCLUDE(SYS2.ORDMS.FILES.PROD))  -
>   SPHERE   -
>SELECTMULTI(FIRST)   -
>LOGINDDNAME(DASD1)  -
> OUTDD(TAPE1) OPT(4) ALLDATA(*) ALLEXCP -
>  TOL(ENQF)
>   /*
> 
> 
> 
> 
> --
> 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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-13 Thread Rick J. Valles 
This is what we use (from my friend, John C. Miller @ jmit.com 
):


//S1  EXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN'
//SYSPRINT DD  SYSOUT=*
//TAPE DD  DUMMY
//SYSINDD  *
 DUMP DS(INC(**) BY(CATLG EQ NO)) OUTDD(TAPE) LOGINDYNAM(SYC500)


r

> On Aug 13, 2019, at 9:00 AM, John McKown  wrote:
> 
> On Tue, Aug 13, 2019 at 9:37 AM esmie moo <
> 012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
> 
>> Gentle Readers,
>> Is there a way of weeding out dsns with cataloged entries only.  I tried
>> DFDSS logical backup with NORUN option but it did not give me the desired
>> results.  I coded the VOLSER of the disk to no avail.  I am doing this
>> exercise in preparation of removing old dasd but experiences of the past
>> jobs failed because the dsn is not accessible
>> Any suggestions would be helpful and welcomed.Here is an example of my jcl:
>> //NORUN   EXEC PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>>  //*DFDSS1   EXEC PGM=ADRDSSU,REGION=4096K,TIME=1440
>>  //DASD1DD UNIT=SYSALLDA,VOL=SER=PROD91,DISP=SHR
>>  //TAPE1  DD DSN=SYS2.CLOGR1.CLOGR2.LOGICAL,DISP=(,CATLG,DELETE), //
>>   UNIT=3490,TRTCH=COMP,LABEL=(1,SL) //SYSPRINT
>> DD  SYSOUT=*  //SYSMAP   DD
>> SYSOUT=*   //SYSINDD  *
>>   DUMP
>> DATASET(INCLUDE(SYS2.ORDMS.FILES.PROD))  -  SPHERE
>> -
>> SELECTMULTI(FIRST)   -
>> LOGINDDNAME(DASD1)  -
>> OUTDD(TAPE1) OPT(4) ALLDATA(*) ALLEXCP -
>> TOL(ENQF)  /*
>> 
>> 
>> 
> Do you mean DSNs in a catalog that don't exist on some volume (I am
> guessing DASD in particular)? ADRDSSU won't address that. T-REX has a SCRUB
> command which will do it. We use that at disaster recovery. I am not aware
> of any z/OS "built in" facility to do that.
> 
> -- 
> A sine curve goes off to infinity, or at least the end of the blackboard.
> -- Prof. Steiner
> 
> Maranatha! <><
> John McKown
> 
> --
> 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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-13 Thread ITschak Mugzach 
If I recall correctly, the VTOC command (CBT) has an option to list
datasets catalog status. Using volume masking you can achive need needs.

ITschak

On Tue, Aug 13, 2019 at 6:01 PM John McKown 
wrote:

> On Tue, Aug 13, 2019 at 9:37 AM esmie moo <
> 012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
>
> > Gentle Readers,
> > Is there a way of weeding out dsns with cataloged entries only.  I tried
> > DFDSS logical backup with NORUN option but it did not give me the desired
> > results.  I coded the VOLSER of the disk to no avail.  I am doing this
> > exercise in preparation of removing old dasd but experiences of the past
> > jobs failed because the dsn is not accessible
> > Any suggestions would be helpful and welcomed.Here is an example of my
> jcl:
> > //NORUN   EXEC PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
> >   //*DFDSS1   EXEC PGM=ADRDSSU,REGION=4096K,TIME=1440
> >   //DASD1DD UNIT=SYSALLDA,VOL=SER=PROD91,DISP=SHR
> >   //TAPE1  DD DSN=SYS2.CLOGR1.CLOGR2.LOGICAL,DISP=(,CATLG,DELETE), //
> >UNIT=3490,TRTCH=COMP,LABEL=(1,SL)
>  //SYSPRINT
> > DD  SYSOUT=*  //SYSMAP   DD
> > SYSOUT=*   //SYSINDD  *
> >DUMP
> > DATASET(INCLUDE(SYS2.ORDMS.FILES.PROD))  -
> SPHERE
> >  -
> > SELECTMULTI(FIRST)   -
> > LOGINDDNAME(DASD1)  -
> > OUTDD(TAPE1) OPT(4) ALLDATA(*) ALLEXCP -
> > TOL(ENQF)  /*
> >
> >
> >
> Do you mean DSNs in a catalog that don't exist on some volume (I am
> guessing DASD in particular)? ADRDSSU won't address that. T-REX has a SCRUB
> command which will do it. We use that at disaster recovery. I am not aware
> of any z/OS "built in" facility to do that.
>
> --
> A sine curve goes off to infinity, or at least the end of the blackboard.
> -- Prof. Steiner
>
> Maranatha! <><
> John McKown
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Contiguous Monitoring
for Legacy **|  *

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

Re: WEEDING OUT DSNS WITH CATALOG ENTRIES ONLY

2019-08-13 Thread John McKown 
On Tue, Aug 13, 2019 at 9:37 AM esmie moo <
012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:

> Gentle Readers,
> Is there a way of weeding out dsns with cataloged entries only.  I tried
> DFDSS logical backup with NORUN option but it did not give me the desired
> results.  I coded the VOLSER of the disk to no avail.  I am doing this
> exercise in preparation of removing old dasd but experiences of the past
> jobs failed because the dsn is not accessible
> Any suggestions would be helpful and welcomed.Here is an example of my jcl:
> //NORUN   EXEC PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>   //*DFDSS1   EXEC PGM=ADRDSSU,REGION=4096K,TIME=1440
>   //DASD1DD UNIT=SYSALLDA,VOL=SER=PROD91,DISP=SHR
>   //TAPE1  DD DSN=SYS2.CLOGR1.CLOGR2.LOGICAL,DISP=(,CATLG,DELETE), //
>UNIT=3490,TRTCH=COMP,LABEL=(1,SL) //SYSPRINT
> DD  SYSOUT=*  //SYSMAP   DD
> SYSOUT=*   //SYSINDD  *
>DUMP
> DATASET(INCLUDE(SYS2.ORDMS.FILES.PROD))  -  SPHERE
>  -
> SELECTMULTI(FIRST)   -
> LOGINDDNAME(DASD1)  -
> OUTDD(TAPE1) OPT(4) ALLDATA(*) ALLEXCP -
> TOL(ENQF)  /*
>
>
>
Do you mean DSNs in a catalog that don't exist on some volume (I am
guessing DASD in particular)? ADRDSSU won't address that. T-REX has a SCRUB
command which will do it. We use that at disaster recovery. I am not aware
of any z/OS "built in" facility to do that.

-- 
A sine curve goes off to infinity, or at least the end of the blackboard.
-- Prof. Steiner

Maranatha! <><
John McKown

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