You’re right. It stops with the //. ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Bob Bridges <[email protected]> Sent: Friday, December 22, 2023 11:04:09 AM To: [email protected] <[email protected]> Subject: Stupid JCL question
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. --- Bob Bridges, [email protected], cell 336 382-7313 /* "Poor Diogenes; if you knew how to get on with people you wouldn't have to live like that." / "Poor Aristippos; if you knew how to live like this you wouldn't have to get on with people." -a condensation of their respective schools of thought a few centuries BC */ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
