Operational reporting from TSM 5.5 on TSM 6.x

[Mita201]

There is a document on IBM site how to modify TSM Operational reporting of TSM 5.5 to work with TSM 6.x.
Basically, you edit few queries, and drop some.
Two queries that you should edit are Tape Mount Count (TMS) and number of minutes tapes has been mounted (MTM)
If you test those queries, they work as expected. But, in reports, they only add count on old value every day. Eg, if I had 5 tape mounts yesterday, and 120 minutes tapes has been mounted, and I have 3 tape mounts today + 80 minutes today, report from today will show 8 mounts and 200 minutes. Tomorrow it will add on top of it.
Anyone know why is that?

 

[Mita201]

I have fixed this.
Queries should not be as stated in document:
http://www-01.ibm.com/support/docview.wss?uid=swg27019794
but this way:

For TMS: select count(*) as TMS from summary where activity='TAPE MOUNT' and TIMESTAMPDIFF (8,CHAR(current_timestamp-start_time )) <%s
For MTM: select (sum(minute(end_time-start_time))) as MTM from summary where activity='TAPE MOUNT' and TIMESTAMPDIFF (8,CHAR(current_timestamp-start_time )) <%s

Hope this will help somebody...

 

[mladams]

I am not familiar w/ sequel so am struggling a bit. I can get the first half of the command to work fine but when I add in the TIMESTAMPDIFF I can't get it to work. I would like to get the MTM to run daily and calculate the MTM for 24 hours. The error I'm getting is below:
ANR0516E SQL processing for statement select ( sum ( minute ( end_time-start_time ) ) ) as MTM from summary where activity = 'TAPE MOUNT' and TIMESTAMPDIFF ( 8 , CHAR (
current_timestamp-start_time ) ) < %s failed.

 

[Mita201]

Hm, it works with my 6.2 server.
Here is my statement, copy/pasted:
select (sum(minute(end_time-start_time))) as MTM from summary where activity='TAPE MOUNT' and TIMESTAMPDIFF (8,CHAR(current_timestamp-start_time )) <%s

What is your TSM version?

 

[mladams]

Version 6.2.1 Our IBM consultant has found that some of the sequel commands do not run on 6.2.1 but appear to work with 6.2.2. Are you at 6.2.1 or 6.2.2 ?

 

[Mita201]

Version 6.2.1 Our IBM consultant has found that some of the sequel commands do not run on 6.2.1 but appear to work with 6.2.2. Are you at 6.2.1 or 6.2.2 ?

I run it against 6.2.2, AND 6.1.3 as well.
Please find attached complete xml, so try putting it in your OR.

 

[mladams]

Thanks so much. I'll give it a try!! Much appreciated.
Maura

 

[sheenp]

We've recently moved to this configuration and were having occasional issues with the hourly operational monitor generating an email with errors and the hourly web page with collapsible heading "Error -- Server Information". Reviewing the monitor trace (below) it appears when we get the error there are two threads get initiated around the same time for the same monitor. Does any one have any experience with this sort of error? Any suggestions for resolving this. We've had some earlier issues with reports not being produced which were resolved with a reboot.

Thanks,
Pat


03/30/2011 15:29:59 # 2128 # tsmreptsvc.cpp # 1527 # ******** EVENT - Operation starting
03/30/2011 15:29:59 # 2128 # tsmreptsvc.cpp # 1739 # Monitor, repeat interval: 1, HasRun: True
03/30/2011 15:29:59 # 2128 # tsmreptsvc.cpp # 1983 # INFO - TIMER - Set timer for monitor: supbackup1, Server1, Hourly Monitor
03/30/2011 15:29:59 # 2128 # tsmreptsvc.cpp # 1991 # -- it will start in 0 days, 0 hours, 1 minutes (1 total minutes)
03/30/2011 15:29:59 # 2128 # tsmreptsvc.cpp # 1592 # Timer went off. Adding the Monitor for supbackup1,Server1,Hourly Monitor,1 to the ready queue.
03/30/2011 15:29:59 # 2168 # tsmreptsvc.cpp # 2806 # Worker Thread 2 running report for supbackup1,Server1,Hourly Monitor,1.
03/30/2011 15:29:59 # 2168 # tsmreptsvc.cpp # 2823 # Worker Thread 2 is waiting for report completion.
03/30/2011 15:29:59 # 2168 # tsmreptsvc.cpp # 3048 # begin report...
03/30/2011 15:30:59 # 2128 # tsmreptsvc.cpp # 1527 # ******** EVENT - Operation starting
03/30/2011 15:30:59 # 2128 # tsmreptsvc.cpp # 1739 # Monitor, repeat interval: 1, HasRun: True
03/30/2011 15:30:59 # 2128 # tsmreptsvc.cpp # 1983 # INFO - TIMER - Set timer for monitor: supbackup1, Server1, Hourly Monitor
03/30/2011 15:30:59 # 2128 # tsmreptsvc.cpp # 1991 # -- it will start in 0 days, 1 hours, 0 minutes (60 total minutes)
03/30/2011 15:30:59 # 2128 # tsmreptsvc.cpp # 1592 # Timer went off. Adding the Monitor for supbackup1,Server1,Hourly Monitor,1 to the ready queue.
03/30/2011 15:30:59 # 2156 # tsmreptsvc.cpp # 2806 # Worker Thread 0 running report for supbackup1,Server1,Hourly Monitor,1.
03/30/2011 15:30:59 # 2156 # tsmreptsvc.cpp # 2823 # Worker Thread 0 is waiting for report completion.
03/30/2011 15:30:59 # 2156 # tsmreptsvc.cpp # 3048 # begin report...
03/30/2011 15:31:00 # 2156 # tsmreptsvc.cpp # 3099 # end report, RC: 0
03/30/2011 15:31:00 # 2156 # tsmreptsvc.cpp # 2881 # Worker Thread 0 completed Hourly Monitor.
03/30/2011 15:31:00 # 2156 # tsmreptsvc.cpp # 2763 # Worker Thread 0 waiting for work.
03/30/2011 15:31:09 # 2168 # tsmreptsvc.cpp # 3099 # end report, RC: 0
03/30/2011 15:31:09 # 2168 # tsmreptsvc.cpp # 2881 # Worker Thread 2 completed Hourly Monitor.
03/30/2011 15:31:09 # 2168 # tsmreptsvc.cpp # 2763 # Worker Thread 2 waiting for work.

 

[StephaneD]

I have set those two following report to run daily at 9h20 and somehow it run at 9:19 then at 9h20
see LogReportSVC.

02/15/2012 09:19:27: Active Report for VAN, VAN, Usage is set to run at 09:20 (0 hours 1 minutes).
02/15/2012 09:19:27: Adding the Report for VAN,VAN,Usage,0 to the ready queue.
02/15/2012 09:19:27: Worker Thread 1 running report for VAN,VAN,Usage,0.
02/15/2012 09:19:27: Worker Thread 1 is waiting for report completion.
02/15/2012 09:19:36: Worker Thread 1 completed Usage.
02/15/2012 09:19:36: Worker Thread 1 waiting for work.
02/15/2012 09:20:27: Active Report for VAN, VAN, Usage is set to run at 09:20 (24 hours 0 minutes).
02/15/2012 09:20:27: Adding the Report for VAN,VAN,Usage,0 to the ready queue.
02/15/2012 09:20:27: Worker Thread 3 running report for VAN,VAN,Usage,0.
02/15/2012 09:20:27: Worker Thread 3 is waiting for report completion.
02/15/2012 09:20:35: Worker Thread 3 completed Usage.
02/15/2012 09:20:35: Worker Thread 3 waiting for work.
02/15/2012 09:29:27: Active Report for VAN, VAN, Activity is set to run at 09:30 (0 hours 1 minutes).
02/15/2012 09:29:27: Adding the Report for VAN,VAN,Activity,0 to the ready queue.
02/15/2012 09:29:27: Worker Thread 2 running report for VAN,VAN,Activity,0.
02/15/2012 09:29:27: Worker Thread 2 is waiting for report completion.
02/15/2012 09:29:38: Worker Thread 2 completed Activity.
02/15/2012 09:29:38: Worker Thread 2 waiting for work.
02/15/2012 09:30:27: Active Report for VAN, VAN, Activity is set to run at 09:30 (24 hours 0 minutes).
02/15/2012 09:30:27: Adding the Report for VAN,VAN,Activity,0 to the ready queue.
02/15/2012 09:30:27: Worker Thread 0 running report for VAN,VAN,Activity,0.
02/15/2012 09:30:27: Worker Thread 0 is waiting for report completion.
02/15/2012 09:30:38: Worker Thread 0 completed Activity.

Where can I fix this ie. I need to remove
02/15/2012 09:29:27: Active Report for VAN, VAN, Activity is set to run at 09:30 (0 hours 1 minutes).
and
keep
02/15/2012 09:30:27: Active Report for VAN, VAN, Activity is set to run at 09:30 (24 hours 0 minutes).

also
remove
02/15/2012 09:19:27: Active Report for VAN, VAN, Usage is set to run at 09:20 (0 hours 1 minutes).
and keep
02/15/2012 09:20:27: Active Report for VAN, VAN, Usage is set to run at 09:20 (24 hours 0 minutes).

Also

This problem happen on a random matter, meaning it happening for a week then stop and start again for a day or two etc.

Many thanks

Stéphane