It was a while back, but I'm pretty sureI have used _BPX_SHAREAS and the spawn syscall from REXX, to run Java in the same address space.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lionel B Dyck Sent: Monday, November 4, 2019 12:00 PM To: [email protected] Subject: Re: Improving the performance of an ISPF app using OMVS services (bpxwunix) Thanks for the education. Guess I need to find a faster system 😊 Lionel B. Dyck <sdg>< Website: http://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of ITschak Mugzach Sent: Monday, November 4, 2019 5:52 AM To: [email protected] Subject: Re: Improving the performance of an ISPF app using OMVS services (bpxwunix) No. the fork is a unix issue. the first shell task will be started as a separate asid and then, if _BPXSHAREDAS is on, called shell programs will run in the same (new) asid. You can see in the syslog the evidence of the new ASID started. It is usually has the id of the caller plus numeric value. On Mon, Nov 4, 2019 at 1:46 PM Lionel B Dyck <[email protected]> wrote: > But when rexx, under ispf, invokes bpxwunix won't the sharedas help to > prevent the fork? > > > Lionel B. Dyck <sdg>< > Website: http://www.lbdsoftware.com > > "Worry more about your character than your reputation. Character is > what you are, reputation merely what others think you are." - John > Wooden > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of ITschak Mugzach > Sent: Monday, November 4, 2019 5:36 AM > To: [email protected] > Subject: Re: Improving the performance of an ISPF app using OMVS > services > (bpxwunix) > > That's because _BPX_SHAREDAS is related to a main shell program and > its forks. not to the Rexx (or whatever the caller is) and the unix shell. > > > > On Mon, Nov 4, 2019 at 1:29 PM Lionel B Dyck <[email protected]> wrote: > > > That was my fear 😊 > > > > I did find these which I implemented in my .profile and I'm not > > seeing any visual improvements: > > > > export _BPX_SHAREAS=YES > > export _BPX_SPAWN_SCRIPT=YES > > > > > > Lionel B. Dyck <sdg>< > > Website: http://www.lbdsoftware.com > > > > "Worry more about your character than your reputation. Character is > > what you are, reputation merely what others think you are." - John > > Wooden > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > > Behalf Of ITschak Mugzach > > Sent: Monday, November 4, 2019 5:25 AM > > To: [email protected] > > Subject: Re: Improving the performance of an ISPF app using OMVS > > services > > (bpxwunix) > > > > Lionel, > > > > The secret is that zPDT systems are not heavily loaded. As you load > > the system (or start mot guests, if running under z/vm), the system > > starts to slow down. BPXWUNIX starts a new address space, so by > > definition it is more cpu consuming, that affects elapse. > > > > ITschak > > > > On Mon, Nov 4, 2019 at 1:20 PM Lionel B Dyck <[email protected]> wrote: > > > > > Are there any hints/tips to improve the performance of an ISPF > > > application that uses BPXWUNIX? In running on my normal system > > > the performance is very slow compared to a friends system running > > > on a > zPDT. > > > > > > > > > > > > I couldn't find a SHARE presentation (but I may not have used the > > > correct > > > keywords) and the IBM pubs are not speaking to me as nothing jumps out. > > > > > > > > > > > > > > > > > > Lionel B. Dyck <sdg>< > > > Website: <http://www.lbdsoftware.com/> http://www.lbdsoftware.com > > > > > > "Worry more about your character than your reputation. Character > > > is what you are, reputation merely what others think you are." - > > > John Wooden > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > -- > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO > > > IBM-MAIN > > > > > > > > > -- > > ITschak Mugzach > > *|** IronSphere Platform* *|* *Information Security Contiguous > > Monitoring for Legacy **| * > > > > -------------------------------------------------------------------- > > -- 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 > > > > > -- > ITschak Mugzach > *|** IronSphere Platform* *|* *Information Security Contiguous > Monitoring for Legacy **| * > > ---------------------------------------------------------------------- > 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 > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * ---------------------------------------------------------------------- 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 -- 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
