Re: OC1 regs in log oddity
I *think* some z/OS services use the top halves of R14 to R1 as scratch pads. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Thigpen Sent: Wednesday, March 10, 2021 4:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: OC1 regs in log oddity That makes sense. I guess that R15 still contained some 'garbage' left by the OS when it initially loaded and branched to the program. Tony Thigpen Binyamin Dissen wrote on 3/10/21 12:50 AM: > If all top-halfs are zero, it skips them. > > On Wed, 10 Mar 2021 00:28:07 -0500 Tony Thigpen wrote: > > :>I just noticed something I had not noticed before. > :> > :>I have a little test program that I am doing all sorts of things to see > :>how things work. So, of course, I am crashing it a lot. Sometimes even > :>on purpose using DC x'' instructions. > :> > :>What I have noticed is that the log shows the registers differently > :>sometimes. For example: > :> > :>SYSTEM COMPLETION CODE=0C1 REASON CODE=0001 > :> TIME=00.40.10 SEQ=00137 CPU= ASID=0034 > :> PSW AT TIME OF ERROR 078D 8CD8 ILC 2 INTC 01 > :>ACTIVE LOAD MODULE ADDRESS=7000 OFFSET=1CD8 > :>NAME=COPYTPX > :>DATA AT PSW 8CD2 - 4710B03A 4D10 B0308F00 > :>GR 0: _9018 1: _901F > :> 2: _7604 3: _AFFC > :> 4: _9018 5: _901F > :> 6: _0004 7: _FD00 > :> 8: _9010 9: _80008036 > :> A: _AFE0 B: _8CB0 > :> C: _40008010 D: _8E98 > :> E: _92A8 F: 7FFAEA00_8CB0 > :>vs. the following: > :> > :>SYSTEM COMPLETION CODE=0C1 REASON CODE=0001 > :> TIME=00.39.24 SEQ=00136 CPU= ASID=0034 > :> PSW AT TIME OF ERROR 078D 8CE4 ILC 2 INTC 01 > :>ACTIVE LOAD MODULE ADDRESS=7000 OFFSET=1CE4 > :>NAME=COPYTPX > :>DATA AT PSW 8CDE - 8DE00A13 47F0 B0A29680 > :>GR 0: 0950 1: 009C36B0 > :> 2: 7604 3: AFFC > :> 4: 9018 5: 901F > :> 6: 0004 7: FD00 > :> 8: 9010 9: 80008036 > :> A: AFE0 B: 8CB0 > :> C: 40008010 D: 8E98 > :> E: 92A8 F: > :> > :>The only difference is that 64 bit regs are shown if I have not done an > :>OPEN macro while 31 bit registers are shown if I have issued an OPEN macro. > :>Test code snipit: > :> > :>*DC X'' > :> OPEN (SNAPDCB,(OUTPUT)) > :> DC X'' > :> > :>The program in question is assembled AMODE=24,RMODE=24. > :> > :>OK, whats up with this? > > -- > Binyamin Dissen > http://www.dissensoftware.com > > Director, Dissen Software, Bar & Grill - Israel > > > Should you use the mailblocks package and expect a response from me, > you should preauthorize the dissensoftware.com domain. > > I very rarely bother responding to challenge/response systems, > especially those from irresponsible companies. > > -- > 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
Re: OC1 regs in log oddity
That makes sense. I guess that R15 still contained some 'garbage' left by the OS when it initially loaded and branched to the program. Tony Thigpen Binyamin Dissen wrote on 3/10/21 12:50 AM: If all top-halfs are zero, it skips them. On Wed, 10 Mar 2021 00:28:07 -0500 Tony Thigpen wrote: :>I just noticed something I had not noticed before. :> :>I have a little test program that I am doing all sorts of things to see :>how things work. So, of course, I am crashing it a lot. Sometimes even :>on purpose using DC x'' instructions. :> :>What I have noticed is that the log shows the registers differently :>sometimes. For example: :> :>SYSTEM COMPLETION CODE=0C1 REASON CODE=0001 :> TIME=00.40.10 SEQ=00137 CPU= ASID=0034 :> PSW AT TIME OF ERROR 078D 8CD8 ILC 2 INTC 01 :>ACTIVE LOAD MODULE ADDRESS=7000 OFFSET=1CD8 :>NAME=COPYTPX :>DATA AT PSW 8CD2 - 4710B03A 4D10 B0308F00 :>GR 0: _9018 1: _901F :> 2: _7604 3: _AFFC :> 4: _9018 5: _901F :> 6: _0004 7: _FD00 :> 8: _9010 9: _80008036 :> A: _AFE0 B: _8CB0 :> C: _40008010 D: _8E98 :> E: _92A8 F: 7FFAEA00_8CB0 :>vs. the following: :> :>SYSTEM COMPLETION CODE=0C1 REASON CODE=0001 :> TIME=00.39.24 SEQ=00136 CPU= ASID=0034 :> PSW AT TIME OF ERROR 078D 8CE4 ILC 2 INTC 01 :>ACTIVE LOAD MODULE ADDRESS=7000 OFFSET=1CE4 :>NAME=COPYTPX :>DATA AT PSW 8CDE - 8DE00A13 47F0 B0A29680 :>GR 0: 0950 1: 009C36B0 :> 2: 7604 3: AFFC :> 4: 9018 5: 901F :> 6: 0004 7: FD00 :> 8: 9010 9: 80008036 :> A: AFE0 B: 8CB0 :> C: 40008010 D: 8E98 :> E: 92A8 F: :> :>The only difference is that 64 bit regs are shown if I have not done an :>OPEN macro while 31 bit registers are shown if I have issued an OPEN macro. :>Test code snipit: :> :>*DC X'' :> OPEN (SNAPDCB,(OUTPUT)) :> DC X'' :> :>The program in question is assembled AMODE=24,RMODE=24. :> :>OK, whats up with this? -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- 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
Re: OC1 regs in log oddity
If all top-halfs are zero, it skips them. On Wed, 10 Mar 2021 00:28:07 -0500 Tony Thigpen wrote: :>I just noticed something I had not noticed before. :> :>I have a little test program that I am doing all sorts of things to see :>how things work. So, of course, I am crashing it a lot. Sometimes even :>on purpose using DC x'' instructions. :> :>What I have noticed is that the log shows the registers differently :>sometimes. For example: :> :>SYSTEM COMPLETION CODE=0C1 REASON CODE=0001 :> TIME=00.40.10 SEQ=00137 CPU= ASID=0034 :> PSW AT TIME OF ERROR 078D 8CD8 ILC 2 INTC 01 :>ACTIVE LOAD MODULE ADDRESS=7000 OFFSET=1CD8 :>NAME=COPYTPX :>DATA AT PSW 8CD2 - 4710B03A 4D10 B0308F00 :>GR 0: _9018 1: _901F :> 2: _7604 3: _AFFC :> 4: _9018 5: _901F :> 6: _0004 7: _FD00 :> 8: _9010 9: _80008036 :> A: _AFE0 B: _8CB0 :> C: _40008010 D: _8E98 :> E: _92A8 F: 7FFAEA00_8CB0 :>vs. the following: :> :>SYSTEM COMPLETION CODE=0C1 REASON CODE=0001 :> TIME=00.39.24 SEQ=00136 CPU= ASID=0034 :> PSW AT TIME OF ERROR 078D 8CE4 ILC 2 INTC 01 :>ACTIVE LOAD MODULE ADDRESS=7000 OFFSET=1CE4 :>NAME=COPYTPX :>DATA AT PSW 8CDE - 8DE00A13 47F0 B0A29680 :>GR 0: 0950 1: 009C36B0 :> 2: 7604 3: AFFC :> 4: 9018 5: 901F :> 6: 0004 7: FD00 :> 8: 9010 9: 80008036 :> A: AFE0 B: 8CB0 :> C: 40008010 D: 8E98 :> E: 92A8 F: :> :>The only difference is that 64 bit regs are shown if I have not done an :>OPEN macro while 31 bit registers are shown if I have issued an OPEN macro. :>Test code snipit: :> :>*DC X'' :> OPEN (SNAPDCB,(OUTPUT)) :> DC X'' :> :>The program in question is assembled AMODE=24,RMODE=24. :> :>OK, whats up with this? -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
