🚀 go-pugleaf

Gary Long <garyl@magna.com> wrote:

=>>From: d4dmitc@sr.pacbell.com (Dave Mitchell)
=>>Subject: Vis Basic to MVS DB2
=>>Date: Tue, 07 May 1996 20:41:34 GMT
=>>
=>>We are converting our existing COBOL/DB2/CICS apps to a Visual
Basic
=>>front-end (running on Win/NT or Win 3.11) but the data will remain
in
=>>DB2 on MVS.  Has anyone had experience with doing this - what will
[snip]
=>>Thanks,
=>>
=>>Dave

=>Dave, it depends a lot on the type of application you are creating.
If it is 
=>retrieval-intensive -- DSS or whatever -- then a DBMS gateway such
as DDCS is 
=>the right choice.  If it is transaction-oriented, then I highly
recommend 
=>IBM's CICS External Client Interface (ECI).

=>For transacations, ECI is easy and clean.  Works like a charm.

=>Your PC can send a message directly to a CICS/ESA COBOL program via
SNA.  
=>(ECI also works with to CICS/AIX.)  The CICS COBOL program gets the
message 
=>in the COMMAREA and replies the same way.  You can access data of
any kind, 
=>and also reuse legacy code.

=>Only problem with the ECI is that it is C-oriented making it a
little hard
=>to use from PB or VB.  For our Application Generator we wrote a DLL
to make 
=>it easy (not a real big deal).

=>-- Gary

We are currently using DDCS.  As you said, retrieval works well and is
fairly quick.  Updating, on the other hand, with any volume, stinks.

We are in the process of creating stored procedures on the mainframe
to handle all updates.  Plan is to batch all updates and let the
stored procedure parse and apply.

Anyone have any real life experience with this type of approach?