ADSM-L

Re: Query Event for Previous day shows status In Progress

2003-11-06 17:41:36
Subject: Re: Query Event for Previous day shows status In Progress
From: "Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 6 Nov 2003 16:41:08 -0600
Here's the descriptions we give for the Failed Status to users:

In Progress used to be (?) - which in all the cases I've seen actually makes
more sense!  Event's "In Progress" show as "Started" all the time for us.



Status
======

In Progress   - Schedule not completed, status not reported to server
                  - check dsmerror.log, dsmsched.log and OS Event logs
              - Usually means session severed to TSM server
              - Could be caused by Network error, TSM Server or client error
during schedule
              - Restart TSM Client Schedule Service

Completed(4)  - The operation completed successfully, but some files were
not processed
              - Files are not processed for various reasons. The most common
reasons are:
              - The file was in use by another application and could not be
accessed by the client
              - The file changed during the operation to an extent
prohibited by the copy serialization attribute
              - (See client errors attachment for failed files)

Completed(8)  - The operation completed with at least one warning message
              - Check Windows Event Log or dsmerror.log and dsmsched.log

Failed        - Client reported a failure - check dsmerror.log and
dsmsched.log
              - Archives may show Failed if files opened with exclusive
access were not processed
              - (These files should be excluded, or the application should
be stopped via pre/post cmds)

Missed        - TSM Server could not contact client during startup window
              - This could indicate a problem with TSM Server, TSM client or
network (including firewall rules)
              - Ensure TSM Client Schedule Service is running

Restarted     - Schedule was still running when report was run
              - Session lost and reconnected during startup window (eg.
Reboot)
              - Check dsmsched.log/event logs for final status

Started       - Schedule was still running when report was run
              - Check dsmsched.log/event logs for final status