"QUERY SESSION # F=D" should show you when the first data was sent for that session. If you look in the activity log around the time of that first data being sent, I expect you'll find a BACKUP DB command starting that never finishes. The userid you're seeing is what your intra-TSM DB2 instance uses to do its DB backup.
If a TSM BACKUP DB command has hung this way, I hope you open a PMR with IBM; this shouldn't happen. Nick On Wed, Sep 4, 2013 at 7:14 AM, Arbogast, Warren K <warbo...@iu.edu> wrote: > There is a session on the TSM server for client name $$_TSMDBMGR_$$ with > negative wait time of -1,944,199 The session information says Bytes Sent > 1.5 K and Bytes Recvd of 21.4 G, which has not changed for at least 24 > hours. > > What is that session, and what is it doing? Can, or should, it be > cancelled? > > The TSM server is at version 6.3.2 on RHEL 5. > > With many thanks, > Keith Arbogast > Indiana University >
