DB Integrator - embedded SQL in COBOL to access SQLserver

[shivkumar ramraj]

I read about this layered product and want to know if it is still supported on VMS 7.3-2.

My basic requirement is using VMS COBOL with embedded SQL to access a SQLserver database on Windows NT.

[Craig A Berry]

According the the rollout report here:

http://h71000.www7.hp.com/openvms/os/swroll/62ONLY.HTML

it is a retired product and not supported on any version of VMS after v6.2. I believe Attunity Connect is the supported follow-on product. There are also various other third-party ODBC drivers and other client libraries. This comes up fairly often and you will probably find quite a bit about it in the archives of this forum and/or the comp.os.vms newsgroup.

Is it mandatory that you have embedded SQL, or will any API that provides SQL Server access meet your needs?

[Arch_Muthiah]

Shiva,

go thru this site, www.trifox.com, you can find couple of Db connectivity tools to connect to various database including SQL Server from VMS using various language.


Archunan

[Arch_Muthiah]

Shiva,

I just googled and found DB Integrator is used to connect to DEC's RMS, Rdb, and IBM's DB2, and Sybase's SQL Server DB, but they did not mention about MS SQL Server.

And there is a another connectivity software called CONNEX, VMS version is available to connect with MS SQL Server.


Archunan

[shivkumar ramraj]

It is mandatory to have embedded SQL since our's is a legacy application. I am looking at the various other products suggested in this forum. Thank you for all your suggestions.

[Richard J Maher]

Hi Shivkumar,

It is my understanding that the DB Integrator product is no longer supported. (By all accounts it still works well, but. . .) See www.oracle.com/rdb for more.

As far as what you are trying to achieve, may I suggest that "Big Bang" conversions (architectural sea changes) rarely work. IMHO you'd be better served deciding exactly what your future/going-forward development strategy is going to be. (If that involves, any "development" at all; and sadly for many it doesn't.) Then investigate, how best to integrate your "legacy" VMS applications and data.

If you have indeed chosen Windows2000, SQL Server and .NET as the tools of choice at your company for future applications development, then I have other suggestions on how best to integrate your Rdb/VMS apps.

Long-term, peaceful, coexistance of new and pre-loved applications is a strategy that seems to be seldom chosen, yet it is the one that both makes the most sense and stands the greatest chance of success.

Lamentably, many "new" whiz-bang developments are sold on the streangth of exaggerated cost-savings from the future decomissioning of the "Legacy" systems. From painfull experience we all know that the cost-savings never materialize, but the opportunity to best integrate these systems is lost.

Cheers Richard

[Jan van den Ende]

Shivkumar,

Please read the answer by Richard very carefully!.
It contains a wealth of experimental wisdom.

Richard,
you worded it very nicely, very conciselt.

I trust you will not mind if I will quote you as often as I see need when trying to convince those who have to make decisions without knowledge themselves (you recognise the type!).

Proost.

Have one on me.

jpe