On Sep 18, 2006, at 2:04 PM, Clark F Morris wrote:
On 18 Sep 2006 11:33:20 -0700, in bit.listserv.ibm-main you wrote:
ISPF Service LMMList can do it.
Or you could write a little REXX to LISTDSI the dataset and pick
up the
unit and volser. Then you could build your IEHLIST control card
dynamically and get the same output you are familiar with.
Isn't IEHLIST long overdue for eliminating the need for specific
volume information? It is aggravations like this that make zOS look
dumb to those on other platforms.
Wasn't IEHLIST Functionally stabalized?
Ed
-----Original Message-----
From: CAPRON Romain [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 17, 2006 11:50 PM
To: [email protected]
Subject: IEHLIST LISTPDS in an SMS environment
Hello,
We're going to use SMS allocation in our z/OS 1.4 Production systems.
I have a little problem: a lot of our job batch use IEHLIST utility
LISTPDS command to retrieve the member list of some PDS.
With this utility, you have to put the right volser to make it
working...
But, with our SMS constructs, we won't know the volser and we
don't want
to know it :-) We don't want to use the Guaranteed Space attribute...
Is there another way to generate the member list of a PDS in a batch
environment without giving the volser?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
