LOADPLUS EXEC statement

The LOADPLUS EXEC statement specifies the module to be executed for the LOADPLUS utility.

The LOADPLUS module name is AMUUMAIN. The EXEC statement also specifies LOADPLUS utility parameters, which are described in Utility parameters on the LOADPLUS EXEC statement, below.

You can use the REGION parameter to specify the region size on either your EXEC statement or your JOB statement. For recommendations, see REGION parameter.

When you are loading a large number of partitions and dynamic allocation is active, we recommend that you specify DYNAMNBR=1600 on the EXEC statement of your execution JCL. Including this parameter enables the system to acquire adequate resources immediately before their use and to release them immediately after use.

REGION parameter

Include the REGION parameter on either your JOB statement or your EXEC statement to specify the region size (the amount of virtual storage used by the utility).

For the best performance, we recommend that you specify REGION=0M to allocate the optimal amount of available virtual storage to the utility job. If your data center does not permit you to specify REGION=0M, specify the amount that allows the most virtual storage both above and below the 16-megabyte line. Using a region size that is less than optimal risks the following potential issues:

Running less efficiently, could result in additional CPU and elapsed time
Encountering memory failures or jobs that fail when new versions implement changes that require additional memory

Important

If you specify a value for REGION other than 0M, ensure that you have an appropriate value set for the MEMLIMIT parameter, either as your site’s default SMF option or on your JOB statement or EXEC statement.

Specify NOLIMIT to allow unlimited above-the-bar memory.
If you are unable to specify NOLIMIT, specify at least 4 GB; if you are operating on LOB or XML data, specify at least 32 GB.

Utility parameters on the LOADPLUS EXEC statement

The LOADPLUS EXEC statement includes the following utility parameters:

DB2 subsystem ID or group attachment name
Utility ID
Restart parameter
TSO user ID for notification of progress made on the load
Message level
Installation options module

The following illustration shows the format of the EXEC statement:

//<stepName> EXEC PGM=AMUUMAIN,
//PARM='<ssid>,<utilityID>,<restartParameter>,<userID>,MSGLEVEL(<n>),<optionsModule>'

The LOADPLUS utility parameters are positional. If you do not specify a value for a parameter (thus allowing the default value), you must substitute a comma for that parameter if additional parameters follow. The comma indicates that a parameter was omitted.

DB2 subsystem identifier (SSID)

This parameter specifies the four-character Db2 subsystem ID (SSID) that indicates where the table space resides.

If you do not specify the SSID, LOADPLUS uses the Db2 installation default from the DSNHDECP module. LOADPLUS depends on the application defaults module being named DSNHDECP. If you do not specify an SSID and LOADPLUS cannot find a module named DSNHDECP in your LINKLIST or STEPLIB, LOADPLUS terminates.

The following considerations apply when running LOADPLUS in a data sharing environment:

When you supply a group attachment name as the SSID, LOADPLUS uses the name to connect all plans. LOADPLUS then determines the actual Db2 SSID from within that group to use for the current load job.
When restarting in a data sharing environment, LOADPLUS might use any member of the specified group.
When both of the following conditions exist, specify a member SSID for your load job instead of a group attachment name. Ensure that the Db2 version of the SSID that you specify corresponds to the version of the Db2 load library that you specify in your STEPLIB.
- You are using table space compression.
- The subsystems in your data sharing group are not all at the same DB2 version.

Utility identifier (utility ID)

This parameter specifies the 1- to 16-character utility ID that gives a unique name to a utility job. If you omit this parameter, LOADPLUS uses the default, userID.jobName. Each BMC Software utility job should have a unique utility ID.

Important

Utility IDs that include special characters might cause LOADPLUS to generate invalid data set names when using dynamic allocation. For more information, see the discussion about using the utility ID variable with the DSNPAT option on DSNPAT.

Restart parameter

The restart parameter can have one of the following values:

Blank or not specified
RESTART
RESTART(PHASE)
NEW
NEW/RESTART
NEW/RESTART(PHASE)
TERM
MAINT

For more information about specific circumstances for which you should use a particular value, see Restarting-LOADPLUS.

For DSNUTILB jobs, LOADPLUS passes the restart parameter to DSNUTILB after the UTILINIT phase. Restart processing is handled by the IBM Db2 LOAD utility.

Value	Description
Blank or not specified	By not specifying a restart parameter, LOADPLUS initiates a new BMC utility job. The utility ID that you specify cannot currently exist in the BMCUTIL table.
RESTART	With the following exception, specifying this value restarts a BMC utility from the last restart sync point. LOADPLUS takes restart sync points as each phase completes and as the processing of each Db2 object completes. The utility ID must exist in the BMCUTIL table. If the utility ID does not exist in the BMCUTIL table, LOADPLUS ends with return code 8. Exception: For partition-by-growth table spaces when the LOAD or COMBINED phase has not been completed, LOADPLUS restarts at the first new row written during the original job. LOADPLUS starts the copy process with the first copy that did not completed.
RESTART(PHASE)	For a two-phase load, specifying this value restarts LOADPLUS at the beginning of the last incomplete phase. In general, for a single-phase load or for an SQLAPPLY load, LOADPLUS treats RESTART(PHASE) as if you specified RESTART. The utility ID must exist in the BMCUTIL table. If the utility ID does not exist in the BMCUTIL table, LOADPLUS ends with return code 8. Exception: For partition-by-growth table spaces when the LOAD phase has not completed, LOADPLUS restarts at the first new row written during the original job. LOADPLUS starts the copy process with the first copy that did not completed.
NEW	Specifying this value initiates a new BMC utility job or replaces an existing utility ID. Specifying this value allows you to start a utility without having to end the utility ID separately. Warning Use care when you specify NEW. When you replace or terminate a utility ID for LOADPLUS, data from the PRELOAD or COMBINED phase is lost and existing data in the table space can also be lost. If you specify NEW and the utility ID has a status of X (executing), LOADPLUS issues the error message BMC50012E and ends with return code 8.
NEW/RESTART	With the following exception, specifying this value restarts a BMC utility from the last restart sync point if the utility ID exists. Otherwise, specifying this value starts a utility as NEW. LOADPLUS takes restart sync points as each phase completes and as the processing of each Db2 object completes. Exception: For partition-by-growth table spaces when the LOAD or COMBINED phase has not been completed, LOADPLUS restarts at the first new row written during the original job. LOADPLUS starts the copy process with the first copy that did not completed.
NEW/RESTART(PHASE)	For a two-phase load, specifying this value restarts LOADPLUS at the beginning of the last incomplete phase if the utility ID exists. Otherwise, for a two-phase load, specifying this value starts LOADPLUS as NEW. Exception: For partition-by-growth table spaces when the LOAD phase has not been completed, LOADPLUS restarts at the first new row written during the original job. LOADPLUS starts the copy process with the first copy that did not completed. In general, for a single-phase load or for an SQLAPPLY load, LOADPLUS treats NEW/RESTART(PHASE) as if you specified NEW/RESTART.
TERM	Specifying this value terminates the existing utility, removes the utility ID from the BMCUTIL table, and removes the corresponding rows from the BMCUTIL2, BMCSYNC, and BMCDICT tables. After removing all sync points and restarting information, LOADPLUS terminates without performing a load. LOADPLUS terminates with return code 0, regardless of whether the utility ID exists. For a DSNUTILB load, LOADPLUS also terminates an existing Db2 utility ID. When specifying TERM, you need only minimal JCL. Your JCL must include at least an SYSPRINT DD statement and STEPLIB to the LOADPLUS load library. Warning Use care when you specify TERM. When you replace or terminate a utility ID, data from the PRELOAD phase or the COMBINED phase is lost and existing data in the table space can also be lost.
MAINT	Specifying this value forces MSGLEVEL(1) and causes LOADPLUS to print the following information: An options module report that lists the values in the installation options module that you are using The values in the DSNHDECP module that LOADPLUS uses (which is the DSNHDECP module that Db2 loads) A summary report of all of the product fixes that you have applied When you specify the MAINT parameter, the job ends without affecting any utility that is running. For this parameter, you need only minimal JCL. Your JCL must include at least an SYSPRINT DD statement and STEPLIB to the LOADPLUS and Db2 load libraries.

User identifier (user ID)

This parameter specifies the TSO user ID that LOADPLUS notifies after the completion of each phase and at the end of utility command execution.

Message level (MSGLEVEL)

This parameter controls which messages 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.

You can use the MSGLEVEL installation option to change the default value of this parameter. For details, see MSGLEVEL=1.

Installation options module

This parameter allows you to identify which installation options module to use. If you include this parameter, you must specify the full name of the options module. If you omit this parameter, LOADPLUS uses the default installation options module, AMU$OPTS.

For more information about installation options, see Installation-options. For information about how to create multiple installation options modules, see Installation System.