I solve this type of data passing requirement by generating JCL SET statements (in job #1, stored in a PDS member) and using those SET (they are symbolics without using a PROC) definitions to substitute PARM= and JCL DD statement parameters. The subsequent job would use a JCLLIB and JCL INCLUDE MEMBER= statement to reference in the "variable" information. Obviously job #2 cannot enter the JES until job #1 has completed. Check the IBM-MAIN archives for prior discussions on JCLLIB/SET usage for variable data.
Sincerely, Scott Barry SBBWorks, Inc. George Dranes wrote: > I have a bit of a weird situation in which I'm running a clist in a step > of a batch job. In this clist I'm reading an input file containing > variables that I would like to use in the following steps of the same job. > For example as datasetnames, PARM options etc. I hope I'm making sense. > Is this possible? I'm open to any alternative options. Thanks for your > help. ---------------------------------------------------------------------- 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
