Descriptions of basic installation options

For more information about setting the values of some of these options at runtime, see LOADPLUS-command-options. For more information about the performance implications of these options, see Tuning-jobs. 

APCOLLECTION=

This option is valid only for SQLAPPLY load jobs.

The APCOLLECTION option specifies the ID for the collection to which High-speed Apply dynamically binds packages during execution. If you change the value for this installation option, you can specify a collection ID with a length of up to 128 bytes. LOADPLUS passes the value of this option to High-speed Apply.

Overriding this option

You can override the value for this option by using the APCOLLECTION command option.

If you keep the null value that was shipped with LOADPLUS and no value is specified for the APCOLLECTION command option, High-speed Apply uses the default value of the CollectionID parameter in the Bind section of High-speed Apply. You cannot specify a null value for the APCOLLECTION command option. 

APCOMMIT=2500

This option is valid only for SQLAPPLY load jobs.

The APCOMMIT option specifies the number of records that you want each High-speed Apply agent to load before issuing a COMMIT statement. Valid values for this option are 1 through 32767.

LOADPLUS passes the value of this parameter to the StatementCount parameter in the CommitTriggers section of High-speed Apply. For more information, see the High-speed Apply Engine documentation.

Overriding this option

You can override the value for this option by using the APCOMMIT command option. 

APDOPTS=

This option will be used in a future release. 

APMULTIROW=100

This option is valid only for SQLAPPLY load jobs.

The APMULTIROW option tells High-speed Apply whether to insert multiple rows in a single insert action and, if so, how many rows to insert at one time. You can specify a value from 0 through 32767.

A value of 0 or 1 tells High-speed Apply to insert one row at a time.

LOADPLUS passes this value to the MultiRowInsert and MaxRows parameters in the MultiRowInsert section of High-speed Apply. For more information about these parameters, see theHigh-speed Apply Engine documentation.

Overriding this option

You can override the value for this option by using the APMULTIROW command option. 

APMXAGNT=10

This option is valid only for SQLAPPLY load jobs.

The APMXAGNT option specifies the maximum number of agents that High-speed Apply can start for this load. Valid values for this option are 1 through the number of batch threads that are available in your Db2 subsystem.

APMXAGNT affects only partitioned or multi-table table spaces. LOADPLUS uses at most one agent per partition and table. For partition-by-growth table spaces, LOADPLUS uses only one agent per load regardless of the value that you specify.

LOADPLUS passes the value of this parameter to the MaxAgents parameter in the Agent section of High-speed Apply. For more information, see theHigh-speed Apply Engine documentation.

Overriding this option

You can override the value for this option by using the APMAXAGENTS command option. 

APOWNER=

This option is valid only for SQLAPPLY load jobs.

The APOWNER option specifies the authorization ID that High-speed Apply uses to bind the Db2 plan and packages for the apply request. If you change the value for this installation option, you can specify an owner ID with a length of up to 128 bytes. LOADPLUS passes this value to High-speed Apply.

Overriding this option

You can override the value for this option by using the APOWNER command option.

If you keep the null value that was shipped with LOADPLUS and do not specify a value for the APOWNER command option, High-speed Apply uses the default value of the BindOwner parameter in the Bind section of High-speed Apply. You cannot specify a null value for the APOWNER command option. 

APRETLIM=COUNT

This option is valid only for SQLAPPLY load jobs.

The APRETLIM option tells High-speed Apply how to respond to an SQL -911, -913, or -904 error. You can specify one of the following options:

• COUNT tells High-speed Apply to retry the number of times specified in the APRETVAL option.
• TIME tells High-speed Apply to continue to retry until it reaches the number of seconds specified in APRETVAL.

LOADPLUS passes the value of this parameter to the RetryLimit parameter in the Conflict section of High-speed Apply. For more information, see theHigh-speed Apply Engine documentation.

Overriding this option

You can override the value for this option by using the APRETRYLIM command option. 

APRETVAL=5

This option is valid only for SQLAPPLY load jobs.

The APRETVAL option specifies the High-speed Apply retry limit following an SQL -911, -913, or -904 error. Depending on the value for APRETLIM, this limit is either the number of retry attempts or the number of seconds after which High-speed Apply is to stop retrying. Valid values are 0 through 32767. A value of 0 tells High-speed Apply not to retry.

LOADPLUS passes the value of this parameter to the RetryValue parameter in the Conflict section of High-speed Apply. For more information, see theHigh-speed Apply Engine documentation.

Overriding this option

You can override the value for this option by using the APRETRYVAL command option. 

AUTOENUMROWS=YES

The AUTOENUMROWS option specifies whether to automate input file size estimation for dynamic allocation and sort processing optimization. Valid values for this option are YES and NO.

YES automates file size estimation. Automating file size estimation eliminates the need to provide an estimate with the ENUMROWS command option when enabling dynamic data set allocation or specifying the ANALYZE command option. For more information about automated file size estimation, see ENUMROWS.

If you specify NO, the following conditions and requirements apply:

• If you do not specify a value for the ENUMROWS command option, the memory allocated for each sort process could be limited.
• To enable dynamic allocation (except for a DSNUTILB load) or if you specify the ANALYZE command option, you must specify a value for the ENUMROWS command option.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the ENUMROWS command option. 

AVAILPAGEPCT=0

The AVAILPAGEPCT option controls memory that LOADPLUS allocates to BMCSORT for concurrent sort processing. AVAILPAGEPCT specifies the maximum percentage of available 4-KB pages, as obtained from the system, that LOADPLUS can allocate. You can specify any integer from 0 through 100.

A value of 0 tells LOADPLUS to ignore the number of available pages when allocating sort memory.

A value of 1 through 100 tells LOADPLUS to use up to the specified percentage of available pages when allocating sort memory. For example, AVAILPAGEPCT=50 indicates that LOADPLUS should use no more than 50 percent of the available pages.

Additional considerations

The following additional information applies to the AVAILPAGEPCT option:

• Because available pages are rarely subject to system paging, changing this value will have a minimal effect, if any, on system performance.
• When you specify values greater than 0 for both AVAILPAGEPCT and TOTALPAGEPCT, LOADPLUS uses the lesser of the two calculated results as the maximum amount of memory for sort processing.
• If LOADPLUS is unable to perform an optimal sort due to an insufficient number of available or total pages that it is enabled to allocate, the SHORTMEMORY installation or command option controls the action that LOADPLUS takes.
• When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the AVAILPAGEPCT command option. 

CBUFFS=30

The CBUFFS option specifies a multiple of 32 KB to use to define the amount of buffer pool storage for each copy data set. LOADPLUS allocates as many buffers as will fit into the calculated space. If you are making multiple copies, the same set of buffers is used, not an additional set. For more information, see Copy-data-sets-in-LOADPLUS. 

CENTURY=(1950,2049)

The CENTURY option specifies the 100-year range that determines the century for the DATE and TIMESTAMP external formats that contain two-digit year values. The value for this option is two four-digit years in the format (ccyy,ccyy). The first four-digit year value must be less than the second four-digit year. You must specify both values, and these values must span 100 years.

Any two-digit year in your input data that lies between the first yy specification and 99 is prefixed with the first cc value to create a four-digit year. Any two-digit year in your input data that lies between 00 and the second yy specification is prefixed with the second cc value to create a four-digit year.

For example, if you specify CENTURY(1950,2049), LOADPLUS places 19 in front of each two-digit year with a value 50 through 99, and places 20 in front of each two-digit year with a value 00 through 49. The date 99/12/31 becomes 1999/12/31 and 00/12/31 becomes 2000/12/31.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the CENTURY command option or the CENTURY field specification parameter. 

CHEKPEND=(YES,)

The CHEKPEND option specifies whether you want to set dependent table spaces to CHECK pending (CHKP) status. For details about CHKP status, see Referential-and-check-constraints and CHECK CONSTRAINTS.

The following table describes the action that LOADPLUS takes for each set of values that you can specify:

Overriding this option

Unless you specify the ENFORCE keyword with this option, you can override the value for this option by using the CHECKPEND command option. 

COPYDDN=(BMCCPY, BMCCPZ)

The COPYDDN option specifies default ddnames or ddname prefixes for the local copy data sets that receive either an image copy or a DSN1COPY-type copy of the table space or partitions that you are loading. If you are registering the copies, the first name is the local primary copy and the second name is the local backup copy.

When using this name as a prefix, allow sufficient bytes for the partition number to be added and still have a valid ddname (eight bytes or less). If you change the default ddnames from BMCCPY and BMCCPZ and you are not dynamically allocating your copy data sets, you must change the ddnames in your JCL. For more information, see Copy-data-sets-in-LOADPLUS.

If you are loading a partition-by-growth table space, ensure that the ddname prefix that you specify allows for the number of partitions specified for MAXPARTITIONS in your table space definition.

When invoking DSNUTILB, LOADPLUS includes this information in the TEMPLATE control statement that it builds for the IBM Db2 LOAD utility.

This option does not apply to LOB or XML copy data sets.

Overriding this option

You can override the value for this option by using the COPYDDN command option. 

COPYLVL=FULL

The COPYLVL option specifies how LOADPLUS is to assign dynamically allocated image copy data sets when loading a partitioned table space. You can specify one of the following options:

• FULL allocates a single copy data set to contain all partitions that are being loaded in either of the following cases:
  • You are loading all partitions.
  • You are loading a subset of contiguous partitions (specified on the PART command option), and you specify YES for the COPYSUBSET installation option.
• PART allocates individual copy data sets for each partition that you are loading. The following considerations apply to PART:
  • If you specify PART, LOADPLUS appends the partition number to the ddname prefixes that you specify in the COPYDDN and RCVYDDN options. The values that you specify for these options plus the highest partition number must not exceed eight characters. For more information, see Specifying ddname prefixes.
  • PART is not valid when LOADPLUS invokes DSNUTILB (and you specify COPY YES). If this value is in effect at runtime, LOADPLUS terminates.

Overriding this option

You can override the value for this option by using the COPYLVL command option. For additional considerations, see the command option description. 

COPYPEND=(YES,)

The COPYPEND option specifies whether you want LOADPLUS to set the table space to COPY pending status if a copy was not made as part of the load job.

The following table describes the actions that LOADPLUS takes for each set of values that you can specify:

Unless you specify the ENFORCE keyword with this option, you can override this value by using the COPYPEND command option. 

COPYSUBSET=NO

The COPYSUBSET option tells LOADPLUS whether to use a single copy data set for a subset of partitions. You can specify one of the following options:

• NO does not allow this single copy data set.
• YES enables a single copy data set. You must also meet the following requirements:
  • Specify a single subset of contiguous partitions with the PART command option.
  • For the local primary image copy, either activate dynamic allocation or allocate a single copy data set in your JCL.
  • If you dynamically allocate your copy data sets, specify FULL for the COPYLVL installation or command option. 

DELFILES=(YES,NO)

The DELFILES option tells LOADPLUS whether to delete the SORTOUT, SORTWK, SYSUT1, SYSERR, and SYSDISC files after the load completes successfully. The first value tells LOADPLUS whether to delete your SORTOUT, SORTWK, SYSUT1, and SYSERR files after the load completes successfully, regardless of whether LOADPLUS uses the files. The second value tells LOADPLUS how to handle the discard file (SYSDISC). LOADPLUS deletes any SYSDISC files only if there were no discarded records during the load process.

If you specify YES for these parameters, LOADPLUS deletes the appropriate file, regardless of the JCL disposition for the data set.

The following table describes the action that LOADPLUS takes for each set of values that you can specify:

The following considerations apply to the DELFILES option:

• If the SYSDISC or SYSERR data set is allocated as a GDG data set, LOADPLUS deletes only the generation that was created during the current job.
• If your work files are defined with DISP=(any,DELETE,DELETE), LOADPLUS deletes these work files after the load completes even if you specify NO on this option.
• When LOADPLUS invokes DSNUTILB, SYSERR and SYSDISC files are not deleted, regardless of the value of this option.
• If you also specify a value for the RETPD or EXPDT option for your dynamically allocated SYSERR or SYSDISC data sets, LOADPLUS deletes your data sets only if the expiration date is earlier than the current date, or if RETPD is 0 or blank.

Overriding this option

You can override the value for this option by using the DELETEFILES and SYSDISC command options.

Running in a worklist environment

If you are running the load job in a worklist environment, LOADPLUS functions differently. In this environment, LOADPLUS always ignores the value for the first parameter of the DELFILES installation option and, by default, does not delete the work files. LOADPLUS functions this way so that the work files exist for subsequent executions in the worklist. If you want to delete the work files, you must specify DELETEFILES YES on the LOAD command in the worklist.

For SYSDISC files in a worklist environment, LOADPLUS functions in one of the following ways:

• If you allocate your own SYSDISC file, LOADPLUS also ignores the value of the second parameter of the DELFILES installation option. In this case, if you want to delete SYSDISC (if it is empty), you must specify SYSDISC YES on the LOAD command in the worklist.
• If you have LOADPLUS dynamically allocate SYSDISC, LOADPLUS honors the value of the second parameter of the DELFILES installation option and deletes SYSDISC if that value is YES (and if SYSDISC is empty). 

DISCARDLIMRC=8

The DISCARDLIMRC option allows you to specify a default user-defined return code that LOADPLUS uses when the number of discard violations reaches the discard limit that you specify with the DISCARDS command option. You can specify any integer greater than 7.

LOADPLUS always ends with the highest return code assigned during the load job. For more information, see Return-code-hierarchy-in-LOADPLUS.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the IFDISCARDLIMIT command option. 

DISCARDRC=0

The DISCARDRC option allows you to specify a default user-defined return code that LOADPLUS uses upon successful completion of the job when LOADPLUS discards one or more input records. You can specify any integer from 0 through 7.

LOADPLUS always ends with the highest return code assigned during the load job. For more information, see Return-code-hierarchy-in-LOADPLUS.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the IFDISCARDS command option. 

DISCDDN=SYSDISC

The DISCDDN option specifies a default ddname for the discard data set. LOADPLUS places a record in this data set when that record cannot be loaded for any of the reasons that are listed in SYSDISC-data-set-in-LOADPLUS. If you change the default ddname from SYSDISC, you must also change the ddname in your JCL.

When invoking DSNUTILB, LOADPLUS uses this option only to pass a value for the &DDNAME variable for the data set name pattern. LOADPLUS includes this information in the TEMPLATE control statement that it builds for the IBM Db2 LOAD utility.

Overriding this option

You can override the value for this option by using the DISCARDDN command option. 

DRNDELAY=1

After a drain times out, the DRNDELAY option specifies the minimum number of seconds that you want LOADPLUS to wait before it tries again to obtain the drain. The number of seconds can range from 1 through 1800.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the RETRY_DELAY command option. 

DRNRETRY=255

The DRNRETRY option specifies the maximum number of times that you want LOADPLUS to attempt to obtain a drain before terminating the job. The number of retry attempts can range from 0 through 255.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the RETRY command option. 

DRNWAIT=NONE

The DRNWAIT option specifies the drain timeout value to use. Specify one of the following values:

• NONE, which tells the drain request issued by LOADPLUS to time out immediately if the drain cannot acquire the lock

  NONE prevents any application transactions from being queued during the drain process. BMC recommends that you specify NONE in high-transaction environments.

• UTIL, which tells LOADPLUS to use the standard Db2 utility timeout value defined in DSNZPARMS for your site (IRLMRWT multiplied by UTIMOUT)

  The wait time applies to each object involved in the load.

• SQL, which tells LOADPLUS to use the standard SQL timeout value (IRLMRWT) as the drain timeout value

  The wait time applies to each object involved in the load.

• Any integer value from 0 through 1800
  • 0 is equivalent to the value UTIL.
  • 1 through 1800 specifies the number of seconds to wait to obtain the drain for each drain retry before timing out.

If LOADPLUS cannot drain all of the objects within the time period specified by DRNWAIT, LOADPLUS completes the following process:

1. Releases the drains that it has obtained so far
2. Waits the length of time that you specify in the DRNDELAY installation option (or RETRY_DELAY command option)
3. Tries again to drain the objects for the number of times that you specify in the DRNRETRY installation option (or RETRY command option)

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the DRAIN_WAIT command option. 

DSNUEXIT=(NONE,ASM)

The DSNUEXIT option specifies the name of a user-defined exit routine that creates data set name patterns, and the programming language in which the routine is written. This user exit provides the user-defined variables for constructing data set name patterns (with the DSNPAT option) that LOADPLUS uses when dynamically allocating data sets. For information about user-defined exit routines, see LOADPLUS-user-exits.

The following values are valid for the programming language:

• ASM
• COBOL2
• LE_COBOL
• C
• LE_C

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the DSNUEXIT command option. 

DSNUTILB=YES

The DSNUTILB option tells LOADPLUS whether to invoke DSNUTILB to pass processing to the IBM Db2 LOAD utility. LOADPLUS uses this option to enable support for certain objects or features. For the list of features, see Load-jobs-that-invoke-DSNUTILB.

You can specify one of the following values:

• YES tells LOADPLUS to invoke DSNUTILB when it is required to support the object type that is involved in the load. If you are loading a multi-table table space and any table in that table space (regardless of whether it is participating in the load) has a feature that is supported only by invoking DSNUTILB, LOADPLUS invokes DSNUTILB for the load job.

  For requirements and restrictions that apply when LOADPLUS invokes DSNUTILB, see Load-jobs-that-invoke-DSNUTILB.

• NO tells LOADPLUS to not invoke DSNUTILB. If the type of load job that you are running requires DSNUTILB, LOADPLUS terminates.

Overriding this option

You can override the value for this option by using the DSNUTILB command option. 

ENFORCE=CHECK

The ENFORCE option allows you to specify a default behavior for checking Db2-defined referential constraints and check constraints in your load jobs.

The following table describes the options that you can specify:

For more information about how LOADPLUS handles referential and check constraints, see Referential-and-check-constraints.

Overriding this option

You can override the value for this option by using the ENFORCE command option. 

ERRDDN=SYSERR

The ERRDDN option specifies a default ddname for the error data set (the data set that contains information about records that are discarded because of errors). If you change the default ddname from SYSERR, you must also change the ddname in your JCL. For more information, see SYSERR-data-set-in-LOADPLUS.

When invoking DSNUTILB, LOADPLUS uses this option only to pass a value for the &DDNAME variable for the data set name pattern. LOADPLUS includes this information in the TEMPLATE control statement that it builds for the IBM DB2 LOAD utility.

Overriding this option

You can override the value for this option by using the ERRDDN command option. 

EXCLDUMP=(X37,X22,X06)

The EXCLDUMP option allows you to limit the conditions under which LOADPLUS generates a system dump when the SDUMP option contains values other than NO. This option tells LOADPLUS to exclude the listed abend codes when generating the dump.

Specify a three-digit abend code, such as 806 or 222, or prefix an 'X' to a two-digit abend code to exclude all abend codes that end in those two digits. For example, if you specify X37, LOADPLUS will not generate a system dump for all abend codes that end in 37 (such as B37 or E37). You can specify up to 10 abend codes.

Specify EXCLDUMP=0 (without parentheses) if you want all abend codes to be candidates for a system dump. 

FASTSWITCH=NO

This option is valid only for SHRLEVEL CHANGE (except an SQLAPPLY load) or SHRLEVEL REFERENCE load jobs.

The FASTSWITCH option tells LOADPLUS how to handle staging data sets after the load process is complete. Valid values are NO, YES, and ZPARM:

• NO tells LOADPLUS to rename the staging data sets to the original data set names.

• YES tells LOADPLUS to bypass the VSAM rename process and directly update the Db2 catalog to point to the staging data sets.

  Consider the following information about the FASTSWITCH process:

  • When loading clone tables or base objects that participate (or have participated) in a clone relationship, LOADPLUS changes FASTSWITCH YES to FASTSWITCH NO.
  • BMC recommends using the FASTSWITCH process when you are loading objects with more than 200 data sets, such as a segmented table space that contains many tables that each have an index.
  • The FASTSWITCH process requires updates to the Db2 catalog and directory. In some environments, LOADPLUS might have difficulty acquiring the necessary locks, which results in contention or deadlocks. Minimizing use of the FASTSWITCH process can reduce this contention and allow the process to be more effective when it is needed. Frequently reorganizing the Db2 catalog and directory can also help prevent contention.
• ZPARM tells LOADPLUS to use the value that is set in IBM DSNZPARM for FASTSWITCH. FASTSWITCH=ZPARM, enables you to use Db2 parameters to manage the FASTSWITCH setting, without changing your LOADPLUS installation options module.

For more information about these methods for handling staging data sets, see Staging-data-sets.

Overriding this option

You can override the value for this option by using the FASTSWITCH command option. 

FILECHK=FAIL

The FILECHK option specifies the action that LOADPLUS should take when encountering a work file that has been allocated in one of the following ways:

• As a temporary data set

  For a definition of temporary data sets within LOADPLUS, see Check for data set attributes.

• As DD DUMMY or DSN=NULLFILE

Specify one of the following options:

• FILECHK=FAIL tells LOADPLUS to terminate.
• FILECHK=WARN tells LOADPLUS to issue a warning message and continue processing.

When invoking DSNUTILB, LOADPLUS ignores this option. 

FILEVAR (obsolete)

In version 11.1 and earlier, this option told LOADPLUS whether to allow file reference subtypes in your field specifications when loading LOB or XML data via DSNUTILB.

Beginning with version 11.2, LOADPLUS no longer requires or supports the FILEVAR option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

FORCE=NONE

The FORCE option specifies whether to cancel Db2 threads that might prevent a drain process from completing. Specify one of the following options:

• NONE tells LOADPLUS not to cancel Db2 threads.
• READERS tells LOADPLUS to cancel read claimers at the point specified by the FORCE_AT option.
• ALL tells LOADPLUS to cancel both read and write claimers at the point specified by the FORCE_AT option.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the FORCE command option. The FORCE command option provides an additional option, REPORTONLY, that tells LOADPLUS to display a report of the threads that would have been canceled if you had specified FORCE ALL. 

FORCE_AT=(START,3)

The FORCE_AT option tells LOADPLUS when to cancel Db2 threads that might prevent the drain process from completing. This option is applicable only when FORCE READERS, FORCE ALL, or FORCE REPORTONLY is in effect.

The first parameter of this option indicates at which point during the drain process to begin canceling threads. The second parameter indicates how long to delay the start of the cancelation process from the specified point in the drain process.

For the first parameter of this option, specify one of the following values:

• START tells LOADPLUS to start canceling threads when the drain request begins.
• RETRY tells LOADPLUS to start canceling threads the first time the drain process times out and LOADPLUS attempts to retry the drain.
• LASTRETRY tells LOADPLUS to start canceling threads at the beginning of the last retry attempt following a drain process timeout. You can control the number of drain retry attempts with the RETRY command option or DRNRETRY installation option.

For the second parameter of this option, specify an integer value to indicate hundredths of a second. For example, specify 7 to tell LOADPLUS to wait .07 seconds. Specify an integer value of 0 or greater. The default, 0, tells LOADPLUS to start the cancelation process immediately upon reaching the point specified by the FORCE_AT option.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for the first parameter of this option by using the FORCE_AT suboption of the FORCE command option. You can override the value for the second parameter by using the FORCE_DELAY suboption of the FORCE command option. 

FORCE_RPT=NO

The FORCE_RPT option tells LOADPLUS whether to display a report of the canceled threads.

Specify one of the following values for this option:

• YES tells LOADPLUS to display the report. This value is applicable only when FORCE READERS or FORCE ALL is in effect.

  If your JCL includes a BMCFORCE DD statement, LOADPLUS sends the canceled threads report to that data set. Otherwise, the report is displayed in the LOADPLUS SYSPRINT.

• NO tells LOADPLUS not to display the report.

LOADPLUS ignores this option when either of the following conditions exists:

• LOADPLUS is invoking DSNUTILB
• You specify FORCE REPORTONLY on the LOAD command

Overriding this option

You can override the value for this option by using the FORCE_RPT suboption of the FORCE command option. 

HASHAX (obsolete)

In version 11.1 and earlier, this option told LOADPLUS whether to load (by invoking DSNUTILB) a table that was defined as ORGANIZE BY HASH.

Beginning with version 11.2, LOADPLUS no longer requires or supports the HASHAX installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

HISTORY=YES

(BMC.DB2.SPE2304)

The HISTORY option specifies whether to update the BMCHIST table. If you specify YES, LOADPLUS inserts a utility history row into the BMCHIST table when the load is successfully completed. If you specify NO for this option, LOADPLUS bypasses any updates to the BMCHIST table.

IBUFFS=20

The IBUFFS option specifies a multiple of either 32 KB or 256 KB to use to define the amount of buffer pool storage for each active input (SYSREC) data set. LOADPLUS allocates as many buffers as will fit into the calculated space. The multiplier that LOADPLUS applies to the IBUFFS option value varies as follows:

• For SYSREC data sets with a block size greater than 32 KB, LOADPLUS uses a multiplier of 256 KB. In this case, if the IBUFFS option has a value greater than 6, LOADPLUS ignores that setting and uses 6.
• For all other SYSREC data sets, LOADPLUS uses a multiplier of 32 KB.

For more information, see Performance-considerations-for-buffer-options. 

IDCACHE=1000

The IDCACHE option allows you to specify the size of the cache that LOADPLUS uses when generating values for an identity column. Specify the size as the number of values to reserve. LOADPLUS reserves this cache in SYSIBM.SYSSEQUENCES and reserves at least one cache for each read task. Valid values for this option are 1 through 100000.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the IDCACHE command option. 

IDCDDN=SYSIDCIN

The IDCDDN option specifies a default ddname for the input data set containing the IDCAMS command statements that LOADPLUS uses to redefine VSAM data sets. For more information, see SYSIDCIN-data-set-in-LOADPLUS.

Overriding this option

You can override the value for this option by using the IDCDDN command option. 

IDERROR=DISCARD

The IDERROR option tells LOADPLUS how to handle rows with generated identity columns values that are outside the range that is defined on the identity column. Valid values are DISCARD and FAIL:

• DISCARD tells LOADPLUS to discard these rows. DISCARD is not valid when LOADPLUS invokes DSNUTILB. If this value is in effect at runtime for a DSNUTILB load, LOADPLUS issues message BMC50178E and terminates.
• FAIL tells LOADPLUS to terminate as soon as it encounters a generated identity column value that is outside this range. LOADPLUS ignores this option for an SQLAPPLY load job.

Overriding this option

You can override the value for this option by using the IDERROR command option. 

INDDN=SYSREC

The INDDN option specifies a default ddname or ddname prefix for the input data set. When using this name as a prefix, allow sufficient bytes for LOADPLUS to add the number of input files and still have a valid ddname (eight bytes or less). If you change the default ddname from SYSREC and you are not using the INDSN command option, you must change the ddname in your JCL. For more information, see SYSREC-data-sets-in-LOADPLUS.

If any DD statements in your JCL match the value for INDDN and you specify the INDSN command option, LOADPLUS issues message BMC50460E and fails.

Overriding this option

You can override the value for this option by using the INDDN command option. 

INFORI=NO

The INFORI option tells LOADPLUS how to handle the enforcement of informational referential constraints:

• NO tells LOADPLUS to ignore informational referential constraints.

• YES tells LOADPLUS to enforce informational referential constraints in the same way as other referential constraints.

  Be aware of the following information when you specify INFORI=YES:

  • LOADPLUS discards any violating rows, just as it does for other referential constraints.

  • If LOADPLUS sets CHKP status on a table because it enforced informational referential constraints on the parent table, you might not be able to use the standard methods for resetting CHKP status. Therefore, if you are enforcing only informational constraints, BMC recommends that you also specify CHECKPEND NO.

    For more information about resetting CHKP status, see Restoring integrity.

  • When LOADPLUS invokes DSNUTILB, the following actions occur:
    • For an SQLAPPLY load, LOADPLUS ignores this option.
    • Otherwise, if this value is in effect at runtime, LOADPLUS issues message BMC50178E and terminates.

Overriding this option

You can override the value for this option by using the INFORI option of the ENFORCE CONSTRAINTS or ENFORCE RI command options. 

INLINECP=YES

The INLINECP option tells LOADPLUS whether to create inline image copies. You can specify YES or NO:

• YES tells LOADPLUS to create an inline image copy while loading the table space. This value requires that COPY YES be specified on the LOAD command.
• NO tells LOADPLUS to not make an inline image copy while loading the table space, but to create an image copy after loading the table space.

When invoking DSNUTILB, LOADPLUS ignores this option.

If any of the following conditions apply to your load job, LOADPLUS functions as if you specified NO, regardless of the value that you specify either here or on the LOAD command:

• You are loading XML data.
• You specify LOAD RESUME YES, unless you also specify PART n REPLACE for all participating partitions.
• The copy data sets are on a stacked tape.
• You restart your load job, with the following exception: If you are running a two-phase load job and you specify RESTART(PHASE) on your EXEC statement, LOADPLUS generates an inline copy if the value of INLINE is YES.

• The size of the table space page is greater than 4 KB, you are loading multiple partitions, and you have one image copy data set.

  An exception to this condition exists for partition-by-growth table spaces. LOADPLUS can create inline image copies of partition-by-growth table spaces in this case.

Overriding this option

You can override the value for this option by using the INLINE command option. 

INLOB (obsolete)

In LOADPLUS versions 10.2 and earlier, this option told LOADPLUS whether to load (by invoking DSNUTILB) table spaces that contain an inline LOB column.

Beginning with version 11.1, LOADPLUS no longer requires this option. The value of the DSNUTILB option determines whether LOADPLUS will invoke DSNUTILB to load inline LOB data.

If your installation options module contains the INLOB option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete.

INVALIDATECACHE=YES

(SPE2010) The INVALIDATECACHE option indicates whether the SQL Statements in the Dynamic Cache should be invalidated for the processing object.

• (Default) INVALIDATECACHE=YES tells LOADPLUS to invalidate the SQL Statements in the Dynamic Statement Cache. 
• INVALIDATECACHE=NO tells LOADPLUS not to invalidate the SQL Statements in the Dynamic Statement Cache.
• When SHRLEVEL CHANGE is specified, LOADPLUS ignores this option.

Additional considerations

Note the following additional information for INVALIDATECACHE=YES:

• When invoking DSNUTILB, and the UPDATEDB2STATS YES is specified on Db2 version 12, LOADPLUS passes this option to the IBM DB2 LOAD utility for processing.
• The Dynamic Statement Cache is NOT flushed when LOADPLUS executes with the SHRLEVEL CHANGE option. 

IXONEX (obsolete)

In LOADPLUS 11.1 and earlier, this option told LOADPLUS whether to load (by invoking DSNUTILB) table spaces that contained an index that contained a key derived from certain expressions.

Beginning with version 11.2, LOADPLUS no longer requires or supports the IXONEX installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

IXRANDOM (obsolete)

In LOADPLUS 11.1 and earlier, this option told LOADPLUS whether to load (by invoking DSNUTILB) table spaces that contained an index that contained a key with random ordering.

Beginning with version 11.2, LOADPLUS no longer requires or supports the IXRANDOM installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

KEEPDICTIONARY=NO

The KEEPDICTIONARY option tells LOADPLUS whether to keep the existing compression dictionary when running a LOAD REPLACE or LOAD RESUME YES PART n REPLACE job:

• NO tells LOADPLUS to build a new compression dictionary.
• YES tells LOADPLUS to keep the existing compression dictionary. If a dictionary does not exist, LOADPLUS builds one.

When LOADPLUS invokes DSNUTILB, the following actions occur:

• For an SQLAPPLY load, LOADPLUS ignores this option.
• Otherwise, LOADPLUS passes KEEPDICTIONARY=YES to the IBM Db2 LOAD utility as KEEPDICTIONARY, and ignores KEEPDICTIONARY=NO.

For details about when LOADPLUS builds and keeps a dictionary, see Considerations-for-table-space-compression.

Restrictions

The following restrictions apply to the KEEPDICTIONARY option:

• The KEEPDICTIONARY option is valid only if the table space or partition that you are loading has the COMPRESS YES attribute.
• If a table space is compressed and a load job would convert the row format from BRF to RRF, LOADPLUS builds a new dictionary except when both of the following options are in effect:
  • The value of the LOADPLUS KEEPDICTIONARY option is YES.
  • The value of the DB2 subsystem parameter HONOR_KEEPDICTIONARY is YES.

Overriding this option

You can override the value for this option either at the table space level, by using the KEEPDICTIONARY option with LOAD REPLACE, or at the partition level, by using the KEEPDICTIONARY option with PART n REPLACE. 

LBUFFS=20

The LBUFFS option specifies a multiple of 32 KB to use to define the amount of buffer pool storage that is allocated for each active load (SORTOUT) data set. LOADPLUS allocates as many buffers as will fit into the calculated space. For more information, see Performance-considerations-for-buffer-options. 

LOADDN=SORTOUT

The LOADDN option specifies a default ddname or ddname prefix for the output data set from the PRELOAD phase. When using this name as a prefix for a partitioned table space, allow sufficient bytes for the partition number to be added and still have a valid ddname (eight bytes or less). If you change the default ddname from SORTOUT and you are not dynamically allocating your SORTOUT data sets, you must change the ddname in your JCL. For more information, see SORTOUT-data-sets-in-LOADPLUS.

Additional considerations

The following considerations apply to the LOADDN option:

• If you specify or default to a prefix with a length of 7 or more characters, and the value for the SMAX installation option is greater than 9, LOADPLUS reduces the value of SMAX to 9.
• When invoking DSNUTILB, LOADPLUS uses this option only to pass a value for the &DDNAME variable for the data set name pattern. LOADPLUS includes this information in the TEMPLATE control statement that it builds for the IBM Db2 LOAD utility.

Overriding this option

You can override the value for this option by using the LOADDN command option. 

LOB (obsolete)

In LOADPLUS 11.1 and earlier, this option told LOADPLUS whether to load LOB data in a LOB table space when DSNUTILB was required.

Beginning with version 11.2, LOADPLUS no longer requires or supports the LOB installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

LOBAVGPCT=50

The LOBAVGPCT option provides LOADPLUS with an estimate of the size of your LOB data. LOADPLUS uses this information to balance the number of tasks needed to load the base table, load the LOB table space, and build the indexes. LOADPLUS also uses this information when allocating LOB copy data sets.

Specify a percentage of the maximum size defined for the LOB that you are loading. Valid values are 1 through 100.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option either at the global level, by using the LOBAVGPCT option, or at the field level, by using the AVGSIZE field option on the BLOB, BLOBF, CLOB, CLOBF, DBCLOB or DBCLOBF field specification. The field-level option overrides the global option. 

LOCKROW=YES

The LOCKROW option tells LOADPLUS which serialization method to use when updating the BMCSYNC and BMCUTIL tables:

• YES tells LOADPLUS to use MVS enqueues instead of SQL LOCK TABLE statements for serialization. Using LOCKROW=YES should prevent most SQL -911 return codes that occur when multiple BMC products concurrently update these tables.
• NO tells LOADPLUS to use SQL LOCK TABLE statements for serialization when updating the BMCSYNC and BMCUTIL tables.

Additional considerations

The following considerations apply to the LOCKROW option:

• Using LOCKROW=YES requires row-level locking. You must define the BMCSYNC and BMCUTIL tables with LOCKSIZE ROW to achieve row-level locking.
• The following BMC products must use the same LOCKROW value within a subsystem: CHECK PLUS, BMC AMI Copy, LOADPLUS, BMC AMI Recover, REORG PLUS, and UNLOAD PLUS. Regardless of the value assigned for LOCKROW, BMC AMI Copy and BMC AMI Recover always behave as if LOCKROW=YES.
• In a future version, LOADPLUS will no longer require or support the LOCKROW installation option. 

LONGNAMETRUNC=MIDDLE

The LONGNAMETRUNC option tells LOADPLUS where to truncate names that are longer than the area that is available in a LOADPLUS report-style message.

The following table describes the valid values and the symbol that appears in the message based on that value:

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the LONGNAMETRUNC command option. 

MAPDDN=SYSMAP

The MAPDDN option allows you to specify the default &DDNAME variable for the data set name pattern for the mapping data set. LOADPLUS includes this information in the TEMPLATE control statement that it builds for the IBM Db2 LOAD utility.

Overriding this option

You can override the value for this option by using the MAPDDN command option. 

MAXP=5

The MAXP option specifies the maximum number of partitions to load concurrently. For more information, see Performance-considerations-for-the-MAXP-installation-option. 

MAXSORTMEMORY=0

The value that you specify, in kilobytes, for the MAXSORTMEMORY option helps LOADPLUS determine the maximum amount of memory to allocate to each sort task.

BMC strongly recommends that you use the shipped value of 0, which tells LOADPLUS to automatically compute the maximum amount of memory that is needed to perform each sort task. In addition to 0, you can specify any value between the value that you specify for the MINSORTMEMORY option and 2097152.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the MAXSORTMEMORY command option. 

MAXTAPE=3

The MAXTAPE option specifies the maximum number of tape drives to dynamically allocate at one time. The value must be greater than zero.

For partition-by-growth table spaces, if you are making partition-level copies and sending them to tape, ensure that the value for MAXTAPE takes potential expansion into account. For details about determining this value, see MAXTAPE.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the MAXTAPE command option. 

MGEXTENT=CONTINUE

The MGEXTENT option specifies how to allocate the extents of a Db2 object when creating a new data set during extend processing. Specify one of the following options:

• CONTINUE tells LOADPLUS to allocate the extents as follows:
  • Allocate the primary extent with the greater of the original primary quantity or the last secondary quantity of the previous data set.
  • Allocate the first secondary extent with the last secondary quantity of the previous data set.
• RESET tells LOADPLUS to allocate the primary and first secondary extents by using the original values from the Db2 object allocation.

With the exception of this option, LOADPLUS allocates secondary extents in the same way that Db2 does. LOADPLUS uses a sliding-scale calculation for secondary extents, if applicable, that is similar to the method that Db2 uses. For more information, see the Db2 documentation that describes the sliding-scale algorithm.

MINSORTMEMORY=0

The value, in kilobytes, that you specify for the MINSORTMEMORY option helps LOADPLUS determine the minimum amount of memory to allocate to each sort task. 

We strongly recommends that you use the shipped value of 0, which tells LOADPLUS to automatically compute the minimum amount of memory that is needed to perform each sort task. In addition to 0, you can specify any value between 1280 and the value that you specify for the MAXSORTMEMORY installation or command option.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the MINSORTMEMORY command option. 

MSGLEVEL=1

The MSGLEVEL option controls the messages that LOADPLUS returns in the SYSPRINT and SYSPRIN2 data sets. MSGLEVEL=0 returns minimal messages. MSGLEVEL=1 returns additional messages to help you diagnose problems and fine-tune performance.

Overriding this option

You can override the value for this option by using the MSGLEVEL parameter on the EXEC statement. 

OPNDB2ID=YES

The OPNDB2ID option tells LOADPLUS whether to use the Db2 RACF ID or the user’s RACF ID:

• YES tells LOADPLUS to use the Db2 RACF ID (instead of the RACF ID of the user who is running LOADPLUS) when opening or performing Access Method Services (AMS) functions on Db2 data sets.
• NO tells LOADPLUS to use the RACF ID of the user who is running LOADPLUS. If you specify NO, the user must have the appropriate RACF authorization.

For any security system other than RACF, specify OPNDB2ID=NO to have LOADPLUS use the security authorization ID of the user who is running LOADPLUS. 

ORIGDISP=DELETE

This option is valid only for SHRLEVEL CHANGE (except an SQLAPPLY load) or SHRLEVEL REFERENCE load jobs.

The ORIGDISP option specifies the action that LOADPLUS should take after it has successfully renamed or switched the staging data sets during a SHRLEVEL CHANGE (except SQLAPPLY) or SHRLEVEL REFERENCE job:

• DELETE tells LOADPLUS to delete the original data sets.

• RENAME tells LOADPLUS to rename the original data sets to the staging data set names.

  RENAME preserves the space that was initially allocated for the original data sets. As a result, the staging data sets are ready to use in a subsequent load job.

  LOADPLUS ignores a value of RENAME if either of the following conditions exists:

  • You specify YES for the FASTSWITCH option.
  • You specify ZPARM for the FASTSWITCH installation option, and the DB2 ZPARM value is YES.

  In these cases, no rename is needed. The data sets keep their original names, and the space is preserved for use in a subsequent load job.

For more information about the rename and FASTSWITCH processes, see Staging-data-sets.

Overriding this option

You can override the value for this option by using the ORIGINALDISP command option. 

PAUSEDISCARDRC=4

The PAUSEDISCARDRC option allows you to designate a default user-defined return code that LOADPLUS uses when pausing after the PRELOAD phase due to discarded records. The value for this option is in effect only if you specify PRELOAD PAUSE ANYDISCARDS on the LOAD command.

You can specify any positive integer. Note the following results for certain values:

• LOADPLUS always ends with the highest return code assigned during the load job. Therefore, because PRELOAD PAUSE normally ends with return code 4, specifying a value of 4 or less has no effect. For more information, see Return-code-hierarchy-in-LOADPLUS.
• If you specify an integer that is greater than 31, LOADPLUS issues a user abend that is equal to the integer that you specify.
• If you specify an integer that is greater than 4095, the LOADPLUS job step terminates with a system abend 001.

Overriding this option

You can override the value for this option by using the RETCODE keyword of the PRELOAD PAUSE ANYDISCARDS command option. 

PLAN=AMU1120

The PLAN option specifies the name of the product plan. This plan contains the packages that provide the various capabilities of LOADPLUS. 

PREFORMAT=NO

The PREFORMAT option tells LOADPLUS whether to preformat unused data set pages:

• NO tells LOADPLUS not to preformat unused pages in a data set.
• YES tells LOADPLUS to write full pages initialized with zeros up to the high-allocated RBA of the participating table space and index spaces.

When invoking DSNUTILB, LOADPLUS passes PREFORMAT=YES to the IBM Db2 LOAD utility as PREFORMAT and ignores PREFORMAT=NO.

Overriding this option

You can override the value for this option, either at the table space level or at the partition level, by using the appropriate PREFORMAT option. 

PRELOAD=LOAD

The PRELOAD option specifies whether to use two-phase or single-phase processing for your load jobs. You can specify CONTINUE or LOAD for the installation option.

PRELOAD=LOAD tells LOADPLUS to use single-phase load processing, which combines the functions of the PRELOAD and LOAD phases into the COMBINED phase. This value can improve performance in most cases.

PRELOAD=CONTINUE tells LOADPLUS to use two-phase processing and to continue with the LOAD phase after the PRELOAD phase is completed.

Considerations

The following considerations apply to the PRELOAD option:

• If PRELOAD CONTINUE is in effect at runtime when you are loading LOB or XML data, LOADPLUS invokes DSNUTILB.
• LOADPLUS terminates if PRELOAD CONTINUE is in effect at runtime and you also specify ENFORCE RI or ENFORCE CONSTRAINTS, LOADPLUS terminates.
• LOADPLUS ignores the value for this option in the following cases:
  • When invoking DSNUTILB
  • When you are running an SQLAPPLY load

SQLAPPLY load jobs always use single-phase processing.

Overriding this option

You can override the value for this option by using the PRELOAD command option. Additional values are available with the command option. 

RCVYDDN=(BMCRCY, BMCRCZ)

The RCVYDDN option specifies default ddnames or ddname prefixes for remote copy data sets. These data sets are the ones that receive either an image copy or a DSN1COPY-type copy of the table space or partitions that you are loading. If you are registering the copies, the first name is the remote primary copy, and the second name is the remote backup copy.

When using this name as a prefix, ensure that you allow sufficient bytes for the partition number to be added and still have a valid ddname (eight bytes or less). In addition, if you change the default ddnames from BMCRCY and BMCRCZ and you are not dynamically allocating your copy data sets, you must change the names in your JCL. For more information, see Copy-data-sets-in-LOADPLUS.

If you are loading a partition-by-growth table space, ensure that the ddname prefix that you specify allows for the number of partitions specified for MAXPARTITIONS in your table space definition.

When invoking DSNUTILB, LOADPLUS includes this information in the TEMPLATE control statement that it builds for the IBM Db2 LOAD utility.

This option does not apply to LOB or XML copy data sets.

Overriding this option

You can override the value for this option by using the RECOVERYDDN command option. 

REDEFINE=YES

The REDEFINE option tells LOADPLUS whether to delete and redefine the VSAM data sets for the table space and index spaces that are participating in the load. LOADPLUS can delete and redefine both user-defined (VCAT-defined) data sets and data sets that are defined in Db2 storage groups (STOGROUP-defined).

You can specify the following values:

• For SHRLEVEL NONE, REDEFINE=YES tells LOADPLUS to delete and redefine the VSAM data sets for the space before loading it. For jobs that use staging data sets, LOADPLUS deletes and defines the staging data sets.
• REDEFINE=NO tells LOADPLUS not to delete and redefine the existing VSAM data sets for the table space or indexes. Instead, LOADPLUS issues message BMC50391I, reuses the existing data sets, and resets the high-used RBA.

Additional considerations

The following considerations apply to the REDEFINE option:

• If you anticipate loading a large number of partitions, BMC recommends that you specify REDEFINE NO.
• When invoking DSNUTILB, LOADPLUS passes REDEFINE=NO to the IBM Db2 LOAD utility as REUSE and ignores REDEFINE=YES.

Overriding this option

You can override the value for this option by using the REDEFINE command option. For information about the command option and more information about how LOADPLUS functions under each value of this option, see REDEFINE. 

RENMMAX=30

The RENMMAX option indicates the maximum number of tasks to start during the staging data set rename and delete process. You can specify the following values:

• 0 to have LOADPLUS determine the number of tasks to start
• n to specify that LOADPLUS can start a maximum of n tasks (where n is a positive integer from 1 through 32767) 

RULES=STANDARD

The RULES option specifies the set of comparison rules for LOADPLUS to use in WHEN, NULLIF, and DEFAULTIF processing. You can specify STANDARD or BMC. This specification determines the following information:

• The order in which WHEN testing and data conversion, if any, is performed
• Which set of operators can be used in comparisons
• How constants are handled during translation

For information about the differences between STANDARD and BMC, see RULES-installation-option.

When your LOAD command contains the FORMAT UNLOAD, FORMAT BMC, or FORMAT BMCUNLOAD option, LOADPLUS changes the value of the RULES option to BMC, regardless of the value that you specify. When your LOAD command contains the FORMAT CSV option, LOADPLUS changes the value of this option to STANDARD, regardless of the value that you specify. 

SDUMP=(ALLPSA,CSA,RGN,SQA,LSQA,SUM,TRT,IO)

The SDUMP option tells LOADPLUS to generate a system dump, using the information listed in the option, if a load job abnormally terminates. The values listed provide diagnostic information to BMC Customer Support. Although you can specify any values that IBM allows for the SDATA parameter on the SDUMPX macro, BMC recommends that you do not change the values that were shipped with the product. For a complete list and description of the values that you can specify for this option, see the IBM SDUMPX macro description.

LOADPLUS uses the system-defined dump data set to hold the data. In cases where multiple abends occur, LOADPLUS generates the dump for only the first abend. The SDUMP option allows you to generate a system dump, regardless of your access to storage keys 0 through 7.

You can specify SDUMP=NO (without parentheses) to not generate a system dump.

To limit the conditions under which LOADPLUS generates the system dump, you can exclude selected abend codes by using the EXCLDUMP option. 

SHORTMEMORY=CONTINUE

The SHORTMEMORY option controls the action that LOADPLUS should take when one of the following memory shortages exists during sort processing:

• The system contains insufficient available or total pages of memory for LOADPLUS to perform an optimal sort.
• The region contains insufficient memory for LOADPLUS to perform a minimum number of tasks, given the amount of memory required to perform an optimal sort. However, the region does contain at least 1280 KB of memory, or the minimum amount of memory specified by the MINSORTMEMORY option. If the region contains 1280 KB of memory and the amount of memory specified by MINSORTMEMORY is available, LOADPLUS uses the greater amount of memory.

You can specify one of the following values for the SHORTMEMORY option:

• CONTINUE, the shipped value, indicates that, when a memory shortage exists, LOADPLUS should continue sort processing.
• FAIL indicates that LOADPLUS should fail when a memory shortage exists.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the SHORTMEMORY command option. 

SHRLEVEL=(NONE,NONE)

The SHRLEVEL option specifies the level of access that Db2 has, during LOADPLUS processing, to the objects that you are loading. The first parameter provides the default SHRLEVEL value for LOAD RESUME NO and LOAD REPLACE jobs. The second parameter provides the default SHRLEVEL value for LOAD RESUME YES jobs.

You can specify the values that the following table describes:

Overriding this option

You can override the value for this option by using the SHRLEVEL command option. For more information about SHRLEVEL options, see SHRLEVEL. 

SMAX=16

The SMAX option specifies the maximum number of each type of task that can run concurrently.

The following table describes the type of tasks that SMAX controls:

When invoking DSNUTILB, LOADPLUS ignores this option.

If the value of the LOADDN option is 7 or more characters and the value of the SMAX option is greater than 9, LOADPLUS reduces the value of the SMAX option to 9.

Overriding this option

The MAXSORTS command option overrides the SMAX option only when the MAXSORTS value is smaller than the SMAX value, and only for those tasks that MAXSORTS controls. For more information about the command option, see MAXSORTS. 

SMCORE=(0K,0K)

The SMCORE option specifies the amount of memory that you want each invocation of BMCSORT to use. The values 0K and 0K tell LOADPLUS to determine the appropriate amount of memory to use for each sort process. For more information, see Tuning memory use in sort processing.

The first value specifies the total amount of memory to use both above and below the 16-megabyte line for each sort process. You can specify this value in either kilobytes or megabytes. The following values are valid for this parameter:

• 0K (or 0M) tells LOADPLUS to determine the appropriate amount.
• Any value from 4096K through 65536K (or 4M through 64M) tells LOADPLUS to use the specified amount.

The second value specifies the amount of memory that is required below the 16-megabyte line for each sort process. You can specify this value in either kilobytes or megabytes. The following values are valid for this parameter:

• 0K (or 0M) tells LOADPLUS to determine the appropriate amount.
• Any value from 256K through 4096K (or 1M through 4M) tells LOADPLUS to use the specified amount.

When invoking DSNUTILB, LOADPLUS ignores this option. 

SORTDEVT=(,SYSALLDA)

The SORTDEVT option specifies the device type for the sort work files that are allocated dynamically.

The first parameter of this option is the device type to use for non-DSNUTILB load jobs. This parameter overrides the first parameter of the BMCSORT DYNALOC installation option. If the value of the third parameter in the BMCSORT DYNALOC installation option is OFF, specifying a value for this parameter turns BMCSORT dynamic allocation on

The second parameter of this option is the device type to use for DSNUTILB load jobs. When invoking DSNUTILB, LOADPLUS passes this option to the IBM DB2 LOAD utility for processing.

Overriding this option

You can override the values for both parameters of this option by using the SORTDEVT command option. 

SORTNUM=32

The SORTNUM option affects the allocation of sort work files in the following cases. You can specify any integer value from 0 through 255.

DSNUTILB load jobs

When invoking DSNUTILB, LOADPLUS passes this value to the IBM Db2 LOAD utility as the number of sort work files to allocate dynamically. For this type of load, the value must be 2 or greater.

All other load jobs

This value is in effect when BMCSORT is allocating your sort work files dynamically.

The following table describes the action that BMCSORT takes for each value that you can specify for this option. The table also provides any additional considerations for these values.

Overriding this option

You can override the value for this option by using the SORTNUM command option. 

SQLDELAY=3

The SQLDELAY option specifies the number of seconds that LOADPLUS should wait between retry attempts after receiving an SQL -911 return code. This interval is in addition to the time that elapses when DB2 waits for a timeout or deadlock. The number of seconds can range from 1 through 655. 

SQLRETRY=100

The SQLRETRY option specifies the number of times that LOADPLUS should attempt an SQL statement. The number of attempts can range from 1 through 255. 

SSIGNRPAUSE

The SSIGNRPAUSE option tells LOADPLUS to ignore the PRELOAD PAUSE keyword and continue as if PRELOAD CONTINUE were in effect when using SmartSwitch and switching to BMC AMI Utilities. The values are as follows:

SSREPORT

SSREPORT determines which cases are written to the SmartSwitch tracking table. The values are as follows:

• REPORT_NGT: Cases are written to the tracking table only when ran under REPORT_NGT rule.
• ALL:  Cases are written to the tracking table regardless of the rule they run under: REPORT_NGT, ALLOW_NGT, and FORCE_CLASSIC. 

STOP@CMT=YES

This option applies to SHRLEVEL NONE and SHRLEVEL REFERENCE only.

The STOP@CMT option specifies whether to add the 'AT(COMMIT)' parameter to all DB2 STOP commands that LOADPLUS issues. YES adds the parameter and NO does not.

We recommend that you specify the value for STOP@CMT based on your environment and your availability goals. Under certain circumstances, using STOP@CMT=NO might result in the object being placed in STOP pending status (STOPP) and failure of the load. LOADPLUS issues the following message in this case:

This situation might result when you are loading one partition of a partitioned table space while an application thread is using other partitions of the same table space.

By using STOP@CMT=YES, you might avoid this problem, but application threads might be affected. When a thread performs a commit, Db2 might stop the object, although the thread continues to run. For details and implications of the 'AT(COMMIT)' parameter, see the IBM Db2 command reference manual. 

STOPDELAY=1

The STOPDELAY option specifies the number of seconds that LOADPLUS waits before it checks again to determine whether Db2 has stopped the object. The number of seconds can be any nonzero positive integer. 

STOPRETRY=300

The STOPRETRY option specifies the number of times that LOADPLUS checks to determine whether Db2 has changed the status of an object from stop pending (STOPP) to stopped (STOP). The number of checks can be any nonzero positive integer.

If you plan to load objects with more than 2000 partitions, BMC recommends that you specify a minimum value of 450. 

TAPEDISP=DELETE

The TAPEDISP option specifies the final disposition of tape work files when the value of the DELFILES installation option or the DELETEFILES or SYSDISC command option is YES.

If you specify TAPEDISP=DELETE, each tape file will have a disposition of OLD,DELETE,DELETE when the tape is deallocated.

If you specify TAPEDISP=UNCATLG, each tape file will have a disposition of OLD,UNCATLG,UNCATLG when the tape is deallocated. Depending on your tape management environment, using UNCATLG can prevent a tape remount. 

TEMPRALDATA (obsolete)

In LOADPLUS 11.1 and earlier, this option told LOADPLUS whether to load (by invoking DSNUTILB) a temporal table under certain conditions.

Beginning with version 11.2, LOADPLUS no longer requires or supports the TEMPRALDATA installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

TOTALPAGEPCT=30

The TOTALPAGEPCT option controls memory that LOADPLUS allocates to BMCSORT for concurrent sort processing. TOTALPAGEPCT specifies the maximum percentage of total 4-KB pages, as obtained from the system, that LOADPLUS can allocate. You can specify any integer from 0 through 100.

A value of 0 tells LOADPLUS to ignore the number of total pages when allocating sort memory.

A value of 1 through 100 tells LOADPLUS to use up to the specified percentage of total pages when allocating sort memory. For example, TOTALPAGEPCT=50 indicates that LOADPLUS should use no more than 50 percent of the total pages.

Additional considerations

The following additional information applies to the TOTALPAGEPCT option:

• Because total pages are subject to more system paging than available pages, changing the value for this option is more likely to affect system performance than changing the value for the AVAILPAGEPCT option.
• When you specify values greater than 0 for both TOTALPAGEPCT and AVAILPAGEPCT, LOADPLUS uses the lesser of the two calculated results as the maximum amount of memory for sort processing.
• If LOADPLUS is unable to perform an optimal sort due to an insufficient number of available or total pages that it is enabled to allocate, the SHORTMEMORY installation option or command option controls the action that LOADPLUS takes.
• When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the TOTALPAGEPCT command option. 

TSSAMPLEPCT=100

The TSSAMPLEPCT option enables you to specify a percentage of table space pages that you want LOADPLUS to sample when gathering statistics. The following values are valid:

• 1 through 50 tells LOADPLUS to sample the specified percentage of the table space pages.
• 100 tells LOADPLUS to read all table space pages instead of sampling.

LOADPLUS ignores the TSSAMPLEPCT option for either of the following types of load jobs:

• A DSNUTILB load
• An SQLAPPLY load

Overriding this option

You can override the value for this option by using the TSSAMPLEPCT command option. 

UNICODE (obsolete)

In LOADPLUS version 11.1 and earlier, this option told LOADPLUS whether to invoke DSNUTILB when the requested translation required it.

Beginning with version 11.2, LOADPLUS no longer requires or supports the UNICODE installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

UPDMAXA=NO

The UPDMAXA option tells LOADPLUS whether to update the MAXASSIGNEDVAL column of SYSIBM.SYSSEQUENCES when loading identity column values from an input file.

Valid values for this option are YES and NO.

To enable LOADPLUS to update MAXASSIGNEDVAL when UPDMAXA=YES, one of the following authorization IDs must have ALTER privileges on the table that you are loading:

• User ID of the job owner, when UPDMAXA_AUTHID=USER
• INSTALL SYSADM, when UPDMAXA_AUTHID=INSTALLSYSADM

The UPDMAXA_AUTHID option controls which ID must have these privileges.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the UPDATEMAXA command option. 

UPDMAXA_AUTHID=USER

The UPDMAXA_AUTHID option controls which authorization ID must have ALTER privileges to enable LOADPLUS to update MAXASSIGNEDVAL when UPDATEMAXA YES is in effect. These privileges must be on the table that you are loading.

You can specify the following values:

• USER tells LOADPLUS to ensure that the user ID of the job owner has ALTER privileges.
• INSTALLSYSADM tells LOADPLUS to ensure that the INSTALL SYSADM authorization ID has ALTER privileges. 

UTILB_COLCCSID (obsolete)

In LOADPLUS version 11.1, this option told LOADPLUS whether to load (by invoking DSNUTILB) a table that contained columns defined with a CCSID specification.

Beginning with version 11.2, LOADPLUS no longer requires or supports the UTILB_COLCCSID installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

UTILB_NULLIX (obsolete)

In LOADPLUS 11.1, this option told LOADPLUS whether to load (by invoking DSNUTILB) table spaces that contained an index that was defined with EXCLUDE NULL KEYS.

Beginning with version 11.2, LOADPLUS no longer requires or supports the UTILB_NULLIX installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

UXSTATE=SUP

The UXSTATE option tells LOADPLUS how to invoke Db2 user exits:

• UXSTATE=SUP specifies that LOADPLUS should call Db2 user exits (such as EDITPROCs or date/time exits) in supervisor state (and PSW key=7).
• UXSTATE=PROB tells LOADPLUS to call Db2 user exits in problem state (and PSW key=7).

The requirements of the exits dictate the UXSTATE setting. Check with the exit author (or vendor) before changing to UXSTATE=PROB. 

WBUFFS=(20,10)

WBUFFS specifies a multiple of 32 KB to use to define the amount of buffer pool storage for each work (SYSUT1) data set. LOADPLUS allocates as many buffers as will fit into the calculated space.

LOADPLUS uses the first number if you specify only one work data set. LOADPLUS uses the second number for each data set if you specify multiple work data sets. For more information, see Performance-considerations-for-buffer-options. 

WORKDDN=SYSUT1

WORKDDN specifies a default ddname or ddname prefix for the index work data set. When using this name as a prefix, ensure that you allow sufficient bytes for LOADPLUS to add the number of indexes and still have a valid ddname (eight bytes or less). In addition, if you change the default ddname from SYSUT1 and you are not dynamically allocating your SYSUT1 data sets, you must change the name in your JCL. For more information, see SYSUT1-data-sets-in-LOADPLUS.

When invoking DSNUTILB, LOADPLUS uses this option only to pass a value for the &DDNAME variable for the data set name pattern. LOADPLUS includes this information in the TEMPLATE control statement that it builds for the IBM DB2 LOAD utility.

Overriding this option

You can override the value for this option by using the WORKDDN command option. 

WORKUNIT=SYSALLDA

WORKUNIT specifies the unit to use for a temporary work data set. VIO is an acceptable value for this option. 

WRLOG=NO

(SPE2005)

This feature is supported only for Db2 V12 with APAR PH11871 applied.

The WRLOG option specifies whether to write Db2 diagnostic log records to notify that a refresh is required for replicated objects.

The default is NO. The value YES invokes DSNUTILB with REPAIR to write Db2 diagnostic log records.

(BMC.DB2.SPE2401)When the BMCSYSADM user option parameter is present, LOADPLUS uses it for DSNUTILB REPAIR when WRLOG=YES is specified.

When SmartSwitch with the BMCSYSADM switches to a BMC AMI Utility, the BMCSYSADM and WRLOG are not passed to the BMC AMI Utility product. The BMC +SQLID and +WRLOG(YES) global parameters are used instead.

Overriding this option

There is no command to override WRLOG option.

XBLKS=3

XBLKS specifies the number of blocks per receiving process to use for the following types of transfers during the PRELOAD phase or the COMBINED phase:

• Data from the read task to the data process
• Index data from the data process to the index-building process

The minimum value is 3. For more information, see Performance-considerations-for-the-XBLKS-installation-option. 

XBMID=

XBMID specifies the XBM subsystem (SSID) that LOADPLUS accesses when it uses XBM or SUF. Specify a value for this option if you want to use a specific XBM subsystem for snapshot processing and zIIP processing in LOADPLUS.

The SSID is the unique identifier that was specified when XBM or SUF was installed. If you are using XBM or SUF in a Db2 data sharing environment, you can use the value of the XBMGROUP parameter instead of the XBM SSID. The XBMGROUP name is the name of the cross-system coupling facility (XCF) group that is defined to the XBM subsystem, and its default value is XBMGROUP.

If you specify an XBM subsystem, it must be:

• Available
• At a supported maintenance level
• Enabled for the required function

If you do not specify an XBM subsystem (either here or with the XBMID installation option), LOADPLUS automatically searches for an XBM subsystem that meets the same criteria. If you have multiple subsystems that meet these criteria, LOADPLUS can use any one of these subsystems.

For more information about using XBM or SUF with LOADPLUS, see XBM-and-SUF-considerations.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the XBMID command option. 

XML (obsolete)

In LOADPLUS 11.1 and earlier, this option told LOADPLUS whether to load XML data when DSNUTILB was required.

Beginning with version 11.2, LOADPLUS no longer requires or supports the XML installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete. 

XMLAVGSIZE=10M

The XMLAVGSIZE option provides LOADPLUS with an estimate of the actual size of your XML data. LOADPLUS uses this information to balance the number of tasks needed to load the base table, load the XML table space, and build the indexes. LOADPLUS also uses this information when allocating XML copy data sets.

Specify a number for the estimated size of your XML data, optionally followed by a unit of measure (K, M, or G). The default unit of measure is K. The minimum value that you can specify is 1K. The maximum value that you can specify is 2G, 2048M, or 2097152K.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option either at the global level, by using the XMLAVGSIZE option, or at the field level, by using the AVGSIZE field option on the CLOBF or XML field specification. The field-level option overrides the global option. 

ZEROROWRC=0

ZEROROWRC allows you to specify a default user-defined return code that LOADPLUS uses upon successful completion of the job when LOADPLUS does not load any rows. You can specify any integer from 0 through 7.

LOADPLUS always ends with the highest return code assigned during the load job. For more information, see Return-code-hierarchy-in-LOADPLUS.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the IFZEROROWS command option. 

ZIIP=ENABLED

The ZIIP option tells LOADPLUS whether to attempt to use IBM z Integrated Information Processors (zIIPs). LOADPLUS can use enclave service request blocks (SRBs) to enable zIIP processing automatically while running jobs. Using zIIP processing can reduce the overall CPU time for LOADPLUS jobs.

You can specify one of the following values:

• ENABLED tells LOADPLUS to attempt to offload eligible processing to an available zIIP. If the zIIP is busy or not available, normal processing continues on a general-purpose processor.
• DISABLED tells LOADPLUS not to attempt to use zIIP processing.

• (BMC.DB2.SPE2110)

   LEVEL1 tells LOADPLUS not to use zIIP offloading for new zIIP workload.

To enable and use zIIP processing with LOADPLUS, you must

• Have an installed authorized version of XBM or SUF
• Start and maintain an XBM subsystem in your environment
• Have a zIIP available in your environment

You can specify a particular XBM subsystem to use by specifying a value for the XBMID installation or command option. For more information, see XBMID.

For more information about using XBM or SUF with LOADPLUS, see XBM-and-SUF-considerations.

When invoking DSNUTILB, LOADPLUS ignores this option.

Overriding this option

You can override the value for this option by using the ZIIP command option.