Re: XMEM and Swap ability
Rob I understand now however the second address space is a started task So I don't have axlist,tklist,lxlist available I guess thinking about it the design was a good Idea as we shouldn't be "hacking" into system Address spaces Sent from my iPhone > On May 17, 2016, at 8:22 AM, Rob Scott <rsc...@rocketsoftware.com> wrote: > > If you are in control of both address spaces (ie the second ASID is not > "foreign"), there are all sorts of non-common memory sharing options > available to you, including (but not limited to) : > > (1) ASID1 starting ASID2 using ASCRE - you can get an official cross-memory > bind and then use ALETs to access data in ASID2 from ASID1 > (2) Use shared memory objects > (3) Use PC-ss owned by either/both ASIDs to add items to queues in the other > ASID > (4) SCOPE=ALL dataspaces > (5) IARVSERV > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of michelbutz > Sent: Tuesday, May 17, 2016 12:59 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: XMEM and Swap ability > > So the face that a SRB is running in space #2 > > Would automatically mKe it swapped in ? > > If I had to go thru all that trouble of writing A routine I would rather XMEM > post space #2 to do A SYSEVENT TRANSWAP > > Sent from my iPhone > >>> On May 15, 2016, at 3:59 PM, Ed Jaffe <edja...@phoenixsoftware.com> wrote: >>> >>> On 5/15/2016 11:12 AM, michealbutz wrote: >>> Hi, >>> >>> Transferring data between 2 address spaces weather its MVCP/MVCS or >>> AR mode there is always the possibility of a S0C4. >>> >>> What the best way of making sure the target Address Space is Swapped in. >>> Doing XMEM post to the target address space to do a SYSEVENT ? >> >> Space #1 should schedule an SRB to Space #2. That SRB can PC back to a >> routine in the private area of Space #1. That routine can use AR mode to >> copy anything it wants in either direction without fear of abend caused by >> swap out of either space. >> >> -- >> Edward E Jaffe >> Phoenix Software International, Inc >> 831 Parkview Drive North >> El Segundo, CA 90245 >> http://www.phoenixsoftware.com/ >> >> -- >> 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 > > Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ > +1 877.328.2932 ■ +1 781.577.4321 > Unsubscribe From Commercial Email – unsubscr...@rocketsoftware.com > Manage Your Subscription Preferences - > http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html > Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy > > > This communication and any attachments may contain confidential information > of Rocket Software, Inc. All unauthorized use, disclosure or distribution is > prohibited. If you are not the intended recipient, please notify Rocket > Software immediately and destroy all copies of this communication. Thank you. > > -- > 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
Re: XMEM and Swap ability
If you are in control of both address spaces (ie the second ASID is not "foreign"), there are all sorts of non-common memory sharing options available to you, including (but not limited to) : (1) ASID1 starting ASID2 using ASCRE - you can get an official cross-memory bind and then use ALETs to access data in ASID2 from ASID1 (2) Use shared memory objects (3) Use PC-ss owned by either/both ASIDs to add items to queues in the other ASID (4) SCOPE=ALL dataspaces (5) IARVSERV -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of michelbutz Sent: Tuesday, May 17, 2016 12:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: XMEM and Swap ability So the face that a SRB is running in space #2 Would automatically mKe it swapped in ? If I had to go thru all that trouble of writing A routine I would rather XMEM post space #2 to do A SYSEVENT TRANSWAP Sent from my iPhone > On May 15, 2016, at 3:59 PM, Ed Jaffe <edja...@phoenixsoftware.com> wrote: > >> On 5/15/2016 11:12 AM, michealbutz wrote: >> Hi, >> >> Transferring data between 2 address spaces weather its MVCP/MVCS or >> AR mode there is always the possibility of a S0C4. >> >> What the best way of making sure the target Address Space is Swapped in. >> Doing XMEM post to the target address space to do a SYSEVENT ? > > Space #1 should schedule an SRB to Space #2. That SRB can PC back to a > routine in the private area of Space #1. That routine can use AR mode to copy > anything it wants in either direction without fear of abend caused by swap > out of either space. > > -- > Edward E Jaffe > Phoenix Software International, Inc > 831 Parkview Drive North > El Segundo, CA 90245 > http://www.phoenixsoftware.com/ > > -- > 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 Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ +1 877.328.2932 ■ +1 781.577.4321 Unsubscribe From Commercial Email – unsubscr...@rocketsoftware.com Manage Your Subscription Preferences - http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMEM and Swap ability
So the face that a SRB is running in space #2 Would automatically mKe it swapped in ? If I had to go thru all that trouble of writing A routine I would rather XMEM post space #2 to do A SYSEVENT TRANSWAP Sent from my iPhone > On May 15, 2016, at 3:59 PM, Ed Jaffewrote: > >> On 5/15/2016 11:12 AM, michealbutz wrote: >> Hi, >> >> Transferring data between 2 address spaces weather its MVCP/MVCS or AR mode >> there is always the possibility of a S0C4. >> >> What the best way of making sure the target Address Space is Swapped in. >> Doing XMEM post to the target address space to do a SYSEVENT ? > > Space #1 should schedule an SRB to Space #2. That SRB can PC back to a > routine in the private area of Space #1. That routine can use AR mode to copy > anything it wants in either direction without fear of abend caused by swap > out of either space. > > -- > Edward E Jaffe > Phoenix Software International, Inc > 831 Parkview Drive North > El Segundo, CA 90245 > http://www.phoenixsoftware.com/ > > -- > 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
Re: XMEM and Swap ability
On Sun, 15 May 2016 15:55:37 -0400 michelbutzwrote: :>Forget about my design how about :>A general XMEM question what the point if :>You are going to get S0C4 Why would I ignore a bad design? If you are asking for advice, be humble enough to accept that others already went down the path and are aware of the dangers. Explain why you need access to the other address space. What is your business case? :>> On May 15, 2016, at 2:30 PM, Binyamin Dissen wrote: :>> On Sun, 15 May 2016 14:12:39 -0400 michealbutz :>> wrote: :>> :>Transferring data between 2 address spaces weather its MVCP/MVCS or AR mode :>> :>there is always the possibility of a S0C4. :>> :>What the best way of making sure the target Address Space is Swapped in. :>> :>Doing XMEM post to the target address space to do a SYSEVENT ? :>> Terrible design. You should rethink it. -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMEM and Swap ability
On 5/15/2016 11:12 AM, michealbutz wrote: Hi, Transferring data between 2 address spaces weather its MVCP/MVCS or AR mode there is always the possibility of a S0C4. What the best way of making sure the target Address Space is Swapped in. Doing XMEM post to the target address space to do a SYSEVENT ? Space #1 should schedule an SRB to Space #2. That SRB can PC back to a routine in the private area of Space #1. That routine can use AR mode to copy anything it wants in either direction without fear of abend caused by swap out of either space. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMEM and Swap ability
Forget about my design how about A general XMEM question what the point if You are going to get S0C4 Sent from my iPhone > On May 15, 2016, at 2:30 PM, Binyamin Dissen> wrote: > > On Sun, 15 May 2016 14:12:39 -0400 michealbutz > wrote: > > :>Transferring data between 2 address spaces weather its MVCP/MVCS or AR mode > :>there is always the possibility of a S0C4. > > :>What the best way of making sure the target Address Space is Swapped in. > :>Doing XMEM post to the target address space to do a SYSEVENT ? > > Terrible design. You should rethink it. > > -- > Binyamin Dissen > http://www.dissensoftware.com > > Director, Dissen Software, Bar & Grill - Israel > > > Should you use the mailblocks package and expect a response from me, > you should preauthorize the dissensoftware.com domain. > > I very rarely bother responding to challenge/response systems, > especially those from irresponsible companies. > > -- > 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
Re: XMEM and Swap ability
On Sun, 15 May 2016 14:12:39 -0400 michealbutzwrote: :>Transferring data between 2 address spaces weather its MVCP/MVCS or AR mode :>there is always the possibility of a S0C4. :>What the best way of making sure the target Address Space is Swapped in. :>Doing XMEM post to the target address space to do a SYSEVENT ? Terrible design. You should rethink it. -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
XMEM and Swap ability
Hi, Transferring data between 2 address spaces weather its MVCP/MVCS or AR mode there is always the possibility of a S0C4. What the best way of making sure the target Address Space is Swapped in. Doing XMEM post to the target address space to do a SYSEVENT ? Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN