Re: Productivity

Just my two cents - Data Warehousing often requires a really staggering
amount of data manipulation and reduction before it is stored in the
warehouse. COBOL, in particular BATCH COBOL, is really good for this.

Secondly, OLTP systems usually have a batch processing back end to them
somewhere or another. BATCH processing is just cheaper and faster, and as
such will stick around for a long time to come. ;) COBOL is again, good for
that.

-Paul

"Pete Dashwood" <dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4vis2tF1cbkkdU1@xxxxxxxxxxxxxxxxxxxxx

"Howard Brazee" <howard@xxxxxxxxxx> wrote in message
news:dnn7p2lh7524u11iuvt77dcchh76c53cfk@xxxxxxxxxx
On Thu, 28 Dec 2006 14:34:05 +1300, "Pete Dashwood"
<dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Yes, COBOL is excellent for sequential batch processing and will fill
that
requirement for some time to come. Eventually, transactions will be
processed so fast that Batch will not be necessary, even reports will be
spooled online as transactions occur, and so there will be less
dependence
on Batch. Only historical reporting would need a batch approach. But that
time is still a few years off yet.

I see lots of shops going with data warehouses on one side, and
on-line transactions on the other side - with interfaces between the
web servers accessing both. Where is batch CoBOL needed in that?

A good question. I hadn't considered that scenario. Thanks, Howard.

Pete.



.

Relevant Pages