Custom properties modify the job scheduler configuration. You can use these settings to tune the job scheduler behavior beyond the settings that are in the administrative console.
Define this custom property if you want to disable the application placement controller (APC). By default, the APC is enabled. You must have WebSphere® Virtual Enterprise installed along with Compute Grid to create this custom property. UseAPCEndpointSelection is an optional custom property.
Scope | Job scheduler |
---|---|
Valid values | true: Enables the application placement controller for endpoint selection. false: Disables the application placement controller for endpoint selection. |
Default | true (enabled) |
Define this custom property if jobs are being dispatched slowly when large numbers of jobs are submitted. MaxConcurrentDispatchers is an optional custom property. The default value for the property is 100.
Define this custom property to customize the time in seconds for the scheduler job class timer to wake up and do output queue cleanup processing. The output.queue.cleanup.interval property is an optional custom property. The default value for the property is 60 seconds.
MAX_JOBID is a property maintained in the JOBIDCONTROL table of the job scheduler database. Every job when submitted to Compute Grid application gets a unique job number. The job numbers are then handed out sequentially starting from 0 and ending at the specified maximum number (MAX_JOBID). The default maximum value is 99,999. After the specified maximum value is reached, the job sequence rolls over and starts counting at 0 again.
The users can increase or decrease the MAX_JOBID value according to their requirement. For example, on zOS and Solaris platforms, the ZFS file system has a restriction of allowing only 32,768 subfolders to exist in any one parent folder. Compute Grid application creates a new folder to store the logs for each job submitted. If the user wants to store the joblogs on a ZFS file system, the user might want to limit the MAX_JOBID to < 32k to avoid reaching that file system limitation.
To update the value, the customer must manually execute a SQL Statement against the job scheduler database. The SQL statement is as follows:
UPDATE LRSSCHEMA.JOBIDCONTROL SET CONTROLVALUE=32768 WHERE CONTROLNAME='MAX_JOBID';
Job scheduler servers must be recycled after changing the property value.