Isn't creating the COBOL run unit a one time thing for the job? Just make sure there is a COBOL program early in the stack.
Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx
-----Paul Roy <paul.roy@xxxxxxx> wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Paul Roy <paul.roy@xxxxxxx>
Date: 05/31/2017 09:02AM
Subject: Re: Performance - RPG vs Cobol
I you regenerate the full application, this is not an issue but .
There is a possible performance issue if you mix RPG and COBOL.
Calling RPG from a COBOL program has no overhead whilst if you call a
COBOL program from RPG there is a big overhead in creating the COBOL run
unit !
Paul
From: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 31/05/2017 14:11
Subject: Re: Performance - RPG vs Cobol
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I would not think there would be a performance difference.
That being said however, there are some interesting defaults...
For example, an RPG Input Primary file has some interesting record
blocking which I've found to be a performance boost. Sure, you can tailor
your blocking factor in other files but I was talking about defaults here.
Just look at the compiler messages on an Input Primary file about
blocking.
However, since their generator supports both RPG and COBOL what are the
odds they are using Input Primary files?
Defaults are important when the gods forbid you to modify generated code.
Rob Berendt
midrange.com
