Re: Road Map to move a home grown application from RPG to DB2 SQL or to any other data base platform -- MIDRANGE-L

Birgitta , when I say SQL I mean SQL/CLI they are SQL program procedures
written in SQL similar to what we see in SQL Server procedures and PL/SQL
oracle.

I understand there are certain things we can do in RPG like creating
reports while processing data.. ofcourse we have to prepare some reporting
tables during conversion so that they can be used to generate reports using
some reporting tool like Tableau/Cognos/Crystal .. as I am not aware of any
COOL reporting tool running on iSeries. Our focus is to convert core RPG
processing programs into SQL/CLI.. Once that is done then we can move on
to bigger tasks like screens.. it will be a multi year project so time is
not an issue .. just want to make sure we are starting it right..

On Wed, Jan 11, 2017 at 9:52 PM, Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:

Even though I agree with converting DDS to DDL, I'd not agree to translate
RPG into SQL, because there are a lot of things available in RPG that
cannot
be covered with SQL.

I'd first try to move business logic from RPG into the database, i.e.
creating and using complex views and use them composition with embedded
SQL.
Adding check constraints, referential integrities and triggers to the
database tables.
Also I'd create service programs that include all database access
procedures. And finally there will be only a single procedure (per table)
that will solely do the update, another one that will do the insert and a
third one that will cover the delete.
Additional check procedures that are also called before the insert, update
or delete and that will check whether the insert, update or delete can
performed and that will set default values, can be added.

After all of the logic is moved from the RPG-programs into the database,
there will be only a minimum of source code left.
Whether you keep those sources in RPG or decide sometime to convert it into
any other programming language (not SQL because it may not cover what is
left, but may be Java or what ever will be a nice programming language in
future) does not matter.
The main work is done by the database.

Also if you reduce the source code for data access and want to have a
graphical user interface, you may translate your dialog programs into PHP
or
Java Script or whatever. All of these languages can use SQL.
You even can register RPG functions as UDFs to be called from SQL.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
„Train people well enough so they can leave, treat them well enough so they
don't want to.“ (Richard Branson)

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Mohammad Tanveer
Sent: Donnerstag, 12. Januar 2017 00:32
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

yes DDS to SQL is the first step baby steps to make sure we test
application
on each step to make sure nothing is broken...

1. change PF/LFs to SQL tables and indexes.
2. Convert RPG programs to SQL/CLI so that it can be migrated to SQL
Server.
3. Convert RPG reports to Tableu/Cognos/Crystal reports 4. Convert DSPF
screens to some frame work like Angular JS 5. Migrate everything to another
platform/cloud..(if there is a need)

Regards

On Wed, Jan 11, 2017 at 3:05 PM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

My idea is to migrate RPG into SQL/CLI procedures on System i First...

I should make it clear that I don't support the migration of IBM i
applications to other platforms. But if you envision this to be a
gradual process, you might consider a migration from DDS to SQL DDL as
a first step
- before migrating RPG code to SQL stored procedures.

http://www.adsero-optima.com/index.html
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD