Difference: WmsxReference (14 vs. 15)

Revision 152009-07-10 - AndrasLaszlo

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

WMSX

Line: 39 to 39
 
-rememberafs
Will ask for your AFS password and renew AFS tokens until provider is running. It only works if you do not quit the interactive terminal (when you quit interactive session, AFS automatically deletes your tokens).
-forgetafs
Forget the AFS password.
-vo yourvo
Set the VO for all future job submissions to yourvo.
Changed:
<
<
-remembergrid
Will ask for your Grid password and renew the Grid tokens until there are no more managed jobs. If your grid key files (userkey.pem and usercert.pem, typically located under ~/.globus) are located on AFS space, you should use -rememberafs, and should not quit the interactive terminal. If this is not feasible, copy the .globus directory to some local disk space, and point the environmental variables X509_USER_CER and X509_USER_KEY to the absolute path of usercert.pem and userkey.pem, respectively, and also copy your ~/.glite directory to some local disk space, and point the environmental variable GLITE_USER_HOME to the absolute path of that directory.
>
>
-remembergrid
Will ask for your Grid password and renew the Grid tokens until there are no more managed jobs. If your grid key files (userkey.pem and usercert.pem, typically located under ~/.globus) are located on AFS space, you should use -rememberafs, and should not quit the interactive terminal. If this is not feasible, copy the .globus directory to some local disk space, and point the environmental variables X509_USER_CER, X509_USER_KEY and X509_CERT_DIR to the absolute path of usercert.pem, userkey.pem files and certificates directory, respectively, and also copy your ~/.glite directory to some local disk space, and point the environmental variable GLITE_USER_HOME to the absolute path of that directory.
  The possible job submission procedures are described in the next sections.
Line: 117 to 117
 If the COMMAND_postexec script returns 1, the script COMMAND_chain is invoked (must be executable). In this case, if present, it is automatically called by the framework with the AbsCOMMAND as first argument, the name of the job output directory as second argument, and with all the given arguments from ArgList as following arguments.

The output of COMMAND_chain is interpreted by the framework as ArgList lines, just as if they were lines from the initial ArgList file. Therefore, it can be used to lauch further jobs by a finished job, depending on the decision of the COMMAND_postexec script. This is called the job chaining. (The COMMAND_chain may have multiple lines as output. Each line is interpreted like a line from the ArgList file, so multiple jobs may also be lauched: the job chain may also fork.) \ No newline at end of file

Added:
>
>

The backend concept

The backend is the system which is actually taking care about your job submission. This section needs expansion...

Graphical User Interface

A simple graphical interface is written to help job flow monitoring. Start with:

wmsx-gui.sh

-- AndrasLaszlo - 10 Jul 2009

 
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