ADSM-L

[ADSM-L] Strange TSM SQL behaviour

2009-11-03 02:27:53
Subject: [ADSM-L] Strange TSM SQL behaviour
From: Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 3 Nov 2009 10:25:42 +0300
Hello,
I need somebody's comments on next result of select query:

Session established with server BKME: AIX-RS/6000
  Server Version 5, Release 5, Level 3.0
  Server date/time: 11/03/2009 10:16:16  Last access: 11/03/2009 10:13:43

ANS8000I Server command: 'select sum(bytes) as sumbytes, 
sum(cast((end_time-start_time)seconds as decimal)) as sumtime, sum(affected) as 
sumaffected, sum(failed) as sumfailed, sum(mediaw) as summediaw from summary 
where entity in (select node_name from nodes)  and 
cast((current_timestamp-start_time)hours as decimal)>10000'

       SUMBYTES:
         SUMTIME:
SUMAFFECTED:
     SUMFAILED:
   SUMMEDIAW:

ANS8002I Highest return code was 0.

It looks as a bug. It should show all sums equal 0.
What is this?

Thank you very much in advance.


Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme 
DOT com<mailto:G.Solonovitch AT bkme DOT com>

Please consider the environment before printing this Email


Please consider the environment before printing this Email.

________________________________
"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."

<Prev in Thread] Current Thread [Next in Thread>
  • [ADSM-L] Strange TSM SQL behaviour, Grigori Solonovitch <=