1. Unified scripts ● Currently they are composed of a main shell script and a few auxiliary ones that handle mostly the local differences. ● Local scripts are sourced to modify local variables eg whether to modify.bashrc or to add a modules-env module or to modify the.softenv etc. ● Later on, based on application asked, the input file may be checked for keywords

2. ● Currently only gaussian has a separate script that is sourced – would like to better incorporate this in main script for maintenability.Scheduler specific preample is created ● Scheduler submit script is created – Includes the uberftp commands at the end of the script ● Job submitted ● The jobid is sent back to the calling script by means of a "unique" keyword in the output

3. TODOs ● Radium.ncsa needs to be included in the unified scripts ● External user implementation ● Input files should be scanned further for consistency and for keywords like Gamess “Memory” etc - does it make sense to have this done on clusterscripts or client

4. ● What part of the server scripts and cluster scripts will still be used in six months when we go to web services ● (relates to server scripts too) We have the specifications.cfg and the mysql database and the "local scripts' - should we simplify/unify by only using the mysql database? Comments/Questions

5. ● Clean up of ccguser directory including scratch – For each job now there are 2 dirs – Use of local $TMPDIR at OSC (local disk space)?

6. ● Improve debugging (relates to server scripts) – Need to separate the error log of the cgi scripts to job specific error log (eg add the “$PROCESS_ID” at the end of the log file to make it specific for the job) - but then we ll need to clean up those logs ● Is it worth centralizing all the cluster-scripts by keeping them and executing them on the GMS server instead of in clusters? – Will easy modifications – One less place to look at and worry about