On 2010-06-24 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.
Back in 1991, I greatly appreciated the JCL enhancements that came in MVS/ESA 4.1 (INCLUDE, SET, proc/include nesting, etc), but I felt disappointed that in-line control-cards were still incompatible with PROCs - like you say. Since the target became MVS/ESA 4.1, most of the VSE/MVS conversions I was involved in didn't use procedures in their MVS JCL, because most of the reasons procs had to be used before MVS/ESA 4.1 were gone. Several of these conversion projects had a VSE scheduler that supported variables in control cards, and needed something equivalent in MVS. So, in MVS, they used TSREPVAR, TSIDCAMS, other similar utilities, or SUBSYS=(CCSS,... -- they're described here: http://gsf-soft.com/Products/CCSS.shtml -- Gilbert Saint-Flour GSF Software http://gsf-soft.com PS: Sorry it took me so long to reply to this message. ---------------------------------------------------------------------- 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
