Jim, for questions about migration to DB2 for z/OS you can drop an e-mail
to this address:

db2...@us.ibm.com

The folks there should at least get you pointed in the right direction on
the database front.

If you're also interested in converting Natural, there are several
potential options. I find that the reasons Natural was chosen versus other
programming languages often still apply. So that tends to suggest keeping a
4th generation language (4GL) in place. Thus I tend to look at those
migration options first, but your mileage may vary.

In IBM's stable there's the Rational Migration Extension for Natural (RMEn)
tool, and optional migration services are available as well. Here's its
announcement letter:

http://www.ibm.com/common/ssi/rep_ca/2/897/ENUS208-162/ENUS208-162.PDF

RMEn is designed to convert Natural to Enterprise Generation Language
(EGL). EGL can deploy just about everywhere, although most Natural for z/OS
shops would probably choose the Rational Runtime for z for performance
reasons. (Any Java runtime, such as WebSphere Application Server for z/OS,
is another choice.) You can write EGL in ISPF if you wish, but most people
nowadays prefer the graphical tooling. Any of these tools support EGL:

Rational Developer for System z with EGL (the most likely choice in this
case)
Rational Business Developer
Rational EGL Community Edition (no charge download)

Other targets are possible besides EGL, including 3rd generation languages,
using other vendors' tools. There are several vendors that advertise
products to convert Natural. Or, as mentioned, you can keep Natural but
change the database.

- - - - -
Timothy Sipples
IBM Consulting Enterprise Software Architect
Based in Tokyo, Serving IBM Japan / Asia-Pacific
E-Mail: timothy.sipp...@us.ibm.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to