Hi, My exprience is that it is the dsmc programme that runs the scheduled jobs, usually when things get "odd" we restart this scheduler process on the client. dsmcad is the deamon required to run the web interface to do backup and restores. But I am on Solaris not RD Linux.
Regards Pete -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Jurjen Oskam Sent: 15 September 2005 11:48 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Scheduled session remains active Hi, I have a problem with a scheduled command. The TSM server is 5.3.1.4 on AIX 5.3 ML2, the affected client is 5.2.2.0 on Red Hat Linux Advanced Server 2.1 (i386). SCHEDmode is PROMPTed, the client has MANAGEDSERVICES WEBCLIENT SCHEDULE and dsmcad is runnning. There are two schedules defined for this client, to run after each other: Policy Domain Name: PD_TRIAS Schedule Name: DB_DIGIDATA_DDM+MIS Description: Backup DigiData databases Action: Command Options: Objects: /home/oracle/scripts/sh/backup-digiddm-digimis.sh Priority: 5 Start Date/Time: 02/25/05 21:00:00 Duration: 30 Minute(s) Schedule Style: Classic Period: 1 Day(s) Day of Week: Weekday Month: Day of Month: Week of Month: Expiration: Last Update by (administrator): JOSKAM Last Update Date/Time: 09/14/05 11:19:42 Managing profile: Policy Domain Name: PD_TRIAS Schedule Name: INCR_AIX Description: Daily incremental backup for AIX systems Action: Incremental Options: Objects: Priority: 5 Start Date/Time: 04/12/02 22:00:00 Duration: 4 Hour(s) Schedule Style: Classic Period: 1 Day(s) Day of Week: Weekday Month: Day of Month: Week of Month: Expiration: Last Update by (administrator): JOSKAM Last Update Date/Time: 09/14/05 11:34:31 Managing profile: As you can see, the first schedule completed successfully and on time: Policy Domain Name: PD_TRIAS Schedule Name: DB_DIGIDATA_DDM+MIS Node Name: COOKIEMONSTER Scheduled Start: 09/14/05 21:00:00 Actual Start: 09/14/05 21:00:09 Completed: 09/14/05 21:42:13 Status: Completed Result: 0 Reason: All operations completed successfully. The problem is that the second schedule (INCR_AIX) is never started. SCHEDMODE is PROMPTed, but the TSM server never prompts the client to start the INCR_AIX schedule. I believe I have found the cause for this: 09/14/05 21:00:01 ANR2561I Schedule prompter contacting COOKIEMONSTER (session 2636) to start a scheduled operation. (SESSION: 26) 09/14/05 21:00:09 ANR0406I Session 2637 started for node COOKIEMONSTER (Linux86) (Tcp/Ip cookiemonster.trias.nl(33983)). (SESSION: 2637) [...] 09/14/05 21:42:13 ANR2507I Schedule DB_DIGIDATA_DDM+MIS for domain PD_TRIAS started at 09/14/2005 21:00:00 for node COOKIEMONSTER completed successfully at 09/14/2005 21:42:13. (SESSION: 2637) 09/14/05 21:42:13 ANR0403I Session 2637 ended for node COOKIEMONSTER (Linux86). (SESSION: 2637) 09/14/05 21:42:13 ANR0406I Session 2700 started for node COOKIEMONSTER (Linux86) (Tcp/Ip cookiemonster.trias.nl(34037)). (SESSION: 2700) 09/14/05 21:42:13 ANR0403I Session 2700 ended for node COOKIEMONSTER (Linux86). (SESSION: 2700) 09/15/05 02:00:01 ANR2578W Schedule INCR_AIX in domain PD_TRIAS for node COOKIEMONSTER has missed its scheduled start up window. 09/15/05 03:00:34 ANR0403I Session 2636 ended for node COOKIEMONSTER (). (SESSION: 26) As you can see, session 2636 isn't ended until 03:00:34. I don't understand why. My guess is that it's ended due to a timeout on the server side (COMMTIMEOUT is 3600). On the client, the scheduler logfile contains: [...] 09/14/2005 21:00:09 Executing Operating System command or script: /home/oracle/scripts/sh/backup-digiddm-digimis.sh 09/14/2005 21:42:13 Finished command. Return code is: 0 09/14/2005 21:42:13 ANS1908I The scheduled command completed successfully. 09/14/2005 21:42:13 Scheduled event 'DB_DIGIDATA_DDM+MIS' completed successfully . 09/14/2005 21:42:13 Sending results for scheduled event 'DB_DIGIDATA_DDM+MIS'. 09/14/2005 21:42:13 Results sent to server for scheduled event 'DB_DIGIDATA_DDM+ MIS'. [...] 09/14/2005 21:42:13 Next operation scheduled: 09/14/2005 21:42:13 ------------------------------------------------------------ 09/14/2005 21:42:13 Schedule Name: INCR_AIX 09/14/2005 21:42:13 Action: Incremental 09/14/2005 21:42:13 Objects: 09/14/2005 21:42:13 Options: 09/14/2005 21:42:13 Server Window Start: 22:00:00 on 09/14/2005 09/14/2005 21:42:13 ------------------------------------------------------------ 09/14/2005 21:42:13 Scheduler has been stopped. ... and the dsmwebcl.file shows: [...] 09/14/2005 21:42:14 (dsmcad) Waiting to be contacted by the server. I don't understand why session 2636 remains active for so long, while the schedule already ran successfully. That session seems to cause the TSM server to not prompt that client for the next session, which is a problem. I already searched ADSM.QuickFacts and the IBM Technotes and APARs, but couldn't find a solution. Maybe someone here ran into something like this and knows a solution? Thanks, -- Jurjen Oskam
