Re: Discrepancy select vs. q act
2005-06-23 10:08:44
You don't mention version numbers of the TSM components. However, IC33840
might explain the trouble (go to www.ibm.com and search on IC33840).
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.
Dave Zarnoch <zarnocd AT NATIONWIDEPROVIDENT DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2005-06-23 06:56
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Discrepancy select vs. q act
Folks....I have a problem when creating a report:
Using "q act begind=-1 se=PROV1010":
06/23/05 02:19:35 ANE4961I (Session: 201, Node: PROV1010) Total
number of
bytes transferred: 2.14 GB
Using "select * from summary":
START_TIME: 2005-06-23 00:48:03.000000
END_TIME: 2005-06-23 02:19:35.000000
ACTIVITY: BACKUP
NUMBER: 201
ENTITY: PROV1010
COMMMETH: Tcp/Ip
ADDRESS: 172.28.254.70:32385
SCHEDULE_NAME: PROV1010
EXAMINED: 1103951
AFFECTED: 2727
FAILED: 2
BYTES: 0
IDLE: 0
MEDIAW: 0
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
Why is the select statement giving me 0 bytes instead of 2.14GB
Am I missing something here?
Thanks!
DaveZ
|
|
|