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
