Hi Alle n,
One package does have the obvious advantage of being - one package. Do you have a decent scheduling system, one that can track completion, and handle predessors and successors, etc.? Ours does. Our p rocesses are set up in 'family' groups, for example xxxJ0110, xxxJ0120, xxxJ0130, and so on. ABEND recovery and restart is generally much simpler wth the smaller jobs in a family group. Linda ----- Original Message ----- From: "Allen Gainsford" <[email protected]> To: [email protected] Sent: Thursday, June 2, 2011 6:36:04 PM Subject: Re: JCL: IF and ABEND > <snip> > On Thu, Jun 2, 2011 at 5:30 PM, Gainsford, Allen > <[email protected]>wrote: > > > Normally (by default), if a jobstep abends, subsequent steps are flushed. > > There ought to be a better way! Have I missed something obvious? Can > > anyone offer a suggestion? > > > > <unsnip> > > can this be managed by breaking the jcl into multiple jobs and posting > conditions to the scheduler and let the scheduling system manage the > process? Yes, but at the cost of making the process even more complex. :) I tend to think that, from a support viewpoint (i.e. from the viewpoint of someone who has to go in and look at job output and possibly trace results), one job is a lot easier to handle than two or three. It's definitely a lot tidier. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
