Assuming the code to be equally efficient, you won't be able to see a
difference between COBOL and RPG. In the end they produce about the same
executable.
That said (I am a COBOL fan) if you have the choice I'd go with RPG. The
development of the language is significantly better than COBOL. Mainly IBM
owns RPG and can do with it what it wants. COBOL on the other hand has ANSI
standards that it must adhere to, even if IBM does put extensions into the
language for compatibility to their systems, IBM I, Mainframe, and AIX.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vinay
Gavankar
Sent: Tuesday, May 30, 2017 6:02 PM
To: Midrange Systems Technical Discussion
Subject: Performance - RPG vs Cobol
Hi,
I was wondering whether there is a performance difference between RPG and
Cobol code trying to execute the same functionality which is I/O heavy
(rather than calculations).
I realize that a lot might depend on how the actual code is written, but is
there a general guideline?
My client uses Synon 2E (which allows you to generate OPM/ILE RPG/Cobol
source), and there are some programs which are currently OPM Cobol. We are
planning on regenerating them as ILE and we have a choice of doing either
RPG or Cobol. Is there any particular reason that we should choose one over
the other?
The plan is to change all the programs in the job stream to ILE just to keep
them in the same Activation Group.
These are common modules which are being called from a various RPG/Cobol
programs.
The programs accept a bunch of parameters. Are there any pitfalls if we
convert to ILE RPG in accepting the parameters?
--
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
As an Amazon Associate we earn from qualifying purchases.