![]() |
![]() |
To start the client scheduler on your client node and connect to the server schedule, change to the Tivoli Storage Manager installation directory and enter the following command:
dsmc schedule
When you start the client scheduler, it runs continuously until you close the window, end the process, or log off your system.
To run the schedule command in the background and to keep the client scheduler running, even if you log off your system, enter the following:
nohup dsmc schedule 2> /dev/null &
If a Tivoli Storage Manager password is required for your workstation and you want to run the schedule command in the background, enter the password with the command.
Root User: To start the client scheduler automatically, ensure that the passwordaccess option is set to generate in your client system options file (dsm.sys), then follow the procedure below for your operating system:
tsm::once:/usr/bin/dsmc sched > /dev/null 2>&1 # TSM scheduler
cd /usr/lpp/Tivoli/tsm/client/ba/bin sleep 60 ./dsmc scheduleThis prevents the creation of two jobs with the same name and enables automatic shutdown. You may need to customize the time for your system. Refer to the user's manual for complete client scheduler instructions.
# Set environment variables to retrieve the servername and # nodename options from dsm.sys. export DSM_DIR=/tivoli/tsm/client/ba/bin export DSM_CONFIG=/tivoli/tsm/client/ba/bin/dsm.opt # Start the TSM Client scheduler and redirect outputs to # schedule.out instead of the /etc/log file. _BPX_JOBNAME='ADSMCLNT' /tivoli/tsm/client/ba/bin/rundsmc 1>/tivoli/tsm/client/ba/bin/schedule.out 2>&1 &
The client scheduler may fail to initialize properly at IPL because TCP/IP is not fully initialized. You may need to customize the time for your system to compensate for this.
Tivoli Storage Manager does not recognize changes made to the dsm.opt or the dsm.sys file while the client scheduler is running. If you make changes to these files while the client scheduler is running, and you want to use the new values immediately, stop the client scheduler and restart it. For example, if you change the inclexcl option in your dsm.sys file to point to a different include-exclude options file, you must stop the client scheduler and restart it before Tivoli Storage Manager uses the new file.
To manually stop the client scheduler, enter the kill command if it is running in the background, or press q or Ctrl+C if it is running in the foreground. To restart the client scheduler, enter the schedule command again.
Tape prompting does not occur during a scheduled event regardless of the tapeprompt option setting in your options file.
Use the Client Acceptor daemon to manage the Client Scheduler. See Managing the Client Scheduler Using the Client Acceptor Daemon for more information.