I use this sort of trick often for controlling sections of JCL, For example, I might have a step or two that deletes and allocates files, then another step that processes data into the new files, and finally a step that prints report files from the job. Then at the top I would SET ALLOC = either 1 to run or 0 to not run, SET PROCESS to 1/0, and SET REPORTS to 1/0.
In the JCL I start with a do-nothing BR14, and then surround each section with IF &ALLOC=1 THEN......ENDIF If &PROCESS=1 THEN.....ENDIF and If &REPORTS=1 THEN.....ENDIF This might be a weak example, but I can't go into more specific "real" details of our jobs. I think you can get the idea. billy On Thu, Feb 23, 2012 at 2:22 AM, Andrew Armstrong < androidarmstr...@gmail.com> wrote: > On Tue, 21 Feb 2012 15:48:12 -0600, Paul Gilmartin <paulgboul...@aim.com> > wrote: > > >Nope. RTFM. > > ...nevertheless (even though it's not in the fine manual) something that > appears to work for me is: > > // IF 1 = 1 THEN > ...do this stuff... > // ENDIF > > and > > // IF 1 = 0 THEN > ...don't do this stuff... > // ENDIF > > hmmm...bug or feature? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > -- Thank you and best regards, *Billy Ashton* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
