Hi Vikas
I am so sorry it has taken me so long to respond. I am looking at your
output that you provided, and it looks like all of the values are in hours,
which used to be in days and weeks. I am pretty sure that what you are
seeing is Listener that OC uses to get updates from Spectrum Protect has
crashed. This would result in OC not updating results. We have fixed this
crashing in 7.1.3. The only other work around is to restart OC. Sorry.

Rob Jose
TSM OC UI Developer / L3 Support
rjose AT us.ibm DOT com
(971) 238 - 8998

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/13/2015
05:52:05 AM:

> From: Vikas Arora <vikaroin AT GMAIL DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 10/13/2015 05:53 AM
> Subject: Re: [ADSM-L] Operation Center Blues!!
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Hello Robert,
>
> Did you find any possibilities for any improvements?
>
> thanks
>
> Vikas
>
>
>
>
>
>
>
>
> Grüße
> Vikas Arora
>
> *e Mail* : vikaroin AT gmail DOT com
>
> On 9 October 2015 at 09:20, Vikas Arora <vikaroin AT gmail DOT com> wrote:
>
> >
> > On 8 October 2015 at 19:33, Robert Jose <rjose AT us.ibm DOT com> wrote:
> >
> >> name, sec_last_catalog_backup from tsmgui_allsrv_grid
> >
> >
> > Hi Robert,
> >
> > Here is the select output.
> >
> > tsm: TSM197LM>select name, sec_last_catalog_backup from
tsmgui_allsrv_grid
> >
> > NAME
> >  SEC_LAST_CATALOG_BACKUP
> > ------------------------------------------------------------------
> > ------------------------
> > ERR_TAPES
> >                     0
> > TSM101
> >                19538
> > TSM102D
> >                 21248
> > TSM103D
> >                  3421
> > TSM104D
> >                 32247
> > TSM105
> >                21536
> > TSM106D
> >                 15261
> > TSM202D
> >                 54993
> > TSM203D
> >                 38068
> > TSM204D
> >                  7104
> > TSM205
> >                22205
> > TSM229D
> >                 16253
> > TSM232D
> >                 30587
> > TSM197LM
> >                 6912
> > TSM209D
> >                  8198
> > TSM206D
> >                 18679
> > TSM201D
> >                 40166
> > TSM231D
> >                 28114
> > TSM230D
> >                 33762
> > TSM210D
> >                 23540
> > TSM215
> >                35205
> > TSM226
> >                35257
> > TSM227
> >                45998
> > TSM228
> >                14412
> > TSM211
> >                20907
> > TSM296LM
> >                    0
> > TSM291LM
> >                    0
> > TSM292LM
> >                66247
> > TSM293LM
> >                43328
> > TSM294LM
> >                    0
> > TSM191LM
> >                43889
> > TSM192LM
> >                 4721
> > TSM21
> >                 65029
> > TSM207D
> >               3951802
> > TSMNLAMS101
> >                 10279
> >
> >
> > So TSM201D was just an example, there are other servers too which shows
> > last data collected 2 days ago in  'sh monservers' output.
> >
> > is the value in the bottom right of the grid updating the last
> > refreshed time?   >>> Yes, see the link
> >
> >
> > https://drive.google.com/file/d/0BwDDdmz6R7PtUmxqblVER3BKRmc/view?
> usp=sharing
> >
> >
> > Also TSM server count sometime is false, or may be due to no data
> > collection, see Yellow marks in the screenshots.
> >
> > Many thanks
> >
> >
> >
> >
> > Grüße
> > Vikas Arora
> >
> > *e Mail* : vikaroin AT gmail DOT com
> >
>