I have server AIX 433 running TSM 4.1.4.5 & 4.1.3 client. The TSM scheduler runs out of /usr/tivoli/tsm/client/ba/bin. Over the past week, the TSM scheduler just quits. example of scheduler process w
Author: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
Date: Tue, 26 Feb 2002 11:30:08 -0500
Look in your dsmsched.log and dsmerror.log on this client and see if there are any messages indicating problem. I have one AIX client that occaisionally has a memory problem and that shows up in logs
Author: "Malbrough, Demetrius" <DMalbrough AT TTIINC DOT COM>
Date: Tue, 26 Feb 2002 10:35:45 -0600
Maybe you need to try the 'respawn' instead of 'once'! It may not be supported but I have been using 'respawn' for while with no problems! adsmschd:a2:respawn:/etc/rc.adsmc >/dev/null 2>&1 #Start ADS
Author: George Lesho [mailto:GLesho AT AFCE DOT COM]
Date: Sun, 04 Oct 2015 17:12:14 -0500
I have server AIX 433 running TSM 4.1.4.5 & 4.1.3 client. The TSM scheduler runs out of /usr/tivoli/tsm/client/ba/bin. Over the past week, the TSM scheduler just quits. example of scheduler process w
No... The scheduler had stopped and needed to be restarted two days ago. Fearing a problem, I added the script yesterday that I put in my original email which checks every hour to ensure that the sch
Author: Justin Bleistein <justin.bleistein AT SUNGARD DOT COM>
Date: Tue, 26 Feb 2002 13:36:02 -0500
Just use "respawn" in init, that's what we did to correct this problem. --Justin Richard Bleistein George Lesho George Lesho <GLesho@AFCE. To: ADSM-L AT VM.MARIST DOT EDU COM> cc: Sent by: Subject: R
Author: Guenther Bergmann <g.bergmann AT PRINTCOM.DEUTSCHEPOST DOT DE>
Date: Wed, 27 Feb 2002 10:36:15 +0100
Hi George, did you check the dsmerror.log? We also run TSM Client 4.1.3 on AIX 4.3.3. We experience core dumps, caused by SIGNAL 11 every once in a while. So the scheduler has to be restarted. A PMR
Author: David Longo [mailto:David.Longo AT HEALTH-FIRST DOT ORG]
Date: Sun, 04 Oct 2015 17:12:14 -0500
Look in your dsmsched.log and dsmerror.log on this client and see if there are any messages indicating problem. I have one AIX client that occaisionally has a memory problem and that shows up in logs