Article View: bit.listserv.asm370
Article #231Re: AR/XM question
From: Ing Usar
Date: Tue, 25 Oct 2005 19:13
Date: Tue, 25 Oct 2005 19:13
63 lines
3440 bytes
3440 bytes
Thanks Jonathan for the reply. Please see below
On Tue, 25 Oct 2005 12:33:48 -0600, Jonathan Scott
<jonathan_scott@vnet.ibm.com> wrote:
>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.
Ing>> The symptom string is as follows:
AR/GR 0: 80C36E58/00000000_00000040 1: 00000000/00000000_87C9805C
2: 00000000/00000000_089006C9 3: 00000000/00000000_008E4AD4
4: 00000000/00000000_089006E4 5: 00000001/00000000_08900F8C
6: 00000000/00000000_88900C08 7: 00000000/00000000_FD000000
8: 00000000/00000000_088E3D48 9: 00000000/00000000_008EC9A0
A: 00000000/00000000_00007F18 B: 00000000/00000000_87C98002
C: 00000000/00000000_88900BF8 D: 00000000/00000000_00006F60
E: 00000000/00000000_87C98064 F: 00000000/00003100_00000008
>
>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.
Ing>> Auth has been given to all ASNs using AXSET with AX=1
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!
>
Ing>> Yes, I agree. Its just that I was trying everything possible to see
it work
>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:
<200510251913.j9PHuVYI032576@malibu.cc.uga.edu>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news.glorb.com!news-in.ntli.net!newsrout1-win.ntli.net!ntli.net!sn-xit-03!sn-xit-08!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!YAHOO.COM!inguser2005Show 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!news3.google.com!news.glorb.com!news-in.ntli.net!newsrout1-win.ntli.net!ntli.net!sn-xit-03!sn-xit-08!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!YAHOO.COM!inguser2005
From: Ing Usar <inguser2005@YAHOO.COM>
Newsgroups: bit.listserv.asm370
Subject: Re: AR/XM question
Date: Tue, 25 Oct 2005 15:13:56 -0400
Organization: SAS Inc.
Lines: 63
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <200510251913.j9PHuVYI032576@malibu.cc.uga.edu>
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 1130267946 3347 10.19.150.41 (25 Oct 2005 19:19:06 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Tue, 25 Oct 2005 19:19:06 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 25 Oct 2005 19:19:02.0230 (UTC)
FILETIME=[F5386F60:01C5D998]
Originator: daemon@mozart.unx.sas.com