Starting and stopping the client service can sometimes help to resolve client scheduling problems.
dsmcutil query /name:"TSM Client Scheduler" /computer:ntserv1.ibm.com
Issue
the following queries to restart a scheduler service that is missing
schedules:dsmcutil stop /name:"TSM Client Scheduler" /computer:ntserv1.ibm.com
dsmcutil start /name:"TSM Client Scheduler" /computer:ntserv1.ibm.com
Therefore,
if you use the client acceptor daemon (CAD) to manage the scheduler,
you might have to restart the CAD service or stop the scheduler service
and restart the CAD service with the following queries:dsmcutil query /name:"TSM Client Scheduler" /computer:ntserv1.ibm.com
dsmcutil query /name:"TSM Client Acceptor" /computer:ntserv1.ibm.com
dsmcutil stop /name:"TSM Client Scheduler" /computer:ntserv1.ibm.com
dsmcutil stop /name:"TSM Client Acceptor" /computer:ntserv1.ibm.com
dsmcutil start /name:"TSM Client Acceptor" /computer:ntserv1.ibm.com
#!/bin/ksh
# Use the following script to kill the currently running instance
# of the TSM scheduler, and restart the scheduler in nohup mode.
#
# This script will not work properly if more than one scheduler
# process is running.
# If necessary, the following variables can be customized to allow an
# alternate options file to be used.
# export DSM_DIR=
# export DSM_CONFIG=
# export PATH=$PATH:$DSM_DIR
# Extract the PID for the running TSM Scheduler
PID=$(ps -ef | grep "dsmc sched" | grep -v "grep" | awk {'print $2'});
print "Original TSM scheduler process using PID=$PID"
# Kill the scheduler
kill -9 $PID
# Restart the scheduler with nohup, redirecting all output to NULL
# Output will still be logged in the dsmsched.log
nohup dsmc sched 2>&1 > /dev/null &
# Extract the PID for the running TSM Scheduler
PID=$(ps -ef | grep "dsmc sched" | grep -v "grep" | awk {'print $2'});
print "New TSM scheduler process using PID=$PID"
For AIX, HP-UX, Linux, and Solaris, if you want to use the CAD managed method to manage the client scheduler, set the managedservices option to schedule or schedule webclient in the dsm.sys file. For Mac OS X, if you do not specify the managedservices option, the CAD manages both the scheduler and the web client, by default.
tsm::once:/usr/bin/dsmcad > /dev/null 2>&1 # TSM Client
Acceptor Daemon
# service dsmcad start
# service dsmcad stop
# service dsmcad restart
# service dsmcad statis
To enable the CAD to start automatically after a system
restart, add the service as follows, at a shell prompt:# chkconfig --add dsmcad
/bin/launchctl load -w com.ibm.tivoli.dsmcad
To
stop the CAD, issue the following command in the Terminal window:/bin/launchctl unload -w com.ibm.tivoli.dsmcad
You
can also control the CAD with the TSM Tools for Administrators application.