I seem to remember that there was a JOB restructuring function available with Batch Pipes. Not aware that it was used much. Or if its still around. The problem with that product was that it relied on history. As soon as you change a JOB, for the next N (not sure how many) runs it does no optimization. This is while it relearns the new JOB structure. I think any JCL change to the JOB would stop the optimization. Thus the batch window will run longer for this period of relearning. Also there were several things it could not detect. Me, I would go with a manual process to fix the big gains. Terry Draper zSeries Performance Specialist
--- On Thu, 19/3/09, Spencer, Mike <mike_spen...@bmc.com> wrote: From: Spencer, Mike <mike_spen...@bmc.com> Subject: Re: Any Batch Pipes experience? To: IBM-MAIN@bama.ua.edu Date: Thursday, 19 March, 2009, 11:26 AM Ah, to keep with the 80's theme, "way, dude" if you have lots of time on your hands. Yes, the user could insert another JOB card, but with thousands of jobs executing, and not being a consultant, I have better things to do than waste my company's dollars trying to manually streamline my batch processes. And of course there are no IO savings by inserting another JOB card. MAINVIEW Batch Optimizer provides the ability to pipe around DB2 or IMS steps to negate any negative impact. It's all a very simple process to implement. Michael Spencer BMC Software -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Nemo Sent: Wednesday, March 18, 2009 12:59 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Any Batch Pipes experience? On Wed, 18 Mar 2009 07:45:09 -0500, Spencer, Mike wrote: >Batch Pipes can only move data between two different jobs. It cannot >move data between steps because in a Batch Pipes world, there is no way to get multiple steps running in parallel for the pipe to work. "no way"?!? All the user needs to do is insert another JOB card (non-duplicate name is a plus but not a requirement if JES' duplicate jobs are allowed to execute concurrently). That sounds like a "way" to me. >MAINVIEW Batch Optimizer from BMC will run steps in parallel, entire >jobs in parallel, and optimizes QSAM and native VSAM I/O processing among other items. Does BMC's MAINVIEW Batch Optimizer have a clue if more than one of those parallel job steps are updating the same DB2 table (and thus potentially causing damage)? Some steps have implicit serialization requirements. How does BO cope with those? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html