S0C3 abend, SYSUDUMP, SYSABEND, and no dump output
Cecere, Sal
I have a job here that is sporadically getting S0C3 abends. I'd like to look
at the
dump, but none is produced. There is a SYSUDUMP and a SYSABEND dd in the job
step
that fails. We do have ABENDAID, so we also have a ABNLIGNR dd in this job
step.
There is no slip trap set up for 0C3's on the system.
In spite of this, we do not get a dump when the abend occurs. I am
apparently missing
something that is necessary to obtain this dump. Any ideas on what piece is
missing will
be appreciated.
TIA,
Salvatore Cecere
J. Baker, Inc.
555 Turnpike Street
Canton, MA, 02021
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Dean Montevago
Jon Brock
dump?"
Jon
Cummings, Jennifer , ECSS
had a dump from this job any future dumps will be suppressed. There is a
data set (default SYS1.DAE) that keeps tract of the entries. You can delete
the entry in the data set.
Just a thought.
Mark Thomen
products to cause a program check when a particular error occurs that wouldn't
otherwise cause a program check.
However there may be a recovery routine that is suppressing the dump. I'd check
in LOGREC for any software records related to it. The check to see if DAE is
suppressing the dump is also a good check to make.
Cecere, Sal wrote:
> Hello everyone,
>
> I have a job here that is sporadically getting S0C3 abends. I'd like to look
> at the
> dump, but none is produced. There is a SYSUDUMP and a SYSABEND dd in the job
> step
> that fails. We do have ABENDAID, so we also have a ABNLIGNR dd in this job
> step.
> There is no slip trap set up for 0C3's on the system.
>
> In spite of this, we do not get a dump when the abend occurs. I am
> apparently missing
> something that is necessary to obtain this dump. Any ideas on what piece is
> missing will
> be appreciated.
>
> TIA,
>
> Salvatore Cecere
> J. Baker, Inc.
> 555 Turnpike Street
> Canton, MA, 02021
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
--
Mark Thomen
DFSMS Development - Catalog, IDCAMS, and VSAM
Try the Catalog and VSAM Knowledge Base at:
http://SSDDOM01.storage.ibm.com/TechSup/swtechsup.nsf/support/dfsmsmain (click
"Technical Database")
or http://knowledge.storage.ibm.com/
H Jay Carr
seen
software which issues MVS abend codes for user problems, and forgets to
turn on the
parm which adds the dump.
You could try putting in your own SLIP command to take a dump for the
offending job
and abend code.
Skip Robinson
a wayward recovery routine gone bad. There's nothing peskier than trying to
tree one of those wild and wooly critters. Try setting a SLIP trap that
names the job specifically but does *not* specify any abend code. It may
turn out to be some other abend altogether.
Mark Thomen
<tho...@US.IB To: IBM-...@BAMA.UA.EDU
M.COM> cc:
Sent by: IBM Subject: Re: S0C3 abend, SYSUDUMP, SYSABEND,
Mainframe and no dump output
Discussion
List
<IBM-MAIN@BAM
A.UA.EDU>
08/17/2000
01:07 PM
Please
respond to
IBM Mainframe
Discussion
List
An ABEND0C3 is typically a "trap" kind of program check; frequently used by
products to cause a program check when a particular error occurs that
wouldn't
otherwise cause a program check.
However there may be a recovery routine that is suppressing the dump. I'd
check
in LOGREC for any software records related to it. The check to see if DAE
is
suppressing the dump is also a good check to make.
<snip>
Craddock, Chris
with "EX Rx,*" by the way). Whether or not you get a SYSxDUMP is completely
orthogonal. If the product recovery routine specified "DUMP=NO" in its SETRP
then you will never get a SYSxDUMP - and for systems software nor should
you.
DAE is not involved in suppressing SYSxDUMPs (well, ok SYSMDUMPs) so it
would typically only come into play if the product's recovery routine
requested an SVCDUMP and there were multiple occurrences of the same
symptoms. If you suspect that is true, you can over-ride it by getting into
IPCS and using the DAE information panels to do a "take dump" for that
syptom.
There may or may not be LOGREC records that relate to the problem, its
certainly worth running EREP to find out. If you don't have any other choice
you can set a SLIP trap ("SL SET,ID=xxxx,C=S0C3,A=SVCD,END") to catch a full
SVC dump (but make sure your SVCDUMP options are useful. You need to ensure
that you are dumping ALLPSA, RGN and COMMON at least.
Chris
> -----Original Message-----
> From: Mark Thomen [mailto:tho...@US.IBM.COM]
> Sent: Thursday, August 17, 2000 3:07 PM
> To: IBM-...@BAMA.UA.EDU
> Subject: Re: S0C3 abend, SYSUDUMP, SYSABEND, and no dump output
>
>
> An ABEND0C3 is typically a "trap" kind of program check;
> frequently used by
> products to cause a program check when a particular error
> occurs that wouldn't
> otherwise cause a program check.
>
> However there may be a recovery routine that is suppressing
> the dump. I'd check
> in LOGREC for any software records related to it. The check
> to see if DAE is
> suppressing the dump is also a good check to make.
----------------------------------------------------------------------
Bruce Hewson
I would also suggest that you use IPCS Utilities to list the DAE dataset and
see when the last S0C3 dump was suppressed. You should also have messages in
your SYSLOG regarding the suppressed dumps.
Regards
Bruce Hewson
----------------------------------------
ps: The 3rd Millennium will begin on 01/01/01!
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Thompson, William
-----Original Message-----
From: Craddock, Chris [mailto:Chris_C...@BMC.COM]
Sent: Thursday, August 17, 2000 5:02 PM
To: IBM-...@BAMA.UA.EDU
Subject: Re: S0C3 abend, SYSUDUMP, SYSABEND, and no dump output
(snip)
Whether or not you get a SYSxDUMP is completely orthogonal.
(snip)
Craddock, Chris
variable that has no effect on the variables under consideration is said to
be "orthogonal" because it would be plotted on an axis that is orthogonal to
the variables under consideration.
Chris
> -----Original Message-----
> From: Thompson, William [mailto:wtho...@OKC.DISA.MIL]
>
> "Orthogonal"? As in perpendicular?
>
SMITH, STEVE A. , LNG
wrote:
>
>Regards
>
>Bruce Hewson
>----------------------------------------
>ps: The 3rd Millennium will begin on 01/01/01!
>
Exsqueeze me, but isn't that the date when the 1st millennium began?
* Steve Smith, THEORIS(tm)
* ssm...@theoris.com
Martin Strudwick
-----Original Message-----
From: SMITH, STEVE A. (LNG) [mailto:STEVE....@LEXIS-NEXIS.COM]
Sent: Friday, August 18, 2000 12:10 PM
To: IBM-...@BAMA.UA.EDU
Subject: Re: S0C3 abend, SYSUDUMP, SYSABEND, and no dump output
Rolf Ernst
Rolf
On 18 Aug 2000 07:23:32 -0700, Chris_C...@BMC.COM (Craddock,
Chris) wrote:
>Well yes. As in independent. The term comes from the mathematical world. Any
>variable that has no effect on the variables under consideration is said to
>be "orthogonal" because it would be plotted on an axis that is orthogonal to
>the variables under consideration.
>
>Chris
>
>> -----Original Message-----
>> From: Thompson, William [mailto:wtho...@OKC.DISA.MIL]
>>
>> "Orthogonal"? As in perpendicular?
>>
>> (snip)
>>
>> Whether or not you get a SYSxDUMP is completely orthogonal.
>>
>> (snip)
>
Edward Gould
>wrote:
>
>>
>>Regards
>>
>>Bruce Hewson
>>----------------------------------------
>>ps: The 3rd Millennium will begin on 01/01/01!
>>
>
>Exsqueeze me, but isn't that the date when the 1st millennium began?
>
>* Steve Smith, THEORIS(tm)
>* ssm...@theoris.com
Steve,
nope,,, that was 1/1/1 :)
Ed
Cecere, Sal
I checked DAE and reset it - Of course now the job has run clean ever
since.....
-----Original Message-----
From: Bruce Hewson [mailto:bruce_...@HOTMAIL.COM]
Sent: Friday, August 18, 2000 3:38 PM
To: IBM-...@BAMA.UA.EDU
Subject: Re: S0C3 abend, SYSUDUMP, SYSABEND, and no dump output
And here I just sent Candle 4 S0C3 dumps.
I would also suggest that you use IPCS Utilities to list the DAE dataset and
see when the last S0C3 dump was suppressed. You should also have messages in
your SYSLOG regarding the suppressed dumps.
Regards
Bruce Hewson
----------------------------------------
ps: The 3rd Millennium will begin on 01/01/01!
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
----------------------------------------------------------------------