vtk_output

Usage:         
vtk_output_declare transId placeId  [flags]

Description:   

Without flags, declare an output with force, meaning that output conflicts are resolved with force. 
The flags can be: 
                
* shared, if the output is shared among many {jobs;} all jobs must declare the output as shared; 
* force, if output conflicts are to be ignored (this is the default); 
* noforce, if output conflicts are to generate an error;
* stop_barrier, if the output has a barrier, and the barrier is effective to stop insignificant changes; 
* propagate_barrier, if the output has a barrier, and the barrier allows changes to propagate to the output; 
* ignore_timestamp, if the timestamp of the output is not related to the job execution time 
* optional, if the output may not exist, in which case the dependency is dropped upon completion of the job. 
* sticky, if the output has to remain attached to the transititon even if the dependency cease. 
* fileready, used by a running job to indicate that the output is available for processing by its downcone. 
  In other words, there will be no further changes to this output even though the job is still running. 
* log, the output is one of the main logs of the job 
* normal, an option with no effect 
                
Examples:
vtk_output_declare 12345 4567 
vtk_output_declare 12345 4567 -ignore_timestamp

Usage:         
vtk_output_declare_ex transId placeName  [flags]

Description:   
An alternative to vtk_output_declare, which uses 2 VovIds, while this uses the name of the output.
Without flags, declare an output with force, meaning that output conflicts are resolved with force. 
The flags can be: 
* shared, if the output is shared among many jobs; all jobs must declare the output as shared; 
* force, if output conflicts are to be ignored (this is the {default); 
* noforce, if output conflicts are to generate an error; 
* stop_barrier, if the output has a barrier, and the barrier is effective to stop insignificant changes; 
* propagate_barrier, if the output has a barrier, and the barrier allows changes to propagate to the output; 
* ignore_timestamp, if the timestamp of the output is not related to the job execution time 
* optional, if the output may not exist, in which case the dependency is dropped upon completion of the job. 
* sticky, if the output has to remain attached to the transititon even if the dependency cease. 
* log, the output is one of the main logs of the job 
* nocheck, avoid checking the file on the server side 
* normal, resets all previous options 
* db DB 
  
Examples:
vtk_output_declare_ex 12345 output.log
vtk_output_declare_ex 12345 output.log  -ignore_timestamp