The schedule command starts the client scheduler on your workstation. The client scheduler must be running before scheduled work can start.
Authorized
User: The schedule command starts the client
scheduler on your workstation. The client scheduler must be running
before scheduled work can start.
- The schedule command cannot be used if the managedservices option is set to schedule (does not apply to Mac OS X).
- For Mac OSX only, to use the schedule command,
specify managedservices none in the dsm.sys
file.
- This command is valid only on the initial command line. It is not valid in interactive mode or in a macro file.
If the schedmode option
is set to polling, the client scheduler contacts the server for scheduled
events at the hourly interval you specified with the queryschedperiod option
in your client options file (dsm.opt). If your administrator sets
the queryschedperiod option for all nodes, that setting
overrides the client setting.
If the schedmode option
is set to polling, the client scheduler contacts the server for scheduled
events at the hourly interval you specified with the queryschedperiod option
in your client user-options file (dsm.opt). If your administrator
sets the queryschedperiod option for all nodes, that
setting overrides the client setting.
If
you are using TCP/IP communications, the server can prompt your workstation
when it is time to run a scheduled event. To do so, set the schedmode option
to prompted in the client options file (dsm.opt)
or on the schedule command.
If you are using TCP/IP
communications, the server can prompt your workstation when it is
time to run a scheduled event. To do so, set the schedmode option
to prompted in the client user-options file
(dsm.opt) or on the schedule command.
After you start the client scheduler, it continues
to run and to start scheduled events until you press Ctrl+Break,
restart the workstation, or turn off the workstation to end it.
You can use the sessioninitiation option
with the schedule command to control whether the
server or client initiates sessions through a firewall.
After you start the
client scheduler, it continues to run and to start scheduled events
until you press Ctrl+C, stop the scheduler process with the UNIX kill command,
start the workstation again, or turn off the workstation to end it.
After you start the client scheduler, it continues
to run and to start scheduled events until you press Ctrl+C, press
the Q key twice, start the workstation again, or turn off the workstation
to end it.
Note: You cannot enter
this command in interactive mode. Supported Clients
This command is valid for all clients.
Parameters
| Option | Where to use |
|---|---|
| maxcmdretries |
Client options file (dsm.opt) or command line. |
| maxcmdretries |
Client system options file (dsm.sys) or command line. |
| password |
client options file (dsm.opt) |
| password |
client user options file (dsm.opt) |
| queryschedperiod |
Client options file (dsm.opt) or command line. |
| queryschedperiod |
Client system options file (dsm.sys) or command line. |
| retryperiod |
Client options file (dsm.opt) or command line. |
| retryperiod |
Client system options file (dsm.sys) or command line. |
| schedlogname |
Client options file (dsm.opt) or command line. |
| schedlogname |
Client system options file (dsm.sys) or command line. |
| schedmode |
Client options file (dsm.opt) or command line. |
| schedmode |
Client system options file (dsm.sys) or command line. |
| sessioninitiation |
Client options file (dsm.opt) or command line. |
| sessioninitiation |
Client system options file (dsm.sys) or command line. |
| tcpclientport |
Client options file (dsm.opt) or command line. |
| tcpclientport |
Client system options file (dsm.sys) or command line. |
Examples
- Task
- Start the client scheduler.
Command: dsmc sch –password=notell
- Task
- For AIX®: Start the scheduler
at system bootup time by entering this command in the /etc/inittab
file. Ensure the passwordaccess option
is set to generate.
Command: tsm::once:/usr/bin/dsmc sched > /dev/null 2>&1 #TSM
- Task
- Interactively start the scheduler and keep it running in the background.
Command: nohup dsmc sched 2> /dev/null &
When you run the schedule command,
all messages regarding scheduled work are sent to the dsmsched.log file
or to the file you specify with the schedlogname option
in your client options file (dsm.opt). If you do not specify a directory
path with the file name in the schedlogname option,
the dsmsched.log resides in the current working directory.
When you run the schedule command,
all messages regarding scheduled work are sent to the dsmsched.log file
or to the file you specify with the schedlogname option
in your client system-options file (dsm.sys). If you do not specify
a directory path with the file name in the schedlogname option,
the dsmsched.log resides in the current working directory,
except for Mac OS X. For Mac OS X, the dsmsched.log resides
in the /Library/Logs/tivoli/tsm/ directory.
Important: To
prevent log write failures and process termination in certain cases,
set the DSM_LOG environment variable to name a directory where default
permissions allow the required access.