In [EMAIL PROTECTED], on 03/09/2007
at 12:59 PM, George Dranes [EMAIL PROTECTED] said:
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
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
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
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.
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
5 matches
Mail list logo
