RE: Road Map to move a home grown application from RPG to DB2 SQL or to any other data base platform

[Justin Taylor <JUSTIN@xxxxxxxxxxxxx>]

That's truly fascinating (honestly), but WHY?  If you had a compelling business case to abandon RPG, shouldn't you move to a mainstream, preferably cross-platform, language?



-----Original Message-----
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx] 
Sent: Thursday, January 12, 2017 9:00 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Road Map to move a home grown application from RPG to DB2 SQL or to any other data base platform

Not quite...

SQL actually has (at least) 3 parts
SQL DDL (Data Definition Language)   - for defining tables, views, ....
SQL DML (Data Manipulation Language) - for SELECT, INSERT , and UPDATE of data SQL PSM (Persistent Stored Modules)  - stored procedures, user defined functions, ...

ODBC is basically just SQL DML...

RPG batch programs could conceivably be replaced by SQL PSM.

UI is another story.  5250 programs usually have lots of business logic; which could conceivably be moved to SQL PSM.

But SQL has absolutely nothing for UI.  You'd need another language to provide the UI.

Charles


On Thu, Jan 12, 2017 at 7:32 AM, Mark Murphy/STAR BASE Consulting Inc. < mmurphy@xxxxxxxxxxxxxxx> wrote:

> You do understand that SQL/CLI is basically ODBC. You can no more 
> convert entire RPG programs to SQL/CLI than you could convert a VB 
> program to entirely ODBC. It is just a data access method. The RPG 
> does a lot more than access data. And you don't need CLI to use stored procedures from RPG.
>
> Mark Murphy