Show the code. ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Joseph Reichman <reichman...@gmail.com> Sent: Tuesday, September 19, 2023 7:58 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Why it's important to take Seymour's advice
I am looking at the TCB/rb chain in the SVC dump the IRB epa has a 1 as the last digit I was in amode 31 when I issued schedirb The irb address last digit was a 0 before it pc to schedirb At this point I’m thinking of using the crib macro to build the irb as it gives me more control ie I can look at the irb before it goes to schedirb Thanks > On Sep 19, 2023, at 4:20 PM, Seymour J Metz <sme...@gmu.edu> wrote: > > It's best to use whichever is fitted to the task at hand. There is no one > size fits all. > > ________________________________________ > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of > Joseph Reichman <reichman...@gmail.com> > Sent: Tuesday, September 19, 2023 12:53 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Why it's important to take Seymour's advice > > Hi just did a a SUMM TCBERROR and this is what I got > > Now I was doing something in AMODE 64 prior to the SCHEDIRD But I know I went > back to AMODE 31 > > As an side is it better to USE CRIB to schedule the IRB (in which case it > returns to me the IRB and I can see what I am scheduling or ) SCHEDIRB > > Thank you > > IRB: 008FB710 > KEYSTA... 00 WLIC..... 00040004 EPA...... 9FF01E81 > OPSW..... 078D0000 9FF01EA0 LINK..... 008FEA90 > > PRB: 008FEA90 > WLIC..... 00020001 OPSW..... 071C1000 852CB728 > LINK..... 018E76D0 > EP....... IKJEFT01 ENTPT.... 852C5000 > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Lennie Dymoke-Bradshaw > Sent: Tuesday, September 19, 2023 11:25 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Why it's important to take Seymour's advice > > My experience is that in times past this was definitely true. But nowadays it > no longer is. > I am unsure what changed but I think there was a change somewhere, possibly > in the cross-memory instructions. > Lennie > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU > <mailto:IBM-MAIN@LISTSERV.UA.EDU> > On Behalf Of dailom...@aol.com > <mailto:dailom...@aol.com> > Sent: 19 September 2023 16:16 > To: IBM-MAIN@LISTSERV.UA.EDU <mailto:IBM-MAIN@LISTSERV.UA.EDU> > Subject: Re: Why it's important to take Seymour's advice > > I think the other address space needs to be nonswappable. > > >> On Tuesday, September 19, 2023 at 09:40:36 AM EDT, Adam Johanson >> <0000031ca9d720a7-dmarc-requ...@listserv.ua.edu >> <mailto:0000031ca9d720a7-dmarc-requ...@listserv.ua.edu> > wrote: >> >> Tom Brennan wrote: >> >> I've never written code that runs as an SRB, but over the years I've >> read about them and seen them in action, such as Omegamon poking code >> into other address spaces to grab data or do things like zap memory. > > For what it's worth, you don't need to go through all the rigamarole of an > SRB to go poking around in another address space. > > Given the proper authorization, you can: > > - Issue an AXSET, specifying a value of 1 > - Issue an SSAR instruction identifying the target address space as the > secondary address space > - Use MVCP / MVCS instructions to copy data between your primary address > space and the secondary address space > > > There is also the technique of using the special ALET value of x'00000001' > and using AR mode to reference data from another address space. > > =============================== > Adam Johanson > Broadcom Mainframe Software Division > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu <mailto: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 <mailto: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 <mailto: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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
