TSM Scheduled Operational Reports do not run

pstephen

ADSM.ORG Member
Joined
Sep 23, 2003
Messages
21
Reaction score
0
Points
0
Website
Visit site
I have upgraded the TSM Server to V5.2.9. The Scheduled Operational Reports do not run. IF I stop and restart tsmreptsvc the reports usually run and are emailed the next day, but then the following day they do not run again.

Has anyone seen this behavior?? Any ideas of what to do to correct this??

Thanks for any info.....
 
hello Pstephen,
have a look on your dsmserv.opt file,
and verify that the parameter "DISABLESCHEDS" is set to "NO"
 
Thanks for the idea. I checked dsmserv.opt and "DISABLESCHEDS" is set to "No".

I also looked at TSMreptsvc.txt and I see some entries like the entries below:
This all looks OK to me, but I am not sure exactly what to look for in this file.
Thanks again for any ideas....

01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1376 # ******** EVENT - REPORT_REGISTRY_CHANGED
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1382 # have lock 4
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1507 # sysLCID 00000409
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1556 # No languages installed
01/31/2007 09:45:53 # 4196 # setting3.cpp # 2089 # sn_opts: got report options
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1731 # INFO - TIMER - Set timer for: WOLFIE,Server1,Daily Backup Detail Report to start in 1250 mins, repeating every 0 mins.
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1507 # sysLCID 00000409
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1556 # No languages installed
01/31/2007 09:45:53 # 4196 # setting3.cpp # 2089 # sn_opts: got report options
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1731 # INFO - TIMER - Set timer for: WOLFIE,Server1,Daily Server Backup Report to start in 1218 mins, repeating every 0 mins.
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1507 # sysLCID 00000409
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1556 # No languages installed
01/31/2007 09:45:53 # 4196 # setting3.cpp # 2089 # sn_opts: got report options
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1731 # INFO - TIMER - Set timer for: WOLFIE,Server1,Daily Tape Status Report to start in 1217 mins, repeating every 0 mins.
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1507 # sysLCID 00000409
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1556 # No languages installed
01/31/2007 09:45:53 # 4196 # setting3.cpp # 2089 # sn_opts: got report options
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1731 # INFO - TIMER - Set timer for: WOLFIE,Server1,SQL and Exchange Backup Report to start in 1219 mins, repeating every 0 mins.
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1507 # sysLCID 00000409
01/31/2007 09:45:53 # 4196 # ifcnls.cpp # 1556 # No languages installed
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1731 # INFO - TIMER - Set timer for: WOLFIE,Server1,Hourly Monitor to start in 45 mins, repeating every 0 mins.
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1464 # Worker thread 0 has been running for 0 days, 01 hours, 15 minutes, 32 seconds
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1464 # Worker thread 1 has been waiting for work for 0 days, 00 hours, 15 minutes, 31 seconds
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1464 # Worker thread 2 has been waiting for work for 0 days, 02 hours, 15 minutes, 31 seconds
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1464 # Worker thread 3 has been waiting for work for 0 days, 03 hours, 01 minutes, 28 seconds
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1471 # **** TSM_S_RUNNING
01/31/2007 09:45:53 # 4196 # tsmreptsvc.cpp # 1482 # released lock 4
 
van you do a show time on your TSm server and verify that it's good,
have a look on dsmserv.err too
and did you had some error when you started your TSM server?
 
Thanks Mike;
The reports have been running fine for the last several days now. Unfortunately, I cannot identify any specific change that is different than the way it was set up on Monday (the last time I had the problem with the reports not running).

I did stop and restart the tsmreptsvc on Monday evening, but I have done that many times before and it did not correct the problem. Maybe this time it did? Of course, I did install V5.2.9 last Saturday, and I see that there is some extra report checking in V5.2.9, so maybe this fixed it after I restarted tsmreptsvc. (But I restarted tsmreptsvc on Saturday when I installed the update).

I will follow up if I see the problem come back. I also may just use the command line (tsmrept.exe) to invoke the reports from the Windows Task scheduler if I cannot get the tsmreptsvc to reliably schedule the reports.

Thanks for the offer of help.

Pete
 
Back
Top