gschedwi Manual V0.1.0

The job is planned to run but its start time or other constraints are not yet satisfied.

For a job it means that the associated command is running. For a jobset, it means that all its constraints are satisfied (start time, links, ...) Its jobs can the be started.

The job is successfully completed. For a jobset, all its jobs are completed.

The associated job command has failed. For a jobset it means that at least one job has failed.

One of the job and jobset parameter is the calendar name. This parameter specifies on which days the job or jobset must be run. See the section called “Calendars” for more details.

This parameter specifies the start time of the job or jobset.

Links can be used to chain the execution of jobs and jobsets. A job will not start until all its links are satisfied. Four types of links exist and they specify at which state the linked job must be for the current job to start. For instance the Complete link specifies that the linked job must be completed for the current job to start.

The start of a job can be triggered by the presence (of absence) of one ore more files on remote host.

Specifies if this job or jobset must be taken into account by the Schedwi server engine. If this button is not checked then the job will be ignored by the engine. For a jobset, all its children will be ignored too, even if they are enabled. This mechanism may be useful to prepare a job or a complete jobset hierarchy in advance and to enable it at a specific date.

Name of the job or jobset.

This is the remote agent host name for this job. The remote agent must have been defined first through the Tools->Hostswindow. For a jobset, this host name will be used as a default for its children.

This parameter defines the date at which the job or jobset must run. The calendar must have been defined first through the Tools->Calendarswindow.

This defines the start hour and minute of the job or jobset.

This parameter is the number of minutes for the job or jobset to start after its start time. Past this limit, the job or jobset will be failed. The start delay may be caused by other constraints (a missing constraint file for instance), or by external issues (a network outage between the server and the agent for instance).

0 means no limit.

This is the maximum allowed running duration of the job or jobset (in minutes). Past this limit, the job or jobset will be failed.

0 means no limit.

Free text area to provide a comment or description for the job or jobset.

Command (with its path) to run on the remote agent. Variables defined in environments can be used ($APPLI_HOME/bin/launch for instance). If this field is empty, no command will be run and the job will be immediately completed.

Remote user name to use to run the command.

This is the remote file path which will be used for the output (i.e. stdout) of the command. If the file exists at run time, the command output will be concatenated to the file.

Variables defined in environments can be used.

Empty means no output file.

This is the remote file path which will be used for the error output (i.e. stderr) of the command. If the file exists at run time, the command error output will be concatenated to the file.

Variables defined in environments can be used.

Empty means no error file.

This is the command return code above which the job is failed. If the command return code is equal or lower than this parameter value, the job is declared successfully completed.

This is the list of parameters to pass to the command. Variables defined in environments can be used.

The buttons bellow the list can be used to create a new parameter, to delete the selected one, or to move the selected parameter up or down.

When the option is checked, the user environment on the remote host will be loaded before starting the job. For example, on Unix systems, the .profile, .bashrc or .cshrc files will be loaded. You must ensure that no interactive commands are used in those scripts as nobody will be able to enter a reply.

If this option is checked, only the parent jobset (and its parents up to the Root jobset) environments will be loaded. If not checked you will be able to enter new environments in the list.

This list specifies additional environments to load. A special case is when this list is empty. In this case no environments will be loaded even the ones from the parent jobset.

Note however than the associated remote host environments are always loaded (see the section called “Environment tab”).

The button at the bottom of the list can be used to add, remove or move environments in the list. The order of the environments matters as the last value of a variable defined several times will be used.

Use this button to modify parameters for the selected host.

This button can be used to define a new remote agent.

This button is used to list all the objects associated with the selected remote agent. This is useful as a remote agent cannot be deleted from the list if objects are still associated with it (a job for instance).

Delete the selected remote agent from the list. You cannot remove an agent if some objects are still associated with it. You can use the Host References button to get the list of associated objects.

Refresh the list.

Use this button to change the parameters of the selected calendar.

Create a new calendar or a new folder.

This button can be used to get all the jobs and jobsets using the selected calendar or folder. This is useful as a calendar cannot be deleted from the list if a job or a jobset is still associated with it.

Cut the selected calendar or folder. The cut object can then be paste somewhere else by using the Paste button.

Copy the selected calendar or folder to the clipboard. The copied object can then be pasted.

Paste the previously cut or copied object in the currently selected folder (or the folder of the currently selected calendar).

Delete the selected calendar or folder. If a folder is selected, all the calendars and sub-folders in it are also deleted. You cannot delete calendars if they are used by a job or a jobset.

You can use this button to refresh the list.

Use this button to modify parameters for the selected environment group.

This button can be used to create a new environment group.

This button is used to list all the objects associated with the selected environment group. This is useful as a group cannot be deleted from the list if objects are still associated with it (a job for instance).

Delete the selected Environment group from the list. You cannot remove a group if some objects are still associated with it. You can use the Environment group References button to get the list of associated objects.

Refresh the list.

Host name or IP address of the MySQL server. The provided name must be resolvable through the DNS, NIS or /etc/hosts.

MySQL database name to use.

MySQL user name.

Port number of the MySQL database. This port will only be used if the database server is not on same server as gschedwi (i.e. if the server is not localhost). The socket mechanism is used otherwise (see Socket Name below).

Socket path used to access the MySQL database. This parameter is only used if the database is on the same server as gschedwi.

Revert the database parameters to the previous ones.

Test the parameters by running a database connection test. This test will ask a password for the provided user name.

Defines the color of the grid.

You can fix cell size of the grid.

You can choose to use the default theme font or a customize one, including its size.