Joined: 14 May 2021 Posts: 1 Location: United States
Hi everyone! I'm pretty new to mainframes and so it's still taking time getting used to, and I tried searching for the answer to the question up above on Google and these forums but can't seem to find the right one for my needs.
The problem is there are 58 jobs that need to be submitted. They are not currently set up as PROCs, and they all relatively look similar except for the first job which has a few extra steps. They each have TXYY property which is a year value. I was attempting to do this using ICEGENER but didn't know how to SET the TXYY variable within each job properly (or if it's even possible).
My plan is to duplicate the above code for 56 other jobs. But is there a way to achieve this while also setting a PARM in each of the jobs I'm passing to the internal reader?
1) You must use the code tags when posting any code samples
2) Your example does not include “multiple jobs”, but rather “multiple job steps”
3) You can easily use a local // PROC definition at the top of your (actual) job, to // EXEC this procedure multiple times in the same job
4) Any JCL, before it has been SUBMITted, is just a plain text, nothing else. If only you have any experience with text handling tools (hundreds of them are available, from REXX to SORT utilities, and beyond), then you can easily generate your either jobs, or job steps, or whatever else, and then to SUBMIT it using internal reader.
5) It is unclear, what is your TXYY parameter, and where it is supposed to go? If you clarified this issue, you would get some advice.
6) It seems to be a one-time-task - how to create this “huge”(?) JCL? If so, the best way to do this must be: using ISPF editor to create such JCL once, and then to submit it millions of times.
Now to your parameter question, as sergeyken writes, we need some more info. You might be able to use JCL symbols, but you will need to modify the jobs somehow, unless you use a program to read the jobs and write the result to INTRDR.
And don't post the same question in multiple sections, it is bad form and likely to get you banned
Joined: 30 Nov 2013 Posts: 917 Location: The Universe
Mr. Jensen is correct. What Mr. Jenson did not say is that each job step in GCLionCross's initial post submits a complete job. The second step is not a continuation of the first step.
Another possible concern is the JCLLIB suffix in the data set name. Many times a data set with the JCLLIB suffix contains user cataloged procedures brought into the JCL by using the
// JCLLIB ORDER=(....JCLLIB) JCL statement
A cataloged procedure does not have a // JOB JCL statement; each member specified in the JCL like the JCL in the initial post must have JOB JCL statement.
