Job scheduler custom properties

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.

You can use the custom properties page to define the following job scheduler custom properties:

MaxConcurrentDispatchers

Define this custom property if jobs are being dispatched slowly when large numbers of jobs are submitted. By default, MaxConcurrentDispatchers is set to 100. MaxConcurrentDispatchers is an optional custom property.

Table 1. MaxConcurrentDispatchers custom property values. The table includes the scope, valid values, and default for the custom property.
Scope Valid values Default
Job scheduler Integer value greater than 0 100

UseHTTPSConnection

Define this custom property if you want to enable HTTP SSL connections between the job scheduler and the common batch container. By default, HTTP SSL connections are disabled. UseHTTPSConnection is an optional custom property.

Table 2. UseHTTPSConnection custom property values. The table includes the scope, valid values, and default for the custom property.
Scope Valid values Default
Job scheduler
  • true

    Enables HTTP SSL connections

  • false

    Disables HTTP SSL connections

false (disabled)

RECORD_SMF_SUBTYPES

Define this property to indicate which SMF 120 record subtype you want to use to record job usage data. By default, SMF 120 subtype 20 records are used. RECORD_SMF_SUBTYPES is an optional custom property.

Table 3. RECORD_SMF_SUBTYPES custom property values. The table includes the scope, valid values, and default for the custom property.
Scope Valid values Default
Job scheduler cell
  • 20

    Use SMF120 subtype 20 records.

  • 9
    Use SMF120 subtype 9 records.
    Avoid trouble Avoid trouble: SMF 120 subtype 9 support for batch jobs requires that SMF 120 subtype 9 recording for asynchronous beans is enabled on the endpoint server. SMF 120 subtype 9 support for asynchronous beans is available on WebSphere® Application Server Version 8.0.0.1 or later. Earlier versions are not supported. If you specify RECORD_SMF_SUBTYPES=9 on an earlier version, the job scheduler issues a message. The message indicates that SMF 120 subtype 9 records are not supported on earlier versions of WebSphere Application Server. The job scheduler reverts to SMF 120 subtype 20 records.gotcha
    Avoid trouble Avoid trouble: If you specify RECORD_SMF_SUBTYPES=9 without also enabling SMF 120 subtype 9 recording for asynchronous beans in the endpoint server, the endpoint server issues a message. The message indicates that SMF 120 subtype 9 recording for asynchronous beans is not enabled. No SMF120 subtype 9 job usage records are collected.gotcha
  • ALL

    Use both SMF120 subtype 20 and SMF120 subtype 9 records.

20

JOB_SECURITY_POLICY

Define this property to indicate whether administrative roles, groups, or a combination of the two can act on a set of jobs.

Table 4. JOB_SECURITY_POLICY custom property values. The table includes the scope, valid values, and default for the custom property.
Scope Valid values Default
Job scheduler
  • ROLE

    Specifies that the batch domain applies role-based job security. This behavior is consistent with version 6.1.1 of batch.

  • GROUP

    Specifies that the batch domain uses only group-affiliation as the basis for job security.

  • GROUPROLE

    This setting specifies that the batch domain uses group and role as the basis for job security.

ROLE

JOB_SECURITY_DEFAULT_GROUP

Define this custom property so that you can assign a user group to a job. You can use this property if either group or group and role security is active.

You can also assign a group to a job using the group attribute on the job definition in the xJCL. The group attribute takes precedence over the value on the JOB_SECURITY_DEFAULT_GROUP custom property. If you do not specify the group attribute on the job definition or this custom property, the job scheduler assigns the default group name.

Table 5. JOB_SECURITY_DEFAULT_GROUP custom property values. The table includes the scope, valid values, and default for the custom property.
Scope Valid values Default
Job scheduler A user-defined user group name JSYSDFLT

JOB_SECURITY_ADMIN_GROUP

Define this custom property so that you can assign an administrative group to each job.

Table 6. JOB_SECURITY_ADMIN_GROUP custom property values. The table includes the scope, valid values, and default for the custom property.
Scope Valid values Default
Job scheduler A user defined administrative group name JSYSADMN

UseAPCEndpointSelection

Define this property if you want to use the application placement controller for job placement. You cannot use the application placement controller for job placement on the z/OS platform. Setting this property allows the application placement controller to select the endpoint. Otherwise, the grid application placement does the selection.

Table 7. WXDBulletinBoardProviderOption custom property values. The table includes the scope, valid values, and default for the custom property.
Scope Valid values Default
Job scheduler true false

WXDBulletinBoardProviderOption

Define this property if you want to use the application placement controller for job placement. You cannot use the application placement controller for job placement on the z/OS platform. Setting this custom property with a value of HAMBB overlays the base bulletin board for Intelligent Management with the high availability manager bulletin board. Batch and Intelligent Management can then use the same bulletin board to talk to each other.

Table 8. WXDBulletinBoardProviderOption custom property values. The table includes the scope, valid values, and default for the custom property.
Scope Valid values Default
Job scheduler cell HAMBB None


Terms and conditions for information centers | Feedback

Last updated: April 17, 2014 10:32 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-express-iseries&topic=rgrid_ccgcustprop
File name: rgrid_ccgcustprop.html