Db2 Java arguments for performance improvement

Edit online

A list of Java arguments that you can modify to improve the performance of Unified Management Server, Db2® DevOps Experience, and Db2 Administration Foundation.

Subsystem

List of Java arguments to improve the performance of subsystem registration. For more information, refer to Registering Db2 subsystems
Maximum connection for each subsystem
Determines the maximum number of connections allowed in a specific subsystem. You can configure the maxConnectionsPerSubsystem parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML).
The default value is 500.
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.db2.ConnectionRequestManager.maxConnectionsPerSubsystem=500
Maximum size for queues
Determines the maximum size allowed for queues, which includes the waiting threads for connections.
You can configure the maxSizeForQueue parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML).
The default value is 10000.
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.db2.ConnectionRequestManager.maxSizeForQueue=10000
Weight for interactive requests
Determines the weight for processing the interactive requests.
You can configure the interactiveWeight parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML).
The default value is 3.
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.db2.ConnectionRequestManager.interactiveWeight=3
Frequency for logger entries
Determines the frequency at which the logger entries are written to a log file.
You can configure the infoLoggerFrequency parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML).
The default value is 500.
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.db2.ConnectionRequestManager.infoLoggerFrequency=500
Wait time for connection request
Determines the maximum waiting times for a connection request in Unified Management Server (UMS). You can configure the connectionRequestWaitTimeSeconds parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML).
The default value is 3600 (seconds).
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.db2.ConnectionRequestManager.connectionRequestWaitTimeSeconds=3600
Clean up time
Determines the time interval after which the scheduler cleans the connection pools in the data source. You can configure the DatasourceCleanTime parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML).

The value is given in milliseconds. The default value is 14400000 (milliseconds or 4 hours). For example, 1000L*60*60*4 is 14400000 milliseconds. 

components:
  izp:
    server:
      javaArgs:
        --Dcom.com.rocketsoft.newton.db2.Db2DataSourceManager.defaultDatasourceCleanTime=14400000
Maximum idle time
Determines the maximum time (in seconds) a connection can stay idle in the pool. You can configure the defaultIdleTimeInSec parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML).
The value is given in milliseconds. The default value is 1800 (milliseconds or 30 minutes). For example, 30 * 60 is 1800 milliseconds.
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.db2.Db2DataSourceManager.defaultIdleTimeInSec=1800 (milliseconds)

DDL

List of Java arguments to improve the performance of DDL. For more information, refer to Using Db2 DevOps Experience.

String length
Determines the maximum string length allowed for a DDL during an external deployment. You can configure the maxRequestStringLength parameter by specifying a definition for the javaArgs element in PARMLIB(IZPD2IPM).
The default value is 20000000.
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.platform.config.SpringConfig.maxRequestStringLength=20000000

Worklist

List of Java arguments for generating a unique name for the worklist when submitting the JCL jobs.
Minimum pause time
Determines the minimum sleep time (in milliseconds) for checking the job status. The environment pauses for this duration before polling z/OSMF to check the job status.
The default value is 200 (milliseconds).
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.db2.Db2JobManager.sleepTimeMinInMillis=200
Maximum pause time
Determines the maximum sleep time (in milliseconds) for checking the job status. This limits the exponential backoff to prevent long waits.
The default value is 2000 (milliseconds).
components:
  izp:
    server:
      javaArgs:
        –-Dcom.rocketsoft.newton.db2.Db2JobManager.sleepTimeMaxInMillis=2000
Maximum retry count
Determines the maximum number of retry an application can make to retrieve the status or details of a completed job from z/OSMF after encountering a retrieval error during the initial attempt.
The default value is 1.
components:
  izp:
    server:
      javaArgs:
        -–Dcom.rocketsoft.zos.zosmf.request.jobRetrievalRetryCount=1
Query in worklist generation
Enables or disables a new logic for generating a unique worklist name.
  • If you want to disable a new logic, set the disableQueryInWorklistGeneration parameter to true.
  • If you want to enable a new logic, set the disableQueryInWorklistGeneration parameter to false.
The default value to false. 
components:
  izp:
    server:
      javaArgs:
        -–Dcom.rocketsoftware.newton.policy.utilities.disableQueryInWorklistGeneration=false
Maximum worklist records

Determines the number of records to fetch from the ADBCHKPT table to check the existence of a worklist name.

The default value is 1000.
components:
  izp:
    server:
      javaArgs:
        -–Dcom.rocketsoftware.newton.policy.utilities.fetchMaxWorklistRecords=1000
Maximum worklist retry
Defines the number of retries allowed to generate a unique worklist name.
The default value is 20.
components:
  izp:
    server:
      javaArgs:
        -–Dcom.rocketsoftware.newton.policy.utilities.maxWorklistGenRetry=20

Discovery

Control discovery
The true or false value that you provide for indexspace2index, tablespace2table, and plan2packagecollection parameters in the ZWEYAML can minimize deep discovery within the graphql implementation, which reduces zIIP usage. The default value is false.
Refer to the following example: 
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.model.db2.disable.indexspace2index=<true | false>
        --Dcom.rocketsoft.newton.model.db2.disable.tablespace2table=<true | false>
        --Dcom.rocketsoft.newton.model.db2.disable.plan2packagecollection=<true | false>
  • If db2.disable.tablespace2table is set to true, the Object hierarchy will not be displayed for object types: Index, Package (Db2), Table, Table space, Trigger (Db2), and View (Db2).
  • If db2.disable.plan2packagecollection is set to true, the Object hierarchy will not be displayed for object types: Package (Db2) and Package collection (Db2).

Application

Chunk size
The chunk size decides the number of objects included in a single JCL during DDL generation. The default value for the CHUNK_SIZE parameter is 200. You can configure the CHUNK_SIZE parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML). Every JCL runs in parallel. Proceed with caution while configuring the CHUNK_SIZE parameter to avoid extra load on the server.
It is recommended to set this parameter value to less than 255.
Refer to the following example: 
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.appManifest.getddl.chunkSize=50
Limit for code point
The code point limit decides the size of the YAML file in the JCL. You can configure the codePointLimit parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML). The value for this parameter must be in bytes.
Refer to the following example: 
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.utilities.yaml.codePointLimit=31457280
Skip GIT history records
The performance of registering an application can be improved by skipping the records in the GIT history. You can configure the checkGitHistoryForAddedObjects parameter by specifying a definition for the javaArgs element in PARMLIB(ZWEYAML). The default value is true.
You can set this parameter to false to skip the GIT history records and improve the performance.
Refer to the following example: 
components:
  izp:
    server:
      javaArgs:
        --Dcom.rocketsoft.newton.uri.db2.db2FileUri.checkGitHistoryForAddedObjects=false