Article View: bit.listserv.asm370
Article #230Re: AR/XM question
From: Jonathan Scott
Date: Tue, 25 Oct 2005 18:33
Date: Tue, 25 Oct 2005 18:33
26 lines
2639 bytes
2639 bytes
From the example you give, it's not clear whether you've made sure that AR4 is zero (to access primary) and that AR5 was zero (before the LAM) so that the ALET constant was also loaded from primary. You should normally load them with LAM to make sure, preferably before switching to AR mode. If you access your client's address space using a secondary ALET with SASN=OLD, your server needs AX authority to access the client address space. You can avoid this requirement by instead using a home ALET (value 2), which does not require any special authority (but of course means that you cannot support calls from client code which is already running in cross-memory mode, as the parameters are assumed to be in the home address space rather than the calling address space). I'd also like to comment that if something doesn't work in its original key, switching to key 0 is rarely a good idea! In most cases, cross-memory server code should run in supervisor state but key 8, which allows it to access its own private storage and that of a typical caller without any special key processing, but means that it can use authorized operating system services and switch to key 0 temporarily when necessary. Jonathan Scott IBM Hursley, UK
Technical Details
Message-ID:
<200510251835.j9PIZu5D020866@d01av01.pok.ibm.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!logbridge.uoregon.edu!canoe.uoregon.edu!newsfeed.news.ucla.edu!newsfeed.berkeley.edu!ucberkeley!sn-xit-03!sn-xit-10!sn-xit-01!sn-xit-08!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!vnet.ibm.com!jonathan_scottShow Full Headers
Complete Article Headers
X-Google-Thread: fcdcb,892da0ab58f1661
X-Google-Attributes: gidfcdcb,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!logbridge.uoregon.edu!canoe.uoregon.edu!newsfeed.news.ucla.edu!newsfeed.berkeley.edu!ucberkeley!sn-xit-03!sn-xit-10!sn-xit-01!sn-xit-08!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!vnet.ibm.com!jonathan_scott
From: Jonathan Scott <jonathan_scott@vnet.ibm.com>
Newsgroups: bit.listserv.asm370
Subject: Re: AR/XM question
Date: Tue, 25 Oct 2005 12:33:48 -0600
Organization: SAS Inc.
Lines: 26
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <200510251835.j9PIZu5D020866@d01av01.pok.ibm.com>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Trace: foggy.unx.sas.com 1130265764 1888 10.19.150.41 (25 Oct 2005 18:42:44 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Tue, 25 Oct 2005 18:42:44 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
Approved-By: Jonathan Scott <jonathan_scott@VNET.IBM.COM>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 25 Oct 2005 18:42:41.0364 (UTC)
FILETIME=[E152B140:01C5D993]
Originator: daemon@mozart.unx.sas.com