Re: [ADSM-L] Reporting and BIRT in TSM 6.2
I solved 24 hours in arrears by adjusting the collection and warehouse
intervals to more frequent occurrence. Collecting at 15 minutes and
warehousing at 1 hour.
Your suggestion to go directly to the TSM db2 is good, ALL of the data is there
and timely. We sometimes use the node contact name, which doesn't seem to
appear in the WAREHOUS schema.
I found a couple of errors in the BIRT rtp library as delivered on the TSM 6
package. It wasn't correctly identifying failed schedules on the summary chart
and node listing. Solved the chart by editing the SchedulesSummary Data Set.
Similar edit on the SchedulesMissed data set returns totally incorrect result.
Also haven't figured out how to get a "July 11, 2011 6:00 PM" string out of the
"1110711180000000" string value. It appears the leading 1 and trailing 000 are
I'll be skinning my knees a few times learning to ride this new bicycle.
State of Kansas - DISC
Harold.Vandeventer AT da.ks DOT gov
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sent: Sunday, July 17, 2011 1:51 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] SV: Reporting and BIRT in TSM 6.2
I have been working a little bit with BIRT. One thing you need to remember
about the Warehouse database is that it is 24 hours behind the real world.
You need to open the TSM DB2 database to be accessible direct from TCR and then
write reports direct to the TSM Server to be able to get 20 hours backup status.
Cell: +46-70-325 1577
E-mail: Christian.Svensson AT cristie DOT se
Supported Platform for CPU2TSM::
Från: Vandeventer, Harold [BS] [Harold.Vandeventer AT DA.KS DOT GOV]
Skickat: den 15 juli 2011 18:47
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: Re: Reporting and BIRT in TSM 6.2
I will first admit that I'm a TSM admin, not a "report writer".... but we have
to come up with a replacement for the reporting component on the TSM 5.x
Finally got BIRT Report Designer configured to query the TCR WAREHOUS schema.
When previewing a report in BIRT Report Design the schedule start displays as
'1110714180036000'. That is somehow to be July 14th, 2011 at 6:00 PM.
Running the similar report in Administration Center (Reporting > Common
Reporting) properly displays the "Jul 14, 2011 6:00 PM" format.
The data is defined as CHAR in Birt, not a date/time as I would expect. I
don't know enough DB2 yet to look at the properties in WAREHOUS.
Anyone out there working, successfully, with BIRT?
At least a few of you are holding out for Cognos in a future release.