Customizing job processing on a UNIX workstation - jobmanrc

About this task

A standard configuration script template named TWS_home/config/jobmanrc is supplied with HCL Workload Automation. It is installed automatically as TWS_home/jobmanrc. This script can be used by the system administrator to set the required environment before each job is run. To alter the script, make your modifications in the working copy (TWS_home/jobmanrc), leaving the template file unchanged. The file contains variables which can be configured, and comments to help you understand the methodology. Variables defined by default in the jobmanrc file describes the jobmanrc variables.

Table 1. Variables defined by default in the jobmanrc file
Variable Name	Value
UNISON_JCL	The path name of the job's script file.
UNISON_STDLIST	The path name of the job's standard list file.
UNISON_EXIT	yes \| no If set to yes, the job ends immediately if any command returns a nonzero exit code. If set to no, the job continues to run if a command returns a nonzero exit code. Any other setting is interpreted as no.
LOCAL_RC_OK	yes \| no If set to yes, the user's local configuration script is run (if it exists), passing $UNISON_JCL as the first argument. The user might be allowed or denied this option. See Customizing job processing for a user on UNIX workstations - .jobmanrc for more information. If set to no, the presence of a local configuration script is ignored, and $UNISON_JCL is run. Any other setting is interpreted as no.
MAIL_ON_ABEND	yes \| no For UNIX® operating systems: If set to yes, a message is mailed to the login user's mailbox if the job ends with a non zero exit code. This can also be set to one or more user names, separated by spaces so that a message is mailed to each user. For example, "root mis sam mary". If set to no, no messages are mailed if the job abends. Abend messages have the following format: `cpu#sched.job` `jcl-file failed with exit-code` `Please review standard-list-filename` You can change the wording of the message or translate the message into another language. For an explanation of how to do this, see Customizing the MAIL_ON_ABEND section of jobmanrc.
SHELL_TYPE	standard \| user \| script If set to standard, the first line of the JCL file is read to determine which shell to use to run the job. If the first line does not start with #!, then `/bin/sh` is used to run the local configuration script or $UNISON_JCL. Commands are echoed to the job's standard list file. If set to user, the local configuration script or $UNISON_JCL is run by the user's login shell ($UNISON_SHELL). Commands are echoed to the job's standard list file. If set to script, the local configuration script or $UNISON_JCL is run directly, and commands are not echoed unless the local configuration script or $UNISON_JCL contains a set -x command. Any other setting is interpreted as standard.
USE_EXEC	yes \| no If set to yes, the job, or the user's local configuration script is run using the exec command, thus eliminating an extra process. This option is overridden if MAIL_ON_ABEND is also set to yes. Any other setting is interpreted as no, in which case the job or local configuration script is run by another shell process.