Replacement for LISTDSI for multivolume datasets searched

2012-09-10 Thread Kenneth J. Kripke
These are ALC macros, but, since you have the disk volsers, they can be
used.  

From the manual DFSMSdfp Advanced Services, Document Number SC26-7400-10

Look at OBTAIN and CVAF. 

K. Kripke

kkri...@mindspring.com

 

  

 

 

 

 


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


Re: Replacement for LISTDSI for multivolume datasets searched

2012-09-09 Thread Scott Ford
I don't dispute fact that replacement for an IDCAMS LISTCAT for determining 
statuses of cataloged VSAM datasets , etc could be in the future. The csi 
interface I use.

Scott ford
www.identityforge.com

On Sep 9, 2012, at 1:32 AM, Ed Gould edgould1...@comcast.net wrote:

 Scott:
 I would suggest rather than to suggest a bad approach is to keep looking.
 You never know in 2 years someone might be researching for a similar problem 
 and the issue becomes a problem yet again.
 Ed
 On Sep 8, 2012, at 6:24 PM, Scott Ford wrote:
 
 Ed,
 
 IBM says these things and I understand, but what alternative has been 
 provided and samples with the alternative.
 
 Scott ford
 www.identityforge.com
 
 On Sep 8, 2012, at 7:06 PM, Ed Gould edgould1...@comcast.net wrote:
 
 Scott:
 
 I think IBM seriously suggested that this was not to be used as it is not a 
 programming interface.
 One off the wall vendor does/did that and every few years it breaks as 
 IDCAMS output changes.
 
 Ed
 
 On Sep 8, 2012, at 9:43 AM, Scott Ford wrote:
 
 Jurgen,
 
 You could also call idcams, output sysprint to a Qsam file, read with rexx 
 and parse
 
 Scott ford
 www.identityforge.com
 
 On Sep 8, 2012, at 6:46 AM, Lizette Koehler stars...@mindspring.com 
 wrote:
 
 For NONVSAM LISTDSI may work, for VSAM CSI will work.
 
 And CSI returns the VOLUMES, RBA, and any other catalog information for 
 both VSAM and NONVSAM.  Including if it spans multi volumes.  If you look 
 at my other postings on CSI you will see that IBM has provided other 
 samples to show how to extract those fields.
 
 For NON Vsam datasets LISTDSI may only show first volumes, not if it 
 spans multi volumes.
 
 If you do a LISTC against a dataset and it shows all the volumes, then 
 the CSI will be able to retrieve those for you.
 
 The following version of CSI Rexx I came across is much better than the 
 SYS1.SAMPLIB version.  However, the enhancement you need is to loop 
 through all the volumes for the dataset.  In the SYS1.SAMPLIB Version it 
 only does one even if there are more.  It would be a simple matter to 
 continue until the end of the volumes was found.
 
 
 And for those that want a better interface to CSI, I came across this gem 
 on the IBM Website
 
 ftp://public.dhe.ibm.com/servers/storage/support/software/dfsms/II14316/II14316.clist.clist
 
 or tinyurl
 http://tinyurl.com/chqotev
 
 
 I have not tried it yet, but apar
 II14316: A NEW TOOL IS AVAILABLE TO INVOKE THE CSI (CATALOG SEARCH 
 INTERFACE) VIA REXX.
 
 Has some interesting context about making this easier to use.
 
 Lizette
 
 
 Dear Lizette,
 
 thanks for your fast response. I was already aware of the CSI, I used it 
 in other REXX
 procedures to search for some datasets similar to ISPF 3.4. But AFAIK 
 CSI only gives
 the name of a dataset, but no other attributes (size etc.). In the case 
 I#m talking
 about now, I already have the name, but I'm looking for other 
 attributes, mainly the
 size of these non-VSAM multi-volume files. Because they are multi-volume 
 LISTDSI
 doesn't work, because they are non-VSAM LISTCAT doesn't help although.
 
 
 Am 08.09.2012 00:58, schrieb Lizette Koehler:
 Yes, you can use the Catalog Search Interface (CSI) to do this.
 
 There is documentation in z/OS V1R12.0 DFSMS Managing Catalogs
 
 And a sample in  SYS1.SAMPLIB(IGGCSIRX)
 
 
 Lizette
 
 
 --
 Freundliche Gruesse / Kind regards
 
 
 --
 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


Re: Replacement for LISTDSI for multivolume datasets searched

2012-09-09 Thread Scott Ford
Thanks Walt, that what I thought also..

Scott ford
www.identityforge.com

On Sep 9, 2012, at 7:28 PM, Walt Farrell walt.farr...@gmail.com wrote:

 On Sun, 9 Sep 2012 12:05:02 -0400, Scott Ford scott_j_f...@yahoo.com wrote:
 
 I don't dispute fact that replacement for an IDCAMS LISTCAT for determining 
 statuses of cataloged VSAM datasets , etc could be in the future. 
 The csi interface I use.
 
 I doubt that IBM will provide yet another interface. CSI is what people 
 should be using (and recommending) if a program needs info from the catalog.
 
 -- 
 Walt
 
 --
 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: Replacement for LISTDSI for multivolume datasets searched

2012-09-08 Thread Jürgen Kehr

Dear Lizette,

thanks for your fast response. I was already aware of the CSI, I used it 
in other REXX procedures to search for some datasets similar to ISPF 
3.4. But AFAIK CSI only gives the name of a dataset, but no other 
attributes (size etc.). In the case I#m talking about now, I already 
have the name, but I'm looking for other attributes, mainly the size of 
these non-VSAM multi-volume files. Because they are multi-volume LISTDSI 
doesn't work, because they are non-VSAM LISTCAT doesn't help although.



Am 08.09.2012 00:58, schrieb Lizette Koehler:

Yes, you can use the Catalog Search Interface (CSI) to do this.

There is documentation in z/OS V1R12.0 DFSMS Managing Catalogs

And a sample in  SYS1.SAMPLIB(IGGCSIRX)


Lizette
  
--

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



--
Freundliche Gruesse / Kind regards

*Dipl. Math. Juergen Kehr *
IT Schulung  Beratung / IT Education + Consulting
Elfbuchenstrasse 10
34317 Habichtswald
Germany

Tel. +49-5606-5337408
Fax +49-3222-9341387
Mobil +49-172-5129389
mailto:kehrjuer...@t-online.de
mailto:kehrjuer...@googlemail.com



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


Re: Replacement for LISTDSI for multivolume datasets searched

2012-09-08 Thread Lizette Koehler
For NONVSAM LISTDSI may work, for VSAM CSI will work.  

And CSI returns the VOLUMES, RBA, and any other catalog information for both 
VSAM and NONVSAM.  Including if it spans multi volumes.  If you look at my 
other postings on CSI you will see that IBM has provided other samples to show 
how to extract those fields.
 
For NON Vsam datasets LISTDSI may only show first volumes, not if it spans 
multi volumes.

If you do a LISTC against a dataset and it shows all the volumes, then the CSI 
will be able to retrieve those for you.

The following version of CSI Rexx I came across is much better than the 
SYS1.SAMPLIB version.  However, the enhancement you need is to loop through all 
the volumes for the dataset.  In the SYS1.SAMPLIB Version it only does one even 
if there are more.  It would be a simple matter to continue until the end of 
the volumes was found.


And for those that want a better interface to CSI, I came across this gem on 
the IBM Website

ftp://public.dhe.ibm.com/servers/storage/support/software/dfsms/II14316/II14316.clist.clist

or tinyurl
http://tinyurl.com/chqotev


I have not tried it yet, but apar
II14316: A NEW TOOL IS AVAILABLE TO INVOKE THE CSI (CATALOG SEARCH INTERFACE) 
VIA REXX.

Has some interesting context about making this easier to use.  

Lizette

 
 Dear Lizette,
 
 thanks for your fast response. I was already aware of the CSI, I used it in 
 other REXX
 procedures to search for some datasets similar to ISPF 3.4. But AFAIK CSI 
 only gives
 the name of a dataset, but no other attributes (size etc.). In the case I#m 
 talking
 about now, I already have the name, but I'm looking for other attributes, 
 mainly the
 size of these non-VSAM multi-volume files. Because they are multi-volume 
 LISTDSI
 doesn't work, because they are non-VSAM LISTCAT doesn't help although.
 
 
 Am 08.09.2012 00:58, schrieb Lizette Koehler:
  Yes, you can use the Catalog Search Interface (CSI) to do this.
 
  There is documentation in z/OS V1R12.0 DFSMS Managing Catalogs
 
  And a sample in  SYS1.SAMPLIB(IGGCSIRX)
 
 
  Lizette
 
 
 --
 Freundliche Gruesse / Kind regards
 

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


Re: Replacement for LISTDSI for multivolume datasets searched

2012-09-08 Thread Scott Ford
Jurgen,

You could also call idcams, output sysprint to a Qsam file, read with rexx and 
parse

Scott ford
www.identityforge.com

On Sep 8, 2012, at 6:46 AM, Lizette Koehler stars...@mindspring.com wrote:

 For NONVSAM LISTDSI may work, for VSAM CSI will work.  
 
 And CSI returns the VOLUMES, RBA, and any other catalog information for both 
 VSAM and NONVSAM.  Including if it spans multi volumes.  If you look at my 
 other postings on CSI you will see that IBM has provided other samples to 
 show how to extract those fields.
 
 For NON Vsam datasets LISTDSI may only show first volumes, not if it spans 
 multi volumes.
 
 If you do a LISTC against a dataset and it shows all the volumes, then the 
 CSI will be able to retrieve those for you.
 
 The following version of CSI Rexx I came across is much better than the 
 SYS1.SAMPLIB version.  However, the enhancement you need is to loop through 
 all the volumes for the dataset.  In the SYS1.SAMPLIB Version it only does 
 one even if there are more.  It would be a simple matter to continue until 
 the end of the volumes was found.
 
 
 And for those that want a better interface to CSI, I came across this gem on 
 the IBM Website
 
 ftp://public.dhe.ibm.com/servers/storage/support/software/dfsms/II14316/II14316.clist.clist
 
 or tinyurl
 http://tinyurl.com/chqotev
 
 
 I have not tried it yet, but apar
 II14316: A NEW TOOL IS AVAILABLE TO INVOKE THE CSI (CATALOG SEARCH INTERFACE) 
 VIA REXX.
 
 Has some interesting context about making this easier to use.  
 
 Lizette
 
 
 Dear Lizette,
 
 thanks for your fast response. I was already aware of the CSI, I used it in 
 other REXX
 procedures to search for some datasets similar to ISPF 3.4. But AFAIK CSI 
 only gives
 the name of a dataset, but no other attributes (size etc.). In the case I#m 
 talking
 about now, I already have the name, but I'm looking for other attributes, 
 mainly the
 size of these non-VSAM multi-volume files. Because they are multi-volume 
 LISTDSI
 doesn't work, because they are non-VSAM LISTCAT doesn't help although.
 
 
 Am 08.09.2012 00:58, schrieb Lizette Koehler:
 Yes, you can use the Catalog Search Interface (CSI) to do this.
 
 There is documentation in z/OS V1R12.0 DFSMS Managing Catalogs
 
 And a sample in  SYS1.SAMPLIB(IGGCSIRX)
 
 
 Lizette
 
 
 --
 Freundliche Gruesse / Kind regards
 
 
 --
 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: Replacement for LISTDSI for multivolume datasets searched

2012-09-08 Thread Ed Gould

Scott:

I think IBM seriously suggested that this was not to be used as it is  
not a programming interface.
One off the wall vendor does/did that and every few years it breaks  
as IDCAMS output changes.


Ed

On Sep 8, 2012, at 9:43 AM, Scott Ford wrote:


Jurgen,

You could also call idcams, output sysprint to a Qsam file, read  
with rexx and parse


Scott ford
www.identityforge.com

On Sep 8, 2012, at 6:46 AM, Lizette Koehler  
stars...@mindspring.com wrote:



For NONVSAM LISTDSI may work, for VSAM CSI will work.

And CSI returns the VOLUMES, RBA, and any other catalog  
information for both VSAM and NONVSAM.  Including if it spans  
multi volumes.  If you look at my other postings on CSI you will  
see that IBM has provided other samples to show how to extract  
those fields.


For NON Vsam datasets LISTDSI may only show first volumes, not if  
it spans multi volumes.


If you do a LISTC against a dataset and it shows all the volumes,  
then the CSI will be able to retrieve those for you.


The following version of CSI Rexx I came across is much better  
than the SYS1.SAMPLIB version.  However, the enhancement you need  
is to loop through all the volumes for the dataset.  In the  
SYS1.SAMPLIB Version it only does one even if there are more.  It  
would be a simple matter to continue until the end of the volumes  
was found.



And for those that want a better interface to CSI, I came across  
this gem on the IBM Website


ftp://public.dhe.ibm.com/servers/storage/support/software/dfsms/ 
II14316/II14316.clist.clist


or tinyurl
http://tinyurl.com/chqotev


I have not tried it yet, but apar
II14316: A NEW TOOL IS AVAILABLE TO INVOKE THE CSI (CATALOG SEARCH  
INTERFACE) VIA REXX.


Has some interesting context about making this easier to use.

Lizette



Dear Lizette,

thanks for your fast response. I was already aware of the CSI, I  
used it in other REXX
procedures to search for some datasets similar to ISPF 3.4. But  
AFAIK CSI only gives
the name of a dataset, but no other attributes (size etc.). In  
the case I#m talking
about now, I already have the name, but I'm looking for other  
attributes, mainly the
size of these non-VSAM multi-volume files. Because they are multi- 
volume LISTDSI
doesn't work, because they are non-VSAM LISTCAT doesn't help  
although.



Am 08.09.2012 00:58, schrieb Lizette Koehler:

Yes, you can use the Catalog Search Interface (CSI) to do this.

There is documentation in z/OS V1R12.0 DFSMS Managing Catalogs

And a sample in  SYS1.SAMPLIB(IGGCSIRX)


Lizette



--
Freundliche Gruesse / Kind regards



- 
-

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: Replacement for LISTDSI for multivolume datasets searched

2012-09-08 Thread Scott Ford
Ed,

IBM says these things and I understand, but what alternative has been provided 
and samples with the alternative.

Scott ford
www.identityforge.com

On Sep 8, 2012, at 7:06 PM, Ed Gould edgould1...@comcast.net wrote:

 Scott:
 
 I think IBM seriously suggested that this was not to be used as it is not a 
 programming interface.
 One off the wall vendor does/did that and every few years it breaks as IDCAMS 
 output changes.
 
 Ed
 
 On Sep 8, 2012, at 9:43 AM, Scott Ford wrote:
 
 Jurgen,
 
 You could also call idcams, output sysprint to a Qsam file, read with rexx 
 and parse
 
 Scott ford
 www.identityforge.com
 
 On Sep 8, 2012, at 6:46 AM, Lizette Koehler stars...@mindspring.com wrote:
 
 For NONVSAM LISTDSI may work, for VSAM CSI will work.
 
 And CSI returns the VOLUMES, RBA, and any other catalog information for 
 both VSAM and NONVSAM.  Including if it spans multi volumes.  If you look 
 at my other postings on CSI you will see that IBM has provided other 
 samples to show how to extract those fields.
 
 For NON Vsam datasets LISTDSI may only show first volumes, not if it spans 
 multi volumes.
 
 If you do a LISTC against a dataset and it shows all the volumes, then the 
 CSI will be able to retrieve those for you.
 
 The following version of CSI Rexx I came across is much better than the 
 SYS1.SAMPLIB version.  However, the enhancement you need is to loop through 
 all the volumes for the dataset.  In the SYS1.SAMPLIB Version it only does 
 one even if there are more.  It would be a simple matter to continue until 
 the end of the volumes was found.
 
 
 And for those that want a better interface to CSI, I came across this gem 
 on the IBM Website
 
 ftp://public.dhe.ibm.com/servers/storage/support/software/dfsms/II14316/II14316.clist.clist
 
 or tinyurl
 http://tinyurl.com/chqotev
 
 
 I have not tried it yet, but apar
 II14316: A NEW TOOL IS AVAILABLE TO INVOKE THE CSI (CATALOG SEARCH 
 INTERFACE) VIA REXX.
 
 Has some interesting context about making this easier to use.
 
 Lizette
 
 
 Dear Lizette,
 
 thanks for your fast response. I was already aware of the CSI, I used it 
 in other REXX
 procedures to search for some datasets similar to ISPF 3.4. But AFAIK CSI 
 only gives
 the name of a dataset, but no other attributes (size etc.). In the case 
 I#m talking
 about now, I already have the name, but I'm looking for other attributes, 
 mainly the
 size of these non-VSAM multi-volume files. Because they are multi-volume 
 LISTDSI
 doesn't work, because they are non-VSAM LISTCAT doesn't help although.
 
 
 Am 08.09.2012 00:58, schrieb Lizette Koehler:
 Yes, you can use the Catalog Search Interface (CSI) to do this.
 
 There is documentation in z/OS V1R12.0 DFSMS Managing Catalogs
 
 And a sample in  SYS1.SAMPLIB(IGGCSIRX)
 
 
 Lizette
 
 
 --
 Freundliche Gruesse / Kind regards
 
 
 --
 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: Replacement for LISTDSI for multivolume datasets searched

2012-09-08 Thread Ed Gould

Scott:
I would suggest rather than to suggest a bad approach is to keep  
looking.
You never know in 2 years someone might be researching for a similar  
problem and the issue becomes a problem yet again.

Ed
On Sep 8, 2012, at 6:24 PM, Scott Ford wrote:


Ed,

IBM says these things and I understand, but what alternative has  
been provided and samples with the alternative.


Scott ford
www.identityforge.com

On Sep 8, 2012, at 7:06 PM, Ed Gould edgould1...@comcast.net wrote:


Scott:

I think IBM seriously suggested that this was not to be used as it  
is not a programming interface.
One off the wall vendor does/did that and every few years it  
breaks as IDCAMS output changes.


Ed

On Sep 8, 2012, at 9:43 AM, Scott Ford wrote:


Jurgen,

You could also call idcams, output sysprint to a Qsam file, read  
with rexx and parse


Scott ford
www.identityforge.com

On Sep 8, 2012, at 6:46 AM, Lizette Koehler  
stars...@mindspring.com wrote:



For NONVSAM LISTDSI may work, for VSAM CSI will work.

And CSI returns the VOLUMES, RBA, and any other catalog  
information for both VSAM and NONVSAM.  Including if it spans  
multi volumes.  If you look at my other postings on CSI you will  
see that IBM has provided other samples to show how to extract  
those fields.


For NON Vsam datasets LISTDSI may only show first volumes, not  
if it spans multi volumes.


If you do a LISTC against a dataset and it shows all the  
volumes, then the CSI will be able to retrieve those for you.


The following version of CSI Rexx I came across is much better  
than the SYS1.SAMPLIB version.  However, the enhancement you  
need is to loop through all the volumes for the dataset.  In the  
SYS1.SAMPLIB Version it only does one even if there are more.   
It would be a simple matter to continue until the end of the  
volumes was found.



And for those that want a better interface to CSI, I came across  
this gem on the IBM Website


ftp://public.dhe.ibm.com/servers/storage/support/software/dfsms/ 
II14316/II14316.clist.clist


or tinyurl
http://tinyurl.com/chqotev


I have not tried it yet, but apar
II14316: A NEW TOOL IS AVAILABLE TO INVOKE THE CSI (CATALOG  
SEARCH INTERFACE) VIA REXX.


Has some interesting context about making this easier to use.

Lizette



Dear Lizette,

thanks for your fast response. I was already aware of the CSI,  
I used it in other REXX
procedures to search for some datasets similar to ISPF 3.4. But  
AFAIK CSI only gives
the name of a dataset, but no other attributes (size etc.). In  
the case I#m talking
about now, I already have the name, but I'm looking for other  
attributes, mainly the
size of these non-VSAM multi-volume files. Because they are  
multi-volume LISTDSI
doesn't work, because they are non-VSAM LISTCAT doesn't help  
although.



Am 08.09.2012 00:58, schrieb Lizette Koehler:

Yes, you can use the Catalog Search Interface (CSI) to do this.

There is documentation in z/OS V1R12.0 DFSMS Managing Catalogs

And a sample in  SYS1.SAMPLIB(IGGCSIRX)


Lizette



--
Freundliche Gruesse / Kind regards



--- 
---

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


Replacement for LISTDSI for multivolume datasets searched

2012-09-07 Thread Jürgen Kehr

Hi,

in a REXX application I used LISTDSI to determine the size of some 
datasets, in order to generate a JCL stream and FTP locsite statements. 
Now the datasets growed, so I meeded to define some datasets as multi 
volume files. But here I recognized that LISTDSI doesn't support multi 
volume datasets. So I'm looking for a replacement for LISTDSI to get the 
total size of the files on all volumes.


Any idea appreciated.

--
Freundliche Gruesse / Kind regards

*Dipl. Math. Juergen Kehr *
IT Schulung  Beratung / IT Education + Consulting
Elfbuchenstrasse 10
34317 Habichtswald
Germany

Tel. +49-5606-5337408
Fax +49-3222-9341387
Mobil +49-172-5129389
mailto:kehrjuer...@t-online.de
mailto:kehrjuer...@googlemail.com



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


Re: Replacement for LISTDSI for multivolume datasets searched

2012-09-07 Thread Lizette Koehler
Yes, you can use the Catalog Search Interface (CSI) to do this.

There is documentation in z/OS V1R12.0 DFSMS Managing Catalogs 

And a sample in  SYS1.SAMPLIB(IGGCSIRX)


Lizette
 
Hi,

in a REXX application I used LISTDSI to determine the size of some 
datasets, in order to generate a JCL stream and FTP locsite statements. 
Now the datasets growed, so I meeded to define some datasets as multi 
volume files. But here I recognized that LISTDSI doesn't support multi 
volume datasets. So I'm looking for a replacement for LISTDSI to get the 
total size of the files on all volumes.

Any idea appreciated.

-- 
Freundliche Gruesse / Kind regards


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