ADSM-L

Re: Events table

2006-11-13 07:28:27
Subject: Re: Events table
From: "Smith, I (Ian)" <Ian.Smith AT RABOBANK DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 13 Nov 2006 12:27:46 -0000
 
Richard

Does this make sense:

That when a server is associated to a schedule, the events table
populates an entry for the server back to every scheduled time until the
start_time parameter. Hence all the uncertains. I expect that it then
attempts to poulate the returns be cross referencing the summary table.
If there is no return code in the summary then it assumes missed.


_____________________________
Ian Smith
SAN/TSM Specialist
Hitachi Data Systems Certified Professional
IBM Tivoli Storage Manager Certified Consultant
IT Infrastructure
Rabobank International
Thames Court, One Queenhithe
London EC4V 3RL
t: +44 (0)20 7809 3046
f: +44 (0)20 7809 3599
m: +44 (0)7843 689914
Mailto: ian.smith AT rabobank DOT com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: 13 November 2006 12:25
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Events table

Ian -

The peculiarities of the Events table can be found in many past
discussions preserved in the List archives.  It is not an actual table,
but instead presents information derived from other sources in the TSM
database (see APAR IC28825).  As noted in ADSM QuickFacts, you need to
specify values for the SCHEDULED_START and/or ACTUAL_START columns.  See
other APARs for more perspective.  As you've noticed, you get different
information reported from the table vs. the Query EVent command.

   Richard Sims
_____________________________________________________________

This email (including any attachments to it) is confidential, legally 
privileged, subject to copyright and is sent for the personal attention of the 
intended recipient only. If you have received this email in error, please 
advise us immediately and delete it. You are notified that disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Although we have taken reasonable 
precautions to ensure no viruses are present in this email, we cannot accept 
responsibility for any loss or damage arising from the viruses in this email or 
attachments. We exclude any liability for the content of this email, or for the 
consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently 
confirmed in writing. If this email contains an offer, that should be 
considered as an invitation to treat.
_____________________________________________________________

<Prev in Thread] Current Thread [Next in Thread>