|
View previous topic :: View next topic
|
| Author |
Message |
Josh Keller
New User
Joined: 08 Oct 2007
Posts: 36
Location: Columbia, SC
|
|
|
|
When I'm calling an external routine (cobol or otherwise) in a REXX, I usually program an ISPF SELECT PGM statement. But I'm also aware I can just issue a call directly.
Question: Which is preferred / better / has less overhead?
| Code: |
"ISPEXEC SELECT PGM(MYPROG)"
"CALL 'MY.LOADLIB(MYPROG)'"
"CALL *(MYPROG)" |
My assumption is that the ISPF SELECT has more overhead, but I'm not 100%. I'd figure one of you wise "older" guys would have some proven insight. |
|
| Back to top |
|
 |
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| Overhead or not, note that using an ISPF service of course implies that ISPF is active. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Code: |
"CALL 'MY.LOADLIB(MYPROG)'"
"CALL *(MYPROG)" |
Between those two, my preference is to have a setup exec that allocates the right application libraries and then later in the application logic use
CALL *(myprog).
It is a maintenance concern rather than performance.
1. if the setup is actually in linklib, then the rexx program can run without changes.
2. if the application is distributed to other systems, then the rexx program can run without changes. Otherwise, you might have RACF access problems.
3. You want the customization to be done in a short setup exec, rather than have the installer search and make changes throughout your rexx programs. |
|
| Back to top |
|
|
|
|
