On Nov 13, 2006, at 8:04 AM, Smith, I (Ian) wrote:
So if a scheduled event exists within the eventretention period but
was
before the time the node was associated- will this return a missed
status?
It appears to be the case. You can also encounter "misses" with
small schedule Duration values
So if a scheduled event exists within the eventretention period but was
before the time the node was associated- will this return a missed
status?
_
Ian Smith
SAN/TSM Specialist
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Beh
On Nov 13, 2006, at 7:27 AM, Smith, I (Ian) wrote:
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
atte
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
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 value
> I am not sure you will be able to do what you want even when you get
> the selection criteria sorted out. The events table on our 5.1.7.2
server
> does not have a column for completion time. If the same is true on your
> server you will probably have to use 'query event' output to compute
> durat
> Hi TSM expert
> I am trying to write a script to check a duration time of each
schedule
> in a day. I need to use an events table to select the data. But in this
table it
> show only the information of a current date. I dont know why. But when I
use
> q event begind=-2, it can displ
The problem is when selecting from events table it's by default generated
with the information of todays date only. Using
(CURRENT_TIMESTAMP-SCHEDULED_START<'2 00:00:00') will get information less
than two days old within todays info. See the problem? However if you
specify a specific date (i.e. '2
You might want to read this article on this subject:
http://msgs.adsm.org/cgi-bin/get/adsm0111/816.html
> -Original Message-
> From: David E Ehresman [mailto:[EMAIL PROTECTED]
> Sent: vrijdag 28 maart 2003 14:03
> To: [EMAIL PROTECTED]
> Subject: Events table
>
>
> If I do a "SELECT *
set eventretention . Use q stat to see current value.
_
William Mansfield
Senior Consultant
Solution Technology, Inc
Gerald Wichmann <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
04/26/2002 11:26 AM
Please respond to "ADSM: Dist Sto
y, 14 September 2000 2:53 AM
To: [EMAIL PROTECTED]
Subject: Re: Events Table
Helas, helas
there is no such table to use !
Regards,
René Lambelet
Nestec S.A. / Informatique du Centre
55, av. Nestlé CH-1800 Vevey (Switzerland)
*+41(021) 924 3543 7 +41 (021) 924 4589 * B 133
Visit our site:
The EVENTS table is available in the V3.7 and 4.1 servers.
Regards,
Andy
Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
Helas, helas
there is no such table to use !
Regards,
Ren
é Lamb
Helas, helas
there is no such table to use !
Regards,
René Lambelet
Nestec S.A. / Informatique du Centre
55, av. Nestlé CH-1800 Vevey (Switzerland)
*+41(021) 924 3543 7 +41 (021) 924 4589 * B 133
Visit our site: http://www.nestle.com
This message is intended only for the use of
13 matches
Mail list logo
