Tom,

the command you are looking for is 'slip'.  You can code the command,
described in painful detail in the system commands, and enter it on the console,
or you can add it to sys1.parmlib(ieaslp00) and issue the 'set slip=00' command.

I see that the requester is OAM, not adsm even though adsm took the dump.
Maybe there is something in OAM to fix.

Sorry, I can't code the slip command for you, it is usually an iterative 
process to
get it right.  But as a sample, here is my slip command the make tsm take a dump
when it abends, the reverse of what you want -

SLIP SET,ERRTYP=ABEND,JOBNAME=ADSM3SRV,ID=TSM1,A=SVCD,END

Hope this helps,

Bill Colwell


At 11:45 AM 1/2/2004, you wrote:
>We have a TSM 5.1.7.2 server running under OS/390 2.9 at the moment,
>and expected to be running under OS/390 2.10 within the next few days.
>We occasionally have a process or session cancelled while waiting for
>a tape mount. This triggers a completely useless memory dump from TSM.
>The OS/390 console message describing the dump is as follows:
>
>IEA794I SVC DUMP HAS CAPTURED: 463
>DUMPID=002 REQUESTED BY JOB (ADSM    )
>DUMP TITLE=COMPON=OAM LIBRARY AUTO COMM SERVICE,COMPID=5695-DF1
>           80,ISSUER=CBRLLACS
>
>Is there any way to suppress these dumps, either by changing TSM
>settings or by using OS/390 PARMLIB members or user exits?

----------
Bill Colwell
C. S. Draper Lab
Cambridge Ma.