HP Scheduling jobs, Configuration guidelines, Job configuration approaches

Scheduling jobs

You can schedule a job to automatically run a command or a set of commands without administrative interference. The commands in a job are polled every minute. When the scheduled time for a command is reached, the job automatically executes the command. If a confirmation is required while the command is running, the system automatically inputs Y or Yes. If characters are required, the system automatically inputs a default character string, or inputs an empty character string when there is no default character string.

Job configuration approaches

You can configure jobs in a non-modular or modular approach. Use the non-modular approach for a one-time command execution and use non-modular approach for complex maintenance work.

Table 12 A comparison of non-modular and modular approaches

Comparison item	Scheduling a job in the non-modular	Scheduling a job in the modular
	approach	approach
Configuration method	Configure all elements in one command	Separate job, view, and time settings
Can multiple jobs be	No	Yes
configured?
Can a job have multiple	No	Yes
commands?
Supported views	User view (represented by shell), system	All views (monitor represents user
	view	view)
Supported commands	Commands in user view and system view	Commands in any view
Can a job be repeatedly	No	Yes
executed?
Can a job be saved to the	No	Yes
configuration file?

Configuration guidelines

•To have a job successfully run a command, check that the specified view and command are valid. The system does not verify their validity.

•The configuration interface, view, and user status that you have before job execution restores even if the job has run a command that changes the user interface (for example, telnet, ftp, and ssh2), the view (for example, system-view and quit), or the user status (for example, super).

•The jobs run in the background without displaying any messages except log, trap and debugging messages.

•In the modular approach:

{Every job can have only one view and up to 10 commands. If you specify multiple views, the one specified the last takes effect.

{Input a view name in its complete form. Most commonly used view names include monitor for user view, system for system view, and Vlan-interfacex for VLAN interface view.

{The time ID (time-id) must be unique in a job. If two time and command bindings have the same time ID, the one configured last takes effect.

133