That's actually how I experimented: Created a couple of IEFBR14 statements. '//' between them caused the second to be discarded; when I added a JOB card after the '//', it executed both of them.
I was reluctant to experiment with the real job; it plays with production DSs and takes a while to run. Then "oh, duh!", I thought, and... --- Bob Bridges, [email protected], cell 336 382-7313 /* By 2005 or so, it will be clear that the Internet's impact on the economy has been no greater than the fax machine's. -Paul Krugman, Nobel-prize-winning economist in 1998 */ -----Original Message----- From: [email protected] <[email protected]> Sent: Friday, December 22, 2023 11:20 Never mind - figured it out by experimentation. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of D alta Sent: Friday, December 22, 2023 11:08 Yes - that will work. You can also test it using a few IEFBR14 steps. Insert // after the first one and you will see that the subsequent steps will not execute. --- On Friday, December 22, 2023 at 11:04:26 AM EST, Bob Bridges <[email protected]> wrote: I should know this - I've been using JCL for decades - but I find I'm uncertain about something I haven't done in a while. I have a production job here that will eventually be rewritten, but for now I'm just going to tell it to execute only the first couple steps. I had in mind inserting "//" before the part of the JCL that I want to skip. Very simple. But wait - does the JCL interpreter discard the rest of the job when it sees that empty '//', or does it interpret the rest as the start of a new job? (Since there's no subsequent JOB statement I'm not terribly worried about it, but it's sloppy; maybe I should just use a COND parm on the JOB card.) This info is probably in the JCL ref, but I don't immediately see it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
