This smells a bit like a wild branch. The '0Cx' family of exceptions
typically center around addressing issues. Perhaps a vector/pointer
address has been overlain, there was an undetected/ignored failure in a
getmain, open, or service call that left the regs unpredictable, etc.

Being multi threaded, perhaps one or more of your modules is not really
re entrant /reusable but still bound as such.     

LE has a number of debugging tools. I think you should find an exception
trace: one that only traces the last x number of events. 

I know very little about C, but you should be able to do 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 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. DumpMaster tells me that the ABEND occurs in 
program BPXINLPA, and the PSW is 078D1400 80000002.

But.... no call stack (well, it tells me "UNKNOWN called UNKNOWN called 
UNKNOWN) and that the failing instruction at 00000000 is at offset 
00000000 in program PSA....


The job itself ends with a S422. Some information from the Log:

+CEE0374C CONDITION=CEE3201S TOKEN=00030C81 59C3C5C5 00000000  954
           WHILE RUNNING PROGRAM UNKNOWN
           AT THE TIME OF INTERRUPT
           PSW     078D1400 80000002
           GPR 0-3 00000000 4298A340 40894608 108602CA
           GPR 4-7 4298A3B0 40876C10 C086EA6C 0661F420
           GPR 8-B 40875200 4298A500 00000000 4086E872
           GPR C-F 0000000C 4298A448 00000000 00000000
           FLT 0-2 4848A181A1EE3A55  0000000000000000
           FLT 4-6 0000000000000000  0000000000000000
BPXP011I THREAD 40F74C0000000422, IN PROCESS 211, WAS  955
TERMINATED DUE TO A PTHREAD QUIESCE OF TYPE 2.
BPXP011I THREAD 40FA00E0000002AF, IN PROCESS 211, WAS  956
TERMINATED DUE TO A PTHREAD QUIESCE OF TYPE 2.
BPXP011I THREAD 40F9E2C000000001, IN PROCESS 211, WAS  957
TERMINATED DUE TO A PTHREAD QUIESCE OF TYPE 2.
BPXP011I THREAD 40F9F1D000000002, IN PROCESS 211, WAS  958
TERMINATED DUE TO A PTHREAD QUIESCE OF TYPE 2.
SYSTEM COMPLETION CODE=0C1  REASON CODE=00000001
  TIME=14.27.13  SEQ=44974  CPU=0000  ASID=00C7
  PSW AT TIME OF ERROR  078D1400   80000002  ILC 2  INTC 01
    NO ACTIVE MODULE FOUND
    NAME=UNKNOWN
    DATA AT PSW  00000000 - 000A0000  000130E1  00000000
    GR 0: 00000000   1: 4298A340
       2: 40894608   3: 108602CA
       4: 4298A3B0   5: 40876C10
       6: C086EA6C   7: 0661F420
       8: 40875200   9: 4298A500
       A: 00000000   B: 4086E872
       C: 0000000C   D: 4298A448
       E: 00000000   F: 00000000
  END OF SYMPTOM DUMP
BPXP018I THREAD 40F8976000000424, IN PROCESS 211, ENDED  321
WITHOUT BEING UNDUBBED WITH COMPLETION CODE 940C1000, AND REASON CODE
00000001.
SYSTEM COMPLETION CODE=422  REASON CODE=000001A0
  TIME=14.29.16  SEQ=45446  CPU=0000  ASID=00C7
  PSW AT TIME OF ERROR  070C4400   C08642BE  ILC 2  INTC 78
    NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME
    NAME=UNKNOWN
BPXP023I THREAD 40F9B59000000000, IN PROCESS 211, WAS  342
TERMINATED BY SIGNAL SIGCNCL, SENT FROM THREAD
40F8976000000424, IN PROCESS 211, UID 50049, IN JOB E1407900.



All I tried so far to track this one down failed. I'm at the end of my 
skills :-(



Could anyone please give me some advise how to find this bug? Any good 
manual to read?



Thank you very much,
Michael

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to