Difference: WmsxReference (9 vs. 10)

Revision 102008-04-07 - AndrasLaszlo

Line: 1 to 1
 
META TOPICPARENT name="WmsxSoftware"

WMSX

Line: 97 to 97
  In most times it is useful to have pre-execution and post-execution scripts. These may be used for e.g. preparing the input data files, or archiving output data files etc. If present, these have to be called COMMAND_preexec and COMMAND_postexec. They must be executable. They will be run directly before submission and after job output is retrieved, respectively.
Changed:
<
<
COMMAND_preexec, if present, is automatically called by the framework with the AbsCOMMAND as first argument, and with all the given arguments from ArgList as following arguments.
>
>
COMMAND_preexec, if present, is automatically called by the framework with the AbsCOMMAND as first argument, the name of the job output directory as second argument (automatically generated by the framework), and with all the given arguments from ArgList as following arguments.
  COMMAND_postexec, if present, is automatically called by the framework with the AbsCOMMAND as first argument, the name of the job output directory as second argument (automatically generated by the framework), and with all the given arguments from ArgList as following arguments.
Changed:
<
<
The retrieved outputs of your job will always be in the tarball out.tar.gz under the job output directory.
>
>
The retrieved outputs of your job will always be in the tarball out.tar.gz under the generated job output directory.
  If COMMAND_postexec returns with 0 nothing further happens. If returns with 1, the script COMMAND_chain is called, if present, which can be used to launch further jobs.
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback