 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Isolation level&#8230; Join new JAVA development with old, outdated COBOL code&#8230;</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/isolation-level-join-new-java-development-with-old-outdated-cobol-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/isolation-level-join-new-java-development-with-old-outdated-cobol-code/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 00:46:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: tellme</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/isolation-level-join-new-java-development-with-old-outdated-cobol-code/#comment-36256</link>
		<dc:creator>tellme</dc:creator>
		<pubDate>Tue, 31 Oct 2006 10:54:03 +0000</pubDate>
		<guid isPermaLink="false">#comment-36256</guid>
		<description><![CDATA[Here is one of many possible solutions.
You mentioned the cobol program is a batch job and you are dealing with Java and record locks. The solution needs to deal with single transaction processor where a data queue will funnel the requests to the Cobol program that would stay resident and handle the record locks. The Java front end needs to pass a request to the server side that ends up on the data queue. This eliminates contention for for recod locks.
Don&#039;t have enough information on your situation to advise other solutions...
Yes, the Cobol program will need some modifications to allow for interactive use of its business processing provided...you can improve the business in a tangible way your customer can conceptualize and be willing to pay for.
A few questions you will need (or have answered) are:
Why is a overnight solution not good enough for the future?
How does a quick response improve the business?
What are the benefits?
How will it be measured?
When will it be be done?
]]></description>
		<content:encoded><![CDATA[<p>Here is one of many possible solutions.<br />
You mentioned the cobol program is a batch job and you are dealing with Java and record locks. The solution needs to deal with single transaction processor where a data queue will funnel the requests to the Cobol program that would stay resident and handle the record locks. The Java front end needs to pass a request to the server side that ends up on the data queue. This eliminates contention for for recod locks.<br />
Don&#8217;t have enough information on your situation to advise other solutions&#8230;<br />
Yes, the Cobol program will need some modifications to allow for interactive use of its business processing provided&#8230;you can improve the business in a tangible way your customer can conceptualize and be willing to pay for.<br />
A few questions you will need (or have answered) are:<br />
Why is a overnight solution not good enough for the future?<br />
How does a quick response improve the business?<br />
What are the benefits?<br />
How will it be measured?<br />
When will it be be done?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.014 seconds using memcached
Object Caching 268/271 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-24 00:49:29 -->