Friday Jun 22, 2012

Progress 4GL and DB to Oracle and cloud

Getting from client/server based 4GLs and databases where the 4GL is tightly linked to the database to Oracle and the cloud is not easy. The least risky and expensive option (in the short term) is to use the Progress OpenEdge DataServer for Oracle:
Progress OpenEdge DataServer
This eliminates the need to have to migrate the Progress 4GL to Java/J2EE.
The database can be migrated using SQLWays Ispirer:
Ispirer SQLWays ProgressDB migrations tool

The Progress 4GL can remain as is. In order to get the application on the cloud there are a few approaches:
1. VDI - Virtual Desktop is a way to put all of the users desktop in a centralized environment off the desktop. This is great in cases where it is just not one client/server application that the user needs access too. In many cases, users will utilize MS Access, MS Excel, Crystal Reports and other tools to get at the Progress DB and other centralized databases. Vmware's acquistion of Wanova shows how VDI is growing in usage. Citrix is the 800 pound gorilla in the VDI space with Citrix WinFrame (now called XenDesktop). Oracle offers a VDI solution that Oracle picked up when it acquired Sun.
2. Hypervisor Server Virtualization - Of course you can place applications written in client/server languages like Progress 4GL buy using server virtualization from Oracle, VMWare, Microsoft, Citrix and others.
3. Microsoft Remote Desktop Services (aka: Terminal Services Client)
The entire idea is to eliminate all the client/server desktop devices and connections which require desktop software and database drivers. A solution to removing database drivers from the desktop is to use DataDirect SQLLink

Monday Jun 18, 2012

Mainframe modernization - Getting it to work

Interesting read on a very old (1950s) Medicaid system that the State of NC is struggling to modernize. The new language for the modern system is COBOL. This is causing some 'heads to turn':
State of NC modernization to COBOL

Tuesday May 22, 2012

The COBOL Brain Drain

Cover Story in this edition of Computerworld:
COBOL Brain Drain
Some notable things from article:
1. 48% of companies still use a lot of COBOL. The highest language usage beating even Java!
2. COBOL is being used in 53% of cases for new applications.
3. Move off mainframe / COBOL is not happening any time soon (this is my interpretation) as the article mentions this a couple times 5-10 years people will start
to retire...which means more like 10-15 years.
4. Thought this was funny but sad. US government had IBM look at a System/36 environment to see if should be migrated off this system. IBM concluded it would
be to complicated and costly. This is like hiring Microsoft to see if you should move from Window/SQL Server to Linux/Oracle.

Sunday May 20, 2012

HP and Dell make major moves in modernization and cloud

HP and Dell in same story about my two favorite topics: legacy migrations and cloud computing. I did not realize that Dell is also make a play in the modernization and cloud space in regards to legacy 3270 terminal migration/modernization to newer thin client hardware (Wyse terminals). Did not think of this terminal modernization market before but there is definitely a lot of money to be made selling terminal hardware modernization! Read more: HP and Dell cloud and modernization plays

Wednesday May 16, 2012

RISC to x86 migrations - Or CISC to RISC

Migrating from RISC based systems to x86 (CISC based systems) is another type of cloud migration along with application, database, and mainframe z/OS migrations. However, the steps, best
practices, process, methodology, and tools used are the same. The components of the current RISC based architecture that need to be migrated remain the same:
1. On line application
2. Batch application
3. Integration Infrastructure
4. BI and reporting
5. ETL processing
7. Operating System
Note on OS migration: Although an operating system migration is often assumed (UNIX to Windows/Linux) in a RISC to x86 migrations, this does not necessarily need to be the case as Solaris and HP-UX (announced) run on x86.
It may also be the case you are already running Linux on your RISC system so there is no need to migrate the OS. However, you will probably be upgrading to a
newer release of Linux.
8. Operating System scripts and tools
9. Application, network, database and operating system management and monitoring products and tools
10. Other infrastructure software such as DR, replication servers, gateways, back up and recovery ....
11. Hardware refresh - Of course, you will need to purchase, install, configure and test the x86 based hardware platform. This is a great opportunity to consider hardware infrastructure that is
better suited to the cloud such as blades (Dell, CISCO UCS, Sun/Oracle) or engineered systems (Exadata and Exalogic).
Ultimately the question is how long will it take, what are all the activities involved, and how much will it cost. The answer to these questions is based more on the OS migration that is being done
then the move from RISC to x86. Will the application language or 4GL product run on Linux/Windows? What is the impact of moving the database from one OS to another ? (this should be minimal as all major relational databases run on x86). The biggest impact (for the application migration) could be Unix specific KSH or CSH scripts. You may also be running management, monitoring, or older job scheduling tools that
only run on UNIX/RISC.
As you can see, nothing is different here from what I have blogged about regarding mainframe, client/server, and application cloud migrations.
Intel has a comprehensive RISC migration white paper here:
RISC Migration

Friday May 04, 2012

Migrating DB2 z/OS to Oracle Database

I have been receiving many requests for information on migrating IBM z/OS DB2 databases to Oracle so I thought this would be a great topic.
Third Party Tool Solutions
1.Ispirer- Ispirer - I have worked with there tool before and it is solid. They offer services as well.

Third Party SI Providers (with their own tools)
1.Prac Trans - Prac Trans - I have worked a lot with this company. They have both internal tools to migrate db2 z/OS and very skilled mainframe DB2 resources.

Oracle Solutions
A. Oracle ART Tuxedo Workbench - Oracle ART Workbench
Note: This costs minimum of $80K for two developer licenses.
Solution is disk to disk based.
B. Oracle Warehouse Builder - Free Oracle database ETL tool. You would use JDBC as listed here:
OWB supports importing of COBOL copybooks where DB2 tables are often defined. NOTE: JDBC connection to mainframe DB2 can be slow.
Solution can be disk to Oracle DB or DB2 to Oracle (stream based).
C. Oracle DRDA Gateway - Connect to DB2 on mainframe from Oracle and use Select statements to migrate (nothing to install on mainframe) Oracle DRDA Gateway
Solutions is stream based/disk less.
D. Oracle Data Integrator - No DB2 Knowledge built for DB2 mainframe but one could be developed.

Tuesday May 01, 2012

What makes a DB2 migration easy ?

The four key elements are:
1. COTS application - This means no application database access or database schema to migrate (assuming no database customizations)
2. No integration interfaces - There are no web service, FTP/file, COTS API or other input, output or input/output interfaces.
3. No ETL / batch processing - The is no batch processing or ETL jobs (Oracle Data Integrator, Informatica, IBM DataStage etc.) that are outside the COTS application.
4. No data to migrate - Really ? Yes, all the data is transient. It is part of a print server, real time data capture or caching system.
This may seem like it does not happen. However, I just encountered a set of applications run by a major corporation that has all four elements!

Monday Apr 30, 2012

Forrester comments on Dell and Perot modernization acquisitions

Interesting read;
Forrester Blog Entry
From blog:
1. "MAKE was a software-product company with a services arm" - I would describe MAKE as a tool assisted services company.
2. "Services firms that ignore MAKE's processes tend to fail / require bailout from MAKE to place the project back on the path to success"
- Agree completely! I have seen so many projects fail without a solid process / approach

Saturday Apr 21, 2012

Data migration testing - Oracle Flashback Database makes life easier

Whether it is unit, QA, system or development testing using Oracle Flashback database can reduce time and make the process easier
Oracle Flashback for testing on OTN

Thursday Apr 05, 2012

Dell - Consolidating migration market place ?

First acquisition was re-hosting and now re-architecture:
Dell acquires Make Technologies

Wednesday Apr 04, 2012

Dell getting into platform migration space

Dell has a large service organization with its acquisition of Perot Systems a few years back. It now has expertise in getting companies off a legacy IBM mainframe systems:
Dell acquires Clerity

Thursday Jan 19, 2012

Oracle cloud migration success starts with design

Article on TechTarget is an excerpt from the Migrating to the Cloud book. This excerpt discussing the approaches that can be taken to cloud migrations.
Migrating to the Cloud book excerpt

Migrating legacy client/server and mainframe technologies to the Oracle cloud.


« July 2016