Re: Productivity



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?
.



Relevant Pages

  • Re: Productivity
    ... processed so fast that Batch will not be necessary, even reports will be ... spooled online as transactions occur, and so there will be less ...
    (comp.lang.cobol)
  • Re: Productivity
    ... 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 ...
    (comp.lang.cobol)
  • Re: Productivity
    ... 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 ...
    (comp.lang.cobol)
  • Re: (not entirely...) OT: OPINION... chicken entrails, runic stones, and crystal balls... WAS CoBOL
    ... With the database I use ALL of our batch update ... Journalize the updates along with the existing online transactions. ...
    (comp.lang.cobol)
  • Re: COBOL record length on z/series
    ... transactions loaded on VSAM files used for Random Access from Batch ... Used in Batch Cobol & Assembler, ... USE AFTER ERROR PROCEDURE ON SPANNED-FILE. ...
    (comp.lang.cobol)