It's been a decade or two, but concurrent batch/online was a base feature of IMS. Problems included the difficulty in backing out the effects of a malfunctioning batch program.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Anne & Lynn Wheeler Sent: Monday, May 05, 2008 11:29 PM To: [email protected] Subject: Re: Long running Batch programs keep IMS databases offline The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main as well. "F" <[EMAIL PROTECTED]> writes: > We have IMS 9 on z/OS and I am fairly new to the platform and have a > vested interest in fixing it. Every night we have batch programs that > run which in return keeps our databases offline for a long time and as > a result our applications are not available for processing. > > I want to know why batch programs and databases cannot both be online > at the same time ? If the batch programs read the databases, then why > are they offline ? > > Anyways, what are some ways of ensuring that batch jobs and databases > can both run and be online at the same time ? some recent discussions about "overnight batch window" ... which requires exclusive access to all the information ... as opposed to "online". http://www.garlic.com/~lynn/2008b.html#74 Too much change opens up financial fault lines http://www.garlic.com/~lynn/2008c.html#92 CPU time differences for the same job http://www.garlic.com/~lynn/2008d.html#30 Toyota Sales for 2007 May Surpass GM http://www.garlic.com/~lynn/2008d.html#31 Toyota Sales for 2007 May Surpass GM http://www.garlic.com/~lynn/2008d.html#73 Price of CPU seconds http://www.garlic.com/~lynn/2008d.html#87 Berkeley researcher describes parallel path http://www.garlic.com/~lynn/2008d.html#89 Berkeley researcher describes parallel path http://www.garlic.com/~lynn/2008g.html#55 performance of hardware dynamic scheduling http://www.garlic.com/~lynn/2008h.html#50 Microsoft versus Digital Equipment Corporation there were some number of efforts in the 90s (billions of dollars) that looked at business process re-engineering to leverage killer micros and distributed object-oriented technology to implement "straight-through processing" (eliminating the "overnight batch window"). It turns out that many of these had grandious failures when nobody bothered to do any speeds&feeds until very late in the effort ... frequently belatedly discovering that the distributed object-oriented technology had a factor of 100 times increase in overhead (compared to the typical Cobol batch implementation), totally obliterating any hopes of throughput improvements. ---------------------------------------------------------------------- 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 NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- 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
