Hi, A recent post posed the question:
"I need to schedule the execution of 26 jobs. This has to happen such that the 2nd job should start after the successful execution of the 1st job, the 3rd after the 2nd and so on. Moreover the output of 1st job is the input to the 2nd job. How do I accomplish this using Clist?" If an aim of the list is to foster best practice surely a distinction here needs to be made between Production and Development requirements. For Development, then using a CLIST, or better yet REXX, may well be adequate. As may any number of alternatives using PDS(E) members and a favourite utility to submit successive jobs via the internal reader. Yes in an in JES3 the //*NET statement fits the bill nicely, provided other measures are taken to ensure that sentence 3 of the requirement is met. For Production use it is surely better to use the installation Job Scheduling package. Whilst it is possible that an installation may not have such a product, most sites with modest to sizable batch loads would have one I suspect. Job Scheduler products may not be uppermost in a developers mind if they are divorced from the installation by either politics, geography or both. This is not an attempt to run with the open-sore of out-sourcing, there is enough bile and puss there already. It is an attempt to look at a possible bigger picture. Kind regards - Terry Terry Sambrooks Director KMS-IT Limited 228 Abbeydale Road South Dore Sheffield S17 3LA UK Tel: +44 (0)114 262 0933 WEB: www.legac-e.co.uk www.kmsitltd.co.uk Reg: England & Wales 3767263 at the above address All outgoing E-mails are scanned but it remains the recipients responsibility to ensure that their system is protected from viruses, trojans, worms, and spy-ware. ---------------------------------------------------------------------- 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
