HCL Workload Automation, Version 9.4

Option value inheritance

This property is currently available for r3batch only. Local options files can inherit existing values from the same options in the global options file r3batch.opts. For an access method, the options are listed twice; once as global options and once as local options. If the local options file does not contain a value for the option, then the value for that option in the global options file is used. Otherwise the option value in the local options file is always used.

For example, you might want to define the same value for the Ljuser option and a different value for the retrieve_joblog option. To do this, you define the Ljuser option value in the r3batch.opts file. Then you define a different value for the retrieve_joblog option in each local options file. This results in the following actions when launching the SAP R/3 job:
  • The value for the Ljuser option is extracted from the r3batch.opts file.
  • The value for the retrieve_joblog option is taken from each local options file.