Mark Jacobs wrote:
On 06/24/10 13:59, Frank Swarbrick wrote:
Now that we've been on z/OS for a few weeks I feel to need to ask a
question that has annoyed me since I started working on z/OS two years
ago. Instream datasets are good. Why are they not supported inside
of procs? Is there a technical reason, or is it just "because"? We
use procs for almost all of our production jobs, with many steps that
could take advantage of instream datasets if not for this restriction.
Thanks,
Frank
My WAG would be a combination of the two. There might have been a good
technical reason why not and to change the rules 40+ years after the
fact might break working processes in unexpected ways.
'sFunny, I didn't see your original post, Frank. Are you not
posting to list directly now?
Anyway, it is what it is. But a simple xxxxxx.PARMLIB with members that
contain what you would put into instream data seems to work just fine,
right? Out of curiosity, why do you consider instream data better than
that?
--
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
* To get a good Return on your Investment, first make an investment!
+ Training your people is an excellent investment
----------------------------------------------------------------------
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
