REORG PLUS EXEC statement

The REORG PLUS EXEC statement specifies the module (ARUUMAIN) to be run for the REORG PLUS utility.

The EXEC statement also specifies the utility parameters, which are described in Utility parameters on the REORG PLUS EXEC statement.

You can include the REGION parameter on either your EXEC statement or your JOB statement. For recommendations, see REGION parameter.

When you are reorganizing a large number of partitions and dynamic allocation is active, BMC recommends 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, which 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 REORG PLUS EXEC statement

The REORG PLUS 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 reorganization
Message level
Installation options module parameter

The following illustration shows the format of the EXEC statement:

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

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

Db2 subsystem identifier (SSID)

This parameter specifies the four-character Db2 subsystem ID where the object resides.

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

Note the following considerations when running the utility in a data sharing environment:

The utility supports the Db2 group attachment name capability. When you supply a group attachment name as the SSID, the utility uses it to connect all plans. The utility then determines the actual Db2 SSID from within that group to use for the current reorganization.
When you are restarting in a data sharing environment, the utility can use either the same member that was chosen in the original reorganization or any other member in the specified group.
When both of the following conditions exist, specify a member SSID for your reorganization 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 level.

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, the utility uses the default, userID.jobName. Each BMC utility job should have a unique ID.

Utility IDs that include special characters might cause the utility to generate invalid data set names when using dynamic allocation. For more information, see the DSNPAT or DSNAME option description.

Restart parameter

The restart parameter can have one of the values described in this section. For more information about specific circumstances for which you should use a particular value, see Restarting-REORG-PLUS.

DSNUTILB reorganizations

After the UTILINIT phase, REORG PLUS passes the restart parameter to DSNUTILB. Restart processing is handled by the IBM Db2 REORG utility.

Option	Description
Blank or not specified	By not specifying a restart parameter, REORG PLUS initiates a new BMC utility job. The utility ID that you specify cannot currently exist in the BMCUTIL table.
FORCEID (PTF BQU1094 applied)	FORCEID is equivalent to . If the SmartSwitch feature switches a job from REORG PLUS to the BMC AMI Reorg for Db2 (BMC AMI Reorg) product, FORCEID then operates the same way as FORCEID in BMC AMI Reorg. For information about FORCEID in BMC AMI Reorg, see FORCEID. For information about SmartSwitch, see Overview-of-SmartSwitch-feature. Warning Seek instructions from BMC Customer Support before using FORCEID.
MAINT	Specifying this value forces MSGLEVEL(1) and causes REORG PLUS to print the following information: An options module report that lists the values in the installation options module that you are using for this reorganization The values in the DSNHDECP module that REORG PLUS uses A summary report of all REORG PLUS 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 a SYSPRINT DD statement and STEPLIB to the REORG PLUS and Db2 load libraries.
NEW	NEW initiates a new BMC utility job or replaces an existing utility ID. Specifying this value keeps you from having to end the utility ID separately and then start a utility specifying a blank restart parameter. Warning Use care when you specify NEW. When you replace or terminate a utility ID for REORG PLUS, you might lose data from the UNLOAD or REORG phase, and you cannot restart the utility. If you specify NEW and the utility ID has a status of X (executing), REORG PLUS issues error message BMC50012E and ends with return code 8.
NEW/RESTART	BMC recommends that you specify NEW/RESTART for the restart parameter value. REORG PLUS takes restart sync points as it completes each phase and as it completes the processing of each Db2 object. If the utility ID exists, NEW/RESTART restarts the utility from the last restart sync point. Otherwise, this value starts the utility as NEW. Using NEW/RESTART enhances restartability for a SHRLEVEL CHANGE reorganization. REORG PLUS treats NEW/RESTART the same as NEW if the previous run was a SHRLEVEL CHANGE reorganization that failed before the UTILTERM phase.
NEW/RESTART(PHASE)	This value restarts the utility at the beginning of the last incomplete phase if the utility ID exists. Otherwise, this value starts the utility as NEW.
RESTART	Specifying this value restarts a BMC utility from the last restart sync point. REORG PLUS 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, REORG PLUS ends with return code 8.
RESTART(PHASE)	This value restarts a BMC utility at the beginning of the last incomplete phase. The utility ID must exist in the BMCUTIL table. If the utility ID does not exist in the BMCUTIL table, REORG PLUS ends with return code 8.
TERM	Specifying this value terminates an existing utility, removes the utility ID from the BMCUTIL table, and removes the corresponding rows from the BMCSYNC and BMCDICT tables. After removing all sync point and restart information, REORG PLUS terminates without performing a reorganization. REORG PLUS terminates with return code 0, regardless of whether the utility ID exists. When invoking DSNUTILB, REORG PLUS also terminates an existing Db2 utility ID. The minimum JCL that is required when specifying TERM is the STEPLIB to the REORG PLUS load library and the SYSPRINT DD statement. Warning Use care when you specify TERM. When you terminate a utility ID for REORG PLUS, you might lose existing data from the UNLOAD or REORG phase, and you cannot restart the utility. Similar consequences can occur in other BMC utilities. For more information, see LOADPLUS EXEC statement or UNLOAD PLUS EXEC statement.

User identifier (user ID)

This parameter specifies the TSO user ID that the utility notifies after it completes each phase and after it completes the command execution.

Message level (MSGLEVEL)

This parameter controls which messages REORG PLUS returns to the user 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 set the default value of this parameter. For details, see the description of this option in Descriptions-of-basic-installation-options.

Installation options module

The options module 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, REORG PLUS uses the default installation options module, ARU$OPTS.

For more information about installation options, see REORG-PLUS-installation-options. In addition, the Installation System documentation explains how to create multiple installation options modules.