Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Tandem to Unix/Linux

305 views
Skip to first unread message

Peter Anderson

unread,
Jul 15, 2003, 12:25:08 PM7/15/03
to
Hello all,
I have a company that wants to migrate a legacy
pathway/cobol/screencobol low volumes application (for which nonstop
is not mandatory) from NonStop kernel to Unix/Linux.

DB would be migrated from NonStop SQL to Oracle.

Pathway applications should be either totally or partially rewritten.
For what concerns the scobol user interface, it could be rewritten as
a web application.
The problems come when we want to interface the presentation tier with
business servers (Pathway SEND call) and
define transactions not only at DB level (in this case we need a TP
monitor).

What are, according to your experience, suitable TP monitors for
Unix/Linux ?
What problems do you think we have to solve to develop a framework
that emulates (the main features of) a Pathway environment. The main
items to be addressed I see should be $RECEIVE emulation and
transaction management as mentioned above.

Is anybody of you facing, or is going to, a similar challenge ?

Thanks for your help,
Peter

Daza

unread,
Jul 15, 2003, 12:48:40 PM7/15/03
to
"Peter Anderson" <peter.a...@libero.it> wrote in message
news:7a279bac.03071...@posting.google.com...

Here are my suggestions based on a pilot project I did a few years back.

1) BEA Tuxedo is very similar in concept to Pathway. It's not that hard
to migrate the COBOL85 request/reply messages and $RECIEVE processing to
Tuxedo FML messages etc. Available on leading UNIX & Linux.

2) Micro Focus COBOL is a good migration platform for COBOL85 (assumming
you are not using many Tandem extensions). Available on leading UNIX &
Linux.

3) I believe Oracle still support using an Embedded SQL compiler for
COBOL. I think it is the migration of the SQL code that will cause the
most difficulties.


BEA Tuxedo + Micro Focus COBOL + Oracle sure isn't low cost though! The
pilot proved that it was more cost effective to keep the application
were it was.


Martin Doering

unread,
Jul 16, 2003, 2:55:04 AM7/16/03
to
On 15 Jul 2003 09:25:08 -0700, peter.a...@libero.it (Peter
Anderson) wrote:

>I have a company that wants to migrate a legacy
>pathway/cobol/screencobol low volumes application (for which nonstop
>is not mandatory) from NonStop kernel to Unix/Linux.

We are such a company... :-)

>What are, according to your experience, suitable TP monitors for
>Unix/Linux ?

We also use Bea Tuxedo. We are very satisfied with this product itself

>What problems do you think we have to solve to develop a framework
>that emulates (the main features of) a Pathway environment. The main
>items to be addressed I see should be $RECEIVE emulation and
>transaction management as mentioned above.

Micro Focus Cobol may be a good Cobol environment, and we had been
very satisfied with it for a longer time. But some time ago they
introduced a new runtime licensing scheme, which does not fit to
transactionmonitors at all. You have to license every running
executable. This means for a transaction monitor with 500 running
programs (tuxedo servers), like our's, that you have to pay for each
running program, although you do not really use it actually.

And you can not mix the cheaper runtime licenses with developer
licenses in one Cobol installation (COBDIR). This means, you may have
to pay for 500 expensive developer licenses)

For me as a C programmer it is very strange at all to pay for running
executables. Because of this problem we have lost 1,5 Years with our
migration problem. We are forced to stay with good old tuxedo 6.5,
MqSeries 5.1 and the old Microfocus compiler.

We could not just replace one part of our installation, because of the
introduction of threading in the runtime we are forced to update all
of our components, so that they work together.

For visualisation of screens we use a small mask-interpreter with own
language + converting tools. This is made by a smaller company, but
work pretty well in our production with 3000 workers. Sorry, the page
about this product is just in german:

http://www.itp-online.de/produkt.htm

So my advice:
Do not use this Cobol compiler. Maybe, you could jump onto the Java
train and take legacy J or such. (I'm very angry.) Or do not migrate
at all. And think of all the interdependencies you will have with
different products.

And:
If anybody may have a clue for an alternative cobol compiler running
on HP-UX, Tuxedo and Oracle, you are very welcome!

--
Martin

Daza

unread,
Jul 16, 2003, 6:55:54 AM7/16/03
to
<snip>

> And:
> If anybody may have a clue for an alternative cobol compiler running
> on HP-UX, Tuxedo and Oracle, you are very welcome!
>
> --
> Martin

You might take a look at Fujitsu NETCobol. It supports HP-UX, Solaris,
Linux, Windows

http://www.adtools.com

Don't know how well it works with Tuxedo/Oracle.

Peter Anderson

unread,
Jul 19, 2003, 1:25:02 AM7/19/03
to
Hello all,
I just wanted to say thanks to people who replied to my question.
You gave me good hints.
Thanks
Peter
0 new messages