To be precise, I am generating a JCL and JCL steps using SORT utility for each of the change #no from the input file. I know that we can achieve the above requirement using BUILD and SEQUENCE by incrementing SEQUENCE NO by 14 times for each of the line. but it will take 14 steps all together. So could you please let me know, if we can do this requirement in less no of steps.
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
ISPF file tailoring would be the way to go, do it all in one easy step
and as a bonus you would be using the correct tool for the job
What happens if there are 33 lines in the input file, will that take 33 steps, how do you control the flexibility for a change in the number of records.
Unless you mean the number of lines of code for each step, incidentally only 13 lines.
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
expat wrote:
What happens if there are 33 lines in the input file, will that take 33 steps, how do you control the flexibility for a change in the number of records.
Unless you mean the number of lines of code for each step, incidentally only 13 lines.
enrico-sorichetti wrote:
having batch ISPF jobs in production is usually frown upon
but, why 33 steps ?
Not everywhere frowns upon using ISPF, or other products, to generate batch jobs. I know, I've worked at quite a few