This whole share areas thing is annoying at best. And confounding and time consuming at the worst. Has anyone at IBM thought of a way to actually fix this in a more functional way?
Winning friends and influencing with my tactful opinions, *grin* Rob Schramm On Dec 31, 2013 8:21 AM, "Paul Gilmartin" <paulgboul...@aim.com> wrote: > On Mon, 30 Dec 2013 19:03:38 -0800, Roger Steyn wrote: > > > > > John , > > " This talks about the _BPX_SHAREAS environment > variable. This environment variable is not mentioned anywhere in the > documentation of tcsh."� > > Your are right . BPX_SHAREAS cannot be used for tcsh . It is documented in > USS planning guide . > > _BPX_SHAREAS > Specifies whether the spawned child process is to be run in a separate > address space from the login shell's address space or in the same address > space. Use _BPX_SHAREAS is to improve performance in the z/OS� shell. The > spawn callable service uses _BPX_SHAREAS when creating child processes. > > Is there anything distinctive about tcsh? Wouldn't the same apply to bash, > or ksh, or dash, or any shell a customer cared to install? > > I suppose what distingishes tcsh is that z/OS elects to supply it as a base > function. That ought to make tcsh responsible for being > _BPX_SHAREAS-savvy. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
