| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Conversion IBM Mainframe CICS,DB2 to Oracle PL/SQL, Des2K, Dev2K
In article <7n06bb$p2n$1_at_autumn.news.rcn.net>,
Umar M Badeges <oemar_at_erols.com> wrote:
>I was following the discussion that there is no good Oracle tools in
>existence and that Designer2K and Developer2K are so buggy that the work
>around to make it work takes longer than doing it.
>
>I am about to jump on a project converting IBM Cobol II, CICS, DB-2 on the
>mainframe to Oracle on the network. Is there any book or guidance that is
>available?
>Or do you think this conversion is not worth it. Thank you.
I am working on a project where we rewrote an entire system from IBM Cobol/VSAM/CICS in Oracle and Forms. It took a long time -- several years, but all users are now on the new system, and they love it.
Our forms have the original CICS look: a 'Call Code' for the screen name in the upper left corner, key items on line 2 used to look up the data, and display and update data fields below. We use Forms default processing most places, but the Execute Query process to display the screen runs a procedure that hops around to each base-table data block and does an automatic Execute_Query to query based on the key values in the line-2 fields.
Along the way, we developed a "skeleton" form as a template to use when starting anything new. It helped maintain the same look and feel between screens.
That thread about Developer being too full of bugs to use is pure baloney. Those people are looking for something cheap and easy to learn, simple to use yet still gets everything done exactly the way they want -- something that does not exist. It takes a lot of time to fully understand what Forms can do for you and to use Forms to the fullest extent. But it gets the job done, and the users like it -- a pretty good end result, by my way of thinking.
Steve Cosner
 |
 |