This was a follow up from a suggestion of not knowing what type of storage VSMLOC was processing. I was issuing VSMLOC from an SRB And coding of PVT for a LSQA address would generate a ABEND which I would subsequently Re-try with the correct LSQA PARM in the VSMLOC
I wasn't sure how to get the address space boundaries from the LDA Maybe this was not the correct approach Sent from my iPhone On Jun 15, 2015, at 8:12 AM, Peter Relson <rel...@us.ibm.com> wrote: >> doesn't have an input param for paramters to FRR routine > Because it doesn't need one. > >> I'll just prime R13 from the SDWA with the value that the SRB had for 13 > > This sort of post scares the heck out of experienced z/OS people. > Are you 100% sure that the FRR got control due to an error while your > module (with your R13) was in control? > Are you 100% sure that the FRR got control with valid time-of-error > registers (there are some machine checks for which that information is not > available)? > > If you know that R13 contains some value, then your code put it there. > When? While the SRB routine was running. If your code sets R13, then it > can also set a word in the FRR parameter area, the address of which is > provided to the SRB routine in R2 on entry when that SRB routine requested > the establishment of an FRR. > > For good form, the FRR should always look to see if the information it > expected to be there was indeed there (as opposed to blowing up right > after the FRR was set but before you were able to store the information). > > 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
