Peter Relson wrote
>
>Perhaps with the exception of the (somewhat atypical but allowed) PC-SS
>that is defined not to set new-SASN to old-PASN (ETDEF with SASN=NEW).
>Of course if using that approach you cannot use ALET=1 to access
>caller-provided data that was in the caller's primary address sp
>> Does this mean a Space Switching PC cannot be used to remove the
>> users access ?
>
> That is correct.
Perhaps with the exception of the (somewhat atypical but allowed) PC-SS
that is defined not to set new-SASN to old-PASN (ETDEF with SASN=NEW).
Of course if using that approach you cannot u
IBM Mainframe Discussion List wrote on
01/21/2013 08:53:35 AM:
> From: "esst...@juno.com"
> To: IBM-MAIN@listserv.ua.edu,
> Date: 01/21/2013 02:54 PM
> Subject: Re: 0D7 with ATSET
> Sent by: IBM Mainframe Discussion List
>
> Jim Mulder wrote
>
> >
ed to remove the users access ?
Paul D'Angelo
-- Original Message --
From: Jim Mulder
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: 0D7 with ATSET
Date: Sun, 20 Jan 2013 22:19:14 -0500
IBM Mainframe Discussion List wrote on
01/20/2013 05:08:06 PM:
> From: "esst...@juno.
IBM Mainframe Discussion List wrote on
01/20/2013 05:08:06 PM:
> From: "esst...@juno.com"
> To: IBM-MAIN@listserv.ua.edu,
> Date: 01/20/2013 09:53 PM
> Subject: 0D7 with ATSET
> Sent by: IBM Mainframe Discussion List
>
> Im trying to understand why a 0D7 Abend
Im trying to understand why a 0D7 Abend occurs With ATSET.
Im on a zos 1.7 System, developing some sample cross memory routines.
I am provideing 3 sample Routines (Connect, Disconnect, and a Stacking Space
Switching Service Routine)
The Server Address Space
The Server Address Space sets up
