Seems to be the main DB2 engine.

When I Googled it, this page:
http://bytes.com/topic/db2/answers/181656-db2sysc

has good details on what piece-part is what.



From:
Wanda Prather <wprather AT JASI DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
10/19/2009 02:44 PM
Subject:
Re: [ADSM-L] Will db2sysc ever calm down?
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



What does db2sync do, anyway?

Don't have a process by that name on 6.1.2 Winders....

W

On Mon, Oct 19, 2009 at 2:40 PM, Zoltan Forray/AC/VCU
<zforray AT vcu DOT edu>wrote:

> Yeah, I tried just kill and then kill -2 (someone from IBM told me to
try
> that on something - can't remember what) first, with no results.
>
> I will try -11 next time.
>
>
>
> From:
> Richard Sims <rbs AT BU DOT EDU>
> To:
> ADSM-L AT VM.MARIST DOT EDU
> Date:
> 10/19/2009 02:24 PM
> Subject:
> Re: [ADSM-L] Will db2sysc ever calm down?
> Sent by:
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
> On Oct 19, 2009, at 1:59 PM, Zoltan Forray/AC/VCU wrote:
>
> > Today I found my 6.1.2 Linux server non-responsive.
> >
> > Had to kill -9 the dsmserv process. Restarted it.
>
> Don't know if you did so, but always reserve 'kill -9' for a last
> resort, as SIGKILL cannot be intercepted and handled by a process so
> as to allow it to log diagnostic information, flush buffers, and shut
> down relatively cleanly.  Doing a 'kill -11' has been the preferred
> method, per the historic Problem Determination Guide.  SIGKILL has the
> potential to result in damage.
>
>    Richard Sims
>