On 02/21/2012 10:16 AM, McKown, John wrote:
Do you ever want to "retire" some step(s) from a job? But you don't really want to remove
the step(s) "just in case"? I don't remember this being mentioned before, so I thought I
would. It will work for any step, other than the first one in the job. Find a step, any step,
before the step(s) you want to bypass. Wrap the step(s) you want to bypass with:
// IF (stepname.RUN=TRUE AND stepname.RUN=FALSE) THEN
.... steps to be bypassed
// ENDIF
Replace "stepname" with the name of the step you selected which exists before
the bypassed step(s). This works if the previous step ran or didn't run, regardless of
the step's return code if it did run. Sorry if this was obvious. Maybe my brain has
retired already.
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mck...@healthmarkets.com * www.HealthMarkets.com
...
But be aware there can still be some interactions with the DSNs
referenced in the DDs for the skipped step. Whether a DSN enqueue is
done, the type of enqueue, and how long the enqueue is held may still be
influenced by the reference to the DSN in the skipped step. Also, job
restart managers (ZEBB, CA-11,...) that are configured for auto delete
of existing datasets at start of job if the first reference to that DSN
in the job is with DISP=(NEW...) may be fooled if that first reference
is in a job step that will be skipped.
If you really want guaranteed zero effects from the unwanted step
without complete deletion of step JCL, changing the statements to
comments is the only sure way.
--
Joel C. Ewing, Bentonville, AR jcew...@acm.org
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
