208 - Wie kann ich sicherstellen, dass der Scheduler immer läuft?

Under Unix, the scheduler can be started directly during the boot process. This requires an ISP Scheduler service.
The service is started with /path/to/dsmc sched > /dev/null 2>&1. Example:

/opt/tivoli/tsm/client/ba/bin/dsmc sched >/dev/null 2>&1

How you call this command at system startup depends on your Linux distribution.
The most common ways are:

  • Creating an rc script
  • Add the entry TSM::once:/path/to/dsmc sched > /dev/null 2>&1 to the file /etc/inittab

Start the SP scheduler under Mac OS:

  • Open the IBM Spectrum Protect folder
  • Start ISP Tools for Administrators
  • Then select Start Client Acceptor Daemon 
    After you have selected OK, you will be asked for your local administrative password.
    If you have authenticated yourself correctly, the scheduler will be started and you will receive a corresponding confirmation.
  • The ISP Scheduler will create two log files in the /Library/Logs/tivoli/tsm/ folder: dsmsched.log (stdout) and dsmerror.log (stderr)

Windows:

Under Windows, the corresponding service is configured so that it is started automatically when the computer is rebooted.

Scientific Linux 

Scientific Linux is not fully supported by ISP, so this FAQ is based on SuSE Linux. The Linux distributions differ in many details, including how the scripts are controlled when the computer is started. For example, under Scientific Linux, adding the entry in the /etc/inittab file as described above has no effect.
ADDING OTHER CONFIGURATION HERE WILL HAVE NO EFFECT ON YOUR SYSTEM is also visible in this file. 

The following example of a dsmsched-init script can be helpful to start the ISP scheduler:

#!/bin/sh
### BEGIN INIT INFO
# Provides: dsmcsched
# Required-Start: $network $remote_fs
# Required-Stop: $network
# Default-Start: 3 5
# Default-Stop: 3 5
# Description: Start ADSM/SP scheduler.
### END INIT INFO
PATH=/bin:/usr/bin:/usr/local/bin:/usr/local/adsm:$PATH
DSM_LOG=/tmp
export DSM_LOG
export LANG=de_DE
return=$rc_done
OPTS="--schedlog=/tmp/dsmsched.log --errorlog=/tmp/dsmsched.err"
case "$1" in
stop )
echo -n "Stopping ADSM scheduler now! ..."
rc.dsmc stop -server=local 1>/dev/null 2>>/tmp/dsmcsched.err
echo -e "$return"
;;
start )
echo -n "Starting ADSM in 5 sec"
for i in 1 2 3 4 5; do
echo -n "."
sleep 1
done
echo -n " Please wait ..."
rc.dsmc start $OPTS -server=local 1>/dev/null \
2>>/tmp/dsmcsched.err &
echo -e "$return"
;;
* )
echo $0: unknown command: $1 >&2
;;
esac

This script should be placed in the /etc/init.d folder and made executable.
Under SuSE Linux you can then execute the command insserv dsmsched. This command will include dsmsched in the init procedure.

With RedHat offshoots, which also include Scientific Linux, the entry for dsmsched should be made in the /etc/rc.local file or the soft links in the /etc/init.d/rc3.d and /etc/init.d/rc5.d folders should be created manually, which point to the /etc/init.d/dsmsched script.

The script shown above is an example. The values set for the variables PATH, DSM_LOG and LANG should be set differently on your system if necessary.