Michael Knigge wrote:
Thank you all for your hints... When the bug is found I'll tell you...
If anybody is interested - it is solved!
The bug wasn't found by using IPCS, ABEND-AID, DumpMaster or whatever,
just by using the all time favourite Debugger Eyes'n'Brain ;-)
My application is
Hi Michael, in these days we should code RENT code only.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at
Michael,
I know I'm late on this :-)
PSW 078D1400 8002
GPR 0-3 4298A340 40894608 108602CA
GPR 4-7 4298A3B0 40876C10 C086EA6C 0661F420
GPR 8-B 40875200 4298A500 4086E872
GPR C-F 000C 4298A448
What instruction does R6 point to?
The 'call stack' saying
find something that will trigger an early failure, run a GTF trace with IF
recording. I'd advise using SYSMDUMP rather than SYSUDUMP, so that you can
use IPCS. Of course, if you have SLIP take the dump then you'll have
Hmmm... Never did this before I'll have look this week.
something to
The 'call stack' saying UNKNOWN called UNKNOWN called UNKNOWN called (you get
the picture) basically means that *something* called a BPX service that is
either in LPA or located somewhere in the OMVS address space.
H I'm playing a lot with this POSIX-Threads stuff...
How familiar
In [EMAIL PROTECTED], on 08/13/2008
at 04:40 PM, Michael Knigge [EMAIL PROTECTED] said:
The application sometimes crashes after a few minutes, sometimes after
some days with the S0C1.
Did you look at the last branch address? If that doesn't work and you can
find something that will trigger
Steve,
This particular kind of thing is sometimes seen where a program is
NON-LE compliant and gets called by LE compliant code. R12 is not what
LE want's it to be (and x'000c' is NOT what LE wants) and so it
augers in and makes a crater.
I also currently assume that I have to look in
All,
sind a few days now I try to track down a S0C1 in one of my
applications. The application is a multi-threaded application (TCP/IP
Server) written in C using a bunch of self-written DLL's.
The application sometimes crashes after a few minutes, sometimes after
some days with the S0C1.
written in C using a bunch of self-written DLL's.
When I have an application with multiple programs, I add a trace
capability. Perhaps it is as easy as saving the current program name in a
buffer. Or even issuing WTO's.
Pedro Vera
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Michael Knigge
Sent: Wednesday, August 13, 2008 9:41 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Debugging Tips
All,
sind a few days now I try to track down a S0C1 in one of my
Could anyone please give me some advise how to find this bug? Any good
manual to read?
Thank you very much,
Michael
I would start start by looking up the condition description in the 'LE Run-Time
Messages' manual.
CEE3201S The system detected an operation exception (System Completion
a HANDLE
CONDITION and trap some diagnostic information.
HTH and good luck.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Michael Knigge
Sent: Wednesday, August 13, 2008 9:41 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Debugging Tips
All,
sind
David,
I have some kind of limited skills, but I'm not *THAT* stupid ;)
I would start start by looking up the condition description in the 'LE Run-Time
Messages' manual.
I have some kind of limited skills, but I'm not *THAT* stupid ;) Of
course I've looked up the condition
Being multi threaded, perhaps one or more of your modules is not really
re entrant /reusable but still bound as such.
Well, they are... But I'm using some system stuff Catalog Search
Interface for example, SVC99, and so on. I'll go ahead and read the
manual if there is some kind of
Do you have a standard SYSUDUMP available, and are you on z/OS 1.8 or
above, and on a z9? If so, then find the RTM2WA area in the SYSUDUMP.
Now find the name BEA in the dump. That is the address of the last
successful BRANCH type instruction. It should point you to where you
came from. Find that
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Michael Knigge
Sent: Wednesday, August 13, 2008 9:41 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Debugging Tips
snip
+CEE0374C CONDITION=CEE3201S TOKEN=00030C81 59C3C5C5 954
WHILE
16 matches
Mail list logo
