A productiom job with heavy CPU load and several output files requires
complex scripts and JDL files. When the script used to run the production
job in a local environment is working well, the user must add the statements
needed to run the job in a grid environment. I will not give an example here,
but the guide lines to build the required files.

Note that in general, besides the file needed by the job, the following
files are the minimal set for production submission.

a script that enables submission of several jobs with different
parameters, for example a run number

the job execution script

the JDL file

To the above file, depending on job complexity, a set of output
collecting/validating tools is highly recommended for efficient production.
A good organization of production steps avoids human errors, improves
data storage and statistcs collection.

As production jobs may require very long execution times, both in terms of
CPU and solar time, taking in account also the time needed for the transition of
the job status from scheduling to running, it is important to grant an
suitable expiration time for the user certificate. Thus the user must setup the
automatic proxy renewal using a MyProxy server and the commands:

The production script in the grid environment must take care of the
following items:

set up the GDMP and RC configuration files according to the user VO
membership; Vo variables are defined by the following statement
eval `\$EDG_LOCATION/bin/edg-vo-env --shell=sh alice`

as at present grid does not handle job logging with information about
executing node, timing etc. the script should set up identifying parameters
for better monitoring and statistcs executing at script startup statements
of the following type:

once files are saved on the SE, remove all temporary files from the
SE. Note that in our test, WN run out of local disk space due to automatic
clean up failures. One point here is also a possible failure of file
transfer to the SE so that the file is removed before the save operation is
completed

save end date for later checking and statistics:
echo "Job-end-at: `date`"
Use special strings to enable simple grep operation for monitoring messages
sent to stdout.