Have you looked at LISTDSI or the catalog search interface?

On Wed, Oct 9, 2024 at 5:15 AM Jack Zukt <
[email protected]> wrote:

> Hi Mike
> Thank you for your answer.
> Unfortunately that will give me the extent number but not over how many
> DASD, which is what I need for this specific case.
> I have a DFSORT job that gives me the number of extents for a dataset using
> that specific field. I have been tinkering with it trying to get the number
> of different DASD over which a dataset is allocated. It is not going very
> well either :(
> Regards
> Jack
>
>
> On Wed, 9 Oct 2024 at 11:03, Mike Schwab <
> [email protected]> wrote:
>
> > How about DCOLLECT Record D Either over 40?
> > 77(X'4D') UNSIGNED 1 DCDNMEXT NUMBER OF EXTENTS OBTAINED
> > 122(X'7A') CHARACTER 2 DCDVOLSQ VOLUME SEQUENCE NUMBER
> >
> > On Wed, Oct 9, 2024 at 4:26 AM Jack Zukt
> > <[email protected]> wrote:
> > >
> > >  Hi all,
> > >
> > > I was asked to create a REXX program to identify datasets that are
> > > approaching the 59 volumes extent limit.
> > > I was trying to do that using ICETOOL OCCUR statement and a DCOLLECT
> file
> > > for input. So far it is geting me nowhere fast. Do you think that this
> > is a
> > > feaseble option to get that result?
> > >
> > > The statement that I am using is
> > >
> > > OCCURS FROM (INDD01) ON(DCDDSNAM) ON(DCDVOLSR) LIST(OUT001)
> > >
> > > This is giving one line for dataset but only one volser. I was
> expecting
> > > one lline for dataset and a count for volser. So I am on the wrong
> track.
> > > Any ideas?
> > > Regards
> > > Jack
> > >
> > > ----------------------------------------------------------------------
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to [email protected] with the message: INFO IBM-MAIN
> >
> >
> >
> > --
> > Mike A Schwab, Springfield IL USA
> > Where do Forest Rangers go to get away from it all?
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
> >
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to