This kinda gives you a clue:
"syscalls('ON') ensures that the SYSCALL host command environment is
available in your REXX environment. If the call detects that SYSCALL is not
available in your environment, it dynamically adds it."
"Performance characteristics for dynamically added host commands are not as
good as for host commands that are included in the initial environment:
Every time a command is directed to the SYSCALL host command environment,
the TSO/E REXX support loads the module for the SYSCALL host command."
Page 13
https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3SA232283/$file/bpxb600_v2r3.pdf
So every time you turn off syscalls, and subsequently turn it back on, you
are dynamically adding host support... this is probably the cause of your
performance issues.
Joe
On Mon, Oct 8, 2018 at 3:12 AM Steve Austin <[email protected]> wrote:
> I have some questions regarding the above.
>
> I'm specifying an environment variable of "_BPX_SHAREAS=MUST". Before each
> spawn of the Java program I have a "syscalls('on') and after a
> "syscalls("off"). I'm noticing a significant delay at the "syscalls('off');
> it can be as much as 2 minutes. If I remove the "syscalls('off')" I don't
> get the delay.
>
>
> 1) syscalls('off') is removing the unix environment, but why the
> delay?
>
> 2) By removing the "syscalls('off')" I'm retaining the unix
> environment, but is the Java JVM also retained for reuse? I'm guessing not,
> but it would be nice if it were.
>
> 3) The documentation I've found so far is pretty general. Is there
> documentation somewhere that describes the mechanics in detail?
>
> Thanks
>
> Steve
>
> --
> This e-mail message has been scanned and cleared by Google Message
> Security
> and the UNICOM Global security systems. This message is for the named
> person's use only. If you receive this message in error, please delete it
> and notify the sender.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
