HCL Workload Automation, Version 9.4

Configuration options usage

The format of the configuration file is the following:
with no blanks before the option, after the value, or before or after the equals (=) character.

You can put all the common information, such as the LJuser, IFuser, JobDef, and LogFileName options in r3batch.opts, while you can put tailored data for the target SAP system of the extended agent or dynamic agent (for example, SAP1) in a local configuration file (for example, XA1_r3batch.opts).

You can put a local option in the global configuration file if you want to give the same option to all the r3batch instances. For example, if the SAP user name is the same in all your SAP systems, you can place the r3user option in the global file without duplicating that information in all the local configuration files.

A global option, such as job_sem_proj, only has effect in the global configuration file. If you put global options in a local file they have no effect.

r3batch reads the global configuration file first and then the local file. Every option (except the global options) contained in the local configuration file will override those in the global file. For example, if both the global and the local configuration files contain the r3user option, r3batch uses the one in the local file.

There are six mandatory options that r3batch requires:
  • r3client
  • r3host
  • r3instance
  • r3password
  • r3sid
  • r3user

You can put them all in the local configuration file or you can spread them between the global and the local files. For example, you could put r3user and r3password in the global configuration file and r3sid, r3instance, r3client, and r3host in the local one.

The r3user option is both local and mandatory. It must be put either in the global configuration file or the local configuration file.

Note: These configuration files are not created during the installation process.