What does the script do for you?

By defining one of the [ivru] options, the script follows different behaviors. A generalcommon part of the script does the following:

• It checks for the validity of the options you inserted
• It checks for an environment variable on the WN called VO$\_<EXP>\_$SW_DIR
• It creates (if not yet present) a subdirectory called :
  experimentNameSWnameVersionRelease_install
  This is the installation area or in general the Working Area for that version/release of experiment software.
• It copies then all scripts you sent through the input sandbox, needed in the process, into this area.

After these general actions, we differentiate among the possibilities: If you are in installation/validation/running mode on a WN (without a shared file system) option:

• It checks, using the Replica Manager, the presence on GRID of the whole set of tarball your installation needs. Otherwise it stops the process printing an error message.
• It replicates the tarballs in the SE closest to the WN whenever they are not there already present.
• It copies from the SE to the WN the tarballs.
• It calls the experiment installation script discussed above (provided by the experiment)
• It calls a validation or a running job once the software has been installed successfully.
• You will have back in the stdout and stderr files the report of all that has happened on the WN.
• Depending on your setting in the JDL file you can ask to have some additional output file (hbook file or something like). You must add in the field "OutputSandbox" the name of the file you want

If the action option is set to ``u'' it will uninstall a preexisting version of the software calling the uninstall_sw script the experiment has provided. If you need to do a run and the VO_$<EXP>$_DIR_SW is not ``.'' but an existing path in the shared file system of the Local Farm, you don't need to install again. You have simply to launch your command (a job file usually with the WildCard set properly in the file run_sw).