Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Anchors added

...

Code Block
 [date: date format ]  
 
 '''date format''' must be a valid Java data format string, e.g. '''yyyyMMddHHmmss''' , '''yyyy-MM-dd.HHmmss''' etc. 
 

An example:

Code Block
 <param name="file" value="sample/hello[date:yyyyMMdd].txt" />  
 

On 2050-12-31 the parameter file contains the value "sample/hello20501231.txt" .
This parameter supports substitution of job parameter names with their value if the job parameter name is enclosed by %  and  % .
An example: <param name="file" value"%scheduler_file_path%" />
During the job runtime the parameter file contains the value of the job parameter scheduler_file_path . Using Directory Monitoring with File Orders the job parameter scheduler_file_path contains automatically the path of the file that triggered the order.
Data-Type : SOSOptionString
The default value for this parameter is ..
This parameter is mandatory.

Anchor
file_spec
file_spec
Parameter file_spec: Regular Expression for filename filtering

...

Regular Expression for filename filtering
Regular Expression for file filtering. The behaviour is CASE_INSENSITIVE.
Only effective if the parameter file is a directory.
Some remarks on regular expression, used in JobScheduler.
A regular expression is not a wildcard . To get an impression of the differences one have a look on the meaning of the wildcard .txt, which will select all filenames with the filename-extension ".txt". A regular expression to match, e.g. works the same way, this "wildcard" must look like "^.\.txt$". That looks a little bit strange but it is much more flexible and powerfull on filtering filenames than the concept of wildcards, if one want to filter more complex names or pattern.
The general syntax of an regular expression , also referred to as regex or regexp, is described here . It is different to other RegExp definitions, e.g. as for Perl.
Data-Type : SOSOptionRegExp

Anchor
gracious
gracious
Parameter gracious: Specify error message tolerance

...

Specify error message tolerance
Enables or disables error messages that are caused by an empty result-set, which is the result of an operation, executed by the job. Therefore this parameter can control the sequence of nodes or states in a job-chain.
Valid values:

...

For example, the setting "gracious=all" will suppress all errors regarding an empty result-set and will terminate a Job (standalone and inside a jobchain) as it would be without errors.
Data-Type : SOSOptionGracious
The default value for this parameter is false.

Anchor
max_file_age
max_file_age
Parameter max_file_age: Maximum age of a file

...

maximum age of a file
Specifies the maximum age of a file. If a file is older, then it is deemed not to exist, it will be not included in the result list.
Data-Type : SOSOptionTime
The default value for this parameter is 0.

Anchor
min_file_age
min_file_age
Parameter min_file_age: Minimum age of a file

...

minimum age of a file

Specifies the minimum age of a files. If the file(s) is newer then it is classified as non-existing, it will be not included in the result list.
Data-Type : SOSOptionTime
The default value for this parameter is 0.

Anchor
max_file_size
max_file_size
Parameter max_file_size: Maximum size of a file

...

maximum size of a file

Specifies the maximum size of a file in bytes: should the size of one of the files exceed this value, then it is classified as non-existing.
valid values for file size are

...

Data-Type : SOSOptionFileSize
The default value for this parameter is -1.

Anchor
min_file_size
min_file_size
Parameter min_file_size: Minimum size of one or multiple files

...

minimum size of one or multiple files
Specifies the minimum size of one or multiple files in bytes: should the size of one of the files fall below this value, then it is not included in the result list of the operation.
valid values for file size are

...

Data-Type : SOSOptionFileSize
The default value for this parameter is -1.

Anchor
skip_first_files
skip_first_files
Parameter skip_first_files: Number of files to remove from the top of the result-set

...

number of files to remove from the top of the result-set
The number of files are removed from the beginning of the set resulting by min_file_size , min_file_age etc. These files are excluded from further operations.
The result set is sorted according to the used filter parameters:

...

Only either skip_first_files or skip_last_files is allowed to be set at the same time.
Data-Type : SOSOptionInteger
The default value for this parameter is 0.

Anchor
skip_last_files
skip_last_files
Parameter skip_last_files: Number of files to remove from the bottom of the result-set

...

Number of files to remove from the bottom of the result-set

...

Only either skip_first_files or skip_last_files is allowed to be set at one time.
Data-Type : SOSOptionInteger
The default value for this parameter is 0.

Anchor
count_files
count_files
Parameter count_files: Return the size of resultset

...

Return the size of resultset
If this parameter is set true " true " the number of matches is returned in the order parameter " scheduler_SOSFileOperations_file_count ".
Valid values: true, 1, on, yes, y, ja, j and false, 0, off, no, n, nein
This parameter is valid and available for order driven jobs only. JobChains, for example, are order driven jobs. In standalone jobs this parameter will be ignored without further notice.
Data-Type : SOSOptionBoolean
The default value for this parameter is false.

Anchor
create_order
create_order
Parameter create_order: Activate file-order creation

...

Activate file-order creation
With this parameter it is possible to specify, that for all filenames in the resultlist or for the first file only (see create_orders_for_all_files ) a file-order has to be created and launched.
Valid values: true, 1, on, yes, y, ja, j and false, 0, off, no, n, nein
Data-Type : SOSOptionBoolean
The default value for this parameter is false.
Use together with parameter:
create_orders_for_all_files - Create a file-order for every file in the result-listorder_jobchain_name - next_state -

Anchor
create_orders_for_all_files
create_orders_for_all_files
Parameter create_orders_for_all_files: Create a file-order for every file in the result-list

...

Create a file-order for every file in the result-list
Valid values: true, 1, on, yes, y, ja, j and false, 0, off, no, n, nein
Data-Type : SOSOptionBoolean
The default value for this parameter is false.
Use together with parameter:
create_order - Activate file-order creationorder_jobchain_name - next_state -

...

Anchor
create_orders_for_new_files

...

create_orders_for_new_files
Parameter create_orders_for_new_files: Create a file-order for every new file in the result-list

...

Create a file-order for every new file in the result-list

...

DataType: SOSOptionBoolean

Default: false 

Anchor
param_name_file_path
param_name_file_path
Parameter param_name_file_path:

...

 

This parameter sets the name of the parameter that contains the name of of the transferred file. The default value is scheduler_file_path. The name should be changed from the default if it is not desired to create file_orders that have to handle a file sink.

DataType: SOSOptionString

Default: --- 

Anchor
order_jobchain_name
order_jobchain_name
Parameter order_jobchain_name: The name of the jobchain which belongs to the order

...

The name of the jobchain which belongs to the order
The name of the job chain which has to be launched by the order is the value of this parameter.
One must take into account, that the name of the jobchain must contain a subfolder structure if the jobchain is not in the folder "live". An example: the jobchain "Test" is located in "live/sample/FileOperations/". The value which has to be specfied is then "/sample/FileOperations/Test".
Data-Type : SOSOptionString
Use together with parameter:
create_order - Activate file-order creationnext_state -

Anchor
next_state
next_state
Parameter next_state: The first node to execute in a jobchain

...

The first node to execute in a jobchain
The name of the node of a jobchain, with which the execution of the chain must be started, is the value of this parameter.
Data-Type : SOSOptionJobChainNode
Use together with parameter:
create_order - Activate file-order creationorder_jobchain_name -

Anchor
merge_order_parameter
merge_order_parameter
Parameter merge_order_parameter: Merge actual order parameter into new created order  

...

merge actual order parameter into new created order  
 

...

DataType: SOSOptionBoolean
Default: false 

Anchor
on_empty_result_set
on_empty_result_set
Parameter on_empty_result_set: Set next node on empty result set

...

Set next node on empty result set
The next Node (Step, Job) to execute in a JobChain can be set with this parameter. The value of the parameter is a (valid) node-name of the current JobChain. In case of an empty result-set, e.g. due to non existent files, the current job will end without an errors and the JobChain will continue with the name of the node which is given as the value of this parameter.
Data-Type : SOSOptionJobChainNode
The default value for this parameter is empty.

Anchor
expected_size_of_result_set
expected_size_of_result_set
Parameter expected_size_of_result_set: Number of expected hits in result list

...

Number of expected hits in result-list

Data-Type : SOSOptionInteger
The default value for this parameter is 0.
Use together with parameter:
raise_error_if_result_set_is - raise error on expected size of result-set

Anchor
raise_error_if_result_set_is
raise_error_if_result_set_is
Parameter raise_error_if_result_set_is: Raise error on expected size of result set

...

Raise error on expected size of result-set
With this parameter it is possible to raise an error if the quantity of hits of the result list is according to the value of this parameter.
An example:
Assuming, that the parameter "raise_error_if_result_set_is=ne" is defined and the parameter "expected_size_of_result_set=1" is specified as well. If the number of hits is not equal to "1" an error will raised.

Data-Type : SOSOptionRelOp
The default value for this parameter is 0.
Use together with parameter:
expected_size_of_result_set - number of expected hits in result-list

...

Anchor
result_list_file

...

result_list_file
Parameter result_list_file: Name of the result list file

...

Name of the result-list file
If the value of this parameter specifies a valid filename the result-list will be written to this file.
Data-Type : SOSOptionFileName
The default value for this parameter is empty.

Anchor
check_steady_state_of_files
check_steady_state_of_files
Parameter check_steady_state_of_files: Check the completeness of a file (steady state)

...

Check the completeness of a file (steady state) 

...

DataType: SOSOptionBoolean

Default: false

Anchor
steady_state_count
steady_state_count
Parameter steady_state_count: Maximum Number of Checkpoints

...

Maximum Number of Checkpoints 

...

DataType: SOSOptionInteger

Default: 30

Anchor
check_steady_state_interval
check_steady_state_interval
Parameter check_steady_state_interval: Temporal distance between checkpoints

...

Temporal distance between checkpoints 

...

Alias: Steady_State_Interval

Default: 1

 

Return Parameters from JobSchedulerExistsFile

...

Name

Title

Mandatory

Default

scheduler_file_path

File to process for a file-order

false

empty

scheduler_file_parent

Pathname of the file to process for a file-order

false

empty

scheduler_file_name

Name of the file to process for a file-order

false

empty

scheduler_sosfileoperations_resultset

The result of the operation as a list of items

false

empty

scheduler_sosfileoperations_resultsetsize

The amount of hits in the result set of the operation

false

empty

scheduler_sosfileoperations_file_count

Return the size of the result set after a file operation

false

0

 

...

Anchor
scheduler_file_path

...

scheduler_file_path
Parameter scheduler_file_path: File to process for a file-order

...

file to process for a file-order
Using Directory Monitoring with File Orders the job parameter scheduler_file_path contains automatically the path of the file that triggered the order.
Data-Type : SOSOptionFileName
The default value for this parameter is empty.

Anchor
scheduler_file_parent
scheduler_file_parent
Parameter scheduler_file_parent:

...

Pathname of the file to process for a file-order

...

Pathanme Pathname of the file to process for a file-order

Data-Type : SOSOptionFileName
The default value for this parameter is empty.

Anchor
scheduler_file_name
scheduler_file_name
Parameter scheduler_file_name: Name of the file to process for a file-order

...

Name of the file to process for a file-order

Data-Type : SOSOptionFileName
The default value for this parameter is empty.

Anchor
scheduler_sosfileoperations_resultset
scheduler_sosfileoperations_resultset
Parameter scheduler_sosfileoperations_resultset: The result of the operation as a list of items

...

The result of the operation as a list of items

Data-Type : SOSOptionstring
The default value for this parameter is empty.
Use together with parameter:
scheduler_sosfileoperations_Resultsetsize - scheduler_sosfileoperations_file_count -

Anchor
scheduler_sosfileoperations_resultsetsize
scheduler_sosfileoperations_resultsetsize
Parameter scheduler_sosfileoperations_resultsetsize: The amount of hits in the result set of the operation

...

The amount of hits in the result set of the operation

Data-Type : SOSOptionsInteger
The default value for this parameter is empty.
Use together with parameter:
scheduler_sosfileoperations_ResultSet - scheduler_sosfileoperations_FileCount -

Anchor

...

scheduler_sosfileoperations_file_count

...

...

scheduler_sosfileoperations_

...

file_count
Parameter scheduler_sosfileoperations_file_count: Return the size of the result set after a file operation

...

Return the size of the result set after a file operation

Data-Type : SOSOptionInteger
The default value for this parameter is 0.
Use together with parameter:
scheduler_sosfileoperations_Resultsetsize - scheduler_sosfileoperations_ResultSet -