Defining the global options

r3batch global configuration options lists the options that can be specified only in the global configuration file r3batch.opts.
Table 1. r3batch global configuration options
Option Description Default
dep_sem_proj (Optional) The project ID for the external dependency semaphore used for handling SAP R/3 background processing events as external follows dependencies. d
icp_sem_proj (Optional) The project ID for the job interception semaphore. c
job_sem_proj (Optional) The project ID for the job semaphore. a
max_jobs_to_release_for_user Defines the maximum number of jobs released for each user each time the release job is submitted. If this option is less than or equal to 0, the option is ignored and all jobs are released when the release job is submitted. This option is present both in global and local options. If you define it in both configuration files, the local value overrides the global one. ON
primm_enable (Optional) Enables (ON) the SAP print parameter PRIMM (Print Immediately) for all jobs. OFF
prnew_enable (Optional) Enables (ON) the SAP print parameter PRNEW (New Spool Request) for all jobs. OFF
prrel_enable (Optional) Enables (ON) the SAP print parameter PRREL (Immediately delete the spool output after printing) for all jobs. OFF
prsap_enable (Optional) Enables (ON) the SAP print parameter PRSAP (Print SAP Cover Page) for all jobs. The default value is OFF. OFF
prunx_enable (Optional) Enables (ON) the SAP print parameter PRUNX (Print Operating System Cover Page) for all jobs. OFF
release_all_intercepted_jobs_for_request
Releases jobs for each user on a cyclic basis, based on the number of jobs specified in the max_jobs_to_release_for_user option. The default value is ON, which means that all jobs are submitted for each user:
  • If the max_jobs_to_release_for_user option is less than or equal to 0, all jobs are released for each user.
  • If the max_jobs_to_release_for_user option is higher than 0, the specified number of jobs is submitted for each user on a cyclic basis. For example, if max_jobs_to_release_for_user=5, the first 5 jobs are submitted for each user, then the following 5 jobs for each user, and so on, until all jobs for all users are submitted.
If this option is set to OFF, it releases for each user only the number of jobs specified in the max_jobs_to_release_for_user option. The remaining jobs are submitted only when a new release job is submitted:
  • If the max_jobs_to_release_for_user option is less than or equal to 0, all jobs are released for each user.
  • If the max_jobs_to_release_for_user option is higher than 0, only the specified number of jobs is submitted, then no other job is submitted until the new release job. If max_jobs_to_release_for_user=5, the first 5 jobs are submitted for each user, then no other job is submitted until the new release job.
This option is present both in global and local options. If you define it in both configuration files, the local value overrides the global one.		 00
var_sem_proj (Optional) The project ID for the variant semaphore. b
Note: If the max_jobs_to_release_for_user option is higher than 0, only the specified number of jobs is submitted, then no other job is submitted until the new release job. If max_jobs_to_release_for_user=5, the first 5 jobs are submitted for each user, then no other job is submitted until the new release job.

Modifying the default values of the semaphore options is particularly useful when the IDs that are generated would be the same as the IDs already used by other applications.

On UNIX and Linux, to resolve the problem of duplicated IDs, HCL Workload Automation for SAP uses system-5 semaphores to synchronize critical ABAP function module calls. It uses one semaphore for job-related tasks and another one for tasks related to variant maintenance.

To synchronize on the same semaphore, the communication partners must use the same identifier. There are several ways to choose this identifier. HCL Workload Automation for SAP uses two parameters: a path name and a project ID (which is a character value). The path name parameter is the fully qualified path to the options file. The project ID is taken from the options described in r3batch global configuration options. If these options are omitted, HCL Workload Automation for SAP uses default values, which work for most installations.
Note:
  1. The semaphore options must be edited directly in the global options file using a text editor; you cannot use the options editor to modify these values.
  2. If two semaphore options are assigned the same value, all the semaphore values are reset according to the following rule:
    job_sem_proj
    It keeps the value assigned, or its default value.
    var_sem_proj
    It is reset to the first character that, in the ASCII table, follows the value assigned to var_sem_proj.
    icp_sem_proj
    It is reset to the second character that, in the ASCII table, follows the value assigned to var_sem_proj.
    dep_sem_proj
    It is reset to the third character that, in the ASCII table, follows the value assigned to var_sem_proj.