On Mon, 27 May 2013 14:25:21 +0700, Robin Atwood wrote:
I also
found a presentation that claimed the BEA was saved in low memory at 110.
but a few dumps I looked at did not bear this out (pun intended!).
You should read the POO.
When the PER-3 facility is installed
and a program interruption
In 005001ce5aab$5c511c10$14f35430$@com, on 05/27/2013
at 02:25 PM, Robin Atwood abend...@gmail.com said:
Thanks for the info. The BEA can be easily retrieved from RTWA+6D0. I
also found a presentation that claimed the BEA was saved in low
memory at 110. but a few dumps I looked at did not bear
FWIW,
The BEA can be found in such fields as
SDWABEA
RTM2BEA
LCCABEA2
So to the extent that the SDWA, RTM2WA, and LCCA are formatted in whatever
IPCS report you are using, the BEA value will be presented.
Peter Relson
z/OS Core Technology Design
Abend 0C1
Gerhard Adam wrote:
This entire problem is suspect since the PSW itself isn't valid. There is no
situation of where bits 24-31 can contain an x'E1'
Good catch. Even after reading my Principle of Operations, it is still a good
catch :-)
Of course, the OP discovered later that 'dump
: 23 May 2013 14:29
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mysterious Abend 0C1
Robin Atwood wrote:
OK, this is what happened. The dump analyser is a trusty clist written for
IPCS by me over 20 years ago. It (almost always) works by using the chain:
ASXB - abending TCB - RTWA, from where
It took quite a while but I was glad to see someone finally noticed that
the PSW is not a PSW, and that the OP noticed this too.
My first thought was that it was perhaps displaying just the 8-byte PSW
address (not the whole PSW) and that the program had landed above the bar
in AMODE 64 (in
Here is a puzzle. The program has taken an 0C1 half-way through an
instruction. It cannot have got there via the normal instruction sequence,
so it must have been branched to. However, none of the registers have a
value less than or equal to the PSW. This is compiled C code so no PC/PR
Robin Atwood wrote:
Here is a puzzle. The program has taken an 0C1 half-way through an instruction.
What z/OS and C compiler releases are you using? Did that program worked
correctly in the past? With the same set of input? Did you recompiled it and it
then gave that instruction exception? Can
On 5/22/2013 7:20 AM, Robin Atwood wrote:8
R0R1 R2 R3 R4 R5 R6 R7
7000 00FD6D40 000A
7FF6 0016 92D5 7055MVI85(7),X'D5'
7FFA 001A 91FF 7056
Abend 0C1
On 5/22/2013 7:20 AM, Robin Atwood wrote:8
R0R1 R2 R3 R4 R5 R6
R7
7000 00FD6D40
000A
7FF6 0016 92D5 7055MVI85(7),X'D5'
7FFA 001A 91FF 7056
displacements, so how did we get to that point in the code?
Thanks
-Robin
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Elardus Engelbrecht
Sent: 22 May 2013 19:36
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mysterious Abend 0C1
Robin
R0R1 R2 R3 R4 R5 R6
R7
7000 00FD6D40 000A
7FF6 0016 92D5 7055MVI85(7),X'D5'
7FFA 001A 91FF 7056TM 86(7),X'FF'
On Wed, 22 May 2013 19:20:29 +0800, Robin Atwood wrote:
Here is a puzzle. The program has taken an 0C1 half-way through an
instruction.
If the PSW that you listed is the correct PSW, the code you
have shown is not the correct code. You could not have
received an operation exception for trying
-...@gmx.net
Sent: 22 May 2013 20:02
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mysterious Abend 0C1
R0R1 R2 R3 R4 R5 R6
R7
7000 00FD6D40
000A
7FF6 0016 92D5 7055MVI
On Wed, 22 May 2013 07:24:01 -0500, Tom Marchant m42tom-ibmm...@yahoo.com
wrote:
On Wed, 22 May 2013 19:20:29 +0800, Robin Atwood wrote:
Here is a puzzle. The program has taken an 0C1 half-way through an
instruction.
If the PSW that you listed is the correct PSW, the code you
have shown is
I didn't see mentioned, but if you ever think that the problem is due
to a wild branch of any sort, remember that the BEA Register
contains the address last successfully branched from. It is in the
SYSUDUMP under the PRB of the program which was in execution. So I'd
look at the instruction at that
On Wed, 22 May 2013 06:35:59 -0500, Elardus Engelbrecht wrote:
How could the PSW get to be where it is?
It could be the address is calculated during execution, perhaps on a set of
input?
Or that instruction was overlaid somehow and you ended up in that address.
BALR 15,15 ?
Or
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mysterious Abend 0C1
I didn't see mentioned, but if you ever think that the problem is due to a
wild branch of any sort, remember that the BEA Register contains the
address last successfully branched from. It is in the SYSUDUMP under the
PRB of the program
? It would have been useful in the past!
Cheers
-Robin
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of John McKown
Sent: 22 May 2013 20:38
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mysterious Abend 0C1
I didn't see mentioned
22 de May, 14:29 - +34 671 44 47 12: Hola quien eres
22 de May, 14:30 - +34 671 44 47 12: Tiengo un msn
22 de May, 14:30 - Alvaro Guirao: Ni idea
22 de May, 14:30 - Alvaro Guirao: No te tengo en la agenda
22 de May, 14:31 - Alvaro Guirao: Q pone en el mensaje?
22 de May, 14:31 - +34 671 44 47
Sorry, i sent this message by error, ignore it please.
El 22/05/2013, a las 15:07, Álvaro Guirao López escribió:
22 de May, 14:29 - +34 671 44 47 12: Hola quien eres
22 de May, 14:30 - +34 671 44 47 12: Tiengo un msn
22 de May, 14:30 - Alvaro Guirao: Ni idea
22 de May, 14:30 - Alvaro
On Wed, 22 May 2013 20:57:03 +0800, Robin Atwood wrote:
John -
That's very interesting to know, thanks a lot. Is that a comparatively
recent register? It would have been useful in the past!
z990, IIRC
--
Tom Marchant
-Original Message-
From: IBM Mainframe Discussion List
One thought: Look for the value in the SDWABEA field.
This is the Breaking Event Address
From the POPs:
Breaking-Event-Address Register
When the PER-3 facility is installed, each CPU has a 64-bit register called
the breaking-event-address register. Each time execution of an instruction
other than
: 201-930-8260 | M: 512-627-3803
E: cblaic...@syncsort.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Robin Atwood
Sent: Wednesday, May 22, 2013 6:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Mysterious Abend 0C1
Here is a puzzle
On 5/22/2013 4:20 AM, Robin Atwood wrote:
Here is a puzzle. The program has taken an 0C1 half-way through an
instruction. It cannot have got there via the normal instruction sequence,
so it must have been branched to. However, none of the registers have a
value less than or equal to the PSW.
This entire problem is suspect since the PSW itself isn't valid. There is
no situation of where bits 24-31 can contain an x'E1'
Adam
Using ASXB519 TCB: 007CC950 Abend Code: 0C1000 ILC: 00 Int: 04
PSW: 00 01 80 E1 00 00 80 00 Csect EP:
Looking at it more closely, something is seriously wrong here. The ILC
shows zero. The PSW indicates that DAT is off, Supervisor state, Key 0 and
disabled for I/O, External, and Machine check interrupts.
Toto, I don't think we're in Kansas anymore.
Using ASXB519 TCB: 007CC950 Abend Code:
Gerhard Adam wrote:
This entire problem is suspect since the PSW itself isn't valid. There is no
situation of where bits 24-31 can contain an x'E1'
Good catch. Even after reading my Principle of Operations, it is still a good
catch :-)
Of course, the OP discovered later that 'dump analyser
On 5/22/2013 8:34 AM, Elardus Engelbrecht wrote:
Of course, the OP discovered later that 'dump analyser picked up the wrong PSW
'.
This is why I stopped using all dump analyzers (other than my own brain)
over two decades ago!
I'd much rather find the PSW and registers myself--starting with
On 22 May 2013 12:39, Ed Jaffe edja...@phoenixsoftware.com wrote:
On 5/22/2013 8:34 AM, Elardus Engelbrecht wrote:
Of course, the OP discovered later that 'dump analyser picked up the wrong
PSW '.
This is why I stopped using all dump analyzers (other than my own brain)
over two decades
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Tony Harminc
Sent: Wednesday, May 22, 2013 12:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mysterious Abend 0C1
On 22 May 2013 12:39, Ed Jaffe edja...@phoenixsoftware.com wrote:
On 5/22/2013 8:34 AM
Unfortunately not every shop makes IPCS available to application
programmers. Some of us are stuck with just two choices - commercial abend
analyzer selected by bean counters or read the SYSUDUMP yourself.
Some skills from the days of paper mounds are still important.
Since the OP included
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Gerhard Adam
Sent: Wednesday, May 22, 2013 1:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mysterious Abend 0C1
Unfortunately not every shop makes IPCS available to application
programmers
On 5/22/2013 10:10 AM, Farley, Peter x23353 wrote:
Unfortunately not every shop makes IPCS available to application programmers.
Some of us are stuck with just two choices - commercial abend analyzer selected
by bean counters or read the SYSUDUMP yourself.
What about SYSABEND? ISTR that has
as when one has IPCS
available.
Peter
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ed Jaffe
Sent: Wednesday, May 22, 2013 1:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mysterious Abend 0C1
On 5/22/2013 10:10 AM, Farley, Peter
In 003601ce56eb$dcde9100$969bb300$@com, on 05/22/2013
at 08:57 PM, Robin Atwood abend...@gmail.com said:
That's very interesting to know, thanks a lot. Is that a
comparatively recent register?
The PER-3 facility, including the Breaking-Event-Address Register, was
documented in the fifth
On 5/22/2013 11:44 AM, Shmuel Metz (Seymour J.) wrote:
The PER-3 facility, including the Breaking-Event-Address Register, was
documented in the fifth edition of z/Architecture Principles of
Operation, SA22-7832; I don't recall which processors introduced it.
The BEAR was introduced with the
But then you're trusting IPCS (presumably) to format the trace entries
correctly. Something it has been known to silently get wrong, if there
is a version mismatch between IPCS and dump.
Which you're informed about in bold at the initialization of the dump for the
past 10 years.
Barbara
38 matches
Mail list logo
