Are these in minutes ? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Gerald Michalak Sent: Tuesday, November 08, 2005 11:10 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Log pinned, filled, almost crashed
Here's the technote. Problem Long-running sessions with poor throughput or hung sessions can cause the recovery log to become pinned. This can ultimately result in the TSM Server abending due to an over-committed recovery log. Cause Solution The THROUGHPUTDATATHRESHOLD and THROUGHPUTTIMETHRESHOLD options were introduced to help prevent hung sessions or long-running sessions from pinning the recovery log for any extended period of time. When the THROUGHPUTDATATHRESHOLD and THROUGHPUTTIMETHRESHOLD options are specified in the dsmserv.opt file, the TSM Server will check the status of a client session after the session has been running for X amount of time, where X is the time specified for the THROUGHPUTTIMETHRESHOLD. If the average throughput for this session does not meet or exceed the value specified for THROUGHPUTDATATHRESHOLD, then the session will be cancelled by the TSM Server, thus preventing the recovery log from becoming over-committed. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 11/08/2005 11:47:45 AM: > Have you looked into approaches suggested by IBM Technote 1084167? > > Richard Sims
