Yes, but when I am looking at the actual EVENTS table via ACCESS and
odbc, it appears to only contain data for the current
day......................

>>> storman AT US.IBM DOT COM 06/23/03 11:28AM >>>
You need to do something like this:

   select * from events where scheduled_start>'06/13/2003'

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/23/2003 07:57
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: TSM DB Summary table



Hi,
I can get prior days info by issuing a:
q event * * type=client begindate=06/13/2003 endd=today   exceptions
            only=y
but looking directly at the EVENTS table it contains no data prior to
the current date. I assume the above command goes against the activity
log, since it returns 'uncertain' for days earlier than the life of
the
events log.

>>> storman AT US.IBM DOT COM 06/23/03 10:50AM >>>
You need to specify values for the SCHEDULED_START and/or ACTUAL_START
columns in order to get older data from the EVENTS table. You could do
this via a script that calculates today's date - n days, and plugs
that
into a SELECT statement. Or just go with QUERY EVENTS.

The difficulties in getting the EVENTS table to work with dates other
than
today have been discussed on ADSM-L in the past. Also see APAR IC34609
for
additional info.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/23/2003 07:38
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: TSM DB Summary table



OK. Thanks; the EVENTS table seems to only status dor the current day.

>>> storman AT US.IBM DOT COM 06/23/03 10:27AM >>>
For client operations, the SUCCESSFUL column name is a bit of a
misnomer.
as it really just indicates whether the communications between server
and
client terminated successfully (I believe that this maps to the
"normal
server termination indicator" field in the account log records).

For monitoring client status, use QUERY EVENT FORMAT=DETAILED or the
EVENTS table. See the section on client return codes in the
"Automating
tasks" chapter of the client manual for additional info about client
status reporting.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/23/2003 06:16
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        TSM DB Summary table



Hi:
I'm looking at the contents of the TSM Summary table and the
SUCCESSFUL
column for backups does not seem to relate to failed or missed nodes.
Anyone know how to interpret this column correctly?