Oh thanks, John, I didn't know that.

My IEADMP00 is the default SDATA=SUM.  Is there an option there that
contains the CSA?  Anyway I changed it to this which I copied from our
production machine:

SDATA=(CB,ENQ,TRT,ERR,DM),PDATA=ALLPDATA

I was getting it also by a slip:
slip set action=svcd,comp=0c1,jobname=srbtst,sdata=csa

I managed to schedule an SRB which just did a WTO.  I ran it in another
TSO address space.  My main program ended.  And the SRB ended (I could
see by the WTO).  But the TSO address space started accumulating CPU
time.  It wouldn't cancel so I forced it.  

Then the whole machine hung up a bit and I got this, which I thought was
pretty cool, cause it looks more like a message from a washing machine
than a mainframe. 

PROCESSOR (02) DETECTED AN EXCESSIVE DISABLED SPIN LOOP             
WAITING FOR ADDRESS SPACE TO QUIESCE      FROM PROCESSOR (00).      
AUTOMATIC RECOVERY ACTION IS SPIN                                   
$HASP9202 POTENTIAL JES2 MAIN TASK LOOP DETECTED NEAR HASPNUC +0048C734 



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of John McKown
Sent: 24. elokuuta 2008 2:10
To: [email protected]
Subject: Re: Why don't I see my CSA storage in the dump?


What is actually dumped to SYSUDUMP, SYSABEND, and SYSMDUMP is set by
the 
system programmer in PARMLIB. There are defaults, but they can be 
overridden with the CHNGDUMP (CD) command. I think that the default for 
SYSABEND will contain the common areas. But that's not for sure,
depending 
on your shop standards. If you can do operator commands, you might try 
looking at the output from "D D,O" to see what the dump options are.

-- 
Q: What do theoretical physicists drink beer from?
A: An EIN stein.

Maranatha!
John McKown

----------------------------------------------------------------------
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