In table below, the most used commands with their meaning in the submit files of a HTCondor job [26].
Arguments | List of arguments to be supplied to the executable as part of the command line. |
Error | A path and file name used by HTCondor to capture any error messages the program would normally write to the screen. When the job exits, the resulting file is transferred back to the machine where the job was submitted, and the path is utilized for file placement. More than one job should not use the same error file, since this will cause one job to overwrite the errors of another. |
Executable | An optional path and a required file name of the executable file for the job cluster. |
Log | It is used to specify a file name where HTCondor will write a log file of what is happening with the job cluster, called a job event log. For example, HTCondor will place a log entry into this file when and where the job begins running, when the job produces a checkpoint, or moves (migrates) to another machine, and when the job completes. If no log entry is specified, HTCondor does not create a log for this cluster. |
Output | The output file is written (by the job) in the remote scratch directory of the machine where the job is executed and it captures any information the program would ordinarily write to the screen (that is, this file becomes |
Queue | An integer number is required. Places zero or more copies of the job into the HTCondor queue. |
Request_cpus | A requested number of CPUs (cores). If not specified, the number requested will be 1. |
Request_disk | The requested amount of disk space in KB requested for the job. |
Request_memory | It determines the amount of required RAM in MB. |
Request_<name>=<quantity> | In general, this string represents the requirements of the job. For istance, machines that have available GPUs can define |
Should_transfer_files | This command setting is used to define if HTCondor should transfer files to and from the remote machine where the job runs. If equal to YES, this will cause HTCondor to always transfer files for the job, otherwise NO disables HTCondor’s file transfer mechanism. |
Transfer_input_files | A comma-delimited list of all the files and directories to be transferred into the working directory for the job, before the job is started. |
Transfer_output_files | This command forms an explicit list of output files and directories to be transferred back from the temporary working directory on the execute machine to the submit machine. If there are multiple files, they must be delimited with commas. |
Universe | The vanilla universe is the default (except where the configuration variable |
When_to_transfer_output | This setting command allows or does not allow HTCondor to transfer the job’s output files back to the submitting machine when the job completes. |
+<attribute>=<value> | A line that begins with a ‘+’ (plus) character instructs
Moreover, you can see the Job ClassAd Attributes here [27] for a list of HTCondor job attributes. |
PerusalFilesDestURI | The PerusalFilesDestURI attribute is a string representing the URI of the location on a gridFTP or HTTPS server (HTTPS servers are also supported but this requires to have the GridSite htcp command installed on the WN) where the chunks of files generated by the running job on the WN and specified through the attribute PerusalListFileURI have to be copied. |
PerusalListFileURI | The PerusalListFileURI attribute is a string representing the URI of the file on a gridFTP server, containing the list of files (one for each line), that must be saved and uploaded on the location specified by the attribute PerusalFilesDestURI at regular time intervals. |
PerusalTimeInterval | The PerusalTimeInterval attribute is a positive integer representing the difference in seconds between two subsequent saving (and upload on the location specified by the attribute PerusalFilesDestURI) of the job files generated by the job on the WN. |
Prologue | The Prologue attribute is a string representing the executable/script name of the prologue. The prologue is an executable run within the CREAM job wrapper before the user job is started. |
PrologueArguments | The PrologueArguments attribute is a string containing all the prologue executable command line arguments. All the rules reported in the description of the Arguments attribute also apply to the PrologueArguments attribute. |
Rank | A classad Floating Point expression showing the rank of each CE matching the Requirements expression the highest rank CE will be selected for job execution |
Requirements | It is used to perform matchmacking |
StdError | This is a string representing the file name where the standard error of the job is saved. |
StdInput | This is a string representing the standard input of the job. |
StdOutput | This is a string representing the file name where the standard output of the job is saved. |