Re: Legacy Migration

From: Martyn D. Hodgson <Martyn_D._Hodgson_at_unn.unisys.com>
Date: 1996/04/21
Message-ID: <F4413F2D_CBEE366B_7C86B3_85256313_at_BBLN9.unn.unisys.com>#1/1

There are products available that will allow communications to CICS and other legacy systems, such as Unisys Mapper, UNIFACE, .... You could also use an ODBC interface to CICS.

Martyn

The opinions expressed here are my own and do not represent those of Unisys Corporation

* * * Original Message * * * * In article <04-06-1996.100_at_worldchat.com> Felina Urciuoli of WorldCHAT (tm) Internet writes:

Help!!!!!!

Does anyone have a solution?

We have mainframe applications currently written in CICS/COBOL pointing to VSAM files. We would like a way to migrate the VSAM data to an oracle database but still have the legacy applications stay on the mainframe for now until we can develop new applications using powerbuilder. Is there a way the CICS/COBOL programs can talk to the new oracle database that resides on a HP/UX server?

Does anybody have any other ideas?

Need a solution A.S.A.P.

Thank you.

* * * End Original Message * * * *

Received on Sun Apr 21 1996 - 00:00:00 CEST

This message: [ Message body ]
Next message: Kent Milligan: "Re: Is there a workaround for the 'mutating table' problem in a trigger ?"
Previous message: Dale: "Q: Trigger when users connect or disconnect ??"
In reply to: Felina Urciuoli: "Legacy Migration"
Next in thread: Kent Milligan: "Re: Is there a workaround for the 'mutating table' problem in a trigger ?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message