Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM DB Summary table
In summary, by default this virtual table contains records
for just the current date unless the WHERE clause is
filtering on SCHEDULED_START and the clause is a literal value.
OKit'
10:30
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM DB Summary table
If access is returning all the rows when II look at the table, it is
only returning the current date.
Other tables return rows over a thous
06/23/2003 10:30
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM DB Summary table
If access is returning all the rows when II look at the table, it is
only returning the current date.
Other tables return rows over
riend.
"Good enough" is the enemy of excellence.
Lawrence Clark <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/23/2003 10:08
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
c
st Stor Manager" <[EMAIL PROTECTED]>
06/23/2003 10:08
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM DB Summary table
SELECT [SCHEDULED_START], [ACTUAL_START], [DOMAIN_NAME],
[SCHEDULE_NAME], [NODE_NAME]
ndrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
D]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/23/2003 09:01
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM DB Summary table
Yes, but when I am looking at the actual EVENTS table vi
.
"Good enough" is the enemy of excellence.
Lawrence Clark <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/23/2003 07:57
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Sub
;ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
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
lence.
Lawrence Clark <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/23/2003 07:38
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM DB Summary table
OK. Tha
3 07:38
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM DB Summary table
OK. Thanks; the EVENTS table seems to only status dor the current day.
>>> [EMAIL PROTECTED] 06/23/03 10:27AM >>>
For cli
goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Lawrence Clark <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/23/2003 06:16
Please respond to "ADSM: Dist Stor Manager"
To
ECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/23/2003 06:16
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:TSM DB Summary table
Hi:
I'm looking at the contents of the TSM S
From: Lawrence Clark [mailto:[EMAIL PROTECTED]
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?
As has been said many times in this list, the summary t
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?
15 matches
Mail list logo