Charles 

I think you are spot on 

Just wondering what Peter Relson might
Say If he responds 

SRB and PC are sometimes not particle

AR mode has its risk best to have a recovery 
Routine to address the rare case and maybe issue a SRB to swap back in I’m not 
at that point yet  

Thanks 



> On Feb 23, 2020, at 11:34 AM, Charles Mills <charl...@mcn.org> wrote:
> 
> There is at least a "technical" risk that the status of the address space
> could change to swappable between your TM and whatever action you do based
> on the determination of non-swappability, but for personal use software I
> suppose you might find that risk acceptable.
> 
> Does non-swappable guarantee "swapped in"? That's a serious question. I
> don't know the answer. Can an already swapped-out address space be marked
> non-swappable? Again, probably a manageable risk for personal use software.
> 
> Charles
> 
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Joseph Reichman
> Sent: Sunday, February 23, 2020 7:43 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Cell Pool Services CSRC4EXP
> 
> Then me just say what I do in the SRB
> 
> The following 
> 
>            XR     R1,R1                     Clear R1 as we cann't wait in
> SRB mode
>           SYSEVENT TRANSWAP,ENTRY=BRANCH,ASID=(R4) 
> 
> 
>           Before I issue a get (actually access the cell)  in a other
> address space double check we are okay
> 
>          L     R1,ASCBOUCB-ASCB(R1)                                  
>         USING OUCB,R1                                               
>         TM    OUCBSFL,OUCBNSW        is address space swapped in
> 
>         BZ    NOTSWAP                no;                            
> 
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
> Peter Relson
> Sent: Sunday, February 23, 2020 9:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Cell Pool Services CSRC4EXP
> 
> <snip>
> Should just say data space
> </snip>
> 
> Your logic confounds me. It can certainly be an address space. Whether it is
> an address space or data space, you have to do things right.
> 
> <snip>
> page 217 ( chapter 13) of the assembler services  guide </snip> Page and
> chapter references don't work too well if someone is looking at knowledge
> center. Let alone a reference without indicating the release.
> But I assume that you are referring to Figure 1 within Callable cell pool
> services -> Storage considerations.
> 
> Peter Relson
> z/OS Core Technology Design
> 
> 
> ----------------------------------------------------------------------
> 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
> 
> ----------------------------------------------------------------------
> 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

Reply via email to