...
By default, Qube! will execute the job in the job owner's environment as defined on the Worker. Keep in mind that the job owner may be the user who submits the job, or the job owner may be the generic 'qubeproxy' user, depending on how your installation is configured.
In fact, what happens is that Specifically, the Worker runs setuid to the job owner's ownerID. This isn't the same as loading the user's .cshrc or .bashrc file, so variables defined in those files will not get set. You can control the job's execution environment explicitly by defining environment variables into the /etc/init.d Worker scripts (if they need to be global to the facility), or by setting them as part of the package of job commands that land on the Worker (if you just need to control the environment per job).
...