Hi,

We have the exact same situation. What's more the event keeps on missing
(because one is in progress ?), and, in this particular case the actual
start date is 7 days after the scheduled start date, even though the
startup window is 1 hour. 

Restarting the client appeared to help get the schedule going again.

Need to do a lot of updating to the database :-.

tsm: TSM_SERVER>q eve * linux* begind=-10 endd=today

Scheduled Start      Actual Start         Schedule Name Node Name
Status
-------------------- -------------------- ------------- -------------
---------
11/22/2003 23:30:00  11/29/2003 14:00:36  LINUX_FULL_B- CREDITORS     In
Progr-
                                           ACKUPS
ess
11/24/2003 10:31:55                       LINUX_INCR_B- CREDITORS
Missed
                                           ACKUPS
11/25/2003 10:31:55                       LINUX_INCR_B- CREDITORS
Missed
                                           ACKUPS
11/26/2003 10:31:55                       LINUX_INCR_B- CREDITORS
Missed
                                           ACKUPS
11/27/2003 10:31:55                       LINUX_INCR_B- CREDITORS
Missed
                                           ACKUPS
11/28/2003 10:31:55                       LINUX_INCR_B- CREDITORS
Missed
                                           ACKUPS
11/29/2003 23:30:00                       LINUX_FULL_B- CREDITORS
Missed
                                           ACKUPS
12/01/2003 10:31:55                       LINUX_INCR_B- CREDITORS
Missed
                                           ACKUPS
12/02/2003 10:31:55  12/02/2003 10:40:11  LINUX_INCR_B- CREDITORS
Started
                                           ACKUPS

Regards,

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Stanley, Jon
Sent: 29 November 2003 00:19
To: ADSM-L AT VM.MARIST DOT EDU
Subject: "In Progress" events?


I have several events listed as being "In Progress", with no associated
session.  A restart of both the TSM application and the entire server
has been unsuccessful at resolving the issue, so I think that the issue
is database related, but can't be sure.  Is there something that I can
do to fix this?

TSM Server 4.2.4.1 on Solaris 8.

tsm: TSM2.USSNTC6>q ev * *

Scheduled Start         Actual Start            Schedule Name    Node
Name        Status
--------------------    --------------------    -------------
-------------    ---------
11/28/03   00:00:00                             DAILY_01
I01SV5212-IPP    Missed
11/28/03   00:00:00     11/28/03   00:24:46     DAILY_01
I01SV4365-IPP    In Progr-
 
ess
11/28/03   00:00:00     11/28/03   02:15:31     DAILY_01
I01SV4370-IPP    In Progr-
 
ess
11/28/03   00:00:00     11/28/03   03:09:57     DAILY_01
I01SV4423-IPP    In Progr-
 
ess
11/28/03   00:00:00     11/28/03   00:50:20     DAILY_01
I01SV4363-IPP    In Progr-
 
ess
11/28/03   00:00:00     11/28/03   00:02:27     DAILY_01
I01SV4162-IPP    In Progr-
 
ess


tsm: TSM2.USSNTC6>q sess

  Sess  Comm.   Sess      Wait    Bytes    Bytes  Sess   Platform
Client Name
Number  Method  State     Time     Sent    Recvd  Type
------  ------  ------  ------  -------  -------  -----  --------
--------------------
     5  Tcp/Ip  Run       0 S     6.0 K      286  Admin  SUN SOL-
JSTANLEY
                                                          ARIS

tsm: TSM2.USSNTC6>