|
View previous topic :: View next topic
|
| Author |
Message |
mainframekk
New User
Joined: 11 Jul 2005
Posts: 8
|
|
|
|
as title.
If yes, theorotically, should cobol run faster than easytrieve? |
|
| Back to top |
|
 |
Douglas Wilder
Active User
.jpg)
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
| You may run Easytrieve either interpretive or compiled. It of course runs faster compiled than interpretive. |
|
| Back to top |
|
|
stodolas
Active Member
Joined: 13 Jun 2007
Posts: 632
Location: Wisconsin
|
|
|
|
Douglas,
While I agree with "faster" statement in principal, I haven't experienced that to be true. Do you have runstats to prove the compiled vs interpreted argument? I experienced the difference to be unnoticeable after converting from an interpreted to complied program |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
On a system that is not "pegged" for cpu cycles, i would expect the wall-time/elapsed-time to be about the same. This is because most ezt runs are i/o bound, so the "speed" stays at whatever the i/o can support.
I would also expect that the compiled code uses less cpu time than the interpreted code. |
|
| Back to top |
|
|
mainframekk
New User
Joined: 11 Jul 2005
Posts: 8
|
|
|
|
| Douglas Wilder wrote: |
| You may run Easytrieve either interpretive or compiled. It of course runs faster compiled than interpretive. |
How to distinguish if a Easytrieve program run under interpretive or compiled mode? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
When you compile ezt, the executable will normally have one of "your" load module names.
If you are running ezt from the ezt source, the program executed is usually EZTPA00, EZTPA01, or something similar.
Also compiled modules should run from "your" library, and the easytrieve executables are in that product load library. |
|
| Back to top |
|
|
mainframekk
New User
Joined: 11 Jul 2005
Posts: 8
|
|
|
|
| do you mean "running ezt in compilation mode"="running ezt using EZTPA00"? thank you. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
No, i believe you have that reversed.
Using EZTPA00 is for ezt code that has not been compiled. |
|
| Back to top |
|
|
mainframekk
New User
Joined: 11 Jul 2005
Posts: 8
|
|
|
|
Thank you.
Then what the module name for easytrieve compiler? |
|
| Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
| To compile easytrieve I use PGM=EZTPA00. I use exactly the same PGM=EZTPA00 to run interpretively. I had not really noticed that before. I ran some tests and the wall time and CPU time is not very different for the two. In theory I would expect a bigger difference. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Spoke with a few folks on this system and was told compiled/linked ezt isn't used here.
The manual shows PGM=EZTCOM. If your organization is licensed to use Easytrieve, all of the manuals are available for free from the CA support site. |
|
| Back to top |
|
|
|
|
