Job environment overview

On each workstation, jobs are launched by the batchman production control process. The batchman process resolves all job dependencies to ensure the correct order of job processing, and then queues a job launch message to the jobman process.

Each of the processes launched by jobman, including the configuration scripts and the jobs, retains the user name recorded with the logon of the job. Submitted jobs (jobs, files, or commands submitted not through a scheduled plan, but manually by a user) retain the submitting user's name.

The jobman process starts a job monitor process that begins by setting a group of environment variables, and then runs a standard configuration script named TWS_home/jobmanrc which can be customized. The jobmanrc script sets variables that are used to configure locally on the workstation the way jobs are launched, regardless of the user.

On UNIX® workstations, if the user is allowed to use a local configuration script, and the script USER_HOME/.jobmanrc exists, the local configuration script .jobmanrc is also run. The job is then run either by the standard configuration script, or by the local one. The results of job processing are reported to jobman which, in turn, updates the Mailbox.msg file with the information on job completion status. To have jobs run with the user's environment, add the following instruction in the local configuration script:
. $USER_home/.profile
Note: Before adding the .profile in the .jobmanrc file, make sure that it does not contain any stty setting or any step that requires user manual intervention. In case it does, add in the .jobmanrc file only the necessary steps contained in the .profile.

On Windows workstations the local configuration script djobmanrc.cmd is run if it exists in the user's Documents and Settings directory which is represented by the environment variable %USERPROFILE% and depends on the Windows language installation. The djobmanrc.cmd script will be ran by jobmanrc.cmd script.