Haven't used it myself, but based on the macro expansion the GLUE would only
need to do is to perhaps place R0-R1 in the MSTA and then set R1 from AR0 and
BASR 14,15.

The predefined ARR of IEAARR would receive control upon abend and user the
MSTA area to set the parameter register and branch to the user specified ARR.

The advantage of ARR over ESTAE is that the ARR is automatically available.
The downside is the PC overhead.


On Fri, 21 Apr 2023 21:42:52 GMT "esst...@juno.com" <esst...@juno.com> wrote:

:>Hello
:>.
:>.
:>Can anyone add some additional information regarding IEAARR.
:>I am trying to clean up an existing Associated Recovery Routine,
:>by first using IEAARR to drive a Target Routine that is designed to
:>Abend and drive the Associated Recovery Routine.
:>.
:>This works well .. I have No issues with IEAARR, and no issues with the ARR.
:>.
:>I have provided my IEAARR and its expansion.
:>.
:>IEAARR DYNSTORAGE=AVAIL,     
:>      ARRPTR=ARRRTN@,        
:>      ARRPARAMPTR=ARRPARMS@, 
:>      PARAMPTR=TARGPARMS@,   
:>      TARGETPTR=TARGETRTN@,  
:>      TARGETSTATE=PROB       
:>.
:>400+M00M0011 DS    0H                             IEAARR-0          
:>401+              PUSH  PRINT                                       
:>402+                   PRINT ON                                     
:>403+         L     1,ARRRTN@               Pass ARR address         
:>404+         L     0,ARRPARMS@             Pass ARRPARAM address    
:>405+         L     14,TARGPARMS@           Get parameter address    
:>406+         SAR   0,14                    Pass parameter address   
:>407+         L     15,TARGETRTN@           Pass target address      
:>408+         L     14,16(0,0)              GET CVT ADDRESS          
:>409+         L     14,772(14,0)            GET SFT ADDRESS          
:>410+         L     14,500(14,0)            GET LX/EX FOR SERVICE RTN
:>411+         PC    0(14)                                            
:>412+         POP   PRINT                                            
:>413+*                                            IEAARR-0 
:>.
:>.
:>My understanding is the Expansion of IEAARR issues a Program Call (PC) to the
:>IEAARR service. Register 15 contains the address of the Target Routine.
:>.
:>Does the PC routine (IEAARR) simply branch to the Target Routine (R15) making 
it 
:>an extension of the IEAARR PC Service Routine? 
:>.
:>Is the Target Routine Attached as a separate Task ?
:>.
:>Can anyone add some details as to how IBM architected this..
:>.
:>.
:> Paul 
:>.
:>.
:>.           
:>----------------------------------------------------------------------
:>For IBM-MAIN subscribe / signoff / archive access instructions,
:>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Binyamin Dissen <bdis...@dissensoftware.com>
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

----------------------------------------------------------------------
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