CM batch parameter definitions

You can use Change Management (CM) batch interface parameters to control Change Management (CM) actions and settings.

For the parameters that control utility options, see Utility option parameters. All other CM batch parameters are included in the following list in alphabetical order.
Note: If a parameter has two values listed together, such as YES or Y, the second value (in this case Y) is the short value. Either value is acceptable; they both have the same meaning.
ACCELERATOR_LOAD_LOCKMODE
Specifies the lock mode for the SYSPROC.ACCEL_LOAD_TABLES procedure for accelerated tables.
Values:
TABLESET
TABLE
ROW
PARTITIONS
NONE
Default:
TABLESET

For details on the possible values of lock mode, see the information about lock_mode in SYSPROC.ACCEL_LOAD_TABLES (IBM DB2 Analytics Accelerator for z/OS 7.5).

ACCEPT_FL
Specifies the maximum Db2 version function level (FL) with which the CM batch job is allowed to continue.

If the specified value is greater than the function level that is supported by Db2 Admin Tool, a warning message is issued.

If the specified value is less than the current function level value of the Db2 subsystem, an error message is issued and the CM batch job is terminated.

Values:
An integer value in the range 501 - 999.
Default:
blank

A blank value means that CM batch jobs are not allowed to run if the current function level of the Db2 subsystem is greater than the function level that is supported by Db2 Admin Tool.

ACTION_ANALYZE_CHANGE
Specifies whether to analyze a change. If a change is also being imported, the change that is analyzed is the newly imported change. Otherwise, the change to be analyzed is identified by the CHANGE_OWNER and CHANGE_NAME parameters.
Values:
Y
Specifies that the change identified by the CHANGE_OWNER and CHANGE_NAME parameters is analyzed. If a change is also being imported, the change that is analyzed is the change identified by the NEW_CHANGE_OWNER and NEW_CHANGE_NAME parameters. A change that is already in ANALYZED state is reanalyzed.
N
Specifies that no change is analyzed.
C
Same as the Y parameter value except that the analyze is not done if the change is already in the ANALYZED state. For the C parameter, return codes of 0 and 1 are defined as follows:
  • 0 indicates that analyze is not done because the change is already in the ANALYZED state.
  • 1 indicates that analyze is done, and no warnings or errors are issued. The state is the same the state of ACTION_ANALYZE_CHANGE = 'Y' with RC=0.
There are no changes to the meanings of other RC values.
blank
Specifies that this parameter defaults to Y if a change is imported during this call to the Change Management batch interface.
Default:
blank
ACTION_BUILD_RUN_JOB
Specifies whether a run job is created for a change. If a change is also being imported, a run job is created for the newly imported change. Otherwise, a run job is created for the change identified by the CHANGE_OWNER and CHANGE_NAME parameters.
Values:
Y
Specifies that a run job is created for the change identified by the CHANGE_OWNER and CHANGE_NAME parameters. If a change is also being analyzed, a run job is created for the change after it is analyzed.
N
Specifies to not create a run job for the change.
blank
Specifies that this parameter should default to Y if a change is analyzed during this call to the Change Management (CM) batch interface.
Default:
blank
ACTION_CANCEL_CHANGE
Specifies whether to cancel a change that is specified by the CHANGE_OWNER and CHANGE_NAME parameters. No other CM Batch actions are allowed when you are requesting a change to be canceled. Any type of change can be canceled except for a multi-target change and a change that is in COMPLETE state.
Values
U
Specifies an unconditional cancel change. The specified change is canceled even if other changes have the change as a prerequisite. If other changes have the change as a prerequisite, the changes that depend on the change that is being canceled are set to DEFINED status and must be analyzed before being run. A list of changes that have the change to be canceled as a prerequisite are listed.
C
Specifies a conditional cancel change. The specified change is canceled if no other changes have the change as a prerequisite change. If other changes have the change as a prerequisite change, an error message is issued. A list of changes that have the change to be canceled as a prerequisite are listed.
N
Specifies to not cancel the change.
Default
N
ACTION_COMPARE
Specifies whether to run the IBM® Db2 Object Comparison Tool for z/OS to define a change that can be imported and managed by Db2 Admin Tool Change Management.
Values
Y
Specifies to run Db2 Object Comparison Tool to define a change that can be managed by Db2 Admin Tool Change Management. A compare report and a delta change file is generated that can be imported as a new change. The delta change file attributes are taken from the parameters for ADMIN_DATASET_TYPE = 'DELTA'.

By specifying ACTION_COMPARE = 'Y' and ACTION_IMPORT_CHANGE = 'N', you can run Db2 Object Comparison Tool to just generate a compare report and delta change file, without importing the result as a change. This setting enables you to view the differences between the compare source and target, and perhaps run the compare multiples times to fine-tune the differences between the source and target. When no more compares are needed and the change is ready to be deployed, the delta change file can be imported as a new change.

The files with DD names that start with IMCHG are not used.
N
Specifies to not run Db2 Object Comparison Tool to define the change.
Default
N
ACTION_CONVERT_TO_ISPF_WSL
Specifies whether the text WSL given by the CM batch parameters will be converted to an ISPF table format. This parameter is supported by CAF.
Values:
Y
Converts the readable work statement list (WSL) to an ISPF table. The readable WSL is specified by the PDS_FOR_WSL_CONV and WORKLIST_NAME_CONV parameters. The ISPF WSL is specified by the PDS_FOR_WSL and WORKLIST_NAME parameters.
N
Does not convert the WSL.
Default:
N
ACTION_CONVERT_TO_READ_WSL
Specifies whether the WSL that is given by the CM batch parameters will be converted to a readable data set. This parameter is supported by CAF.
Values:
Y
The WSL will be converted to a readable data set that is specified by the parameters PDS_FOR_WSL_CONV and WORKLIST_NAME_CONV.
N
Does not convert the WSL.
Default:
blank
ACTION_DELETE_CHANGE
Specifies whether to delete a change specified by the CHANGE_OWNER and CHANGE_NAME parameters. No other CM Batch actions are allowed when you are requesting a change to be deleted. Any type of change can be deleted except for a multi-target change.
Values
C
Specifies a conditional delete change. The specified change is deleted if no other changes have the change as a prerequisite. If other changes have the change as a prerequisite, an error message is issued. A list of changes that have the change to be deleted as a prerequisite are listed.
N
Specifies to not delete the change.
U
Specifies an unconditional delete change. The specified change is deleted even if other changes have the change as a prerequisite. If other changes have the change as a prerequisite, the changes that depend on the change that is being deleted are set to DEFINED status and must be analyzed before being run. A list of changes that have the change to be deleted as a prerequisite are listed.
Default
N
Start of changeACTION_DELETE_MASKEnd of change
Start of changeSpecifies whether to delete the mask specified by the MASK_OWNER and MASK_NAME parameters. No other CM Batch actions are allowed when you are requesting a mask to be deleted.
Values
C
Delete the mask if it is not associated with a registered change that needs the mask for implementation. If the mask is needed by one or more changes for implementation, the names of changes are displayed and the mask is not deleted.

CONDITIONAL mode does not cover the scenario in which changes can have a mask associated with it but the mask is no longer needed to implement the change. For example, when a change is imported using masking, after the import completes the mask is no longer needed to implement that change.

N
The delete mask action is not enabled.
U
Delete the mask even if it is associated with a registered change that needs the mask for implementation. The names of changes that need the mask for implementation are displayed and the mask is deleted.

UNCONDITIONAL mode does not cover the scenario in which changes can have a mask associated with it but the mask is no longer needed to implement the change. For example, when a change is imported using masking, after the import completes the mask is no longer needed to implement that change. In this scenario, UNCONDITIONAL does not report the imported change.

Default
N
End of change
ACTION_EXPORT_CHANGE
Specifies whether to export the indicated changes into a delta change file. The changes to export are identified by using the CHANGE_OWNER and CHANGE_NAME parameters. Each pair of CHANGE_OWNER and CHANGE_NAME parameters must end with a semi-colon. For example, to export changes A.C1 and A.C2, in this order, the following set of parameters can be specified:
//PARMS DD *

ACTION_EXPORT_CHANGE = 'ASIS'

CHANGE_OWNER = 'A'

CHANGE_NAME = 'C1';

CHANGE_OWNER = 'A'

CHANGE_NAME = 'C2';

The delta change file is created according the template for ADMIN_DATASET_TYPE = 'DELTA'. For more information about these templates, see Db2 Admin Tool data set templates .

Values
ASIS
The specified changes are exported in the order that is specified by the CHANGE_OWNER and CHANGE_NAME parameters.
PREREQ
Db2 Admin Tool analyzes the specified changes for prerequisites and includes any prerequisite changes for the listed changes.
NO
The changes are not exported.
Default
NO
ACTION_GENERATE_BASE_VERSION
Specifies whether and how to generate a base version. This parameter enables you to start Change Management (CM) batch interface only to generate a base version. The GENERATE_BASE_VERSION_BEFORE_RUN and GENERATE_BASE_VERSION_AFTER_RUN parameters enable you to configure Change Management (CM) batch interface so that base versions are automatically generated during the run change process. Generating a base version by using the ACTION_GENERATE_BASE_VERSION parameter and choosing to generate DDL from a base version (GENERATE_DDL_FROM_BASE_VERSION parameter) in the same invocation of Change Management (CM) batch interface enables to you save the current definitions of objects in the base version and also to generate a DDL file from these object definitions.
Values:
AUTO
A base version is generated and the content is automatically determined by the product for the specified change entry. The content of the base version is based on the registered change statements for the specified change entry.
USER
A base version is generated and the content is determined by a user-specified version scope.
NO
A base version is not generated. However, this setting has no control over whether a base version is automatically generated as determined by the GENERATE_BASE_VERSION_BEFORE_RUN and GENERATE_BASE_VERSION_AFTER_RUN parameters.
Default:
NO
ACTION_GENERATE_DDL_FROM_BASE_VERSION
Specifies whether to generate DDL from a base version. The generated file must be run by using the Db2 Admin Tool ADBTEP2 program. See ADBTEPR SAMP member for a sample job of running ADBTEP2.
Values:
BEFORE_RUN
DDL and Db2 Admin Tool statements are generated for the base version that was created before the specified change was implemented.
AFTER_RUN
DDL and Db2 Admin Tool statements are generated for the base version that was created after the specified the change was implemented.
SOURCE
DDL and Db2 Admin Tool statements are generated for the base version that is recorded as the source base version for the specified change.
TARGET
DDL and Db2 Admin Tool statements are generated for the base version that is recorded as the target base version for the specified change.
USER
DDL and Db2 Admin Tool statements are generated for the user-specified base version that is identified by the BASE_VERSION_OWNER and BASE_VERSION_NAME parameters.
NO
DDL and Db2 Admin Tool statements are not generated for any base version.
Default
NO
ACTION_GENERATE_JCL_FROM_WSL
Generate JCL based on an existing WSL or a WSL that is being generated in the same batch job by Db2 Object Comparison Tool.
Values:
Y
Generate JCL for one of the following WSLs:
  • An existing WSL. In this case, you must specify the PDS_FOR_WSL parameter and the following parameter values:
    ACTION_COMPARE = 'N'
    ACTION_GENERATE_WSL = 'N'
  • A WSL that is being generated while running a comparison that does not use Change Management. This action is indicated by the following parameter values:
    ACTION_COMPARE = 'Y'
    ACTION_GENERATE_WSL = 'Y'
    In this case, the PDS_FOR_WSL parameter is optional.

If you specify Y, the WORKLIST_NAME parameter is required and is used for the JCL member name. Optionally, you can use the PDS_FOR_RUN_JCL parameter to specify the name of partitioned data set (PDS). You cannot specify any other ACTION_xxxx parameter.

N
Do not generate JCL.
Default:
N
ACTION_GENERATE_WSL
Specifies whether to generate a work statement list (WSL) when ACTION_COMPARE=Y. This option is ignored when a value for the ACTION_COMPARE parameter is not specified or it is set to N.
Values:
Y
Yes. A work statement list is generated when ACTION_COMPARE= Y. Such a work statement list can be run directly by specifying ACTION_RUN_WSL=Y.

If you specify Y, you must specify ACTION_IMPORT_CHANGE=N.

N
No. A WSL is not generated.
Default:
N
ACTION_IMPORT_CHANGE
Specifies whether a change is imported. If ACTION_COMPARE = 'N', the DDL or delta change files that are defined by the files that begin with IMCHG (for example, IMCHG001, IMCHG002, and so on) are imported as a new change. If ACTION_COMPARE = 'Y', the result of the compare is imported as a new change.
Values:
Y
If ACTION_COMPARE = 'N', specifies that the content of files IMCHG001 up through IMCHG999 are imported into a new change. You do not need to define all of the IMCHG* files must be defined. For example, only 2 DDL files or delta change files is imported, you need to define only IMCHG001 and IMCHG002.
If ACTION_COMPARE = 'Y', specifies that the result of the compare is imported as a new change. The contents of the files with names IMCHG001 through IMCHG999 are not imported as a new change.
N
Specifies that no importing of a change is done.
blank
Specifies that this parameter defaults to Y if either of the following is true:
  1. ACTION_COMPARE = 'N', and the IMCHG001 DD is defined and not empty.
  2. ACTION_COMPARE = 'Y'.
Default:
blank
ACTION_IMPORT_IGNORE
Specifies whether an ignore that is defined by the IMIGNORE DD statement is imported as a new ignore.
Values:
Y
Specifies that the content of the IMIGNORE DD statement is imported into a new ignore.
N
Specifies that no importing of an ignore is done.
blank
Specifies that this parameter defaults to Y if the IMIGNORE DD statement is defined and not empty.
Default:
blank
ACTION_IMPORT_MASK
Specifies whether a mask that is defined by the IMMASK DD statement is imported as a new mask.

Start of changeOptionally, use the NEW_MASK_OWNER and NEW_MASK_NAME parameters to specify the owner and the name of the imported mask. End of change

Values:
Y
Specifies that the content of the IMMASK DD statement is imported into a new mask.
N
Specifies that no importing of a mask is done.
blank
Specifies that this parameter defaults to Y if the IMMASK DD statement is defined and not empty.
Default:
blank
ACTION_RECOVER_CHANGE
Specifies whether to recover the change.
Values:
Y
Specifies to recover the change.
N
Specifies to not recover the change.
Default:
N
ACTION_RUN_CHANGE
Specifies whether to run the change. If a change is also being imported, the change that is run is the newly imported change. Otherwise, the change to be run is identified by the CHANGE_OWNER and CHANGE_NAME parameters.
Values:
Y
Runs the change.
N
Does not run the change.
Default:
N
ACTION_RUN_WSL
Specifies whether to run a WSL.
Values:
Y
Runs the work statement list. The PDS_FOR_WSL parameter must be provided to indicate the PDS where the work statement list resides. The WORKLIST_NAME parameter must be provided to specify the PDS member.
N
Does not run the WSL.
Default:
N
ADBTEP2_AC
Specifies whether to use autocheck when a change is run. Certain SQL or utility operations can place an object into check-pending state. If you set the Autocheck (AC) parameter value to YES, run change (ADBTEP2) tracks the statements and processes that can place an object in check-pending. If one of these statements is encountered while running a change, an automatic CHECK DATA is done to remove the check-pending state. For the complete description see The Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
YES
The automatic check process is performed.
NO
The automatic check process is not performed.
Default:
NO
ADBTEP2_ADVISORYAUTOREBUILD
Specifies whether the product, when a change is run, initiates a REBUILD when an object is in certain rebuild pending states. For the complete description and list of values see The Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
YES
The product automatically attempts a REBUILD if the object is in the ARBDP state.

However, if the parameter RUN_REORG_REBUILD was specified as 'A - All relevant' to generate an explicit REBUILD during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REBUILD that duplicates the explicit REBUILD.

NO
The product does not automatically attempt a REBUILD if the object is in the ARBDP state.
Default:
NO
ADBTEP2_ADVISORYAUTOREORG
Specifies whether the product, when a change is run, initiates a REORG when an object is in certain reorganization-pending states. For the complete description see The Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
YES
The product automatically attempts a REORG if the object is in AREOR or AREO* state.

However, if the parameter RUN_REORG_REBUILD was specified as 'A - All relevant' to generate an explicit REORG during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REORG that duplicates the explicit REORG.

NO
The product does not automatically attempt a REORG if the object is in AREOR or AREO* state.
Default:
NO
Start of changeADBTEP2_AUTOREBINDEnd of change
Start of changeControls whether an automatic rebind is performed during ADBTEP2 processing.
Values:
YES or Y
An automatic rebind will be performed when packages are invalidated by processed statements.
NO or N
An automatic rebind will be not performed.
ALL or A
An automatic rebind will be performed when packages are invalidated by processed statements. Additionally, a REBIND command is generated when a new index is created on the table so that the access paths are refreshed for dependent packages. ALL requires the ADBTEP2_AUTOREBIND_APREUSE value to be NONE or blank.
Default:
NO

If ADBTEP2 is processing a REBIND statement that was generated by Object Compare, ADBTEP2 does not generate the same REBIND operation.

If you request that automatic rebinds be performed (ADBTEP2_AUTOREBIND = YES or ALL), you can set the following additional values to control the REBIND options:

End of change
Start of changeADBTEP2_AUTOREBIND_APREUSEEnd of change
Start of changeSpecifies whether Db2 is to try to reuse previous access paths for SQL statements in the package when performing an automatic rebind during ADBTEP2 processing. ADBTEP2_AUTOREBIND_APREUSE is applicable only if ADBTEP2_AUTOREBIND is set to YES. If ADBTEP2_AUTOREBIND is set to ALL, ADBTEP2_AUTOREBIND_APREUSE must be NONE or blank.
Values:
NONE or N
APREUSE(NONE) is added to the REBIND statement.
WARN or W
APREUSE(WARN) is added to the REBIND statement.
ERROR or E
APREUSE(ERROR) is added to the REBIND statement.
blank
The APREUSE option is not added to the REBIND statement.
Default:
blank
End of change
Start of changeADBTEP2_AUTOREBIND_EXPLAINEnd of change
Start of changeSpecifies whether an automatic rebind during ADBTEP2 processing is to capture EXPLAIN information for SQL statements in the package. ADBTEP2_AUTOREBIND_EXPLAIN is applicable only if ADBTEP2_AUTOREBIND is set to YES or ALL.
Values:
YES or Y
EXPLAIN(YES) is added to the REBIND statement.
NO or N
EXPLAIN(NO) is added to the REBIND statement.
ONLY
EXPLAIN(ONLY) is added to the REBIND statement
blank
The EXPLAIN option is not added to the REBIND statement.
Default:
blank
End of change
Start of changeADBTEP2_AUTOREBIND_OWNEREnd of change
Start of changeSpecifies the package owner for an automatic rebind during ADBTEP2 processing. ADBTEP2_AUTOREBIND_OWNER is applicable only if ADBTEP2_AUTOREBIND is set to YES or ALL.
Values:
A valid owner name. The maximum length is 128 characters.
Default:
blank
End of change
Start of changeADBTEP2_AUTOREBIND_OWNERTYPEEnd of change
Start of changeSpecifies whether the owner that is specified for ADBTEP2_AUTOREBIND_OWNER is a role or user authorization ID.
Values:
USER or U
OWNERTYPE (USER) is added to the REBIND statement.
ROLE or R
OWNERTYPE (ROLE) is added to the REBIND statement.
blank
The OWNERTYPE option is not added to the REBIND statement.
Default:
blank
End of change
Start of changeADBTEP2_AUTOREBIND_ADDITIONAL_OPTSEnd of change
Start of changeSpecifies any additional REBIND options, such as FLAG(I) IMMEDWRITE(NO), for any automatic rebinds during ADBTEP2 processing. ADBTEP2_AUTOREBIND_ADDITIONAL_OPTS is applicable only if ADBTEP2_AUTOREBIND is set to YES or ALL.
Values:
A string up to 325 characters. The specified additional options are added to the REBIND statement as is; the syntax is not checked or formatted. The specified options apply only to rebinds of packages with TYPE=' ' (blank) and not to trigger, procedure, or function packages.
Default:
blank
End of change
ADBTEP2_AUTOREBUILD
Specifies whether the product, when a change is run, initiates a REBUILD when an object is in certain rebuild pending states. For the complete description see The Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
YES
The product automatically attempts a REBUILD if the object is in one of these states: RBDP, RBDP*, or PSRBD state.

However, if the parameter RUN_REORG_REBUILD was specified as 'M - Mandatory' or 'A - All relevant' to generate an explicit REBUILD during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REBUILD that duplicates the explicit REBUILD.

NO
The product does not automatically attempt a REBUILD if the object is in one of these states: RBDP, RBDP*, or PSRBD state.
Default:
YES
ADBTEP2_AUTOREORG
Specifies whether the product, when a change is run, initiates a REORG when an object is in certain reorganization-pending states. For the complete description see The Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
YES
The product automatically attempts a REORG if the object is in the REORP state.

However, if the parameter RUN_REORG_REBUILD was specified as 'M - Mandatory' or 'A - All relevant' to generate an explicit REORG during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REORG that duplicates the explicit REORG.

NO
The product does not automatically attempt a REORG if the object is in the REORP state.
Default:
YES
ADBTEP2_BINDERROR
Specifies how BIND or REBIND errors are handled when running a change. For the complete description see The Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
MAXE
Start of changeThe failed command is written to the ADBHOLD table. The MAXERROR setting (as specified by the ADBTEP2_MAXE parameter) determines if the processing stops immediately, after nn errors, or if the bind error does not stop processing. End of change
SAVE
The failed command is written to the ADBHOLD table. Processing continues.
IGNORE
The failed command is not written to the ADBHOLD table. Processing continues.
Default:
MAXE
Start of changeADBTEP2_MAXEEnd of change
Start of changeSpecifies the maximum number of errors. Specifically, this parameter indicates the number of DSN commands that can fail before the batch job is terminated.
Values:
-1
All errors are ignored. The batch job does not stop for any error.
0
No errors are allowed. The batch job stops on the first error.
1-99
The specified number of errors are ignored. The batch job stops on the next DSN command that fails. For example, if you specify 5, the batch job stops when the sixth DSN command fails.
For more information about MAXE, see Parameters passed to the ADBTEP2 program.
Default:
0
End of change
ADBTEP2_PENDINGCHANGESCHECK
Specifies whether a check is made when a change is run to avoid losing any Db2 pending changes as part of a DROP action.
Values:
YES
The DROP is not performed if a Db2 pending change exists.
NO
The DROP is performed without checking for pending changes.
Default:
NO
ADBTEP2_RESTART
Specifies the RESTART value that is passed to the ADBTEP2 (adbtepx) program. You can restart a change at the beginning of the change WSL, at the point where the change stopped running in a previous run, or at a particular point in the WSL that you specify.
Values:
Y
Yes. RESTART(YES) is used when ADBTEP2 is called.
N
No. RESTART(NO) is used when ADBTEP2 is called.
F
Force. RESTART(FORCE) is used when ADBTEP2 is called.
U
User. RESTART(USER_RESTART_NAME) is used when ADBTEP2 is called. If you specify U, you must specify a value for the ADBTEP2_USER_RESTART_NAME parameter.
Default:
Y
ADBTEP2_USER_RESTART_NAME
Specifies the name of the location where you want to restart the ADBTEP2 run of the WSL, irrespective of the previous failure point. If ADBTEP2_USER_RESTART=U is specified, this parameter is required.
Values:
A valid restart location. 1 - 128 characters.
Default:
blank
ADBTEP2_RESTART_ENV
Specifies the use of checkpoint record environment variables, if they are present, during the restart and execution of set statements in the WSL prior to the restart point.
Values:
CKPT
Uses the environment variables from the checkpoint record during the restart, if they are present.
INPUT
Runs set statements in the WSL before the restart point.
BOTH
Uses the environment variables from the checkpoint record during the restart, if they are present, and runs set statements in the WSL before the restart point.
Default:
The default value is blank.
ADBTEP2_RESTART_REPORT_ONLY
Specifies whether to actually run the restart job or to only simulate the run.
Values:
Y
Yes
N
No
Default:
blank
ADBTEP2_RESTART_SQLID
Specifies the SQL ID to use at the restart point.
Values:
A valid SQL ID. 1 - 8 characters.
Default:
blank
ADBTEP2_RESTART_SCHEMA
Specifies the current schema special register to use at the restart point. Valid values are 1 - 128 characters. The default value is blank.
Values:
A valid schema name. 1 - 128 characters.
Default:
blank
ADBTEP2_RESTART_SERVER
Specifies the location name of the current server.
Values:
A valid location name. 1 - 16 characters.
Default:
blank
ADBTEP2_RESTART_PATH
Specifies the SQL path that is used when unqualified function names, procedure names, data type names, and module object names in dynamically prepared SQL statements are resolved.
Values:
A valid path name. 1 - 254 characters.
Default:
blank
ADBTEP2_RESTART_PRECISION
Specifies the current precision. Valid values are 1 - 5 characters. The default value is blank.
Values:
A valid precision value. 1 - 5 characters.
Default:
blank
ADBTEP2_RESTART_RULES
Specifies the current rules.
Values:
DB2
SQL statements are run based on Db2 rules.
STD
SQL statements are run based on standard SQL rules.
Default:
The default value is blank.
ADBTEP2_RESTART_DECFLOAT_ROUNDING_MODE
Specifies the system default action that is used to round decimal floating-point values.
Values:
  • ROUND_CEILING
  • ROUND_DOWN
  • ROUND_FLOOR
  • ROUND_HALF_DOWN
  • ROUND_HALF_EVEN
Default:
blank
ADBTEP2_RESTART_ROUTINE_VERSION
Specifies the CURRENT ROUTINE VERSION special register.
Values:
Valid routine version names. 1 - 64 characters.
Default:
blank
ADBTEP2_RESTART_BUSINESS_TIME
Specifies value of the CURRENT TEMPORAL BUSINESS_TIME special register.
Values:
Valid business time values. 1 - 10 characters.
Default:
blank
ADBTEP2_RESTART_SYSTEM_TIME
Specifies value of the CURRENT TEMPORAL SYSTEM_TIME special register. Valid system times are 1 - 10 characters. The default value is blank.
Values:
Valid system time values. 1 - 10 characters.
Default:
blank
ADBTEP2_RESTART_GETARCHIVE
Specifies the value of GET_ARCHIVE global variable.
Values:
Y
Yes. When a table-reference is an archive-enabled table, the table reference includes rows in the associated archive table.
N
No. When a table-reference is an archive-enabled table, the table reference does not include rows in the associated archive table.
Default:
N
ADBTEP2_RESTART_MOVETOARCHIVE
Specifies the value of MOVE_TO_ARCHIVE global variable.
Values:
Y
Yes. When a row in an archive-enabled table is deleted, a copy of the deleted row is stored in the associated archive table.
N
No. When a row in an archive-enabled table is deleted, a copy of the deleted row is not stored in the associated archive table.
Default:
N
ADBTEP2_RESTART_UNLLOBXML
Specifies whether ADBTEP2 should end with an error or unload the table space when an image copy of a table space is requested and any table in the table space contains LOB or XML columns.
Values:
E
ADBTEP2 ends with an error.
U
The table space is unloaded.
Default:
The default value is blank.
ADBTEP2_RESTART_UNLNOIC
Specifies whether ADBTEP2 should end with an error or unload the table space when an image copy of a table space is requested but an image copy is not found.
Values:
E
ADBTEP2 ends with an error.
U
The table space is unloaded.
Default:
The default value is blank.
ADBTEP2_RETRY_DEPRECATED_OBJ
Specifies whether ADBTEP2 is to retry an SQL statement at a lower Db2 function level to create a deprecated object.

This parameter applies only if you are running at Db2 12 function level 504 or higher.

Values:
Yes
Retry the statement.

When the current application compatibility level is Db2 12 function level 504 or higher, and an SQL statement returns SQLCODE -20008 (because it is trying to create a deprecated object), ABDTEP2 takes the following actions:

  • Sets the APPLCOMPAT value to V12R1M503
  • Retries the statement
  • Changes APPLCOMPAT back to the previous value.
No
Do not retry the statement.
Default:
Yes
ADBTEP2_SPANNED
Specifies the SPANNED value that is passed to the ADBTEP2 (adbtepx) program. For the complete description and list of values, see The Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
Yes
Adds a SPANNED keyword to the UNLOAD statement when the table that is being unloaded has an XML or LOB column.
No
Spanned keyword is not added to Unload statement.
Default:
No
ADBTEP2_STOGROUP_AUTO_REORG_REBUILD
Specifies whether the product, when a change is run, initiates a REORG or REBUILD for the table space or index to implement the effect of altering STOGROUP attribute. For the complete description and list of values see Using the Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
YES
The product automatically attempts a REORG or REBUILD for the table space or index after SQL statement ALTER STOGROUP is executed. However, if the parameter RUN_REORG_REBUILD was specified as 'A - All relevant' to generate an explicit REORG or REBUILD during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REORG or REBUILD that duplicates the explicit REORG or REBUILD.
NO
The product does not automatically attempt a REORG or REBUILD for the table space or index after SQL statement ALTER STOGROUP is executed.
Default:
NO
ADBTEP2_TIMEOUT_RETRIES
Specifies the maximum number of times that ADBTEP2 is to retry either executing the statement or restarting from the last checkpoint when one of the following conditions occurs:
  • For a timeout condition with SQLCODE -913 and reason code x'00C9008E' or a resource unavailable condition (SQLCODE -904 and reason code x'00C200EA'), ADBTEP2 retries executing the statement.
  • For a timeout condition with SQLCODE -911 and reason code x'00C9008E', ADBTEP2 tries restarting from the last checkpoint.
Values:
An integer value from 0 to 99. A value of 0 means that ADBTEP2 is not to attempt any retries.
Default:
0
ADBTEP2_TIMEOUT_WAIT_TIME
Specifies the duration, in seconds, between retries by ADBTEP2.
Values:
An integer value from 1 to 3600.
Default:
120
ADBTEP2_TSACCESS
Specifies whether to preserve the access state of the table spaces being accessed. If you set the ADBTEP2_TSACCESS parameter value to YES, run change (ADBTEP2) tracks the statements and processes that can place a table space in a different access state and preserves the state the table space is in.
Values:
YES
The access state of the table space is preserved.
NO
The access state of the table space is not preserved.
Default:
NO
ADMIN_DATASET_BUFNO
Specifies the BUFNO attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set. The BUFNO attribute is for the number of buffers to be assigned for data control blocks. For more information, see the ADMIN_DATASET_TYPE parameter.
Values:
An integer value 1-255, blank
blank
The BUFNO attribute is not specified for the ALLOCATE statement.
Default:
blank
ADMIN_DATASET_DATACLAS
Specifies the DATACLAS attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set. The DATACLAS attribute is for the data class name. For more information, see the ADMIN_DATASET_TYPE parameter.
Values:
A valid data class name
Db2 Admin Tool does not validate this value. If an invalid value is specified, an error message is generated from TSO when the allocate of the data set is attempted. Db2 Admin Tool then sets the RECFM, LRECL, and BLKSIZE attributes by specifying these attributes on the ALLOCATE statement. By default, Db2 Admin Tool specifies the space attributes on the allocate statement but you can omit the space attributes from the ALLOCATE statement by specifying ADMIN_DATASET_SPACE_PRIQTY = '<NONE>' for the Db2 Admin Tool.
blank
The DATACLAS attribute is not specified for the ALLOCATE statement.
Default:
blank
ADMIN_DATASET_DEVICE_UNIT
Specifies the device unit for the Db2 Admin Tool data set. For more information, see the ADMIN_DATASET_TYPE parameter.
Values:
A valid device unit, <NONE>
<NONE>
Specifies that the UNIT clause is omitted from the ALLOCATE statement.
Default:
SPACE_UNIT_NAME (See SPACE_UNIT_NAME.)
ADMIN_DATASET_DIR
Specifies the DIR attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set. The DIR attribute is for the number of directory blocks. For more information, see the ADMIN_DATASET_TYPE parameter. This parameter is only used for the following types of Db2 Admin Tool data sets: IFF, DELTA, DDL SRCVF, TGTVF, MTC.

If the SPACE(priqty,secqty) clause is omitted, then no default value is specified.

Values:
An integer greater than zero, blank
blank
If the SPACE(priqty,secqty) clause is not to be omitted, specifies that the following default values are used for the Db2 Admin Tool data set type that is in effect:
  • IFF: 60. A user specified value for directory blocks that you specify only if the Db2 Admin Tool default is insufficient for the change that is being analyzed.
  • DELTA: 60
  • DDL: 60
  • SRCVF: 60
  • TGTVF: 60
  • MTC: 60
Default:
blank
ADMIN_DATASET_DSN
Specifies the data set name for the Db2 Admin Tool data set. For more information, see the ADMIN_DATASET_TYPE parameter.
Values:
A valid data set name.
The data set name can be 1 to 46 characters or blank.
blank
Specifies that the following default values are to be used for the indicated Db2 Admin Tool data set type that is in effect:
  • CHG: &SSID..&CHGTAG..CHG
  • DDL: &SSID..&CHGTAG..T&TIME..DDL
  • DELTA: D&DATE..T&TIME..DELTA
  • IFF: &SSID..&CHGTAG..IFF
  • MTC: &SSID..D&DATE..T&TIME..MTC
  • SRCVF: OC.D&DATE..T&TIME..SRCVF
  • TGTVF: OC.D&DATE..T&TIME..TGTVF
Default:
blank
ADMIN_DATASET_DSNTYPE
Specifies the DSNTYPE attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set. The DSNTYPE attribute is for the type of data set. For more information, see the ADMIN_DATASET_TYPE parameter. This parameter is only used for the following types of Db2 Admin Tool data sets: IFF, DELTA, DDL SRCVF, TGTVF, MTC.
Values:
LIBRARY, PDS, blank
blank
For data set type IFF, the default is PDS. Otherwise the DSNTYPE attribute is not added to the ALLOCATE statement.
Default:
blank
ADMIN_DATASET_EXPDT
Specifies the EXPDT attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set. The EXPDT attribute is an expiration date. For more information, see the ADMIN_DATASET_TYPE parameter. This parameter is mutually exclusive with the ADMIN_DATASET_RETPD parameter.
Values:
A valid expiration date as defined for the EXPDT attribute for the TSO ALLOCATE statement, blank
blank
The EXPDT attribute is not specified for the ALLOCATE statement.
Default:
blank
ADMIN_DATASET_MAXVOL
Specifies the MAXVOL attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set. For more information, see the ADMIN_DATASET_TYPE parameter.
Values:
A valid maxvol value as defined by the TSO ALLOCATE statement
Db2 Admin Tool does not validate this value. If an invalid value is specified, an error message is generated from TSO when the allocate of the data set is attempted.
blank
The MAXVOL attribute is not specified for the ALLOCATE statement.
Default:
blank
ADMIN_DATASET_MGMTCLAS
Specifies the MGMTCLAS attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set. The MGMTCLAS attribute is for the management class name. For more information, see the ADMIN_DATASET_TYPE parameter.
Values:
A valid management class name
Db2 Admin Tool does not validate this value. If an invalid value is specified, an error message is generated from TSO when the allocate of the data set is attempted.
blank
The MGMTCLAS attribute is not specified for the ALLOCATE statement.
Default:
blank
ADMIN_DATASET_RETPD
Specifies the RETPD attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set. The RETPD attribute is a retention period specified in number of days. For more information, see the ADMIN_DATASET_TYPE parameter. This parameter is mutually exclusive with the ADMIN_DATASET_EXPDT parameter.
Values:
An integer value representing the number of days, blank
blank
The RETPD attribute is not specified for the ALLOCATE statement.
Default:
blank
ADMIN_DATASET_SPACE_PRIQTY
Specifies the primary quantity for the Db2 Admin Tool data set. For more information, see the ADMIN_DATASET_TYPE parameter.
Values:
A valid PRIQTY value, <NONE>, blank
<NONE>
Specifies that the SPACE(priqty,secqty), unit of space clauses, and space directory attributes be omitted from the ALLOCATE statement.
blank
Specifies that the following default values are to be used for the indicated Db2 Admin Tool data set type that is in effect:
  • CHG: 10
  • DDL: 10
  • DELTA: 10
  • IFF: 2
  • MTC: 10
  • SRCVF: 10
  • TGTVF: 10
Default:
blank
ADMIN_DATASET_SPACE_SECQTY
Specifies the secondary quantity for the Db2 Admin Tool data set. For more information, see the ADMIN_DATASET_TYPE parameter.

If the SPACE(priqty,secqty) clause is omitted, then no default value is specified.

Values:
A valid SECQTY value, blank
blank
If the SPACE(priqty,secqty) clause is not to be omitted, the following default values are used for the Db2 Admin Tool data set type that is in effect:
  • CHG: 10
  • DDL: 10
  • DELTA: 10
  • IFF: 2
  • MTC: 10
  • SRCVF: 10
  • TGTVF: 10
Default:
blank
ADMIN_DATASET_SPACE_TYPE
Specifies the space unit type for the Db2 Admin Tool data set.

If the SPACE(priqty,secqty) clause is omitted, no default value is specified.

Values:
CYL
Specifies that the space unit type is cylinders.
TRK
Specifies that the space unit type is tracks.
blank
Specifies that the following default values are used for the Db2 Admin Tool data set type that is in effect:
  • CHG: CYL
  • DDL: CYL
  • DELTA: CYL
  • IFF: CYL
  • MTC: CYL
  • SRCVF: CYL
  • TGTVF: CYL
Default:
blank
Related information:
ADMIN_DATASET_STORCLAS
Specifies the STORCLAS attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set. The STORCLAS attribute is for the storage class name. For more information, see the ADMIN_DATASET_TYPE parameter.
Values:
A valid storage class name
Db2 Admin Tool does not validate this value. If an invalid value is specified, an error message is generated from TSO when the allocate of the data set is attempted.
blank
The STORCLAS attribute is not specified for the ALLOCATE statement.
Default:
blank
ADMIN_DATASET_TYPE
Specifies the type of data set to which the subsequent Db2 Admin Tool data set type template parameters apply.

You can specify multiple data set types. Separate each type with a semicolon. All data set template parameters that are specified before the next semicolon in the parameter list apply to the type of data set specified. For more information about the syntax of specifying the data set type parameters, see Db2 Admin Tool data set templates.

Values:
CHG
The CHG data set.
Recommendation: When generating a recover change, use CHG_RO or CHG_RE. Specifying CHG when generating a recover change affects the CHG data set for only the change itself; it does not affect the CHG data set for the recover change. If CHG_RO or CHG_RE is not specified, the default recover change CHG data set is created.
CHG_RO
The CHG data set for a recover to original data change. A recover to original data change is specified by the following two options:
  • GENERATE_RECOVER_CHANGE = ‘Y’
  • DATA_TO_RECOVER = ‘O’ or DATA_TO_RECOVER = ‘B’
CHG_RE
The CHG data set for a recover to existing data change. A recover to existing data change is specified by the following two options:
  • GENERATE_RECOVER_CHANGE = ‘Y’
  • DATA_TO_RECOVER = ‘E’ or DATA_TO_RECOVER = ‘B’
DDL
The DDL Admin data set. This data set is the output data set when generating DDL from a base version.
DELTA
The compare delta change file.
IFF
The IFF PDS Db2 Admin Tool data set.
Recommendation: When generating a recover change, use IFF_RO or IFF_RE. Specifying IFF when generating a recover change affects the IFF data set for only the change itself; it does not affect the IFF data set for the recover change. If IFF_RO or IFF_RE is not specified, the default recover change IFF data set is created.
IFF_RO
The IFF PDS Db2 Admin Tool data set for a recover to original data change. A recover to original data change is specified by the following two options:
  • GENERATE_RECOVER_CHANGE = ‘Y’
  • DATA_TO_RECOVER = ‘O’ or DATA_TO_RECOVER = ‘B’
IFF_RE
The IFF PDS Db2 Admin Tool data set for a recover to existing data change. A recover to existing data change is specified by the following two options:
  • GENERATE_RECOVER_CHANGE = ‘Y’
  • DATA_TO_RECOVER = ‘E’ or DATA_TO_RECOVER = ‘B’
MTC
The multi-target change file.
SRCVF
A compare source version work file.
TGTVF
A compare target version work file.
blank
The Db2 Admin Tool data set template parameters are ignored until a supported value for ADMIN_DATASET_TYPE is specified.
Default:
blank
ADMIN_DATASET_VOLUME
Specifies the VOLUME attribute of the TSO ALLOCATE statement for the Db2 Admin Tool data set.
Values:
One or more serial numbers separated by a comma, blank
blank
The VOLUME attribute is not specified for the ALLOCATE statement.
Default:
blank
Related information:
ALLOW_IMPLICIT_DROP_OF_EXCLUDED_OBJECTS
Specifies whether excluded objects can be dropped implicitly.
Values:
YES
Excluded objects can be dropped implicitly.
NO
Excluded objects cannot be dropped implicitly.
Default:
NO
ALLOW_PBR2_TO_PBR_CHANGES
Specifies whether PBR2 table space objects can be reverted to PBR.
Values:
Y
Revert PBR2 table space objects back to PBR.
N
Do not revert PBR2 table space objects back to PBR.
Default:
N
ALLOW_ROTATE_PARTS
Specifies whether to generate the rotate partition or alter partition statement when the condition for a rotate is met.
Values:
Y
Generate the rotate partition statement. Data from the rotating partitions is unloaded before the rotate takes place. You can either reload the data or discard it.
N
Generate the alter partition statement. Data from the rotating partitions is reloaded into the table. Logical and physical partitions are preserved.
Default:
Y
AUTH_SWITCH_SECADM
Specifies the SECADM authority to use when auth-switching is enabled. The SECADM authority is used to manage all security-related tasks. This parameter applies only if the facility has been enabled for the subsystem as part of the customization process, and applies only when Db2 Admin Tool is connected to Db2 10 or later.
Values:
An SQLID with SECADM authority
Specify a SECADM authority to manage all security-related tasks.
Default:
blank
AUTH_SWITCH_USERID
Specifies the auth-switch ID to use when auth-switching is enabled. This parameter applies only when the facility has been enabled for the subsystem as part of customization process.
Values:
An SQLID
The ID to connect as when auth-switching.
<NONE>
Avoids producing auth-switch work-statement lists (WSL).
<SQLID>
Enables the SQLID authorization switching feature.
blank
Produces auth-switch WSL, with the ID portion of the WSL as comments.
Default:
<NONE>
AUTH_SWITCHING_ENABLED
Specifies whether auth-switching is enabled.
Values:
Y
Auth-switching is used if an auth-switch ID is specified.
N
Auth-switching is used.
Default:
N
Start of changeAUTO_VIEW_REGENERATEEnd of change
Start of changeSpecifies whether ALTER VIEW REGNERATE statements are automatically generated after a column change that alters the data type, length, precision, or scale of the column.
Values:
YES or Y
An ALTER VIEW REGNERATE statement is generated for each view that references the affected columns. If no such views exist, no statements are generated.
NO or N
No ALTER VIEW REGNERATE statements are generated.
Default:
NO
End of change
BASE_VERSION_NAME
Specifies the name of the base version to perform the action on. If a base version is being saved or generated, this parameter specifies the name for the new base version if the other base version name parameters are blank. If a base version is not being saved or generated, the value of this parameter must identify the name of an existing base version.
The base version parameter hierarchy is as follows:
  • BASE_VERSION_OWNER
    • NEW_BASE_VERSION_OWNER
      • BASE_VERSION_OWNER_BEFORE_RUN
      • BASE_VERSION_OWNER_AFTER_RUN
  • BASE_VERSION_NAME
    • NEW_BASE_VERSION_NAME
      • BASE_VERSION_NAME_BEFORE_RUN
      • BASE_VERSION_NAME_AFTER_RUN
Values:
A valid 1- to 128-character version name.
Default:
AUTO:&CURTS.
BASE_VERSION_NAME_AFTER_RUN
Specifies the name for a new base version that is created after a change is implemented.
The base version parameter hierarchy is as follows:
  • BASE_VERSION_OWNER
    • NEW_BASE_VERSION_OWNER
      • BASE_VERSION_OWNER_BEFORE_RUN
      • BASE_VERSION_OWNER_AFTER_RUN
  • BASE_VERSION_NAME
    • NEW_BASE_VERSION_NAME
      • BASE_VERSION_NAME_BEFORE_RUN
      • BASE_VERSION_NAME_AFTER_RUN
Values:
Valid version name; 1 to 128 characters
Default:
NEW_BASE_VERSION_NAME
BASE_VERSION_NAME_BEFORE_RUN
Specifies the name for a new base version that is created before a change is implemented.
Base version parameter hierarchy:
  • BASE_VERSION_OWNER
    • NEW_BASE_VERSION_OWNER
      • BASE_VERSION_OWNER_BEFORE_RUN
      • BASE_VERSION_OWNER_AFTER_RUN
  • BASE_VERSION_NAME
    • NEW_BASE_VERSION_NAME
      • BASE_VERSION_NAME_BEFORE_RUN
      • BASE_VERSION_NAME_AFTER_RUN
Values:
Valid version name; 1 to 128 characters
Default:
NEW_BASE_VERSION_NAME
BASE_VERSION_OWNER
Specifies the owner of the base version to perform the action on. If a base version is being saved or generated, this parameter specifies the owner for the new base version if the other base version owner parameters are blank. If a base version is not being saved or generated, the value of this parameter must identify the owner of an existing base version.
Base version parameter hierarchy:
  • BASE_VERSION_OWNER
    • NEW_BASE_VERSION_OWNER
      • BASE_VERSION_OWNER_BEFORE_RUN
      • BASE_VERSION_OWNER_AFTER_RUN
  • BASE_VERSION_NAME
    • NEW_BASE_VERSION_NAME
      • BASE_VERSION_NAME_BEFORE_RUN
      • BASE_VERSION_NAME_AFTER_RUN
Values:
Valid version name; 1 to 128 characters
Default:
&CURSQLID.
BASE_VERSION_OWNER_AFTER
Specifies the owner for a new base version that is created after a change is implemented.
Base version parameter hierarchy:
  • BASE_VERSION_OWNER
    • NEW_BASE_VERSION_OWNER
      • BASE_VERSION_OWNER_BEFORE_RUN
      • BASE_VERSION_OWNER_AFTER_RUN
  • BASE_VERSION_NAME
    • NEW_BASE_VERSION_NAME
      • BASE_VERSION_NAME_BEFORE_RUN
      • BASE_VERSION_NAME_AFTER_RUN
Values:
Valid version name; 1 to 128 characters
Default:
NEW_BASE_VERSION_OWNER
BASE_VERSION_OWNER_BEFORE_RUN
Specifies the owner for a new base version that is created before a change is implemented.
Base version parameter hierarchy:
  • BASE_VERSION_OWNER
    • NEW_BASE_VERSION_OWNER
      • BASE_VERSION_OWNER_BEFORE_RUN
      • BASE_VERSION_OWNER_AFTER_RUN
  • BASE_VERSION_NAME
    • NEW_BASE_VERSION_NAME
      • BASE_VERSION_NAME_BEFORE_RUN
      • BASE_VERSION_NAME_AFTER_RUN
Values:
Valid version name; 1 to 128 characters
Default:
NEW_BASE_VERSION_OWNER
BASE_VERSION_SCOPE_NAME
Specifies the default name of an existing version scope to use when generating a new base version using the USER method.
Base version scope parameter hierarchy:
  • BASE_VERSION_SCOPE_OWNER
    • BASE_VERSION_SCOPE_OWNER_BEFORE_RUN
    • BASE_VERSION_SCOPE_OWNER_AFTER_RUN
  • BASE_VERSION_SCOPE_NAME
    • BASE_VERSION_SCOPE_NAME_BEFORE_RUN
    • BASE_VERSION_SCOPE_NAME_AFTER_RUN
Values:
Valid version name; 1 to 128 characters, blank
Default:
blank
BASE_VERSION_SCOPE_NAME_AFTER_RUN
Specifies the name of an existing version scope to use when generating a new base version after a change is implemented. This applies only if the new base version is created using the USER method.
Base version scope parameter hierarchy:
  • BASE_VERSION_SCOPE_OWNER
    • BASE_VERSION_SCOPE_OWNER_BEFORE_RUN
    • BASE_VERSION_SCOPE_OWNER_AFTER_RUN
  • BASE_VERSION_SCOPE_NAME
    • BASE_VERSION_SCOPE_NAME_BEFORE_RUN
    • BASE_VERSION_SCOPE_NAME_AFTER_RUN
Values:
Valid version name; 1 to 128 characters
Default:
BASE_VERSION_SCOPE_NAME
BASE_VERSION_SCOPE_NAME_BEFORE_RUN
Specifies the name of an existing version scope to use when generating a new base version before a change is implemented. This applies only if the new base version is created using the USER method.
Base version scope parameter hierarchy:
  • BASE_VERSION_SCOPE_OWNER
    • BASE_VERSION_SCOPE_OWNER_BEFORE_RUN
    • BASE_VERSION_SCOPE_OWNER_AFTER_RUN
  • BASE_VERSION_SCOPE_NAME
    • BASE_VERSION_SCOPE_NAME_BEFORE_RUN
    • BASE_VERSION_SCOPE_NAME_AFTER_RUN
Values:
Valid version name; 1 to 128 characters
Default:
BASE_VERSION_SCOPE_NAME
BASE_VERSION_SCOPE_OWNER
Specifies the default owner of an existing version scope to use when generating a new base version using the USER method.
Base version scope parameter hierarchy:
  • BASE_VERSION_SCOPE_OWNER
    • BASE_VERSION_SCOPE_OWNER_BEFORE_RUN
    • BASE_VERSION_SCOPE_OWNER_AFTER_RUN
  • BASE_VERSION_SCOPE_NAME
    • BASE_VERSION_SCOPE_NAME_BEFORE_RUN
    • BASE_VERSION_SCOPE_NAME_AFTER_RUN
Values:
Valid version scope owner; 1 to 128 characters
Default:
&CURSQLID.
BASE_VERSION_SCOPE_OWNER_AFTER_RUN
Specifies the owner of an existing version scope to use when generating a new base version after a change is implemented. This applies only if the new base version is created using the USER method
Base version scope parameter hierarchy:
  • BASE_VERSION_SCOPE_OWNER
    • BASE_VERSION_SCOPE_OWNER_BEFORE_RUN
    • BASE_VERSION_SCOPE_OWNER_AFTER_RUN
  • BASE_VERSION_SCOPE_NAME
    • BASE_VERSION_SCOPE_NAME_BEFORE_RUN
    • BASE_VERSION_SCOPE_NAME_AFTER_RUN
Values:
Valid version scope owner; 1 to 128 characters
Default:
BASE_VERSION_SCOPE_OWNER
BASE_VERSION_SCOPE_OWNER_BEFORE_RUN
Specifies the owner of an existing version scope to use when generating a new base version before a change is implemented. This applies only if the new base version is created using the USER method
Base version scope parameter hierarchy:
  • BASE_VERSION_SCOPE_OWNER
    • BASE_VERSION_SCOPE_OWNER_BEFORE_RUN
    • BASE_VERSION_SCOPE_OWNER_AFTER_RUN
  • BASE_VERSION_SCOPE_NAME
    • BASE_VERSION_SCOPE_NAME_BEFORE_RUN
    • BASE_VERSION_SCOPE_NAME_AFTER_RUN
Values:
Valid version scope owner; 1 to 128 characters
Default:
BASE_VERSION_SCOPE_OWNER
CHANGE_COMMENT
Specifies the comment for a new change.
Values:
1 to 128 characters
Default:
blank
CHANGE_NAME
Specifies the name of the change to perform the action on. If a change is being imported, this parameter specifies the name for the new change if the value for the NEW_CHANGE_NAME parameter is blank. If a change is not being imported, the value for this parameter must identify the name of an existing change.
Values:
Valid change name; 1 to 128 characters. If CHGTAG_TYPE ='NAME', the change name must be 1 to 8 characters due to data set naming restrictions.
Default:
AUTO:&CURTS.
CHANGE_OWNER
Specifies the owner of the change to perform the action on. If a change is being imported, this parameter specifies the owner for the new change if the value for the NEW_CHANGE_OWNER parameter is blank. If a change is not being imported, the value for this parameter must identify the owner of an existing change.
Values:
Valid change owner; 1 to 128 characters
Default:
&CURSQLID.
CHGTAG_TYPE
Specifies the type of values that the Db2 Admin Tool &CHGTAG. symbol variable resolves to. Refer to the product-defined symbol variables information and the definition of the Db2 Admin Tool &CHGTAG. symbol variable for details.
Values:
ID
The &CHGTAG. symbol variable value is based on the Db2 Admin Tool generated change ID.
NAME
The &CHGTAG. symbol variable value is based on the user specified change name.
OWNER
The &CHGTAG. symbol variable value is based on the user specified change owner.
Default:
ID
COMPARE_IGNORE_CHANGES_NAME
Specifies the name of an existing Ignore Changes Specification that is stored in the Change Management database. The COMPARE_IGNORE_CHANGES_OWNER and COMPARE_IGNORE_CHANGES_NAME parameters uniquely identify an Ignore Changes Specification to be used during the compare process.
Values:
A valid ignore changes name, blank
A valid ignore changes name; 1 to 128 characters
Specify a 1- to 128-character Ignore Changes Specification is used during the compare process.
blank
Ignore changes is not used during the compare process.
Default:
blank
COMPARE_IGNORE_CHANGES_OWNER
Specifies the owner of an existing Ignore Changes Specification that is stored in the Change Management database. The COMPARE_IGNORE_CHANGES_OWNER and COMPARE_IGNORE_CHANGES_NAME parameters uniquely identify an Ignore Changes Specification to be used during the compare process.
Values:
Specify a valid 1- to 128-character ignore changes owner.
Default:
&CURSQLID.
COMPARE_IGNORE_FIELDS_DSN
Specifies the name of a data set that contains the ignore fields to be used during the compare. The PREFIX_FOR_DATA_SETS parameter is used to qualify the data set name if the specified data set name is not fully qualified. If the compare ignore fields file IGNORES DD is pre-allocated and this parameter is specified, the ignore fields specified by this parameter are used instead of the pre-allocated compare ignore fields file. The COMPARE_IGNORE_FIELDS_DSN and COMPARE_IGNORE_FIELDS_NAME parameters are mutually exclusive.
Values:
A valid data set name
The data set must contain ignore fields and be a fixed block sequential data set or a member of a partitioned data set with a record length of 80 (RECFM=Fx, LRECL=80). The input must be in columns 1-72 of the data set.
Syntax:
objecttype: field1,field2, .... ,fieldn

where objecttype is the Db2 catalog table name and fieldn : is the Db2 catalog column to be ignored

Examples:
SYSDATABASE: BPOOL
SYSDATABASE: INDEXBP,STGROUP
SYSTABLESPACE: BPOOL
SYSTABLEPART: PQTY,SQTY,STORNAME,VCATNAME
SYSINDEXES: INDEXSPACE
SYSINDEXPART: PQTY,SQTY,STORNAME,VCATNAME

Ignore fields are applied to both the target and the source objects before the definitions are compared.

Default:
blank
COMPARE_IGNORE_FIELDS_NAME
Specifies the name of an existing Ignore Fields Specification that is stored in the Change Management database. The COMPARE_IGNORE_FIELDS_OWNER and COMPARE_IGNORE_FIELDS_NAME parameters uniquely identify the Ignore Fields Specification to be used during the compare process. If the compare ignore fields file IGNORES DD is pre-allocated and this parameter is specified, the ignore fields that are specified by this parameter are used instead of the pre-allocated compare ignore fields file. The COMPARE_IGNORE_FIELDS_DSN and COMPARE_IGNORE_FIELDS_NAME parameters are mutually exclusive.
Values:
A valid ignore fields name, blank
A valid ignore fields name
Specify a 1- to 128-character Ignore Fields name. The specified Ignore Fields Specification is used during the compare process.
Default:
blank
COMPARE_IGNORE_FIELDS_OWNER
Specifies the owner of an existing Ignore Fields Specification that is stored in the Change Management database. The COMPARE_IGNORE_FIELDS_OWNER and COMPARE_IGNORE_FIELDS_NAME parameters uniquely identify the Ignore Fields Specification to be used during the compare process.
Values:
Specify a 1- to 128-character Ignore Fields owner.
Default:
&CURSQLID.
COMPARE_MASK_DSN
Specifies the name of a data set that contains the masks to be used for the compare. The PREFIX_FOR_DATA_SETS parameter is used to qualify the data set name if the specified data set name is not fully qualified. If the compare masks file MASKS DD is pre-allocated and this parameter is specified, the masks that are specified by this parameter are used instead of the pre-allocated compare masks file. The COMPARE_MASK_DSN and COMPARE_MASK_NAME parameters are mutually exclusive.
Values:
A valid data set name

The data set must contain masks and must be a fixed block sequential data set or a member of a partitioned data set with a record length of 80 (RECFM=Fx, LRECL=80). The input must be in columns 1-72 of the data set.

Here are some mask definition examples:

NAME: ABC*, DEF*
NAME: HLQ*D*, NEW**
OWNER: SYSIBM,MYCAT

Masks are applied to the source objects before they are compared with the target. You can define as many masks as you want; however, defining many masks will degrade the performance of compare. The first left hand mask that matches are used and the name is translated to the right hand value. If no match is found it is not translated, but still participate in the compare. Using the above masks a source database with the name 'HLQ47D9' is translated to 'NEW479' before it is compared with the target databases.

Default:
blank
COMPARE_MASK_NAME
Specifies the name of an existing mask entry that is stored in the Change Management database that is to be used for the compare. The COMPARE_MASK_OWNER and COMPARE_MASK_NAME parameters uniquely identify the mask entry to be used during the compare process. If the compare masks file MASKS DD is pre-allocated and this parameter is specified, the masks that are specified by this parameter are used instead of the pre-allocated compare masks file. The COMPARE_MASK_DSN and COMPARE_MASK_NAME parameters are mutually exclusive.
Values:
Specify a valid 1- to 128-character mask name.
Default:
blank
COMPARE_MASK_OWNER
Specifies the owner of an existing mask entry that is stored in the Change Management database that is to be used for the compare. The COMPARE_MASK_OWNER and COMPARE_MASK_NAME parameters uniquely identify the mask entry to be used during the compare process.
Values:
Specify a valid 1- to 128-character mask owner.
Default:
&CURSQLID.
COMPARE_RESULTS_COMMENT
Specifies a comment for the saved compare result. You can use this comment parameter to describe the nature of the compare run. This comment is stored with the saved compare result.
Values:
Specify a 1- to 128-character comment or leave this parameter blank.
Default:
blank
COMPARE_RESULTS_ELIGIBLE_FOR_AUTO_DELETE
Specifies when the saved compare result is eligible for deletion by the auto-delete process of Db2 Admin Tool.
Values:
Number of days until eligible for auto-delete
Specify a number in the range 1-9999.
blank
No auto-deletion will take place.
Default:
blank
COMPARE_RESULTS_NAME
Specifies the name for the compare result that is stored in the Change Management database. The COMPARE_RESULTS_OWNER and COMPARE_RESULTS_NAME together uniquely identify the saved compare result. You can manage the saved compare result using the "MR - Manage saved compare results" dialogs, which you access from the Object Comparison Tool main menu.
Values:
Name for the compare results.
Specify a valid 1- to 128-character compare results name.
Default:
AUTO:&CURTS.
COMPARE_RESULTS_OWNER
Specifies the owner for the compare result that is stored in the Change Management database. The COMPARE_RESULTS_OWNER and COMPARE_RESULTS_NAME together uniquely identify the saved compare result. You can manage the saved compare result using the "MR - Manage saved compare results" dialogs, which you access from the Object Comparison Tool main menu.
Values:
Owner of the compare result
A valid 1- to 128 character name of the compare results owner.
Default:
&CURSQLID.
CONTENT_OF_APPLY_JOBS
Specifies whether to generate changes only to database objects and to not generate unloads, loads or other utilities, except REBIND.
Values:
A
Generate all jobs and processes to reload data.
D
Generate only SQL.
Restriction: You must set the CONTENT_OF_APPLY_JOBS parameter to A if the GENERATE_RECOVER_CHANGE parameter is set to Yes.
Default:
A
DATA_TO_RECOVER
Specifies the type of data that the recover change recovers.
Values:
O
Recover using the original data. The original data is the data that is unloaded when the original change is run. If you use the original data during a recovery operation, consider whether related tables that were not affected by the recover must also be restored to the same point to avoid inconsistencies. This option applies only to tables that were unloaded in the original change.
E
Recover using the existing data. The existing data is the data that exists in the table just before the original change is recovered. If a table is dropped without being re-created in the original change, no data is loaded after the table is created in the recover change.
B
Set up recover with both the existing data and the original data, so that you will have the choice to recover with either type of data. (At the time of recovery, you can specify RECOVER_OPTION=’O’ or RECOVER_OPTION=’E’).
N
Do not use any data to do recover. This option allows for a recovery with DDL only.
Default:
E
DB2_SORT_LINKLIB
Specifies the Db2 Sort SCNKLINK library. This data set must be APF-authorized. This parameter is only valid when parameter Unload_method = 'H' for Db2 High Performance Unload is specified too.
Values:
Valid library names. 1 - 44 characters.
Default:
blank
DB2_SORT_LPALIB
Specifies the Db2 Sort SCNKLPA library. This data set must be APF-authorized. This parameter is only valid when parameter Unload_method = 'H' for Db2 High Performance Unload is specified too.
Values:
Valid library names. 1 - 44 characters.
Default:
blank
DEFAULT_SPACE_PRIQTY
Specifies the default primary space allocation. The default space allocation values are used to allocate, copy, and unload data sets when RUNSTATS or STOSPACE has not been run.
Values:
Specify a valid PRIQTY value.
Default:
30
DEFAULT_SPACE_SECQTY
Specifies the default secondary space allocation. The default space allocation values are used to allocate, copy, and unload data sets when RUNSTATS or STOSPACE has not been run.
Values:
Specify a valid SECQTY value.
Default:
30
DISABLE_OPTIMIZE_REORG
Controls whether the compare process disables the optimization of REORG statements.

This parameter is useful when multiple REORG operations are performed on the same table space because of a change.

Values:
Y
Disables the optimization of REORG statements.
N
REORG statements are optimized. The minimum number of REORG operations are used to try to avoid multiple REORG operations on the same table space.
Default:
N
DISPLAY_MTC_STATEMENTS
Specifies whether the change statements registered for multi-target changes are displayed when analyzing and running of a multi-target change.
Note: These are the change statements on the central system where multi-target change is registered. On each target system, these statements will have variations based on masks applied.
Values:
Y
Display the multi-target change statements
N
Do not display the multi-target change statements.
Default:
N
Start of changeDO_NOT_FORCE_SUPPRESS_FOR_AUTOEnd of change
Start of changeSpecifies whether to force the Suppress DROP of objects option when the target is type AUTO.
Values:
YES
Do not force this option.
NO
Force this option.
Default:
N
End of change
DO_RUNTIME_ANALYZE
Specifies whether to do a runtime analyze before a change is run. The runtime analyze is a safety check to ensure a change being run is based on the latest Db2 catalog information.
Values:
Y
Perform a run-time analyze. If the product detects that the latest Db2 catalog information is not used but is needed, the run process will fail with an error. The change will need to be analyzed again before it can be run.
N
A runtime analyze is not done before a change is run.
Default:
Y
DROP_FKS_NOT_IN_SOURCE
Specify whether the compare process is to drop from the target table any foreign keys that are not specified in the corresponding source table.
Values:
YES or Y
If a table on the target has foreign keys and the table also exists on the source, all foreign keys that are not also on the source will be dropped from the target.
NO or N
The drop behavior is determined by the SUPPRESS_DROP_OF_OBJECTS parameter.
Default:
NO
ENABLE_ACCELERATED_TABLES
Specifies whether to enable acceleration for accelerated tables that are automatically recreated and reloaded in DROP/CREATE or ALTER situations.
Values:
Y
Enables accelerated tables.
N
Does not enable accelerated tables.
Default:
Y

If ENABLE_ACCELERATED_TABLES is set to YES, RELOAD_ACCELERATED_TABLES must also be set to YES.

Start of changeEMBED_IFF_INTO_WSLEnd of change
Start of changeSpecifies whether the WSL is to include the contents of the IFF file in an encoded format. An IFF file is produced if the change requires an unload operation. The benefit of embedding the IFF contents in the WSL is that you can transport the WSL to another system without having to separately transport the IFF file. End of change
Start of change
Values:
YES or Y
Embed the IFF file contents in the WSL.
NO or N
Do not embed the IFF file contents in the WSL. A separate IFF file will be generated if needed.
Default:
NO
End of change
EXISTING_BASE_VERSION_ACTION
Specifies the action to take if a new base version owner and name identify an existing base version.
Values:
REPLACE
The existing base version is replaced with the new base version.
AUTO
The specified base version name is not used. Instead, Db2 Admin Tool uses the product default value for a base version name, such as AUTO:&CURTS.. A warning message is issued to notify you of this event.
Default:
AUTO
EXISTING_CHANGE_ACTION
Specifies the action to be taken when a change already exists.
Values:
REPLACE CONDITIONAL
Replace the change if it is not a prerequisite for other changes. If the change is a prerequisite for other changes, an error message is issued. The names of changes that are dependent on the change are displayed and the replace change request is not processed.
REPLACE UNCONDITIONAL
Replace the change even if it is a prerequisite for other changes. The names of changes that are dependent on the change are displayed.

The change status of changes that are dependent on the change is changed to DEFINED, and the changes must be analyzed before being run.

STOP
Do not replace the change.
Default:
STOP
EXISTING_DATA_SET_ACTION
Specifies the action that occurs if a data set with the same name already exists, and if a supported Db2 Admin Tool data sets is needed. The EXISTING_DATA_SET_ACTION parameter does not apply for WSL members when a conversion to ISPF format is performed. The following data set types support the EXISTING_DATA_SET_ACTION parameter:
  • CHG sequential file
  • IFF PDS
  • WSL PDS member
  • JCL PDS member
  • run job input PDS
If a recover change is generated, the existing data set action option also defines the action for Db2 Admin Tool data sets that are associated with the recover change, for example, recover CHG sequential file or recover IFF PDS, and so on.
Values:
CONDITIONAL
If the data set or PDS member already exists, and the data set or PDS member is already associated with the change from a previous CM action, replace the data set or PDS member. If the data set or PDS member already exists, and the data set or PDS member is not already associated with the change, stop processing.
REPLACE
If the data set or PDS member already exists, replace it.
STOP
If the data set or PDS member already exists, stop processing.
Default:
CONDITIONAL
EXISTING_MASK_ACTION
Specifies the action that occurs during import mask if the mask specified by COMPARE_MASK_OWNER and COMPARE_MASK_OWNER parameters identifies an existing mask entry.
Values:
REPLACE CONDITIONAL
Replace the mask if it is not associated with a registered change that needs the mask for implementation. If the mask is needed by one or more changes for implementation, the names of changes are displayed and the mask is not replaced.

REPLACE CONDITIONAL mode does not cover the scenario in which changes can be associated with a mask but the mask is no longer needed to implement the change. For example, when a change is imported using masking, after the import completes the mask is no longer needed to implement that change. The mask, however, is still associated with the change.

REPLACE UNCONDITIONAL
Replace the mask even if it is associated with a registered change that needs the mask for implementation. The names of changes that need the mask for implementation are displayed and the mask is replaced. Only the changes that need the mask for implementation are reported.

REPLACE UNCONDITIONAL mode does not cover the scenario in which changes can be associated with a mask but the mask is no longer needed to implement the change. For example, when a change is imported using masking, after the import completes the mask is no longer needed to implement that change. In this scenario, REPLACE UNCONDITIONAL does not report the imported change. The mask, however, is still associated with the change.

STOP
Do not replace the mask.
Default:
STOP
GEN_EXCLUDE_NAME
Specifies the name of an Exclude Specification that is stored in the Change Management database. The Exclude Specification is used for the GEN batch job during the CM batch compare.
Values:
A valid 1- to 128-character exclude specification name, blank
Default:
blank
GEN_EXCLUDE_OWNER
Specifies the owner of an Exclude Specification that is stored in the Change Management database. The Exclude Specification is used for the GEN batch job during the CM batch compare.
Values:
A valid 1- to 128-character exclude specification owner.
Default:
&CURSQLID
GENERATE_BASE_VERSION_AFTER_RUN
Specifies whether and how to automatically generate a new base version after a change is implemented. The base version that is generated is associated with the change. Automatically generating a base version after a change is run enables you to keep a record of object definitions after they were changed, and to associate this base version with the change entry.
Values:
AUTO
Db2 Admin Tool automatically determines the objects that are in the base version based on the objects that are being changed.
USER
The objects that are in the base version are defined by a version scope that is specified by the user.
NO
A new base version is not generated after the change is implemented.
Default:
NO
GENERATE_BASE_VERSION_BEFORE_RUN
Specifies whether and how to automatically generate a new base version before a change is implemented. The base version that is generated is associated with the change. Automatically generating a base version after a change is run enables you to keep a record of object definitions after they were changed and to associate this base version with the change entry.
Values:
AUTO
Db2 Admin Tool automatically determines the objects that are in the base version based on the objects that are being changed.
USER
The objects that are in the base version are defined by a version scope that is specified by the user.
NO
A new base version is not generated after the change is implemented.
Default:
NO
GENERATE_JOB_CLASS
Specifies whether to include the CLASS parameter on the job card. If you include the CLASS parameter on the job card, end the last line of the job card with a comma because Db2 Admin Tool places the CLASS parameter on a new line.
Values:
Y
Generate a job class parameter with the value of the JOB_CLASS parameter.
N
Do not generate a job class parameter.
Default:
Y
GENERATE_RECOVER_CHANGE
Specifies whether to generate a recover change if the change does not already have a recover change. If the change already has a recover change, the recover change is regenerated.
Values:
Y
A recover change is generated during analyze.
N
If the change does not have a recover change, a recover change is not generated. Otherwise, this parameter is forced to be set to Y and the recover change is regenerated.
Default:
N
GENERATE_TEMPLATES
Specifies whether to generate templates.
Values:
Y
Use the user-defined templates in the ADBTEMPL DD data definition. Refer to Symbol variables in the ADBTEMPL file: Db2 TEMPLATE support for information about using symbol variables to specify Db2 TEMPLATE statements.
N
Use the Db2 Admin Tool default template statements.
Default:
N
GRANT_ORDER
Specifies which prefix the GRANT statement will use.
Values:
C
Generates the GRANT statement with the CREATE prefix.
P
Generates the GRANT statement with the POSTUTIL prefix.
Default:
C
IDENTITY_START_VALUE
Specifies the START value of an IDENTITY column of a table if the table is re-created.
Values:
O
The START value from the Db2 catalog is used.
C
The START value is computed based on the identity attributes of the column.
Default:
O
Start of changeIGNORE_COLUMN_ORDEREnd of change
Start of changeSpecifies whether to ignore any differences in column order when comparing tables. When you set this parameter to YES, some column changes that otherwise require the table to be dropped and recreated can be done by ALTER operations.
Values:
YES
The column order is ignored. When possible, column changes are done by using ALTER statements.
NO
The column order is not ignored. If necessary to preserve the column order, column changes are made by dropping and recreating the table.
Default:
NO
End of change
IGNORE_COMMENT
Specifies the comment for a new ignore.
Values:
Specify a 1- 128-character comment or leave this parameter blank.
Default:
blank
IGNORE_NAME
Specifies the name for an existing ignore or a new ignore, depending on what action the Change Management (CM) batch interface invoked. If an ignore is being imported and if the value for the NEW_IGNORE_NAME parameter is blank, this parameter specifies the name for the new ignore.
Values:
Specify a valid 1- 128-character ignore name.
Default:
AUTO:&CURTS.
IGNORE_OWNER
Specifies the owner for an existing ignore or a new ignore, depending on what action the Change Management (CM) batch interface invoked. If an ignore is being imported and if the value for the NEW_IGNORE_OWNER parameter is blank, this parameter specifies the owner for the new ignore.
Values:
Specify a valid 1- 128-character ignore owner.
Default:
&CURSQLID.
IMPORT_PENDING_CHANGE_ACTION
Specifies the action that occurs if the import data set contains changes to objects that have changes pending from Db2 Admin Tool Change Management.
Values:
P
Make the pending changes a prerequisite for the imported change.
S
Supersede the pending changes and continue importing the change. The pending changes are placed in DEFINED status and will have the superseded change as a prerequisite.
I
Ignore the pending changes and continue importing the change. Analyzed pending changes are left in ANALYZED status and prerequisites are not established.
C
Cancel the import change process.
Default:
P
JOB_CARD_LINE_1
Specifies line 1 of the job card for generated jobs.
Values:
Specify a 1- to 72-character statement.
Default:
//&USERID.D JOB (&SYSUID),'CM BATCH',
JOB_CARD_LINE_2
Specifies line 2 of the job card for generated jobs.
Values:
Specify a 1- to 72-character statement.
Default:
// REGION=0K,NOTIFY=&SYSUID,MSGCLASS=H,MSGLEVEL=(1,1),
JOB_CARD_LINE_3
Specifies line 3 of the job card for generated jobs.
Values:
Specify a 1- to 72-character statement.
Default:
blank
JOB_CARD_LINE_4
Specifies line 4 of the job card for generated jobs.
Values:
Specify a 1- to 72-character statement.
Default:
blank
JOB_CARD_LINE_5
Specifies line 5 of the job card for generated jobs.
Values:
Specify a 1- to 72-character statement.
Default:
blank
JOB_CLASS
Specifies the CLASS parameter value for the job card.
Values:
Specify a valid job class.
Default:
A
JOB_JCLLIB_LINE_1
Specifies line 1 of the JCLLIB statement. The GOCCM JCL procedure must be accessible in the libraries that are defined by the JCLLIB statement in the run job or in the system procedure libraries.
Values:
Specify a 1- to 72-character statement.
Default:
blank

The following example shows how to set this parameter:

JOB_JCLLIB_LINE_1 = '//GOCCM JCLLIB ORDER=ADB.DEVCUST.JCLLIB’
This example results in the following JCL line in jobs that are generated by Change Management (CM) batch interface:
//GOCCM JCLLIB ORDER=ADB.DEVCUST.JCLLIB
JOB_JCLLIB_LINE_2
Specifies line 2 of the JCLLIB statement.
Values:
Specify a 1- to 72-character statement.
Default:
blank
JOB_JCLLIB_LINE_3
Specifies line 3 of the JCLLIB statement.
Values:
Specify a 1- to 72-character statement.
Default:
blank
JOB_JCLLIB_LINE_4
Specifies line 4 of the JCLLIB statement.
Values:
Specify a 1- to 72-character statement.
Default:
blank
JOB_PARM_LINE_1
Specifies line 1 of the job parameter area.
Values:
Specify a 1- to 72-character statement.
Default:
blank

The following example shows how to set this parameter:

JOB_PARM_LINE_1='S=SYS4A'
This example results in the following line in JCL that is generated by Change Management (CM) batch interface:
/*JOBPARM S=SYS4A
JOB_PARM_LINE_2
Specifies line 2 of the job parameter area.
Values:
Specify a 1- to 72-character statement.
Default:
blank
JOB_PARM_LINE_3
Specifies line 3 of the job parameter area.
Values:
Specify a 1- to 72-character statement.
Default:
blank
JOB_PARM_LINE_4
Specifies line 4 of the job parameter area.
Values:
Specify a 1- to 72-character statement.
Default:
blank
LIST_OPTIONS
Specifies whether ADBMSGS includes the following lists of CM batch parameter values:
  • A list of the parameter values that were provided in an invocation override (by using the PARMS DD statement)
  • A list of the final parameter values that were used
Values:
Y
These two lists are included. Each list is identified in ADBMSGS by message ADB7957I.
N
These lists are not included.
Default:
N
LOAD_ACCELERATED_TABLES_DETECT_CHANGES
Specifies the value of detectChanges for the SYSPROC.ACCEL_LOAD_TABLES procedure for accelerated tables.
Values:
DATA
For information about DATA, see the description of detectChanges in SYSPROC.ACCEL_LOAD_TABLES (IBM DB2 Analytics Accelerator for z/OS 7.5).
PARTITIONS
For information about PARTITIONS, see the description of detectChanges in SYSPROC.ACCEL_LOAD_TABLES (IBM DB2 Analytics Accelerator for z/OS 7.5).
NONE
DetectChanges is not used when calling SYSPROC.ACCEL_LOAD_TABLES.
Default:
DATA
MASK_COMMENT
Specifies the comment for a new mask.
Values:
Specify a 1- 128-character comment or leave this parameter blank.
Default:
blank
MASK_IGNORED_FIELDS
Specifies whether ignores takes precedence for newly added objects when both ignores and masks are specified for a specific attribute.
Values:
YES
Masks are applied to ignored fields.
NO
Ignored fields retain their original values.
Default:
NO
MASK_NAME
Specifies the name for an existing mask or a new mask, depending on what action the Change Management (CM) batch interface invoked. If a mask is being imported and if the value for the NEW_MASK_NAME parameter is blank, this parameter specifies the name for the new mask.
Values:
Specify a 1- 128-character mask name or leave this parameter blank.
Default:
AUTO:&CURTS.
Start of changeMASK_OWNEREnd of change
Start of changeSpecifies the owner for an existing mask or a new mask, depending on what action the Change Management (CM) batch interface invoked. If a mask is imported and if the value for the NEW_MASK_OWNER parameter is blank, this parameter specifies the owner for the new mask.
Values:
Specify a 1- 128-character mask owner or leave this parameter blank.
Default:
&CURSQLID.
End of change
MAX_ALLOCATION_TO_DASD
Specifies the maximum amount of space that can be allocated to DASD. This parameter applies only to new copy and unload data sets. When the space that is required for an unload or copy data set exceeds this threshold value, the data set is allocated to the tape unit that is specified in SPACE_TAPE_UNIT.
Values:
Specify an integer value.
Default:
3145680
MAX_PRIQTY_IN_KB
Specifies the maximum amount of primary space that can be allocated to DASD. This parameter applies only to new copy and unload data sets.
Values:
Specify a valid PRIQTY value. You can specify the following values:
  • A number that indicates the number of space units specified.
  • Blank, which causes the kilobyte value shown to be converted to a value that is measured in terms of the space specified.
  • 99999999, which indicates the maximum space allowed by MVS™ for the space unit that is specified.
Default:
3145680
Start of changeMTC_CENTRAL_LOCATIONEnd of change
Start of changeSpecifies the location to use to look for changes when analyzing a multi-target change. If you do not specify a value, CM batch looks for the specified change at the current location.

To use MTC_CENTRAL_LOCATION, a DRDA connection is required between the central and remote subsystems.

Values:
Specify a valid Db2 location name.
Default:
blank
End of change
NEW_BASE_VERSION_NAME
Specifies the default name for a new base version. If this parameter is not blank, this parameter determines the default name for a new base version. Otherwise, the NEW_BASE_VERSION_NAME parameter determines the name for a new base version.
If a value is specified for a more specific base version type, for example: BASE_VERSION_NAME_BEFORE_RUN, that value is used for that base version type instead of the value specified for NEW_BASE_VERSION_NAME.
Base version parameter hierarchy:
  • BASE_VERSION_OWNER
    • NEW_BASE_VERSION_OWNER
      • BASE_VERSION_OWNER_BEFORE_RUN
      • BASE_VERSION_OWNER_AFTER_RUN
  • BASE_VERSION_NAME
    • NEW_BASE_VERSION_NAME
      • BASE_VERSION_NAME_BEFORE_RUN
      • BASE_VERSION_NAME_AFTER_RUN
Values:
1 to 128 characters
Default:
BASE_VERSION_NAME
NEW_BASE_VERSION_OWNER
Specifies the default owner for a new base version. If this parameter is not blank, this parameter determines the default name for a new base version. Otherwise, the NEW_BASE_VERSION_NAME parameter determines the owner for a new base version.
If a value is specified for a more specific base version type, for example, BASE_VERSION_OWNER_BEFORE_RUN, that value is used for that base version type instead of the value that is specified for NEW_BASE_VERSION_OWNER.
Base version parameter hierarchy:
  • BASE_VERSION_OWNER
    • NEW_BASE_VERSION_OWNER
      • BASE_VERSION_OWNER_BEFORE_RUN
      • BASE_VERSION_OWNER_AFTER_RUN
  • BASE_VERSION_NAME
    • NEW_BASE_VERSION_NAME
      • BASE_VERSION_NAME_BEFORE_RUN
      • BASE_VERSION_NAME_AFTER_RUN
Values:
1 to 128 characters
Default:
BASE_VERSION_OWNER
NEW_CHANGE_NAME
Specifies the name for a new change. If this parameter is not blank, this parameter determines the name for a new change. Otherwise, the CHANGE_NAME parameter determines the name for a new change.
Values:
Specify a 1- to 128-character change name or leave this parameter blank.
Default:
blank, which results in the value of the CHANGE_NAME parameter being used as the name for the new change.
NEW_CHANGE_OWNER
Specifies the owner for a new change. If this parameter is not blank, this parameter determines the owner for a new change. Otherwise, the CHANGE_OWNER parameter determines the owner for a new change.
Values:
Specify a 1- to 128-character change owner or leave this parameter blank.
Default:
blank, which results in the value of the CHANGE_OWNER parameter being used as the name for the new change owner.
NEW_IGNORE_NAME
Specifies the name for a new ignore. If this parameter is not blank, it determines the name for a new ignore. Otherwise, the IGNORE_NAME parameter determines the name for a new ignore.
Values:
Specify a 1- to 128-character ignore name or leave this parameter blank.
Default:
blank, which results in the value of the IGNORE_NAME parameter being used as the name for the new ignore.
NEW_IGNORE_OWNER
Specifies the owner for a new ignore. If this parameter is not blank, it determines the owner for a new ignore. Otherwise, the IGNORE_OWNER parameter determines the owner for a new ignore.
Values:
Specify a 1- to 128-character ignore owner or leave this parameter blank.
Default:
blank, which results in the value of the IGNORE_OWNER parameter being used as the name for the new ignore owner.
NEW_MASK_NAME
Specifies the name for a new mask. If this parameter is not blank, it determines the name for a new mask. Otherwise, the MASK_NAME parameter determines the name for a new mask.
Values:
Specify a 1- to 128-character mask name or leave this parameter blank.
Default:
blank, which results in the value of the MASK_NAME parameter being used as the name for the new mask name.
Start of changeNEW_MASK_OWNEREnd of change
Start of changeSpecifies the owner for a new mask. If this parameter is not blank, it determines the owner for a new mask. Otherwise, the MASK_OWNER parameter determines the owner for a new mask.
Values:
Specify a 1- to 128-character mask owner or leave this parameter blank.
Default:
blank, which results in the value of the MASK_OWNER parameter being used as the name for the new mask owner.
End of change
OVR_CONFIGDB_ERROR
Specifies whether Db2 Admin Tool should continue processing when change information is unable to be stored in the InfoSphere® Optim™ Configuration Manager repository database or the backup tables on the local system. This option applies only if integration with InfoSphere Optim Configuration Manager is enabled and the action on error setting is set to allow the override parameter.
Values:
YES
If integration with InfoSphere Optim Configuration Manager (OCM) is enabled and the action on error setting is set to allow the override parameter, Db2 Admin Tool continues processing the change even if the OCM repository database and the backup tables on the local system are not available.
NO
If integration with InfoSphere Optim Configuration Manager (OCM) is enabled, Db2 Admin Tool stops processing the change if the OCM repository database and the backup tables on the local system are not available.
Default:
NO
PDS_FOR_RECOVER_JCL
Specifies the name of a PDS to store the generated recover jobs.
Values:
A valid PDS data set name
Specify a 1- to 46-character data set name. If this name is not enclosed in single quotation marks, the fully qualified data set name is PREFIX_FOR_DATA_SETS.PDS_FOR_RECOVER_JCL.
Default:
&SSID..RECOVER.JCL
PDS_FOR_RECOVER_WSL
Specifies the name of a PDS to store the work statement lists (WSLs) that the analyze job generates for the recover change.
Values:
A valid PDS data set name
Specify a 1- to 46-character data set name. If this name is not enclosed in single quotation marks, the fully qualified data set name is PREFIX_FOR_DATA_SETS.PDS_FOR_RECOVER_WSL.
Default:
&SSID..RECOVER.WSL
PDS_FOR_RUN_JCL
Specifies the name of a PDS to store the generated run jobs, or, if ACTION_GENERATE_JCL_FROM_WSL = 'Y', a PDS to store the JCL that is generated from a WSL.
Values:
A valid PDS data set name
Specify a 1- to 46-character data set name. If this name is not enclosed in single quotation marks, the fully qualified data set name is PREFIX_FOR_DATA_SETS.PDS_FOR_RUN_JCL.
Default:
&SSID..RUN.JCL
PDS_FOR_RUN_JOB_INPUT
Specifies the name of a PDS in which the run job or recover job input data is stored. This parameter is used only when USE_PERMANENT_DATA_SET_FOR_RUN_JOB_INPUT is set to Y. You must ensure the same run job input PDS is not used for different changes. Using the same run job input PDS for different changes can cause problems when a change is run.
Values:
A valid PDS data set name
Specify a 1- to 46-character data set name. If this name is not enclosed in single quotation marks, the fully qualified data set name is PREFIX_FOR_DATA_SETS.PDS_FOR_RUN_JOB_INPUT.
Default:
&SSID..&CHGTAG..IN
PDS_FOR_WSL
Specifies the name of the PDS to store the work statement list (WSL) that the analyze job generates for the change.
Values:
A valid PDS data set name
Specify a 1- to 46-character data set name. If this name is not enclosed in single quotation marks,, the fully qualified data set name is PREFIX_FOR_DATA_SETS.PDS_FOR_WSL.
Default:
&SSID..RUN.WSL
PDS_FOR_WSL_CONV
Specifies the name of the PDS that has or will have the readable work statement list (WSL). If ACTION_CONVERT_TO_READ_WSL= 'Y' is specified, the readable WSL will be generated. If ACTION_CONVERT_TO_ISPF_WSL = 'Y' is specified, the readable WSL must already exist.
Values:
Valid PDS data set names. 1 - 46 characters. If the name is not enclosed in single quotation marks, the fully qualified data set name is PREFIX_FOR_DATA_SETS.PDS_FOR_WSL_CONV.
Default:
blank
PERCENT_INCREASE_FOR_CONVERTED_DATA_SETS
Specifies the percentage increase in size of the converted unload data set over the unload data set. The ALT/Object Compare process converts data from the UNLOAD step. The newly converted data might require more space than the unload data set. This parameter allows you to increase the size of the converted data set by a percentage greater than the unload data set, therefore helping to avoid out-of-space conditions.
Values:
A number in the range 0-100.
Default:
0
PLAN
Specifies the Db2 plan name to connect with.
Values:
Specify a 1- to 8-character Db2 plan name.
Default:
ADB
PREFIX_FOR_DATA_SETS
Specifies the data set prefix that is used when data sets are allocated, such as: WSL PDS, JCL PDS, UNLOAD, LOAD, and so on.
Values:
Specify a 1- to 17-character data set prefix.
Default:
&USERID.
PRESERVE_ALL_DATA
Specifies whether the change is to be implemented by a series of alter operations or by dropping and recreating the table. This option applies only to those changes that alter the NULLS value of a column that is at the end of the column list and is type VARCHAR.
Values:
YES
The table is dropped and recreated (by using UNLOAD, DROP, CREATE, and LOAD operations) so that the column data is preserved.
NO
The column is altered by using ALTER TABLE statements, which results in data loss for the affected columns. If you want to save a copy of the data, specify UNLOAD_ALTERED_TABLES = YES.
Default:
YES
PROCESSING_ORDER
Specifies the order that the objects will be processed in.
Values:
T
Object type processing will be performed. This process compares one object type at a time.
H
Database hierarchy processing will be performed. This process compares all object types within a database hierarchy at the same time. This is the default value.
Note: If you choose not to disable REORG optimization, the compare process will set your PROCESSING_ORDER value to H and continue processing using REORG optimization.
Default:
H
Start of changeREBIND_ADDITIONAL_OPTSEnd of change
Start of changeSpecifies one or more additional BIND options for the generated REBIND PACKAGE and REBIND TRIGGER PACKAGE statements.

Options must be in the format option_name(option_value). For example:

REBIND_ADDITIONAL_OPTS = 'FLAG(I) IMMEDWRITE(NO)'

The specified additional options are added to the REBIND statement as is; the syntax is not checked or formatted.

Values:
One or more valid REBIND options. The maximum total length of this value is 325 characters.
Default:
blank
End of change
Start of changeREBIND_APREUSEEnd of change
Start of changeSpecifies the APREUSE option for the generated REBIND PACKAGE and REBIND TRIGGER PACKAGE statements. APREUSE specifies whether Db2 tries to reuse previous access paths for SQL statements in the package.
Values:
NONE or N
APREUSE(NONE) is added to the REBIND statement.
WARN or W
APREUSE(WARN) is added to the REBIND statement.
ERROR or E
APREUSE(ERROR) is added to the REBIND statement.
blank
The APREUSE option is not added to the REBIND statement.
Default:
blank
End of change
Start of changeREBIND_EXPLAINEnd of change
Start of changeSpecifies the EXPLAIN option for the generated REBIND PACKAGE and REBIND TRIGGER PACKAGE statements. EXPLAIN specifies whether the bind process is to capture EXPLAIN information for SQL statements in the package.
Values:
YES or Y
EXPLAIN(YES) is added to the REBIND statement.
NO or N
EXPLAIN(NO) is added to the REBIND statement.
ONLY or O
EXPLAIN(ONLY) is added to the REBIND statement
blank
The EXPLAIN option is not added to the REBIND statement.
Default:
blank
End of change
Start of changeREBIND_OWNEREnd of change
Start of changeSpecifies the OWNER option for the generated REBIND PACKAGE statements. OWNER specifies the authorization ID of the package owner.

This option is not generated for REBIND TRIGGER PACKAGE statements.

Values:
A valid owner name. The maximum length is 128 characters.
Default:
blank
End of change
Start of changeREBIND_OWNERTYPEEnd of change
Start of changeSpecifies the OWNERTYPE option for the generated REBIND PACKAGE statements. OWNERTYPE specifies whether OWNER is a role or user authorization ID.

REBIND_OWNERTYPE is used only if REBIND_OWNER is also specified. REBIND_OWNERTYPE is ignored if the Db2 subsystem version is earlier than Db2 13.

Values:
USER or U
OWNERTYPE (USER) is added to the REBIND statement.
ROLE or R
OWNERTYPE (ROLE) is added to the REBIND statement.
blank
The OWNERTYPE option is not added to the REBIND statement.
Default:
blank
End of change
RECOVER_CHANGE_COMMENT
Specifies the comment for a recover change.
Values:
Specify a 1- to 128-character comment or leave this field blank.
Default:
blank
RECOVER_CHANGE_NAME
Specifies the name for a new recover change. If this parameter is not blank, this parameter determines the name for a new recover change. Otherwise, the name for a new recover change is the original change name with _RCVR appended.
Values:
Specify a 1- to 128-character change name.
Default:
The name of original change with _RCVR appended
RECOVER_CHANGE_OWNER
Specifies the owner for a new recover change. If this parameter is not blank, this parameter determines the owner for a new recover change. Otherwise, the owner for a new recover change is the same owner as its original change.
Values:
Specify a 1- to 128-character change owner.
Default:
The owner of original change
RECOVER_OPTION
Specifies the type of recover to be performed by the recover change process if DATA_TO_RECOVER = ‘B’ or if RECOVER_WITHDDL= ‘Y’. If neither of these conditions are true, leave RECOVER_OPTION blank.
Values:
O
Recover using the original data. The original data is the data that is unloaded when the original change is run. If you use the original data during a recovery operation, consider whether related tables that were not affected by the recover must also be restored to the same point to avoid inconsistencies. This option applies only to tables that were unloaded in the original change.
E
Recover using the existing data. The existing data is the data that exists in the table just before the original change is recovered. If a table is dropped without being re-created in the original change, no data is loaded after the table is created in the recover change.
D
Recover with DDL only and ignore data.
Default:
blank
Recover using the option that was specified when the recover change was set up. If DATA_TO_RECOVER= 'B' or RECOVER_WITHDDL = ‘Y’, blank is not valid; you must specify a value for RECOVER_OPTION.
RECOVER_PENDING_CHANGE_ACTION
Specifies the action that occurs if the change being recovered contains changes to objects that have changes pending from Db2 Admin Tool Change Management.
Values:
S
This option recovers the specified change and set to DEFINED status for any pending change that modifies the same or related objects. The recover change supersedes any pending changes that modify the same or related objects.
C
This option prevents the change from being recovered when pending changes will modify the same or related objects. If there are pending changes, the changes are not recovered. To recover this change and to set the status of any pending changes to DEFINED, set the value of this parameter to S (supersede).
Default:
C
RECOVER_WITHDDL
Specifies whether recover change can recover using DDL only and no data.
Values:
Y
Recover change can recover using DDL only and ignore data.
N
Recover change can not recover using DDL only.
Default:
N
RECREATE_ACCELERATED_TABLES
Specifies whether to automatically detect and recreate accelerated tables, in DROP/CREATE or ALTER situations, involving changes to its definition or partitions.
Values:
YES
Recreate accelerated tables.
NO
Do not recreate accelerated tables.
Default:
YES
If RECREATE_ACCELERATED_TABLES is set to NO, the following related options must also be set to NO:
RELOAD_ACCELERATED_TABLES
Specifies whether to automatically detect and reload accelerated tables in DROP/CREATE or ALTER situations of accelerated tables, involving changes to its definition, data or partitions.
Y
Reload accelerated tables.
N
Do not reload accelerated tables.
Default:
Y

If RELOAD_ACCELERATED_TABLES is set to YES, RECREATE_ACCELERATED_TABLES must also be set to YES.

If RELOAD_ACCELERATED_TABLES is set to NO, the following related options must also be set to NO:
REMOVE_ACCELERATED_TABLES
Specifies whether to automatically detect and remove dropped Db2 tables involved in change management from the accelerator.
Values:
YES
Remove accelerated tables.
NO
Do not remove accelerated tables.
Default:
YES
REPLICATE_ACCELERATED_TABLES
Specifies whether to enable replication for accelerated tables that are automatically re-created and reloaded in DROP/CREATE or ALTER situtations.
Values:
Y
Replicates accelerated tables.
N
Does not replicate accelerated tables.
Default:
Y

If REPLICATE_ACCELERATED_TABLES is set to YES, RELOAD_ACCELERATED_TABLES must also be set to YES.

REPORT_EXPECTED_CONVERSION_PROBLEMS
Specifies whether a report is generated of the data conversion problems for tables that are expected to occur when the change is run.
Values:
Y
The report includes the expected conversion problems for tables when the change is run.
N
The report does not include a list of expected conversion problems.
Default:
N
REPORT_OBJECT_COUNT
Specifies whether a statistics report is generated of compared and changed objects for each object type.
Values:
Y
The report includes statistics of compared and changed objects for each object type.
N
The report does not include the object count statistics.
Default:
N
REPORT_OBJECT_TOTALS
Specifies whether a summary report of the overall totals for each object type is generated. The number of altered, created, dropped, or recreated objects for each object type is included.

The Totals Report contains the overall totals of objects affected and includes values from the Analyze step from each of the target systems.

Note: Specifying REPORT_OBJECT_TOTALS = 'Y' forces REPORT_OBJECT_COUNTS to be set to 'Y'.
Values:
Y
The report includes the object totals report.
N
The report does not include the object totals report.
Default:
N
REPORT_ONLY_CHANGED_OBJECTS
Specifies whether to report objects which are identical in the source and the target.
Values:
Y
The report does not include objects that are identical in the source and target.
N
The report includes objects that are identical in the source and the target.
Default:
N
Start of changeREPORT_ORIGINAL_NAMES_ADDED_OBJECTSEnd of change
Start of changeSpecifies whether to report the original names of any objects added to the target. Reporting these names can be useful if the target object names are masked and therefore different than the source object names.
Values:
Y or YES
The summary report is to include the original names. In the report, the original name is listed under Source Object, and the new name is listed under Target Object.
N or NO
The summary report is not to include the original names.
Default:
N
End of change
REPORT_STMT_TOTALS
Specifies whether a totals report of totals for each statement type is generated during the Run phase. The number of ALTER, CREATE, or DROP statements issued for each object type is included.
Values:
Y
The report includes the statement totals report.
N
The report does not include the statement totals report.
Default:
N
REPORT_SUMMARY
Specifies whether to include a brief summary of changes for each object in the report.
Values:
Y
The report includes a brief summary of changes for each object.
N
The report does not include a brief summary.
Default:
N
REPORT_SYSTEM_GENERATED_IGNORE_FIELDS
Specifies whether to include in the report the system generated names of the fields that are ignored.
Values:
Y
The report includes system generated names of the fields that are ignored by the compare or analyze process.
N
The report does not include system generated names of the fields that are ignored.
Default:
N
REPORT_TRANSLATION_MASKS
Specifies whether to report the translation masks that are used.
Values:
Y, N
Y
The report includes the masks used by the compare or analyze process.
N
The report does not include the masks that are used.
Default:
N
REPORT_USER_SPECIFIED_IGNORE_FIELDS
Specifies whether the report includes the user-defined names of the fields that are ignored.
Values:
Y
The report includes user-defined names of the fields that are ignored by the compare or analyze process.
N
The report does not include user-defined names of the fields that are ignored.
Default:
N
RETAIN_GENERATED_ALWAYS_FOR_ROW_CHANGE_TS
Specifies whether to retain GENERATED ALWAYS for the designated column types (ROWID or ROW CHANGE TIMESTAMP).
Values:
Y
Retain the GENERATED ALWAYS attribute for row change time stamp columns.
N
Do not retain the GENERATED ALWAYS attribute for row change time stamp columns.
Default:
N
RETAIN_GENERATED_ALWAYS_FOR_ROWID
Specifies whether to retain GENERATED ALWAYS for the designated column types (ROWID or ROW CHANGE TIMESTAMP).
Values:
Y
Retain the GENERATED ALWAYS attribute for rowid columns.
N
Do not retain the GENERATED ALWAYS attribute for rowid columns.
Default:
N
RUN_CHECK_DATA
Specifies whether to generate a CHECK DATA utility job for the table spaces that are affected by the (RE)LOAD utility jobs that the analyze process generates in the WSL.
Values:
Y
Generate a CHECK DATA utility job for each table space that is affected by a LOAD utility.
N
Do not generate a CHECK DATA utility job.
Default:
N
RUN_REBIND
Specifies whether to generate a job to rebind plans and packages that are affected by changes that are generated by Object Comparison Tool.
Values:
M
Generate REBIND statements for packages only if packages are invalidated by the changes.
A or Y
Generate REBIND statements for packages and plans that are affected by the change.
N
Do not generate REBIND statements.
Default:
N
RUN_REORG_REBUILD
Specifies whether to generate REORG table space and REBUILD index utility jobs after applying the changes from the analyze process, the purpose of which is to make the target operational.
Values:
M
Mandatory. Generate REORG utility statements to remove REORG-pending conditions.
A
All relevant. Generate all needed REORG utility statements to fully implement the effects of the changes, for example, space parameter changes.
N
None. No REORG utility statements are generated. This option is invalid if you specified NO for ALLOW_ROTATE_PARTS.
Default:
N
RUN_RUNSTATS
Specifies whether to generate a RUNSTATS utility job for the table spaces that are affected by the RE(LOAD) utility jobs and for the table spaces, tables, and indexes that are affected by SQL ALTER statements that the analyze process generates in the WSL.
Values:
R
Generate RUNSTATS utility statements for all tables that are affected by the (RE)LOAD utility.
A
Generate RUNSTATS utility statements for all altered table space, table, and index objects.
B
Generate RUNSTATS utility statements for objects that are affected by the RE(LOAD) utility and SQL ALTER statements.
M
Generate RUNSTATS utility statements for the following conditions:
  • If a table space is dropped and recreated, the tables and indexes are included in RUNSTATS.
  • If a table is dropped and recreated, only the indexes, and not the table, are included in RUNSTATS.
  • If an index is created, recreated, or has columns added, the index is included in RUNSTATS.
  • If the index is created with DEFER YES and REBUILD is generated, RUNSTATS is performed after the REBUILD.
N
No RUNSTATS utility statements are generated.
Default:
N
RUN_SQLID
Specifies whether SET CURRENT SQLID statements are generated and, if so, what SQLID value to use.
Values:
An SQLID
The specified Run SQLID is the owner of databases and table spaces. If the specified Run SQLID is different from the current owner, the databases, table spaces, and all dependent objects are dropped and re-created to accomplish the change of owner.
<NONE>
No SET CURRENT SQLID statements are generated.
blank
SET CURRENT SQLID statements are generated when necessary.
Default:
blank
SAVE_COMPARE_RESULTS
Specifies whether compare results are saved during the compare run. You can manage the saved compare result using the "MR - Manage saved compare results" dialogs, which you access from the Object Comparison Tool main menu.
Values:
YES, NO
Default:
NO
SAVE_SOURCE_BASE_VERSION
Specifies whether to save the source base version that is generated for the change during the analyze process. The source base version represents the Db2 object definitions after the change is implemented.
Values:
Y
The source base version generated during analyze is saved as a new base version.
N
The source base version generated during analyze is not saved.
Default:
N
SAVE_TARGET_BASE_VERSION
Specifies whether to save the target base version that is generated for the change during the analyze process. The target base version represents the Db2 object definitions as they existed in the Db2 catalog at analyze time, with Db2 Admin Tool change management pending changes applied, but without the changes for the specified change applied.
Values:
Y
The target base version that was generated during analyze is saved as a new base version.
N
The source base version during analyze is not saved.
Default:
N
SCOPE_WARNING
Specifies whether to issue a warning message if the target of an object comparison operation is automatically selected, and the source is not a table space. This message warns that objects that exist only in the target might be dropped.
Values:
Y
Message ADB7353W is issued for this situation. This message is issued regardless of the value of the value of the Suppress DROP of objects field on the Generate Compare Jobs (GOC5) panel.
N
No message is issued.
Default:
N
SEQUENCE_RESTART_VALUE
Specifies what the value for the RESTART attribute is when a Db2 sequence object is re-created. Use this parameter only for recovery paths.
Values:
ORIGINAL, COMPUTED
Default:
ORIGINAL
SOURCE_DSN
Specifies the name of the data set that contains the compare source. Specifying this parameter overrides a pre-allocated compare source input file (SRCIN DD).
Values:
A data set name
Specify a 1- to 46-character data set name. If SOURCE_TYPE = 'DDL', specify the name of the data set that contains the DDL for the compare source.
If SOURCE_TYPE = 'USER', specify the name of the data set that contains the list of Db2 Admin Tool quick scopes for the compare source.
blank
If SOURCE_TYPE = 'DDL', the SRCIN file must contain the DDL for the compare source.
If SOURCE_TYPE = 'USER', either the SOURCE_VERSION_SCOPE_OWNER and SOURCE_VERSION_SCOPE_NAME parameters must be specified, or the SRCIN file must contain the list of Db2 Admin Tool quick scopes for the compare source.
Default:
blank
SOURCE_EXCLUDE_NAME
Specifies the name of an Exclude Specification that is stored in the Change Management database. The SOURCE_EXCLUDE_OWNER and SOURCE_EXCLUDE_NAME parameters identify an existing Exclude Specification to be used for the compare source.
Values:
A valid exclude specification name, blank
A valid exclude specification name.
Specify a 1- to 128-character exclude specification name. The specified Exclude Specification is used for the source during the compare process.
blank
Exclude objects are not used for the compare source.
Default:
blank
SOURCE_EXCLUDE_OWNER
Specifies the owner of an Exclude Specification that is stored in the Change Management database. The SOURCE_EXCLUDE_OWNER and SOURCE_EXCLUDE_NAME parameters identify an existing Exclude Specification to be used for the compare source.
Values:
Specify a valid 1- to 128-character exclude specification owner.
Default:
&CURSQLID.
Start of changeSOURCE_GEN_FOREIGN_KEYSEnd of change
Start of changeSpecifies whether to generate DDL for ALTER TABLE ADD FOREIGN KEY for the source objects. SOURCE_GEN_FOREIGN_KEYS is valid only for SOURCE_TYPE = 'USER'.
Values:
Y
Generate the DDL.
D
Generate the DDL and extract foreign keys for tables that are dependent on the tables being extracted.
N
Do not generate DDL.
Default:
blank
End of change
SOURCE_LOCATION
Specifies the Db2DB2®location for the compare source when the Db2 objects are located in a Db2 subsystem.
Values:
Specify a valid 1- to 128-character location name that is defined in SYSIBM.LOCATIONS or leave this parameter blank to specify the local Db2 subsystem.
blank
The local Db2 subsystem.
Default:
blank
SOURCE_TYPE
Specifies the type of input that identifies the Db2 objects for the source of the compare.
Values:
DDL
The source is DDL. To specify the data set that contains the DDL, use the compare source input file (SRCIN DD) or the SOURCE_DSN parameter. If the SOURCE_DSN parameter is not specified, the compare source input file (SRCIN DD) must be pre-allocated.
USER
Start of changeThe source is a Db2 subsystem, and the list of object names is provided by the user. To specify the list of Db2 objects, use a Db2 Admin Tool version scope, a list of Db2 Admin Tool quick scopes, or both. A quick scope can include an SQL SELECT statement to identify the objects.

To specify an existing scope, use the SOURCE_VERSION_SCOPE_OWNER and SOURCE_VERSION_SCOPE_NAME parameters. To specify a data set that contains a list of Db2 Admin Tool quick scopes, use the compare source input file (SRCIN DD) or the SOURCE_DSN parameter.

End of change
Default:
DDL
Related information:
SOURCE_VERSION_COMMENT
Specifies a comment or description of the source version.
Values:
Specify a 1- to 128-character comment, or leave this field blank.
Default:
blank
SOURCE_VERSION_NAME
Specifies the name for the base version that will store the generated source base version work file. If the SOURCE_VERSION_OWNER and SOURCE_VERSION_NAME parameters identify an existing base version, the EXISTING_BASE_VERSION_ACTION parameter controls whether the existing base version is replaced or a product-generated version name is used.
Values:
Specify a valid 1- to 128-character version name.
Default:
AUTO:OC.&CURTS..SRCVF
SOURCE_VERSION_OWNER
Specifies the owner for the base version that will store the generated source base version work file. If the SOURCE_VERSION_OWNER and SOURCE_VERSION_NAME parameters identify an existing base version, the EXISTING_BASE_VERSION_ACTION parameter controls whether the existing base version is replaced or a product-generated version name is used.
Values:
Specify a valid 1- to 128-character version owner.
Default:
&CURSQLID.
SOURCE_VERSION_SCOPE_NAME
Specifies the name of the version scope for the compare source. It is only used if the source type is USER.
Values:
A valid version scope name; 1 to 128 characters, blank
A valid version scope name.
Specify a valid 1- to 128-character version scope name. If SOURCE_TYPE = 'USER', the version scope that is specified by SOURCE_VERSION_SCOPE_OWNER and SOURCE_VERSION_SCOPE_NAME is used for the Db2 object list for the compare source.
blank
If SOURCE_TYPE = 'USER', a list of Db2 Admin Tool quick scopes must be specified in a pre-allocated SRCIN DD file or in the data set that is specified by the SOURCE_DSN parameter.
Default:
blank
SOURCE_VERSION_SCOPE_OWNER
Specifies the owner of the version scope for the compare source. This parameter is used only if the source type is USER.
Values:
Specify a valid 1- to 128-character version scope owner.
Default:
&CURSQLID.
SOURCE_VERSION_TYPE
Specifies the final disposition of the generated source base version work file. If the SRCVF file is pre-allocated, this parameter has no effect for types FILE and TEMP.
Values:
FILE
If the SRCVF file is not pre-allocated, it is allocated by using the attributes from ADMIN_DATASET_TYPE = 'SRCVF'.
DB2
If the SRCVF file is not pre-allocated, it is allocated by using the attributes from ADMIN_DATASET_TYPE = 'SRCVF' but as a temporary file. The file contents are stored in the Db2 Admin Tool change management repository using the owner and name values from the SOURCE_VERSION_OWNER and SOURCE_VERSION_NAME parameters.
TEMP
If the SRCVF file is not pre-allocated, it is allocated by using the attributes from ADMIN_DATASET_TYPE = 'SRCVF' but as a temporary file.
Default:
FILE
SPACE_TAPE_UNIT
Specifies the name of a valid tape unit. This parameter applies only to new copy and unload data sets.
Values:
Specify a valid space unit for tape.
Default:
TAPE
SPACE_UNIT
Specifies the units in which new data sets are to be allocated. This parameter applies only to new copy and unload data sets. Specifying BLK causes Db2 Admin Tool to allocate in blocks of 8192 bytes, which is the block size used by the Db2 Unload utility.
Values:
Specify a valid space unit.
Default:
TRK
SPACE_UNIT_NAME
Specifies the default unit name.
Values:
Specify a valid space unit name.
Default:
SYSALLDA
SSID
Specifies the Db2 subsystem to connect to.
Values:
Specify a valid 1- to 4-character Db2 subsystem ID.
Default:
This parameter does not have a default value.
STOP_ON_CONVERSION_ERROR
Specifies whether to stop WSL processing when data conversion errors occur.
Values:
Y
Stop WSL processing with RC=28 when conversion errors occur.
N
Do not stop WSL processing when conversion errors occur.
Default:
N
SUPPRESS_ADDING_COLUMNS
Specifies whether compare should suppress adding target columns.
Values:
YES, NO
Default:
NO
SUPPRESS_DROP_OF_COLUMNS
Specifies whether compare should suppress dropping target columns.
Values:
YES, NO
Default:
NO
SUPPRESS_DROP_OF_OBJECTS
Specifies whether the compare process suppresses dropping target objects that are in the target but that are not in the source.
Values:
YES, NO
Default:
NO

Regardless of the value that you set for this option, IBM Db2 Object Comparison Tool for z/OS replaces all relationships between a parent and a child if a foreign key is specified in the source. To delete a foreign key, both the parent and the child must be present in the source (without a foreign key). If DROP statements are part of the source DDL, objects are dropped regardless of the value that is specified for this parameter.

Regardless of the value that you set for this option, IBM Db2 Object Comparison Tool for z/OS drops all explicit LOB objects from the target if they are not specified on the source. However, if the base table that is associated with the LOB objects is kept because 'Suppress DROP of objects' is set to 'YES', then all of the LOB objects are kept.

Note: If the TARGET_TYPE = 'AUTO' for Target is used, the SUPPRESS_DROP_OF_OBJECTS parameter is forced to a setting of YES. If NO was specified, a warning message is issued stating that the change was made.
SYMBOL_NAME
Specifies the name of a user-defined symbol variable to use to mask some of the parameter values at run time.
Values:
a valid symbol variable name
Specify a valid symbol variable name or leave this parameter blank. A valid symbol variable name begins with the ampersand (&) character and ends with the . character. The name can be 3-128 characters, the total of which includes the & and . characters. The name is converted to upper case.
Default:
blank
SYMBOL_VALUE
Specifies the value of a user-defined symbol variable to be used to mask some of the parameter values at run time.
Values:
Specify a 1- to 128-character value or leave this field blank.
Default:
blank
TAKE_AN_IMAGE_COPY
Specifies whether to generate a COPY utility job for the table spaces that are affected by the RE(LOAD) utility jobs and for the table spaces, tables, and indexes that are affected by SQL ALTER statements that the analyze process generates in the WSL.
Values:
R
Generate COPY utility statements for all tables that are affected by the (RE)LOAD utility.
A
Generate COPY utility statements for all altered table space, table, and index objects.
B
Generate COPY utility statements for objects that are affected by the RE(LOAD) utility and SQL ALTER statements.
N
No COPY utility statements are generated.
Default:
N
TARGET_ASSOCIATIONID
Specifies the association ID provided by multi-target central system used to identify the target change.
Values
The value originates from the multi-target change file, which cannot be modified by the user.
Default:
blank
TARGET_CHANGE_COMMENT
Specifies the comment for a new change on the target system.
Values:
1 to 128 characters
Default:
blank
TARGET_DSN
Specifies the name of the data set that contains the compare target. This parameter is used when the TARGET_TYPE is USER. Specifying this parameter overrides a pre-allocated compare target input file (TGTIN DD).
Values:
A data set name.
Specify a 1- to 46-character data set name. If TARGET_TYPE = 'USER', specify the name of the data set that contains the list of Db2 Admin Tool quick scopes for the compare target; One to 46 characters
blank
If TARGET_TYPE = 'USER', either the TARGET_VERSION_SCOPE_OWNER and TARGET_VERSION_SCOPE_NAME parameters must be specified, or the TGTIN file must contain the list of Db2 Admin Tool quick scopes for the compare target.
Default:
blank
TARGET_EXCLUDE_NAME
Specifies the name of an Exclude Specification that is stored in the Change Management database. The TARGET_EXCLUDE_OWNER and TARGET_EXCLUDE_NAME parameters identify an existing Exclude Specification to be used for the compare target.
Values:
A valid exclude specification name
Specify a valid 1- to 128-character exclude specification name. The specified Exclude Specification is used for the target during the compare process. One to 128 characters
blank
Exclude objects is not used for the compare target.
TARGET_EXCLUDE_OWNER
Specifies the owner of an Exclude Specification that is stored in the Change Management database. The TARGET_EXCLUDE_OWNER and TARGET_EXCLUDE_NAME parameters identify an existing Exclude Specification to be used for the compare target.
Values:
Specify a valid 1- to 128-character exclude specification owner.
Default:
&CURSQLID.
Start of changeTARGET_GEN_FOREIGN_KEYSEnd of change
Start of changeSpecifies whether to generate DDL for ALTER TABLE ADD FOREIGN KEY for the target objects. TARGET_GEN_FOREIGN_KEYS is valid only for TARGET_TYPE = 'AUTO'.
Values:
Y
Generate the DDL.
D
Generate the DDL and extract foreign keys for tables that are dependent on the tables being extracted.
N
Do not generate DDL.
Default:
blank
End of change
TARGET_IGNORE_NAME
Specifies the name of an existing Ignore Fields entry as defined in the Change Management database on the target system. The Ignore Fields entry on the target system, that is identified by the TARGET_IGNORE_OWNER and TARGET_IGNORE_NAME parameters, is used to ignore the Db2 columns when the change on the target system is analyzed.
Values:
A valid Ignore Fields name
Specify a valid 1- to 128-character ignore fields name.
blank
Ignore Fields name is not included in the statement.
Default:
blank
TARGET_IGNORE_OWNER
Specifies the owner of an existing Ignore fields entry defined in the Change Management database on the target system. The Ignore Fields entry on the target system, that is identified by the TARGET_IGNORE_OWNER and TARGET_IGNORE_NAME parameters, is used to ignore the Db2 columns when the change on the target system is analyzed.
Values:
A valid Ignore Fields owner
Specify a valid 1- to 128-character target ignore owner.
blank
Ignore Fields owner is not included in the statement.
Default:
blank
TARGET_LOCATION
Specifies the Db2 location for the compare target when the Db2 objects are located in a Db2 subsystem. If the compare result is imported as a new change (ACTION_IMPORT_CHANGE = 'Y') the target location must be the local Db2 subsystem.
Values:
Specify a location that is defined in SYSIBM.LOCATIONS or leave this field blank to specify the local Db2 subsystem.
Default:
blank
TARGET_MASK_NAME
Specifies the name of an existing mask defined in the Change Management database on the target system. The mask on the target system, that is identified by the TARGET_COMPARE_MASK_OWNER and TARGET_MASK_NAME parameters, is used to mask the change statements when the change on the target system is registered.
Values:
A valid mask name
Specify a valid 1- to 128-character target mask name.
blank
The mask name is not included in the statement.
Default:
blank
TARGET_COMPARE_MASK_OWNER
Specifies the owner of an existing mask defined in the Change Management database on the target system. The mask on the target system, that is identified by the TARGET_COMPARE_MASK_OWNER and TARGET_MASK_NAME parameters, is used to mask the change statements when the change on the target system is registered.
Values:
A valid mask owner
Specify a valid 1- to 128-character target mask owner.
blank
The mask owner is not included in the statement.
Default:
blank
TARGET_TYPE
Specifies the type of input that identifies the Db2 objects for the target of the compare.
Values:
AUTO
The target is a Db2 subsystem. The Db2 objects for the compare target are automatically selected by Db2 Admin Tool based on the content of the compare source.

If TARGET_TYPE=AUTO, you cannot specify TARGET_DSN, TARGET_VERSION_SCOPE_NAME, or a compare target input file (TGTIN DD).

USER
Start of changeThe target is a Db2 subsystem, and the list of object names is provided by the user. To specify the list of Db2 objects, use a Db2 Admin Tool version scope, a list of Db2 Admin Tool quick scopes, or both. A quick scope can include an SQL SELECT statement to identify the objects.

To specify an existing scope, use the TARGET_VERSION_SCOPE_OWNER and TARGET_VERSION_SCOPE_NAME parameters. To specify a data set that contains a list of Db2 Admin Tool quick scopes, use the compare target input file (TGTIN DD) or the TARGET_DSN parameter.

End of change
Start of changeDDLEnd of change
Start of changeThe target is DDL. To specify the data set that contains the DDL, use the compare target input file (TGTIN DD) or the TARGET_DSN parameter. If the TARGET_DSN parameter is not specified, the compare target input file (TGTIN DD) must be pre-allocated.
Attention: If the target DDL that is specified does not match the DDL in the Db2 database, problems might occur when running the resultant change. Therefore, consider using this option only when comparing DDL to DDL (TARGET_TYPE='DDL' and SOURCE_TYPE=’DDL’).
End of change
Default:
AUTO
Related information:
TARGET_VERSION_COMMENT
Specifies a comment or description of the target version.
Values:
Specify a 1- to 128-character comment or leave this field blank.
Default:
blank
TARGET_VERSION_NAME
Specifies the name for the base version that will store the generated target base version work file. If the TARGET_VERSION_OWNER and TARGET_VERSION_NAME parameters identify an existing base version, the EXISTING_BASE_VERSION_ACTION parameter controls whether the existing base version is replaced or a product-generated version name is used.
Values:
Specify a valid 1- to 128-character version name.
Default:
AUTO:OC.&CURTS..TGTVF
TARGET_VERSION_OWNER
Specifies the owner for the base version that will store the generated target base version work file. If the TARGET_VERSION_OWNER and TARGET_VERSION_NAME parameters identify an existing base version, the EXISTING_BASE_VERSION_ACTION parameter controls whether the existing base version is replaced or a product-generated version name is used.
Values:
Specify a valid 1- to 128-character version owner.
Default:
&CURSQLID.
TARGET_VERSION_SCOPE_NAME
Specifies the name of the version scope for the compare target. It is only used if the target type is USER.
Values:
A valid version scope name.
Specify a valid 1- to 128-character version scope name. If TARGET_TYPE = 'USER', the version scope that is specified by TARGET_VERSION_SCOPE_OWNER and TARGET_VERSION_SCOPE_NAME is used for the Db2 object list for the compare target.
blank
If TARGET_TYPE = 'USER', a list of Db2 Admin Tool quick scopes must be specified in a pre-allocated TGTIN DD file or in the data set specified by the TARGET_DSN parameter.
Default:
blank
TARGET_VERSION_SCOPE_OWNER
Specifies the owner of the version scope for the compare target. This parameter is used only if the TARGET_TYPE parameter is set to USER.
Values:
Specify a valid 1- to 128-character version scope owner.
Default:
&CURSQLID.
TARGET_VERSION_TYPE
Specifies the final disposition of the generated target base version work file. If the TGTVF file is pre-allocated this parameter has no effect for types FILE and TEMP.
Values:
FILE
If the TGTVF file is not pre-allocated, it is allocated by using the attributes from ADMIN_DATASET_TYPE = 'TGTVF'.
DB2
If the TGTVF file is not pre-allocated, it is allocated by using the attributes from ADMIN_DATASET_TYPE = 'TGTVF' but as a temporary file. The file contents are stored in the Db2 Admin Tool change management repository. The owner and name values are obtained from the TARGET_VERSION_OWNER and TARGET_VERSION_NAME parameters.
TEMP
If the TGTVF file is not pre-allocated, it is allocated by using the attributes from ADMIN_DATASET_TYPE = 'TGTVF', but as a temporary file.
Default:
FILE
TGT_DB2FL
Specifies the target function level for generated DDL statements. CM batch generates DDL statements based on the syntax requirements for the specified target function level.
Values:
One of the following valid formats to identify a Db2 function level:
  • V13R1Mmmm
  • V12R1Mmmm
  • mmm

For more information about function level identifiers, see Function levels and related levels in Db2 13 (Db2 13 for z/OS).

You can specify any function level equal to or less than the current Db2 function level.

Default:
The current Db2 function level
Start of changeUNLOAD_ALTERED_TABLESEnd of change
Start of changeSpecifies whether to unload altered tables as part of the analyze process. Regardless of the UNLOAD_ALTERED_TABLES value, the table is always unloaded if the change is performed by using DROP and CREATE.
Values:
YES or Y
Unload all altered tables.
DES or D
Unload only those altered tables where the alters are destructive. Destructive alters are changes that might result in the loss of data, such as ALTER TABLE DROP COLUMN.
NO or N
Do not unload any altered tables.
Default:
YES
End of change
UNLOAD_METHOD
Specifies the method that is used to unload the data.
Values:
U
Use the UNLOAD utility.
P
Use the Db2 Parallel UNLOAD utility.
H
Use Db2 High Performance Unload when available. The HPU option is supported only if an HPU load library is specified.
Default:
U
USE_DEFER_YES
Specifies whether to use DEFER YES clauses on any eligible CREATE INDEX statements. Any user-specified masks will have precedence. This value is also used for subsequent runtime analysis to ensure that the same DDL and Db2 Admin Tool statements are generated.
Values:
Y
Specify DEFER YES on eligible indexes.
N
Do not specify DEFER YES.
Default:
USE_DSNUTIL_SP
Specifies whether a Db2 stored procedure is used to run utilities.
Values:
YES or Y
Utilities are run by calling DSNUTILV.
NO or N
Utilities are invoked in the CM batch job.
Default:
YES
USE_IGNORE_FOR_IMPORT_CHANGE
Specifies whether an ignore is used for the imported change.
Values:
Y
If an ignore is also being imported, the ignore that is used for import change is the newly created ignore. Otherwise, the ignore that is used is identified by the IGNORE_OWNER and IGNORE_NAME parameters.
blank
Specifies that this parameter defaults to Y if an ignore and a change are imported.
Default:
blank
USE_MASK_FOR_EXPORT_CHANGE
Specifies whether the data for export change is masked during export.
Values:
Y
If a mask is also being exported, the mask that is used for export change is the newly created mask. Otherwise, the mask that is used is identified by the COMPARE_MASK_OWNER and MASK_NAME parameters.
blank
Specifies that this parameter defaults to Y if a mask and a change are imported.
Default:
blank
USE_MASK_FOR_IMPORT_CHANGE
Specifies whether the input for import change is masked during import.
Values:
Start of changeYEnd of change
Start of changeIf a mask is also being imported, the mask that is used for import change is the newly created mask. (This newly created mask is identified by the NEW_MASK_OWNER and NEW_MASK_NAME parameters.) Otherwise, the mask that is used is identified by the MASK_OWNER and MASK_NAME parameters.End of change
blank
Specifies that this parameter defaults to Y if a mask and a change are imported.
Default:
blank
USE_PERMANENT_DATA_SET_FOR_RUN_JOB_INPUT
Specifies where to store the run job input. The run job input can be put in-stream in the run job itself, or into a PDS.
Values:
Y
Store the run job input data in a permanent data set that is referenced in the run job.
N
Store the run job input data in an in-stream data set in the run job.
Default:
N
USE_UTILITY_OPTIONS
Specifies whether to use the customized utility options. The utility options that you can specify are described in Utility option parameters
Values:
Y
The user-customized utility options are used.
N
The Db2 Admin Tool and Db2 default utility options are used.
Default:
N
UTIL_CLONE_TEMPLATE_COPYDDN1_NAME
Specifies the user-provided template name for the first file of COPYDDN.
Values:
Specify a 1- to 8-character Db2 template name.
Default:
CLNCOPY1
UTIL_CLONE_TEMPLATE_COPYDDN1_USE
Specifies whether to use a user-provided template for the first COPYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_COPYDDN1_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES is set to Y, and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_COPYDDN2_NAME
Specifies the user-provided template name for the second file of COPYDDN.
Values:
A Db2 template name; 1 to 8 characters
Default:
CLNCOPY2
UTIL_CLONE_TEMPLATE_COPYDDN2_USE
Specifies whether to use a user-provided template for the second COPYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_COPYDDN2_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_DISCARDDN_NAME
Specifies the user-provided template name for the DISCARDDN file.
Values:
A Db2 template name; 1 to 8 characters
Default:
CLNDISC
UTIL_CLONE_TEMPLATE_DISCARDDN_USE
Specifies whether to use a user-provided template for the DISCARDDN file. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_DISCARDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_ERRDDN_NAME
Specifies the user-provided template name for the ERRDDN file.
Values:
A Db2 template name; 1 to 8 characters
Default:
CLNERR
UTIL_CLONE_TEMPLATE_ERRDDN_USE
Specifies whether to use a user-provided template for the ERRDDN file. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_ERRDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_FCCOPYDDN_NAME
Specifies the user-provided template name for the FCCOPYDDN file.
Values:
A Db2 template name; 1 to 8 characters
Default:
CLNFCOPY
UTIL_CLONE_TEMPLATE_FCCOPYDDN_USE
Specifies whether to use a user-provided template for the FCCOPYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_FCCOPYDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
Default:
S
UTIL_CLONE_TEMPLATE_LOBCOL_NAME
Specifies the user provided template name for LOB columns.
Values:
A Db2 template name; 1 to 8 characters
Default:
CLNLOBC

The data set name cannot exceed 35 bytes and must be in PDS format. Do not specify a member name

UTIL_CLONE_TEMPLATE_LOBCOL_USE
Specifies whether to use a user-provided template for templates related to LOB columns. If a non-blank value is specified, the template name for LOB columns is determined from the UTIL_CLONE_TEMPLATE_LOBCOL_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES is set to Y.
Values:
a non-blank value
Default:
S

A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES is set to Y, and the template exists in the ADBTEMPL file.

UTIL_CLONE_TEMPLATE_MAPDDNNAME
Specifies the user-provided template name for MAPDDN.
Values:
A Db2 template name.
Specify a 1- to 8-character Db2 template name.
Default:
CLNMAP
UTIL_CLONE_TEMPLATE_MAPDDNUSE
Specifies whether to use a user-provided template for the MAPDDN file. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_MAPDDNNAME parameter. This parameter is only in effect if the GENERATE_TEMPLATES is set to Y.
Values:
A non-blank value.
Specify a non-blank value.

A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES is set to Y, and the template exists in the ADBTEMPL file.

Default:
S
UTIL_CLONE_TEMPLATE_PUNCHDDN_NAME
Specifies the user provided template name for the PUNCHDDN file of the REORG utility.
Values:
A Db2 template name; 1 to 8 characters
Default:
CPUNCH
UTIL_CLONE_TEMPLATE_PUNCHDDN_USE
Specifies whether to use a user provided template for the PUNCHDDN file of the REORG utility. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_PUNCHDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_RECOVERYDDN1_NAME
Specifies the user-provided template name for the first name for RECOVERYDDN.
Values:
A Db2 template name; 1 to 8 characters
Default:
CLNRCVR1
UTIL_CLONE_TEMPLATE_RECOVERYDDN1_USE
Specifies whether to use a user-provided template for the first RECOVERYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_RECOVERYDDN1_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set toY and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_RECOVERYDDN2_NAME
Specifies the user-provided template name for the second name for RECOVERYDDN.
Values:
A Db2 template name; 1 to 8 characters
Default:
CLNRCVR2
UTIL_CLONE_TEMPLATE_RECOVERYDDN2_USE
Specifies whether to use a user-provided template for the second RECOVERYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_RECOVERYDDN2_NAME parameter. This parameter is in effect only if GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_UNLDDN_NAME
Specifies the user provided template name for the UNLDDN file of the REORG utility.
Values:
A Db2 template name; 1 to 8 characters
Default:
CUNL
UTIL_CLONE_TEMPLATE_UNLDDN_USE
Specifies whether to use a user provided template for the UNLDDN file of the REORG utility. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_UNLDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDN_NAME
Specifies the user provided template name for the PUNCHDDN file of the UNLOAD utility.
Values:
A Db2 template name; 1 to 8 characters
Default:
CUPUNCH
UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDN_USE
Specifies whether to use a user provided template for the PUNCHDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDNC_NAME
Specifies the user provided template name for the Db2 Admin Tool converted version of the PUNCHDDN file of the UNLOAD utility. Some types of changes require that the unloaded data be converted by Db2 Admin Tool before the data is loaded. This parameter controls the user provided template for the converted load control card for the unloaded data.
Values:
A Db2 template name; 1 to 8 characters
Default:
CUPUNCHC
UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDNC_USE
Specifies whether to use a user provided template for the Db2 Admin Tool converted version of the PUNCHDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDNC_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y. Some types of changes require that the unloaded data be converted by Db2 Admin Tool before the data is loaded. This parameter controls the user provided template for the converted load control card for the unloaded data.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_UNLOAD_UNLDDN_NAME
Specifies the user provided template name for the UNLDDN file of the UNLOAD utility.
Values:
A Db2 template name; 1 to 8 characters
Default:
CUUNL
UTIL_CLONE_TEMPLATE_UNLOAD_UNLDDN_USE
Specifies whether to use a user provided template for the UNLDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_UNLOAD_UNLDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_UNLOAD_UNLDDNC_NAME
Specifies the user provided template name for the Db2 Admin Tool converted version of the UNLDDN file of the UNLOAD utility. Some types of changes require that the unloaded data to be converted by Db2 Admin Tool before the data can be loaded. This parameter controls the user provided template for the converted data set for the unloaded data.
Values:
A Db2 template name; 1 to 8 characters
Default:
CUUNLC
UTIL_CLONE_TEMPLATE_UNLOAD_UNLDDNC_USE
Specifies whether to use a user provided template for the Db2 Admin Tool converted version of the UNLDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_UNLOAD_UNLDDNC_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y. Some types of changes requires the unloaded data to be converted by Db2 Admin Tool before it can be loaded. This parameter controls the user provided template for the converted data set for the unloaded data.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_WORKDDN1_NAME
Specifies the user-provided template name for the first name for WORKDDN.
Values:
A Db2 template name; 1 to 8 characters
Default:
CLNWORK1
UTIL_CLONE_TEMPLATE_WORKDDN1_USE
Specifies whether to use a user-provided template for the first WORKDDN file. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_WORKDDN1_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if theGENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_WORKDDN2_NAME
Specifies the user-provided template name for the second name for WORKDDN.
Values:
A Db2 template name; 1 to 8 characters
Default:
CLNWORK2
UTIL_CLONE_TEMPLATE_WORKDDN2_USE
Specifies whether to use a user-provided template for the second WORKDDN file. If a non-blank value is specified, the template name is determined from the UTIL_CLONE_TEMPLATE_WORKDDN2_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_CLONE_TEMPLATE_XMLCOL_NAME
Specifies the user-provided template name for XML columns.
Values
A Db2 template name; 1 to 8 characters
Default:
CLNXMLC

The data set name cannot exceed 35 bytes and must be in PDS format. Do not specify a member name.

UTIL_CLONE_TEMPLATE_XMLCOL_USE
Specifies whether to use a user-provided template for templates related to XML columns. If a non-blank value is specified, the template name for XML columns is determined from the UTIL_CLONE_TEMPLATE_XMLCOL_NAME parameter. This parameter is only in effect if the GENERATE_TEMPLATES is set to Y.
Values:
a non-blank value
Default:
S

A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES is set to Y, and the template exists in the ADBTEMPL file.

UTIL_TEMPLATE_COPYDDN1_NAME
Specifies the user provided template name for the first file of COPYDDN.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
COPY1
UTIL_TEMPLATE_COPYDDN1_USE
Specifies whether to use a user provided template for the first COPYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_COPYDDN1_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_COPYDDN2_NAME
Specifies the user provided template name for the second file of COPYDDN.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
COPY2
UTIL_TEMPLATE_COPYDDN2_USE
Specifies whether to use a user provided template for the second COPYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_COPYDDN2_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_DISCARDDN_NAME
Specifies the user provided template name for the DISCARDDN file.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
DISC
UTIL_TEMPLATE_DISCARDDN_USE
Specifies whether to use a user provided template for the DISCARDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_DISCARDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y, and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_ERRDDN_DEVTYPE
Specifies whether the ERRDDN template is on a tape-like device, or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
Default:
DASD
UTIL_TEMPLATE_ERRDDN_NAME
Specifies the user provided template name for the ERRDDN file.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
ERR
UTIL_TEMPLATE_ERRDDN_USE
Specifies whether to use a user provided template for the ERRDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_ERRDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_FCCOPYDDN_NAME
Specifies the user provided template name for the FCCOPYDDN file.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
FCOPY
UTIL_TEMPLATE_FCCOPYDDN_USE
Specifies whether to use a user provided template for the FCCOPYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_FCCOPYDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_LOBCOL_NAME
Specifies the user provided template name for LOB columns.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
LOBC
UTIL_TEMPLATE_LOBCOL_USE
Specifies whether to use a user provided template for templates related to LOB columns. If a non-blank value is specified, the template name for LOB columns is determined from the UTIL_TEMPLATE_LOBCOL_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_MAPDDN_DEVTYPE
Specifies whether the MAPDDN template is on a tape-like device, or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
Default:
DASD
UTIL_TEMPLATE_MAPDDN_NAME
Specifies the user provided template name for MAPDDN.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
MAP
UTIL_TEMPLATE_MAPDDN_USE
Specifies whether to use a user-provided template for the MAPDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_MAPDDN_NAME parameter. This parameter is only in effect if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value.
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y, and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_PUNCHDDN_NAME
Specifies the user provided template name for the PUNCHDDN file of the REORG utility.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
PUNCH
UTIL_TEMPLATE_PUNCHDDN_USE
Specifies whether to use a user provided template for the PUNCHDDN file of the REORG utility. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_PUNCHDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_RECOVERYDDN1_NAME
Specifies the user-provided template name for the first file of RECOVERYDDN.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
RCVR1
UTIL_TEMPLATE_RECOVERYDDN1_USE
Specifies whether to use a user-provided template for the first RECOVERYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_RECOVERYDDN1_NAME parameter. This parameter is only in effect if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value.
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y, and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_RECOVERYDDN2_NAME
Specifies the user-provided template name for the second file of RECOVERYDDN.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
RCVR2
UTIL_TEMPLATE_RECOVERYDDN2_USE
Specifies whether to use a user-provided template for the second RECOVERYDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_RECOVERYDDN2_NAME parameter. This parameter is only in effect if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value.
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y, and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_UNLDDN_NAME
Specifies the user provided template name for the UNLDDN file of the REORG utility.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
UNL
UTIL_TEMPLATE_UNLDDN_USE
Specifies whether to use a user provided template for the UNLDDN file of the REORG utility. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_UNLDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_UNLOAD_PUNCHDDN_NAME
Specifies the user provided template name for the PUNCHDDN file of the UNLOAD utility.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
UPUNCH
UTIL_TEMPLATE_UNLOAD_PUNCHDDN_USE
Specifies whether to use a user provided template for the PUNCHDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_UNLOAD_PUNCHDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_UNLOAD_PUNCHDDNC_NAME
Specifies the user provided template name for the Db2 Admin Tool converted version of the PUNCHDDN file of the UNLOAD utility. Some types of changes require that the unloaded data to be converted by Db2 Admin Tool before the data is loaded. This parameter controls the user provided template for the converted load control card for the unloaded data.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
UPUNCHC
UTIL_TEMPLATE_UNLOAD_PUNCHDDNC_USE
Specifies whether to use a user provided template for the PUNCHDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_UNLOAD_PUNCHDDNc_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y. Some types of changes requires the unloaded data to be converted by Db2 Admin Tool before it can be loaded. This parameter controls the user provided template for the converted load control card for the unloaded data.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_UNLOAD_UNLDDN_DEVTYPE
Specifies whether UTIL_TEMPLATE_UNLOAD_UNLDDN_NAME is on removable media or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
blank
The DEVTYPE option is not added. The Db2 default for this utility option is used.
Default:
DASD
UTIL_TEMPLATE_UNLOAD_UNLDDN_NAME
Specifies the user provided template name for the UNLDDN file of the UNLOAD utility.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
UUNL
UTIL_TEMPLATE_UNLOAD_UNLDDN_USE
Specifies whether to use a user provided template for the UNLDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_UNLOAD_UNLDDN_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_UNLOAD_UNLDDNC_NAME
Specifies the user provided template name for the Db2 Admin Tool converted version of the UNLDDN file of the UNLOAD utility. Some types of changes require that the unloaded data to be converted by Db2 Admin Tool before the data is loaded. This parameter controls the user provided template for the converted data set for the unloaded data.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
UUNLC
UTIL_TEMPLATE_UNLOAD_UNLDDNC_USE
Specifies whether to use a user provided template for the Db2 Admin Tool converted version of the UNLDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_UNLOAD_UNLDDNC_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y. Some types of changes require that the unloaded data to be converted by Db2 Admin Tool before the data is loaded. This parameter controls the user provided template for the converted data set for the unloaded data.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_WORKDDN1_DEVTYPE
Specifies whether the WORKDDN1 template is on a tape-like device, or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
Default:
DASD
UTIL_TEMPLATE_WORKDDN1_NAME
Specifies the user provided template name for the first name for WORKDDN.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
WORK1
UTIL_TEMPLATE_WORKDDN1_USE
Specifies whether to use a user provided template for the first WORKDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_WORKDDN1_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_WORKDDN2_DEVTYPE
Specifies whether the WORKDDN2 template is on a tape-like device, or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
Default:
DASD
UTIL_TEMPLATE_WORKDDN2_NAME
Specifies the user provided template name for the second name for WORKDDN.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
WORK2
UTIL_TEMPLATE_WORKDDN2_USE
Specifies whether to use a user provided template for the second WORKDDN file. If a non-blank value is specified, the template name is determined from the UTIL_TEMPLATE_WORKDDN2_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
UTIL_TEMPLATE_XMLCOL_NAME
Specifies the user provided template name for XML columns.
Values:
A Db2 template name
The Db2 template name can be 1 to 8 character in length.
Default:
XMLC
UTIL_TEMPLATE_XMLCOL_USE
Specifies whether to use a user provided template for templates related to XML columns. If a non-blank value is specified, the template name for XML columns is determined from the UTIL_TEMPLATE_XMLCOL_NAME parameter. This parameter is in effect only if the GENERATE_TEMPLATES parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the GENERATE_TEMPLATES parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S
VALIDATE_DDL
Specifies whether to validate the DDL that is being imported into change management. When the input to be imported is a changes file and not DDL, the value of this parameter is forced to N (NO).

This parameter validates the input DDL directly against the catalog for issuing the Db2 PREPARE statement, checking whether objects exist, and so on. Prerequisite changes are not considered, so an informational message is issued when Y is specified. For example, if the table that is in the DDL does not exist in the catalog, the validation process ends with an error. If a prerequisite change is in the process of creating the table, it is not considered.

The VALIDATE_DDL parameter is an import optional parameter that is limited to validating the DDL. It is not applicable to validating the changes file. For example, if you run a compare and import the changes file, the VALIDATE_DDL parameter is not used, and a warning message that the value of the parameter is forced to N is issued.

Values:
Y
Validates the DDL and displays the report in the job output.
N
The DDL is not validated.
Default:
N
VALIDATE_STMTEXIT
Specifies the REXX exit name for a VALIDATE statement.
Values:
Valid data set names. 1- 8 characters.
Default:
blank
VALIDATE_WSL
Specifies whether to validate the WSL after it is created. If the change has prerequisites, this option is forced to NO.
Values:
Y
Validate the WSL and display the report in the job output.
N
Do not validate the WSL.
Default:
N
VALIDATION_STMTEXIT
Specifies a REXX exec that will be called to validate a Db2 statement.
Values:
A valid data set member name
The data set member name can be 1 to 8 characters or blank.
blank
No validation will be done.
Default:
No default value.
WORKLIST_NAME
Specifies the member name for a PDS dataset that will be used for the WSL generation or run.
Values:
A valid PDS member name. 1 - 8 characters.
Default:
blank
WORKLIST_NAME_CONV
Specifies the member name for a partitioned data set (PDS) that has or will have the readable WSL. This parameter requires a valid PDS member name. Valid names are 1 - 8 characters. If the WSL that you specify in the PDS_FOR_WSL parameter is not found when ACTION_CONVERT_TO_READ_WSL= 'y', error message ADB9972E is displayed.
Values:
Valid PDS member names. 1 - 8 characters.
Default:
If a work statement list (WSL) is being generated (ACTION_GENERATE_WSL = 'Y'), the default is the change tag value that is used by this WSL, as specified in WORKLIST_NAME.

If a change is being analyzed or run, the default is the change tag value that is used by the change. This value depends on the value of CHGTAG_TYPE

Otherwise, the default is blank.

Utility option parameters

Use the following CM batch parameters to set options for various utilities.

Requirement: To specify values for utility options, you must set the USE_UTILITY_OPTIONS parameter to Y. Otherwise, the default values are used.
Recommendations: The following values are some generic recommendations for the utility parameters:
UTIL_COPY_FULL = 'Y'
UTIL_COPY_PARALLEL = '5'
UTIL_COPY_SHRLEVEL = 'C'
UTIL_REORG_KEEPDICTIONARY = 'Y'
UTIL_REORG_LOG = 'N'
UTIL_REORG_LONGLOG = 'D'
UTIL_REORG_MAXRO = '25'
UTIL_REORG_NOSYSREC = 'Y'
UTIL_REORG_RETRY = '6'
UTIL_REORG_RETRY_DELAY = '120'
UTIL_REORG_SHRLEVEL = 'C'
UTIL_REORG_SORTDATA = 'Y'
UTIL_REORG_SORTDEVT = 'SYSDA'
UTIL_REORG_TIMEOUT = 'T'
UTIL_REORG_DEADLINE = 'CURRENT TIMESTAMP + 4 HOURS'
UTIL_RUNSTATS_HISTORY = 'A'
UTIL_RUNSTATS_SHRLEVEL = 'C'
UTIL_RUNSTATS_UPDATE = 'A'
UTIL_CHECK_AUXERROR
Specifies the AUXERROR option for generated CHECK DATA utility statements. AUXERROR specifies the action that CHECK DATA is to take for LOB or XML column check errors.
Values:
R
AUXERROR REPORT is added.
I
AUXERROR INVALIDATE is added.
blank
The AUXERROR option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_CHECK_DRAIN_WAIT
Specifies the DRAIN_WAIT option for generated CHECK DATA utility statements. DRAIN_WAIT specifies the number of seconds that the utility is to wait when it drains the table space or index.
Values:
A valid DRAIN_WAIT value for CHECK DATA; 1 - 1800
Specify a DRAIN_WAIT setting in the range 1 - 1800. The DRAIN_WAIT option is added with the specified value.
blank
The option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_CHECK_EXCEPTIONS
Specifies the EXCEPTIONS option for generated CHECK DATA utility statements. EXCEPTIONS specifies the maximum number of exceptions, after which the utility terminates.
Values:
A valid EXCEPTIONS value for CHECK DATA)
Specify a valid EXCEPTIONS value in the range 0 - 32767. The EXCEPTIONS option is added with the specified value, for example: EXCEPTIONS 2
blank
The option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_CHECK_INCLUDE_XML_TABLESPACES
Specifies the INCLUDE XML TABLESPACES option for generated CHECK DATA utility statements. INCLUDE XML TABLESPACES specifies whether the utility is to also check XML table spaces.
Values:
ALL
The INCLUDE XML TABLESPACES option is added.
blank
The INCLUDE XML TABLESPACES option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_CHECK_RETRY
Specifies the RETRY option for generated CHECK DATA utility statements. RETRY specifies the maximum number of retries that the utility is to attempt.
Values:
A valid RETRY value for CHECK DATA
Specify a RETRY value in the range 0 - 255. The RETRY option is added with the specified value.
blank
The option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_CHECK_RETRY_DELAY
Specifies the RETRY_DELAY option for generated CHECK DATA utility statements. RETRY_DELAY specifies the minimum duration, in seconds, between retries.
Values:
A valid RETRY_DELAY value for CHECK DATA
Specify a RETRY_DELAY setting in the range 1 - 1800. The RETRY_DELAY option is added with the specified value.
blank
The option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_CHECK_SCOPE
Specifies the SCOPE option for generated CHECK DATA utility statements. SCOPE limits the scope of what the utility checks.
Values:
P
SCOPE PENDING is added.
X
SCOPE AUXONLY is added.
A
SCOPE ALL is added.
R
SCOPE REFONLY is added.
M
SCOPE XMLSCHEMAONLY is added.
blank
The SCOPE option is not added. The Db2 default for this utility option is used.
Default:
blank
Start of changeUTIL_CHECK_SHRLEVELEnd of change
Start of changeSpecifies the SHRLEVEL option for generated CHECK DATA utility statements. SHRLEVEL specifies the extent to which applications can concurrently access the table space or partition during the LOAD utility job.
Values:
R
The SHRLEVEL REFERENCE option is added.
C
The SHRLEVEL CHANGE option is added.
blank
The SHRLEVEL option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_CHECK_SORTDEVT
Specifies the SORTDEVT option for generated CHECK DATA utility statements. SORTDEVT specifies the device type for temporary data sets that are to be dynamically allocated by a sort program.
Values:
A valid SORTDEVT value for CHECK DATA
The SORTDEVT option is added with the specified value. For example: SORTDEVT SYSDA.
Default:
SPACE_UNIT_NAME (See SPACE_UNIT_NAME.)
UTIL_CHECK_SORTNUM
Specifies the SORTNUM option for generated CHECK DATA utility statements. SORTNUM specifies the number of temporary data sets that are to be dynamically allocated by the sort program.
Values:
A valid SORTNUM value for CHECK DATA.
Specify a SORTNUM value in the range 1 - 255. The SORTNUM option is added with the specified value.
Default:
4
UTIL_CHECK_XMLSCHEMA
Specifies the XMLSCHEMA attribute of the INCLUDE XML TABLESPACES option for generated CHECK DATA utility statements. XMLSCHEMA specifies that the utility checks XML documents against the stored XML schema.
Important: Start of change UTIL_CHECK_XMLSCHEMA is currently ignored by CM batch. If you set UTIL_CHECK_XMLSCHEMA="YES", warning ADB9985W is issued.End of change
Values:
Start of changeYES or YEnd of change
The XMLSCHEMA option is added if the INCLUDE XML TABLESPACES option is also added.
Start of changeNO or NEnd of change
The XMLSCHEMA option is not added.
Default:
NO
UTIL_COPY_CHANGELIMIT
Specifies the CHANGELIMIT option for generated COPY utility statements. CHANGELIMIT specifies the limit of changed pages at which an image copy is to be taken.
Values:
Start of changeYES or YEnd of change
The CHANGELIMIT option is added with the values that are specified by the UTIL_COPY_CHANGELIMIT_PERCENT_VALUE1 and UTIL_COPY_CHANGELIMIT_PERCENT_VALUE2 parameters.
Start of changeANY or AEnd of change
The CHANGELIMIT(ANY) option is added.
blank
The CHANGELIMIT option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_COPY_CHANGELIMIT_PERCENT_VALUE1
Specifies the first value of the CHANGELIMIT option for generated COPY utility statements.
Values:
A percent value allowed by Db2
This value is specified with the CHANGELIMIT option.
blank
No value is specified with the CHANGELIMIT option. The Db2 default for this utility option is used.
Default:
blank
UTIL_COPY_CHANGELIMIT_PERCENT_VALUE2
Specifies the second value of the CHANGELIMIT option for generated COPY utility statements.
Values:
A percent value allowed by Db2
This value is specified as the second value of the CHANGELIMIT option.
blank
A second value is not specified with the CHANGELIMIT option. The Db2 default for this utility option is used.
Default:
blank
UTIL_COPY_CHANGELIMIT_REPORTONLY
Specifies the CHANGELIMIT REPORTONLY option for generated COPY utility statements. REPORTONLY specifies that image copy information is only displayed; no image copies are taken.
Values:
Start of changeYES or YEnd of change
The REPORTONLY option is added.
Start of changeNO or NEnd of change
The REPORTONLY option is not added.
Default:
N
UTIL_COPY_CHECKPAGE
Specifies the CHECKPAGE option for generated COPY utility statements. CHECKPAGE specifies that each page is to be checked for validity.
Values:
Start of changeYES or YEnd of change
The CHECKPAGE option is added.
Start of changeNO or NEnd of change
N
The CHECKPAGE option is not added. The Db2 default for this utility option is used.
Default:
N
UTIL_COPY_CONCURRENT
Specifies the CONCURRENT option for generated COPY utility statements. CONCURRENT specifies that DFSMSdss concurrent copy is to make the full image copy.
Values:
Start of changeYES or YEnd of change
The CONCURRENT option is added.
Start of changeNO or NEnd of change
The CONCURRENT option is not added.
Default:
N
UTIL_COPY_FLASHCOPY
Specifies the FLASHCOPY option for generated COPY utility statements. FLASHCOPY specifies whether FlashCopy® technology is used to create the copy.
Values:
Start of changeYES or YEnd of change
The FLASHCOPY YES option is added.
Start of changeNO or NEnd of change
The FLASHCOPY NO option is not added.
Start of changeCON or CEnd of change
The FLASHCOPY CONSISTENT option is added.
blank
The FLASHCOPY option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_COPY_FULL
Specifies the FULL option for generated COPY utility statements. FULL specifies whether the utility is to make a full or incremental image copy.
Values:
Start of changeYES or YEnd of change
The FULL YES option is added.
Start of changeNO or NEnd of change
The FULL NO option is added.
blank
The FULL option is not added. The Db2 default for this utility option is used.
Default:
blank
Start of changeUTIL_COPY_NOCHECKPAGEEnd of change
Start of changeSpecifies the NOCHECKPAGE option for generated COPY utility statements. NOCHECKPAGE indicates that COPY is to perform only basic checks on each page.
Values:
Y or YES
The NOCHECKPAGE option is added.
N or NO
The NOCHECKPAGE option is not added.
blank
The NOCHECKPAGE option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_COPY_PARALLEL
Specifies the PARALLEL option for generated COPY utility statements. PARALLEL specifies the maximum number of objects in a list that are to be processed in parallel.
Values:
0 to 99999
The PARALLEL option is added as PARALLEL UTIL_COPY_PARALLEL. Where UTIL_COPY_PARALLEL is the value specified for this parameter.
blank
The PARALLEL option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_COPY_PARALLEL_TAPEUNITS
Specifies the PARALLEL TAPEUNITS option for generated COPY utility statements. TAPEUNITS specifies the maximum number of tape drives that the utility dynamically allocates for the list of objects to be processed in parallel.
Values:
0 to 32767
If the PARALLEL option is added, the TAPEUNITS n option is added. Where n is the value of this parameter.
blank
The TAPEUNITS option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_COPY_SHRLEVEL
Specifies the SHRLEVEL option for generated COPY utility statements. SHRLEVEL specifies whether other programs can access or update the table space or index while COPY is running.
Values:
C
The SHRLEVEL CHANGE option is added.
R
The SHRLEVEL REFERENCE option is added.
blank
The SHRLEVEL option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_LISTDEF_PARTLEVEL
Specifies whether to generate the LISTDEF utility statement with the PARTLEVEL option. PARTLEVEL specifies the partition granularity. UTIL_LISTDEF_PARTLEVEL applies only when using the COPY utility to create image copies of partitioned table spaces.
Values:
Start of changeYES or YEnd of change
The LISTDEF listdef-name... PARTLEVEL statement is generated.
Start of changeNO or NEnd of change
The LISTDEF listdef-name... PARTLEVEL statement is not generated.
Default:
N
Start of changeUTIL_LOAD_BACKOUTEnd of change
Start of changeSpecifies the BACKOUT option for generated LOAD utility statements. BACKOUT specifies whether to delete all rows loaded by the current LOAD operation if any record would leave the object unavailable.
Values:
YES or Y
The BACKOUT option is added.
NO or N
The BACKOUT option is not added.
blank
The BACKOUT option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_DECFLOAT_ROUNDMODEEnd of change
Start of changeSpecifies the DECFLOAT_ROUNDMODE option for generated LOAD utility statements. DECFLOAT_ROUNDMODE specifies the rounding mode to use when DECFLOATs are manipulated.
Values:
Start of changeCEEnd of change
The DECFLOAT_ROUNDMODE ROUND_CEILING option is added.
Start of changeDOEnd of change
The DECFLOAT_ROUNDMODE ROUND_DOWN option is added.
Start of changeFLEnd of change
The DECFLOAT_ROUNDMODE ROUND_FLOOR option is added.
HD
The DECFLOAT_ROUNDMODE ROUND_HALF_DOWN option is added.
HE
The DECFLOAT_ROUNDMODE ROUND_HALF_EVEN option is added.
HU
The DECFLOAT_ROUNDMODE ROUND_HALF_UP option is added.
Start of changeUPEnd of change
The DECFLOAT_ROUNDMODE ROUND_UP option is added.
blank
The DECFLOAT_ROUNDMODE option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_DEFINEAUXEnd of change
Start of changeSpecifies the DEFINEAUX option for generated LOAD utility statements. DEFINEAUX specifies whether LOAD is to define all target auxiliary objects with the DEFINE NO attribute, regardless of whether data is to be loaded into these objects.
Values:
YES or Y
The DEFINEAUX YES option is added. LOAD defines all target LOB and XML objects and their indexes at the start of the utility execution.
NO or N
The DEFINEAUX NO option is added. LOAD takes no special action to define the target auxiliary objects.
blank
The DEFINEAUX option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_LOAD_DISCARDS
Specifies the DISCARDS option for generated LOAD utility statements. DISCARDS specifies the maximum number of source records that are to be written on the discard data set.
Values:
A valid number in the range 0-2147483647
Default:
blank
UTIL_LOAD_ENFORCE
Specifies the ENFORCE option for generated LOAD utility statements. ENFORCE specifies whether LOAD is to enforce check constraints and referential constraints, except informational referential constraints.
Values:
Start of changeYES or YEnd of change
The ENFORCE CONSTRAINTS option is added.
Start of changeNO or NEnd of change
The ENFORCE NO option is added.
Default:
NO
UTIL_LOAD_FLASHCOPY
Specifies the FLASHCOPY option for generated LOAD utility statements. FLASHCOPY specifies whether FlashCopy® technology is used.
Values:
Start of changeYES or YEnd of change
The FLASHCOPY YES option is added.
Start of changeNO or NEnd of change
The FLASHCOPY NO option is added.
Start of changeCON or CEnd of change
The FLASHCOPY CONSISTENT option is added.
blank
The FLASHCOPY option is not added. The Db2 default for this utility option is used.
Default:
blank
Start of changeUTIL_LOAD_FORCEEnd of change
Start of changeSpecifies the FORCE option for generated LOAD utility statements. FORCE specifies the action to be taken when the utility drains the table space.
Values:
N
The FORCE NONE option is added. No action is taken.
R
The FORCE READERS option is added. Read claimers are canceled when LOAD requests DRAIN ALL on the last drain retry.
A
The FORCE ALL option is added. Both read and write claimers are canceled when LOAD requests DRAIN ALL or DRAIN WRITERS on the last drain retry.
blank
The FORCE option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_LOAD_KEEPDICTIONARY
Specifies the KEEPDICTIONARY option for generated LOAD utility statements. KEEPDICTIONARY prevents the LOAD utility from building a new compression dictionary.
Values:
Start of changeYES or YEnd of change
The KEEPDICTIONARY option is added.
Start of changeNO or NEnd of change
The KEEPDICTIONARY option is not added. The Db2 default for this utility option is used.
Default:
NO
Start of changeUTIL_LOAD_INDEXDEFEREnd of change
Start of changeSpecifies the INDEXDEFER option for generated LOAD utility statements. INDEXDEFER specifies whether index builds are done during the BUILD phase of LOAD or are deferred until REBUILD INDEX is run manually.
Values:
NPI or N
The INDEXDEFER NPI option is added. The building of nonpartitioned indexes is not done as part of a BUILD phase of the LOAD utility.
ALL or A
The INDEXDEFER ALL option is added. No indexes are built as part of a BUILD phase of the LOAD utility.
NONE or NO
The INDEXDEFER NONE option is added. Indexes are built during the BUILD phase of LOAD.
blank
The INDEXDEFER option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_INDEXDEFER_NONUNIQUEEnd of change
Start of changeSpecifies whether the INDEXDEFER NONUNIQUE option is added to generated LOAD utility statements. INDEXDEFER NONUNIQUE specifies that building of only nonunique indexes is deferred.
Values:
YES or Y
The INDEXDEFER NONUNIQUE option is added.
NO or N
The INDEXDEFER NONUNIQUE option is not added.
blank
The INDEXDEFER NONUNIQUE option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_LOAD_LOG
Specifies the LOG option for generated LOAD utility statements. LOG specifies whether logging occurs during the load process.
Values:
Start of changeYES or YEnd of change
LOG YES is added.
Start of changeNO or NEnd of change
LOG NO is added.
NOC
LOG NO NOCOPYPEND is added.
blank
The LOG option is not added. The Db2 default for this utility option is used.
Default:
blank
Start of changeUTIL_LOAD_NOCHECKPENDEnd of change
Start of changeSpecifies the NOCHECKPEND option for generated LOAD utility statements. NOCHECKPEND specifies that LOAD does not set the target table space in the CHECK-pending status if at least one referential constraint or check constraint is defined for the table.
Values:
YES or Y
The NOCHECKPEND option is added.
NO or N
The NOCHECKPEND option is not added.
blank
The NOCHECKPEND option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_NOSUBSEnd of change
Start of changeSpecifies the NOSUBS option for generated LOAD utility statements. NOSUBS specifies that LOAD is not to accept substitution characters in a string.
Values:
YES or Y
The NOSUBS option is added.
NO or N
The NOSUBS option is not added.
blank
The NOSUBS option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_LOAD_PARALLEL
Specifies the maximum number of subtasks that are to be used in parallel when loading a table space.
Values:
Start of changeYES or YEnd of change
The PARALLEL option is added.
integer
0-32767. The PARALLEL option is added to the utility statement with the specified value.
blank
The PARALLEL option is not added. The Db2 default for this utility option is used.
Default:
blank
Start of changeUTIL_LOAD_PREFORMATEnd of change
Start of changeSpecifies the PREFORMAT option for generated LOAD utility statements. PREFORMAT specifies that the remaining pages are to be preformatted up to the high-allocated RBA in the partition and its corresponding partitioning index space
Values:
YES or Y
The PREFORMAT option is added.
NO or N
The PREFORMAT option is not added.
blank
The PREFORMAT option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_LOAD_PRESORT
Specifies the PRESORT option for generated LOAD utility statements. PRESORT specifies that input records are to be sorted in clustering order before loading them into the target table space. Existing rows in the table space are not affected.
Values:
YES or Y
The PRESORT option is added.
NO or N
The PRESORT option is not added.
blank
The PRESORT option is not added.
Default:
blank
UTIL_LOAD_PRESORTED
Specifies the PRESORTED option for generated LOAD utility statements. PRESORTED specifies whether the input data set has already been sorted in clustering key order.
Values:
YES or Y
The PRESORTED YES option is added. Input data is sorted.
NO or N
The PRESORTED NO option is added. The input data set is not sorted.
blank
The PRESORTED option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_LOAD_REPLACE
Specifies the REPLACE option for generated LOAD utility statements. REPLACE specifies whether the table space and all its indexes need to be reset to empty before records are loaded.
Values:
Start of changeYES or YEnd of change
The REPLACE option is added.
Start of changeNO or NEnd of change
The REPLACE option is not added.
blank
The REPLACE option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_LOAD_RESUME
Specifies the RESUME option for generated LOAD utility statements. RESUME specifies whether records are to be loaded into an empty or non-empty table space.
Values:
Start of changeYES or YEnd of change
RESUME YES is added.
Start of changeNO or NEnd of change
RESUME NO is added.
blank
The RESUME option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_LOAD_REUSE
Specifies the REUSE option for generated LOAD utility statements. REUSE specifies whether LOAD reuses Db2-managed data sets.
Values:
Start of changeYES or YEnd of change
The REUSE option is added.
Start of changeNO or NEnd of change
The REUSE option is not added.
Default:
NO
UTIL_LOAD_SHRLEVEL
Specifies the SHRLEVEL option for generated LOAD utility statements. SHRLEVEL specifies the extent to which applications can concurrently access the table space or partition during the LOAD utility job.
Important: Start of change UTIL_LOAD_SHRLEVEL is currently ignored by CM batch. If you set UTIL_LOAD_SHRLEVEL="C", warning ADB9985W is issued and the Db2 default SHRLEVEL value will be used.End of change
Values:
N
The SHRLEVEL NONE option is added.
C
The SHRLEVEL CHANGE option is added.
blank
The SHRLEVEL option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_LOAD_SORTDEVT
Specifies the SORTDEVT option for generated LOAD utility statements. SORTDEVT specifies the device type for temporary data sets that are to be dynamically allocated by the external sort program
Values:
A valid SORTDEVT value for LOAD
The SORTDEVT option is added with the specified value. For example: SORTDEVT SYSDA..
SPACE_UNIT_NAME
See SPACE_UNIT_NAME
Default:
SPACE_UNIT_NAME
UTIL_LOAD_SORTKEYS
Specifies the SORTKEYS option for generated LOAD utility statements. SORTKEYS specifies the number of index keys that are to be sorted.
Values:
A valid SORTKEYS value for LOAD.
The SORTKEYS option is added with the specified value.
0
The SORTKEYS option is not added. The Db2 default for this utility option is used.
Default:
0
UTIL_LOAD_SORTNUM
Specifies the SORTNUM option for generated LOAD utility statements. SORTNUM specifies the number of temporary data sets that are to be dynamically allocated by the sort application program
Values:
A valid SORTNUM value for LOAD.
The SORTNUM option is added with the specified value.
Default:
8
Start of changeUTIL_LOAD_STATISTICSEnd of change
Start of changeSpecifies whether the STATISTICS option is to be added to generated LOAD utility statements. STATISTICS specifies that the utility is to gather inline statistics.
Values:
Y or YES
The STATISTICS option is added.
N or NO
The STATISTICS option is not added.
blank
The STATISTICS option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_STATISTICS_FORCEROLLUPEnd of change
Start of changeSpecifies the FORCEROLLUP option for generated LOAD utility statements. FORCEROLLUP specifies whether aggregation or rollup of statistics is to take place when RUNSTATS is executed even if statistics have not been gathered on some partitions.
Values:
Y or YES
The FORCEROLLUP YES option is added.
N or NO
The FORCEROLLUP NO option is added.
blank
The FORCEROLLUP option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_STATISTICS_HISTORYEnd of change
Start of changeSpecifies the HISTORY option for generated LOAD utility statements. HISTORY specifies that all catalog table inserts or updates to the catalog history tables are to be recorded.
Values:
A
The HISTORY ALL option is added. ALL indicates that all collected statistics are to be updated in the catalog history tables.
P
The HISTORY ACCESSPATH option is added. ACCESSAPTH indicates that only the catalog history table columns that provide statistics that are used for access path selection are to be updated.
S
The HISTORY SPACE option is added. SPACE indicates that only space-related catalog statistics are to be updated in catalog history tables.
N
The HISTORY NONE option is added. NONE indicates that no catalog history tables are to be updated with the collected statistics.
blank
The HISTORY option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_STATISTICS_INVALIDATECACHEEnd of change
Start of changeSpecifies the INVALIDATECACHE option for generated LOAD utility statements. INVALIDATECACHE indicates whether statements in the dynamic statement cache are invalidated as a result of the inline statistics collection.
Values:
Y or YES
The INVALIDATECACHE YES option is added.
N or NO
The INVALIDATECACHE NO option is added.
blank
The INVALIDATECACHE option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_STATISTICS_REPORTEnd of change
Start of changeSpecifies the REPORT option for generated LOAD utility statements. REPORT specifies whether a set of messages is to be generated to report the collected statistics.
Values:
Y or YES
The REPORT YES option is added.
N or NO
The REPORT NO option is added.
blank
The REPORT option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_STATISTICS_TABLE_SAMPLEEnd of change
Start of changeSpecifies the TABLE SAMPLE option for generated LOAD utility statements. TABLE SAMPLE indicates the percentage of rows to be sampled when collecting statistics on non-leading-indexed columns of an index or non-indexed columns.
Values:
integer
The TABLE SAMPLE integer option is added. integer can be a value in the range 1 - 100.
blank
The TABLE SAMPLE option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_STATISTICS_TABLESAMPLE_SYSTEMEnd of change
Start of changeSpecifies the TABLESAMPLE SYSTEM option for generated LOAD utility statements. TABLESAMPLE SYSTEM indicates that a sample of data pages from the table is to be used for statistics collection.
Values:
numeric-literal
TABLESAMPLE SYSTEM numeric-literal is added. numeric-literal specifies the sample size as a percentage and can be a value in the range 0.01 - 100.
A or AUTO
TABLESAMPLE SYSTEM AUTO is added. AUTO specifies that LOAD is to determine the sampling rate based on the size of the table when the utility runs.
NONE or N
TABLESAMPLE SYSTEM NONE is added. NONE specifies that page sampling is not to be used for inline statistics.
blank
The TABLESAMPLE SYSTEM option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_STATISTICS_UPDATEEnd of change
Start of changeSpecifies the UPDATE option for generated LOAD utility statements. UPDATE indicates whether the collected statistics are to be inserted into the catalog tables.
Values:
A
The UPDATE ALL option is added. ALL indicates that all collected statistics are to be updated in the catalog.
P
The UPDATE ACCESSPATH option is added. ACCESSAPTH indicates that only the catalog table columns that provide statistics that are used for access path selection are to be updated.
S
The UPDATE SPACE option is added. SPACE indicates that only the catalog table columns that provide statistics to help database administrators assess the status of a particular table space or index are to be updated.
N
The UPDATE NONE option is added. NONE indicates that no catalog tables are to be updated with the collected statistics.
blank
The UPDATE option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
Start of changeUTIL_LOAD_STATISTICS_USE_PROFILEEnd of change
Start of changeSpecifies whether the USE PROFILE option is added to generated LOAD utility statements. USE PROFILE specifies that a stored statistics profile is used to gather statistics for a table.
Values:
Y or YES
The USE PROFILE option is added.
N or NO
The USE PROFILE option is not added.
blank
The USE PROFILE option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_REBUILD_SHRLEVEL
Specifies the SHRLEVEL option for generated REBUILD INDEX utility statements. SHRLEVEL specifies the type of access that is to be allowed for the object that is being processed by the utility.
Values:
C
The SHRLEVEL CHANGE option is added.
R
The SHRLEVEL REFERENCE option is added.
blank
The SHRLEVEL option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_AUX
Specifies the AUX option for generated REORG TABLESPACE utility statements. AUX specifies that associated LOB table spaces are also to be reorganized.
Values:
Start of changeYES or YEnd of change
AUX YES is added.
Start of changeNO or NEnd of change
AUX NO is added.
blank
The AUX option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_DEADLINE
Specifies the DEADLINE option for generated REORG TABLESPACE utility statements. DEADLINE specifies the deadline for the SWITCH phase to begin.
Values:
N
DEADLINE NONE is added.
timestamp
DEADLINE timestamp is added.
labeled-duration-expression
DEADLINE labeled-duration-expression is added.
blank
The DEADLINE option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_DELAY
Specifies the DELAY option for generated REORG TABLESPACE utility statements. DELAY specifies the minimum delay before performing the action that is specified by the LONGLOG parameter.
Values:
integer, blank
integer
The DELAY option is added to the utility statement with the specified value. integer is the number of seconds.
blank
The DELAY option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_DRAIN
Specifies the DRAIN option for generated REORG TABLESPACE utility statements. DRAIN specifies drain behavior.
Values:
W
The DRAIN WRITERS option is added to the utility statement.
A
The DRAIN ALL option is added to the utility statement.
blank
The DRAIN ALL option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_DRAIN_ALLPARTS
Specifies the DRAIN_ALLPARTS option for generated REORG TABLESPACE utility statements. DRAIN_ALLPARTS specifies drain behavior during a partition-level REORG operation when a nonpartitioned secondary index is defined on a partitioned table space.
Values:
Start of changeYES or YEnd of change
The DRAIN_ALLPARTS YES option is added to the utility statement.
Start of changeNO or NEnd of change
The DRAIN_ALLPARTS NO option is added to the utility statement.
blank
The DRAIN_ALLPARTS option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_DRAIN_WAIT
Specifies the DRAIN_WAIT option for generated REORG TABLESPACE utility statements. DRAIN_WAIT specifies hows long the utility waits when draining the table space or index.
Values:
integer
A valid DRAIN_WAIT value for REORG. The DRAIN_WAIT option is added with the specified value.
blank
The DRAIN ALL option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_DROP_PART
Specifies the DROP_PART option for generated REORG TABLESPACE utility statements. DROP_PART controls whether empty partitions are deleted.
Values:
Start of changeYES or YEnd of change
DROP_PART YES is added.
Start of changeNO or NEnd of change
DROP_PART NO is added.
blank
The DROP_PART option is not added; The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_FASTSWITCH
Specifies the FASTSWITCH option for generated REORG TABLESPACE utility statement. FASTSWITCH specifies which switch methodology is to use for the reorganization.
Values:
Start of changeYES or YEnd of change
FASTSWITCH YES is added.
Start of changeNO or NEnd of change
FASTSWITCH NO is added.
blank
The FASTSWITCH option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_FLASHCOPY
Specifies the FLASHCOPY option for generated REORG TABLESPACE utility statements. FLASHCOPY specifies whether FlashCopy® technology is used.
Values:
Start of changeYES or YEnd of change
FLASHCOPY YES is added.
Start of changeCON or CEnd of change
FLASHCOPY CONSISTENT is added.
Start of changeNO or NEnd of change
FLASHCOPY NO is added.
blank
The FLASHCOPY option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_FORCE
Specifies the FORCE option for generated REORG TABLESPACE utility statements. FORCE specifies the action to be taken when the utility drains the table space.
Values:
N
The FORCE NONE option is added. No action is taken.
R
The FORCE READERS option is added. Read claimers are canceled when REORG requests DRAIN ALL on the last drain retry.
A
The FORCE ALL option is added. Both read and write claimers are canceled when REORG requests DRAIN ALL or DRAIN WRITERS on the last drain retry.
blank
The FORCE option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_ICLIMIT_DASD
Specifies the ICLIMIT_DASD option for generated REORG TABLESPACE utility statements. ICLIMIT_DASD specifies the maximum number of sequential image copies that REORG TABLESPACE can allocate to DASD.
Values:
integer
An integer value in the range 0 - 32767.
blank
The ICLIMIT_DASD option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_ICLIMIT_TAPE
Specifies the ICLIMIT_TAPE option for generated REORG TABLESPACE utility statements. ICLIMIT_TAPE specifies the maximum number of sequential image copies that REORG TABLESPACE can allocate to tape.
Values:
integer
An integer value in the range 0 - 32767.
blank
The ICLIMIT_TAPE option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_INDEX_CLONE
Specifies the CLONE option for generated REORG INDEX utility statements. CLONE specifies that only index spaces and indexes on clone tables are to be reorganized.
Values:
Start of changeYES or YEnd of change
CLONE is added.
Start of changeNO or NEnd of change
CLONE is not is added.
Default:
N
Start of changeUTIL_REORG_INDEX_DRAINEnd of change
Start of changeSpecifies the DRAIN option for generated REORG INDEX utility statements. DRAIN specifies drain behavior.
Values:
W
The DRAIN WRITERS option is added to the utility statement.
A
The DRAIN ALL option is added to the utility statement.
blank
The DRAIN ALL option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_REORG_INDEX_FASTSWITCH
Specifies the FASTSWITCH option for generated REORG INDEX utility statements. FASTSWITCH specifies which switch methodology is to use for the reorganization.
Values:
Start of changeYES or YEnd of change
FASTSWITCH YES is added.
Start of changeNO or NEnd of change
FASTSWITCH NO is added.
blank
The FASTSWITCH option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_INDEX_FLASHCOPY
Specifies the FLASHCOPY option for generated REORG INDEX utility statements. FLASHCOPY specifies whether FlashCopy® technology is used.
Values:
Start of changeYES or YEnd of change
FLASHCOPY YES is added.
Start of changeCON or CEnd of change
FLASHCOPY CONSISTENT is added.
Start of changeNO or NEnd of change
FLASHCOPY NO is added.
blank
The FLASHCOPY option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_INDEX_FORCE
Specifies the FORCE option for generated REORG INDEX utility statements. FORCE specifies the action to be taken when the utility drains the table space.
Values:
A
The FORCE ALL option is added. Both read and write claimers are canceled.
R
The FORCE READERS option is added. Read claimers are canceled.
N
The FORCE NONE option is added. No action is taken.
blank
The FORCE option is not added. The Db2 default for this utility option is used.
Default:
blank
Start of changeUTIL_REORG_INDEX_LASTLOGEnd of change
Start of changeSpecifies the LASTLOG option for generated REORG INDEX utility statements with the SHRLEVEL CHANGE option. LASTLOG controls whether the utility applies log records during the last log iteration in the LOG phase.

To use this parameter, the UTIL_REORG_INDEX_ SHRLEVEL parameter value must be C. Otherwise, UTIL_REORG_INDEX_LASTLOG is ignored.

Values:
YES or Y
The LASTLOG YES option is added.
NO or N
The LASTLOG NO option is added. If you specify NO or N, UTIL_REORG_INDEX_DRAIN must be set to A.
blank
The LASTLOG option is not added. The Db2 default for this utility option is used.
Default:
blank
sEnd of change
UTIL_REORG_INDEX_LEAFDISTLIMIT
Specifies the LEAFDISTLIMIT option for generated REORG INDEX utility statements.
Values:
A valid LEAFDISTLIMIT value for REORG INDEX, blank
A valid LEAFDISTLIMIT value for REORG INDEX
LEAFDISTLIMIT is added with the specified value.
blank
The LEAFDISTLIMIT option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_INDEX_NOSYSUT1
Specifies the NOSYSUT1 option for generated REORG INDEX utility statements. NOSYSUT1 specifies that REORG INDEX is not to use the SYSUT1 work data set to hold the unloaded index keys but instead pass these keys in memory. Note that Db2 ignores this keyword if SHRLEVEL NONE is specified or no value is specified for SHRLEVEL, in which case SHRLEVEL NONE is used by default.

Start of changeUTIL_REORG_INDEX_NOSYSUT1 is ignored if the Db2 subsystem is at V13R1M500 or later, because NOSYSUT1 is obsolete. Beginning in Db2 13 function level 500, REORG INDEX no longer requires NOSYSUT1 to be specified; NOSYSUT1 behavior is always the default behavior if SHRLEVEL REFERENCE or SHRLEVEL CHANGE is specified.End of change

Values:
Y
The NOSYSUT1 option is added.
N
The NOSYSUT1 option is not added.
blank
The NOSYSUT1 option is not added.
Default:
blank
UTIL_REORG_INDEX_PARALLEL
Specifies the PARALLEL option for generated REORG INDEX utility statements. PARALLEL specifies the maximum number of subtasks that are to be started in parallel to reorganize the index.
Values:
n
The PARALLEL n option is added. n must be an integer between 0 and 32767, inclusive.
blank
The PARALLEL option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_INDEX_PREFORMAT
Specifies the PREFORMAT option for generated REORG INDEX utility statements. PREFORMAT specifies that the remaining pages are to be preformatted.
Values:
Start of changeYES or YEnd of change
PREFORMAT is added.
Start of changeNO or NEnd of change
PREFORMAT is not added
Default:
N
UTIL_REORG_INDEX_REPORTONLY
Specifies the REPORTONLY option for generated REORG INDEX utility statements. REPORTONLY specifies the utility is to only recommend whether a reorganization is necessary; no reorganization is performed.
Values:
Start of changeYES or YEnd of change
REPORTONLY is added.
Start of changeNO or NEnd of change
REPORTONLY is not added.
Default:
N
UTIL_REORG_INDEX_REUSE
Specifies the REUSE option for generated REORG INDEX utility statements. REUSE specifies that the utility to reuse Db2-managed data sets.
Values:
Start of changeYES or YEnd of change
REUSE is added
Start of changeNO or NEnd of change
REUSE is not added.
Default:
blank
UTIL_REORG_INDEX_SHRLEVEL
Specifies the SHRLEVEL option for generated REORG INDEX utility statements. SHRLEVEL indicates the type of access that is allowed during REORG INDEX processing.
Values:
N
SHRLEVEL NONE is added.
C
SHRLEVEL CHANGE is added. However, the option might not be specified, or might be converted to SHRLEVEL REFERENCE for some generated REORG index statements. SHRLEVEL CHANGE is processed based on the Db2 SHRLEVEL CHANGE restrictions.
R
SHRLEVEL REFERENCE is added. However, the option might not be specified for some generated REORG index statements. SHRLEVEL REFERENCE is processed based on the Db2 SHRLEVEL REFERENCE restrictions.
blank
The SHRLEVEL option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_INDEX_SORTDEVT
Specifies the SORTDEVT option for generated REORG INDEX utility statements. SORTDEVT specifies the device type for temporary data sets that are to be dynamically allocated by the external sort program
Values:
A valid SORTDEVT value for REORG INDEX
The SORTDEVT option is added with the specified value. For example: SORTDEVT SYSDA.
blank
The SORTDEVT option is not added. The Db2 default for this utility option is used.
Default:
SPACE_UNIT_NAME (See SPACE_UNIT_NAME.)
UTIL_REORG_INDEX_SORTNUM
Specifies the SORTNUM option for generated REORG INDEX utility statements. SORTNUM specifies the number of temporary data sets that are to be dynamically allocated when collecting statistics for a data-partitioned secondary index.
Values:
A valid SORTNUM value for REORG INDEX
The SORTNUM option is added with the specified value.
blank
The SORTNUM option is not added. The Db2 default for this utility option is used.
Default:
4
UTIL_REORG_INDREFLIMIT
Specifies the INDREFLIMIT option for generated REORG TABLESPACE utility statements.
Values:
A valid INDREFLIMIT value for REORG
INDREFLIMIT is added with the specified value.
blank
The INDREFLIMIT option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_KEEPDICTIONARY
Specifies the KEEPDICTIONARY option for generated REORG TABLESPACE utility statements. KEEPDICTIONARY prevents the utility from building a new compression dictionary when unloading the rows.
Values:
Start of changeYES or YEnd of change
KEEPDICTIONARY is added.
Start of changeNO or NEnd of change
KEEPDICTIONARY is not added.
Default:
N
Start of changeUTIL_REORG_LASTLOGEnd of change
Start of changeSpecifies the LASTLOG option for generated REORG TABLESPACE utility statements with the SHRLEVEL CHANGE option. LASTLOG controls whether the utility applies log records during the last log iteration in the LOG phase.

To use this parameter, the UTIL_REORG_SHRLEVEL parameter value must be C. Otherwise, UTIL_REORG_LASTLOG is ignored.

Values:
YES or Y
The LASTLOG YES option is added.
NO or N
The LASTLOG NO option is added. If you specify NO or N, UTIL_REORG_DRAIN must be set to A.
blank
The LASTLOG option is not added. The Db2 default for this utility option is used.
Default:
blank
sEnd of change
UTIL_REORG_LISTPARTS
Specifies the LISTPARTS option for generated REORG TABLESPACE utility statements that use a LISTDEF list with PARTLEVL. LISTPARTS specifies the maximum number of data partitions to be reorganized in a single REORG job.

The UTIL_REORG_LISTPARTS and UTIL_REORG_PARALLEL parameters are mutually exclusive.

Values:
Positive integer
The LISTPARTS option is added with the specified value.
blank
The LISTPARTS option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_LOG
Specifies the LOG option for generated REORG TABLESPACE utility statements. LOG specifies whether records are to be logged.
Values:
Start of changeYES or YEnd of change
LOG YES is added.
Start of changeNO or NEnd of change
LOG NO is added.
blank
The LOG option is not added. The Db2 default for this utility option is used.
Default:
N
UTIL_REORG_LOGRANGES
Specifies the LOGRANGES option for generated REORG TABLESPACE utility statements. LOGRANGES specifies whether REORG is to use SYSLGRNX information for the LOG phase.
Values:
Start of changeYES or YEnd of change
LOGRANGES YES is added.
Start of changeNO or NEnd of change
LOGRANGES NO is added.
blank
The LOGRANGES option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_LONGLOG
Specifies the LONGLOG option for generated REORG TABLESPACE utility statements. LONGLOG specifies the action to take if the utility is not reading the application log quickly enough.
Values:
C
The LONGLOG CONTINUE option is added to the utility statement.
T
The LONGLOG TERM option is added to the utility statement.
D
The LONGLOG DRAIN option is added to the utility statement.
blank
The LONGLOG option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_MAPPINGDATABASE
Specifies the MAPPINGDATABASE option for generated REORG TABLESPACE utility statements. MAPPINGDATABASE specifies the database in which the utility implicitly creates the mapping table and index objects.
Values:
A database name; 1 to 8 characters.
Default:
blank
UTIL_REORG_MAPTABLE_NAME
Specifies the mapping table name for generated REORG TABLESPACE utility statements.
Values:
Valid table owner name; 1 to 128 characters
Default:
blank
UTIL_REORG_MAPTABLE_OWNER
Specifies the mapping table owner for generated REORG utility statements.
Values:
Valid table owner name; 1 to 128 characters
Default:
blank
UTIL_REORG_MAXRO
Specifies the MAXRO option for generated REORG TABLESPACE utility statements. MAXRO specifies the maximum amount of time for the last iteration of log processing.
Values:
integer
The MAXRO option is added to the utility statement with the specified value.
D
The MAXRO DEFER option is added to the utility statement.
blank
The MAXRO option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_NEWMAXRO
Specifies the NEWMAXRO option for generated REORG TABLESPACE utility statements. NEWMAXRO specifies the maximum amount of time for the last log iteration after SWITCHTIME is met.
Values:
NONE
The NEWMAXRO NONE option is added.
integer
The NEWMAXRO option with the specified integer value is added.
blank
The NEWMAXRO option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_NOCHECKPEND
Specifies the NOCHECKPEND option for generated REORG TABLESPACE utility statements. NOCHECKPEND specifies that when REORG discards records from a parent table in at least one referential integrity relationship, the utility does not set CHECK-pending status on the dependent table spaces.
Values:
YES or Y
NOCHECKPEND is added.
NO or N
NOCHECKPEND is not added.
blank
NOCHECKPEND is not added.
Default:
blank
UTIL_REORG_NOSYSREC
Specifies the NOSYSREC option for generated REORG TABLESPACE utility statements. NOSYSREC specifies that the utility is not to use an unload data set.
Values:
Start of changeYES or YEnd of change
The NOSYSREC option is added.
Start of changeNO or NEnd of change
The NOSYSREC option is not added.
Default:
N
UTIL_REORG_OFFPOSLIMIT
Specifies the OFFPOSLIMIT option for generated REORG TABLESPACE utility statements.
Values:
A valid OFFPOSLIMIT value for REORG
OFFPOSLIMIT is added with the specified value.
blank
The OFFPOSLIMIT option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_PARALLEL
Specifies the PARALLEL option for generated REORG TABLESPACE utility statements. PARALLEL specifies the maximum number of subtasks that are to be started in parallel to reorganize a table space.
Values:
Start of changeYES or YEnd of change
The PARALLEL option is added.
integer
A valid PARALLEL value for REORG. The PARALLEL option is added to the utility statement with the specified value.
blank
The PARALLEL option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_PREFORMAT
Specifies the PREFORMAT option for generated REORG TABLESPACE utility statements. PREFORMAT specifies that the remaining pages are to be preformatted.
Values:
Start of changeYES or YEnd of change
PREFORMAT is added.
Start of changeNO or NEnd of change
PREFORMAT is not added.
Default:
N
UTIL_REORG_RECLUSTER
Specifies the RECLUSTER option for generated REORG TABLESPACE utility statements. RECLUSTER specifies whether data records are to be reclustered.
Values:
Start of changeYES or YEnd of change
RECLUSTER YES is added.
Start of changeNO or NEnd of change
RECLUSTER NO is added.
blank
The RECLUSTER option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_RETRY
Specifies the RETRY option for generated REORG TABLESPACE utility statements. RETRY specifies the maximum number of retries that the utility is to attempt.
Values:
A valid RETRY value for REORG
The RETRY option is added with the specified value.
blank
The RETRY option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_RETRY_DELAY
Specifies the RETRY_DELAY option for generated REORG TABLESPACE utility statements. RETRY_DELAY specifies the minimum duration, in seconds, between retries.
Values:
A valid RETRY_DELAY value for REORG
The RETRY_DELAY option is added with the specified value.
blank
The RETRY_DELAY option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_REUSE
Specifies the REUSE option for generated REORG TABLESPACE utility statements. REUSE specifies that the utility is to logically reuse Db2-managed data sets.
Values:
Start of changeYES or YEnd of change
REUSE is added.
Start of changeNO or NEnd of change
REUSE is not added.
Default:
N
UTIL_REORG_SHRLEVEL
Specifies the SHRLEVEL option for generated REORG TABLESPACE utility statements. SHRLEVEL indicates the type of access that is to be allowed during utility processing.
Values:
N
SHRLEVEL NONE is added.
C
SHRLEVEL CHANGE is added. However, the option might not be specified, or might be converted to SHRLEVEL REFERENCE for some generated REORG table space statements. SHRLEVEL CHANGE is processed based on the Db2 SHRLEVEL CHANGE restrictions.
R
SHRLEVEL REFERENCE is added. However, the option might not be specified for some generated REORG table space statements. SHRLEVEL REFERENCE is processed based on the Db2 SHRLEVEL REFERENCE restrictions.
blank
Either SHRLEVEL CHANGE or SHRLEVEL REFERENCE is added; Db2 Admin Tool determines the best value (CHANGE or REFERENCE) depending on the circumstance.
Default:
blank
UTIL_REORG_SORTDATA
Specifies the SORTDATA option for generated REORG TABLESPACE utility statements. SORTDATA specifies that the data is to be unloaded by a table space scan, and sorted in clustering order.
Values:
Start of changeYES or YEnd of change
SORTDATA is added.
Start of changeNO or NEnd of change
SORTDATA NO is added.
blank
The SORTDATA option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_SORTDEVT
Specifies the SORTDEVT option for generated REORG TABLESPACE utility statements. SORTDEVT specifies the device type for temporary data sets that are to be dynamically allocated by the external sort program.
Values:
A valid SORTDEVT value for REORG
The SORTDEVT option is added with the specified value. For example: SORTDEVT SYSDA.
blank
The SORTDEVT option is not added. The Db2 default for this utility option is used.
Default:
SPACE_UNIT_NAME (See SPACE_UNIT_NAME.)
UTIL_REORG_SORTKEYS
Specifies the SORTKEYS option for generated REORG TABLESPACE utility statements.

Beginning in DB2 UDB for z/OS 8, the SORTKEYS behavior is the default. The SORTKEYS keyword is ignored.

Values:
Start of changeYES or YEnd of change
SORTKEYS is added.
Start of changeNO or NEnd of change
SORTKEYS is not added.
Default:
N
UTIL_REORG_SORTNPSI
Specifies the SORTNPSI option for generated REORG TABLESPACE utility statements. SORTNPSI specifies when REORG TABLESPACE PART is to sort all keys of a non-partitioned secondary index.
Values:
AUTO or A
SORTNPSI AUTO is added.
YES or Y
SORTNPSI YES is added.
NO or N
SORTNPSI NO is added.
blank
The SORTNPSI option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_SORTNUM
Specifies the SORTNUM option for generated REORG TABLESPACE utility statements. SORTNUM specifies the number of temporary data sets that are to be dynamically allocated for all sorts that the utility performs.
Values:
A valid SORTNUM value for REORG
The SORTNUM option is added with the specified value.
blank
The SORTNUM option is not added. The Db2 default for this utility option is used.
Default:
4
UTIL_REORG_STATISTICS
Specifies the STATISTICS option for generated REORG TABLESPACE utility statements. STATISTICS specifies that statistics are to be gathered.
Values:
Start of changeYES or YEnd of change
The STATISTICS option is added.
Start of changeNO or NEnd of change
The STATISTICS option is not added. Any other specified REORG statistics options are not used.
blank
The STATISTICS option is conditionally added. It is added if a REORG statistics option was explicitly specified. For example, if a value for SAMPLE was specified using the UTIL_REORG_STATISTICS_TABLE_SAMPLE parameter.
Default:
blank
UTIL_REORG_STATISTICS_FORCEROLLUP
Specifies the FORCEROLLUP option for generated REORG TABLESPACE utility statements. FORCEROLLUP specifies whether statistics are to be aggregated.
Values:
Start of changeYES or YEnd of change
FORCEROLLUP YES is added.
Start of changeNO or NEnd of change
FORCEROLLUP NO is added.
blank
The FORCEROLLUP option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_STATISTICS_HISTORY
Specifies the HISTORY option for generated REORG TABLESPACE utility statements. HISTORY specifies that all catalog table inserts or updates to the catalog history tables are to be recorded.
Values:
A
HISTORY ALL is added.
P
HISTORY ACCESSPATH is added.
S
HISTORY SPACE is added.
N
HISTORY NONE is added.
blank
The HISTORY option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_STATISTICS_INDEX_HISTOGRAM
Specifies the HISTOGRAM option for generated REORG TABLESPACE utility statements. HISTOGRAM specifies that histogram statistics are to be gathered for the specified group of columns.
Values:
Start of changeYES or YEnd of change
The HISTOGRAM option is added.
Start of changeNO or NEnd of change
The HISTOGRAM option is not added. Any other specified HISTOGRAM options are not used.
blank
The HISTOGRAM option is conditionally added. It is added if a value is specified for the UTIL_REORG_STATISTICS_INDEX_NUMCOLS parameter or the UTIL_REORG_STATISTICS_INDEX_NUMQUANTILES parameter.
Default:
blank
UTIL_REORG_STATISTICS_INDEX_NUMCOLS
Specifies the NUMCOLS option for generated REORG TABLESPACE utility statements. NUMCOLS specifies the number of key columns that are to be concatenated when collecting histogram statistics from the specified index.

If a value is not specified for the UTIL_REORG_STATISTICS_INDEX_NUMCOLS parameter but a value is specified for the UTIL_REORG_STATISTICS_INDEX_NUMQUANTILES parameter, NUMCOLS 1 is added to generated REORG statements.

Values:
1 - 64
The NUMCOLS option is added with the specified value.
blank
The NUMCOLS option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_STATISTICS_INDEX_NUMQUANTILES
Specifies the NUMQUANTILES option for generated REORG TABLESPACE utility statements. NUMQUANTILES specifies the number of quantiles that are requested.
Values:
1 - 100
The NUMQUANTILES option is added with the specified value.
blank
The NUMQUANTILES option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_STATISTICS_INVALIDATECACHE
Specifies the INVALIDATECACHE option for the generated REORG TABLESPACE utility statements with inline statistics. INVALIDATECACHE indicates whether statements in the dynamic statement cache are invalidated as a result of the inline statistics collection.

If you specify the UTIL_REORG_STATISTICS_INVALIDATECACHE parameter, you must also specify UTIL_REORG_STATISTICS ='Y'.

Values:
Start of changeYES or YEnd of change
INVALIDATECACHE YES is added to the utility statement.
Start of changeNO or NEnd of change
INVALIDATECACHE NO is added to the utility statement.
blank
The INVALIDATECACHE option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_STATISTICS_REPORT
Specifies the REPORT option for generated REORG TABLESPACE utility statements. REPORT specifies whether a set of messages is to be generated to report the collected statistics.
Values:
Start of changeYES or YEnd of change
REPORT YES is added.
Start of changeNO or NEnd of change
REPORT NO is added.
blank
The REPORT option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_STATISTICS_TABLE_SAMPLE
Specifies the SAMPLE option for generated REORG TABLESPACE utility statements. SAMPLE indicates the percentage of rows to be sampled when collecting statistics on non-leading-indexed columns of an index or non-indexed columns.
Values:
1 - 100
The SAMPLE option is added with the specified value.
blank
The SAMPLE option is not added. The Db2 default for this utility option is used.
Default:
blank
Start of changeUTIL_REORG_STATISTICS_TABLESAMPLE_SYSTEMEnd of change
Start of changeSpecifies the TABLESAMPLE SYSTEM option for generated REORG TABLESPACE utility statements. TABLESAMPLE SYSTEM indicates that a sample of data pages from the table is to be used for statistics collection.
Values:
numeric-literal
TABLESAMPLE SYSTEM numeric-literal is added. numeric-literal specifies the sample size as a percentage and can be a value in the range 0.01 - 100.
A or AUTO
TABLESAMPLE SYSTEM AUTO is added. AUTO specifies that REORG is to determine the sampling rate based on the size of the table when the utility runs.
NONE or N
TABLESAMPLE SYSTEM NONE is added. NONE specifies that page sampling is not to be used for inline statistics.
blank
The TABLESAMPLE SYSTEM option is not added. The Db2 default for this utility option is used.
Default:
blank
End of change
UTIL_REORG_STATISTICS_UPDATE
Specifies the UPDATE option for generated REORG TABLESPACE utility statements. UPDATE specifies whether the collected statistics are to be inserted into catalog tables.
Values:
A
UPDATE ALL is added.
P
UPDATE ACCESSPATH is added.
S
UPDATE SPACE is added.
N
UPDATE NONE is added.
blank
The UPDATE option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_STATISTICS_USE_PROFILE
Specifies whether the USE PROFILE option is to be added to the generated REORG TABLESPACE utility statements. USE PROFILE specifies that a statistics profile is to be used to gather statistics.
Values:
Start of changeYES or YEnd of change
USE PROFILE is added.
Start of changeNO or NEnd of change
USE PROFILE is not added.
Default:
blank
UTIL_REORG_SWITCHTIME
Specifies the SWITCHTIME option for generated REORG TABLESPACE utility statements. SWITCHTIME specifies the time for the final log iteration of the LOG phase to begin.
Values:
NONE
SWITCHTIME NONE is added.
timestamp
SWITCHTIME timestamp is added.
labeled-duration-expression
SWITCHTIME labeled-duration-expression is added.
blank
The SWITCHTIME option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_REORG_TIMEOUT
Specifies the TIMEOUT option for generated REORG TABLESPACE utility statements. TIMEOUT specifies the action that is to be taken if the REORG utility gets a timeout condition.
Values:
T
The TIMEOUT TERM option is added to the utility statement.
A
The TIMEOUT ABEND option is added to the utility statement.
blank
The TIMEOUT option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
UTIL_RUNSTATS_HISTORY
Specifies the HISTORY option for generated RUNSTATS utility statements. HISTORY specifies which statistics are to be recorded in the catalog history tables.
Values:
A
HISTORY ALL is added.
P
HISTORY ACCESSPATH is added.
S
HISTORY SPACE is added.
N
HISTORY NONE is added.
blank
The HISTORY option is not added. The Db2 default for this utility option is used.
Default:
blank
Related information:
UTIL_RUNSTATS_INVALIDATECACHE
Specifies the INVALIDATECACHE option for the generated RUNSTATS utility statements. INVALIDATECACHE specifies whether the dynamic statement cache is invalidated.
Values:
Start of changeYES or YEnd of change
INVALIDATECACHE YES is added to the utility statement.
Start of changeNO or NEnd of change
INVALIDATECACHE NO is added to the utility statement.
blank
The INVALIDATECACHE option is not added to the utility statement. The Db2 default for this utility option is used.
Default:
blank
Related information:
UTIL_RUNSTATS_PROFILE
Specifies whether the RUNSTATS utility is to use statistics profiles.
Values:
USE or U
USE PROFILE is added to the utility statement. USE PROFILE specifies that a stored statistics profile is to be used to gather statistics for a table.
DELETE or D
DELETE PROFILE is added to the utility statement. DELETE PROFILE specifies that the existing RUNSTATS profile for the table is to be deleted from the SYSIBM.SYSTABLES_PROFILES catalog table.
blank
Neither PROFILE clause is added to the utility statement.
Default:
blank
Related information:
UTIL_RUNSTATS_REPORT
Specifies the REPORT option for generated RUNSTATS utility statements. REPORT specifies whether RUNSTATS is to generate a set of messages that report the collected statistics.
Values:
Start of changeYES or YEnd of change
REPORT YES is added.
Start of changeNO or NEnd of change
REPORT NO is added.
blank
The REPORT option is not added. The Db2 default for this utility option is used.
Default:
blank
Related information:
UTIL_RUNSTATS_SHRLEVEL
Specifies the SHRLEVEL option for generated RUNSTATS utility statements. SHRLEVEL indicates whether the level of access that other programs have during utility processing.
Values:
C
SHRLEVEL CHANGE is added.
R
SHRLEVEL REFERENCE is added.
blank
The SHRLEVEL option is not added. The Db2 default for this utility option is used.
Default:
blank
Related information:
UTIL_RUNSTATS_SHRLEVEL_CHANGE_REGISTER
Specifies whether, when SHRLEVEL CHANGE behavior is in effect, pages that are read by the RUNSTATS utility in a data sharing environment are registered with the coupling facility.
Values:
YES (or Y)
Pages are registered.
NO (or N)
Pages are not registered.
Default:
YES
Related information:
UTIL_RUNSTATS_SORTDEVT
Specifies the device type that the sort program uses to dynamically allocate the sort work data sets that are required by the RUNSTATS utility.
Values:
device-type
The disk device type.
blank
SORTDEVT is not added to the utility statement.
Default:
blank
Related information:
UTIL_RUNSTATS_SORTNUM
Specifies the number of required sort work data sets that the sort program is to allocate for the RUNSTATS utility.
Values:
integer
The number of temporary data sets. Valid values range from 2 to 255.
blank
SORTNUM is not added to the utility statement.
Default:
blank
Related information:
UTIL_RUNSTATS_UPDATE
Specifies the UPDATE option for generated RUNSTATS utility statements. UPDATE indicates which collected statistics are to be inserted into the catalog tables.
Values:
A
UPDATE ALL is added.
P
UPDATE ACCESSPATH is added.
S
UPDATE SPACE is added.
N
UPDATE NONE is added.
blank
The UPDATE option is not added. The Db2 default for this utility option is used.
Default:
blank
Related information:
UTIL_UNLOAD_DBCS_CCSID
Specifies the DBCS value for the CCSID option for generated UNLOAD utility statements.
Values:
A valid CCSID for DBCS data
The CCSID option is added with the specified value as the third value of the CCSID parameters.

The CCSID is specified as follows: CCSID(UTIL_UNLOAD_SBCS_CCSID, UTIL_UNLOAD_MIXED_CCSID, UTIL_UNLOAD_DBCS_CCSID)

blank
The DBCS value is omitted from the CCSID option. The Db2 default for this utility option is used.
Default:
blank
UTIL_UNLOAD_ENCODINGSCHEME
Specifies which encoding scheme option (EBCDIC, ASCII, or UNICODE) to add to generated UNLOAD utility statements.
Values:
E
The EBCDIC option is added.
A
The ASCII option is added.
U
The UNICODE option is added.
blank
No encoding scheme option is added. The Db2 default for this utility option is used.
Default:
blank
UTIL_UNLOAD_FLOAT
Specifies the FLOAT option for generated UNLOAD utility statements. FLOAT specifies the output format of the numeric floating-point data.
Values:
S
FLOAT S390 option is added.
I
FLOAT IEEE is added.
blank
The FLOAT option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_UNLOAD_FORMAT_INTERNAL
Specifies the FORMAT INTERNAL option for generated UNLOAD utility statements. FORMAT INTERNAL specifies that the output record format is Db2 internal format.
Values:
Start of changeYES or YEnd of change
FORMAT INTERNAL is added.
blank
The FORMAT INTERNAL option is not added.
Default:
blank
UTIL_UNLOAD_IMPLICIT_TZ
Specifies the IMPLICIT_TZ option for generated UNLOAD utility statements. IMPLICIT_TZ specifies the implicit time zone to use when timestamp values are being unloaded from a TIMESTAMP column with no time zone
Values:
A valid IMPLICIT_TZ value for UNLOAD
The IMPLICIT_TZ option is added with the specified value.
blank
The IMPLICIT_TZ option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_UNLOAD_MAXERR
Specifies the MAXERR option for generated UNLOAD utility statements. MAXERR specifies the maximum allowable number of records in error.
Values:
A valid MAXERR value for UNLOAD
The MAXERR option is added with the specified value.
blank
The MAXERR option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_UNLOAD_MIXED_CCSID
Specifies the MIXED value for the CCSID option for generated UNLOAD utility statements.
Values:
A valid CCSID for mixed data
The CCSID option is added with the specified value as the second value of the CCSID parameters.

The CCSID is specified as follows: CCSID(UTIL_UNLOAD_SBCS_CCSID, UTIL_UNLOAD_MIXED_CCSID, UTIL_UNLOAD_DBCS_CCSID)

blank
The value for mixed data is omitted from the CCSID option. The Db2 default for this utility option is used.
Default:
blank
UTIL_UNLOAD_NOPAD
Specifies the NOPAD option for generated UNLOAD utility statements. NOPAD specifies that the variable-length columns are to be unloaded without additional padding.
Values:
Start of changeYES or YEnd of change
NOPAD is added.
Start of changeNO or NEnd of change
The NOPAD option is not added.
Default:
N
UTIL_UNLOAD_NOSUBS
Specifies the NOSUBS option for generated UNLOAD utility statements. NOSUBS specifies that substitution characters are not to be used for any CCSID conversions that occur during unload processing.
Values:
Start of changeYES or YEnd of change
The NOSUBS option is added.
Start of changeNO or NEnd of change
The NOSUBS option is not added.
Default:
N
UTIL_UNLOAD_PARALLEL
Specifies the PARALLEL option for generated UNLOAD utility statements. PARALLEL specifies the maximum number of subtasks that are to be used in parallel when unloading a partitioned table space.
Values:
Start of changeYES or YEnd of change
The PARALLEL option is added.
integer
The PARALLEL option is added to the utility statement with the specified value.
blank
The PARALLEL option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_UNLOAD_SBCS_CCSID
Specifies the SBCS value for the CCSID option for generated UNLOAD utility statements.
Values:
A valid CCSID for SBCS data
The CCSID option is added with the specified value as the first value of the CCSID parameters.

The CCSID is specified as follows: CCSID(UTIL_UNLOAD_SBCS_CCSID, UTIL_UNLOAD_MIXED_CCSID, UTIL_UNLOAD_DBCS_CCSID)

blank
The SBCS value is omitted from the CCSID option. The Db2 default for this utility option is used.
Default:
blank
UTIL_UNLOAD_SHRLEVEL
Specifies the SHRLEVEL option for generated UNLOAD utility statements. SHRLEVEL specifies whether other processes can access or update the table space or partitions while the data is being unloaded.
Values:
1
SHRLEVEL CHANGE ISOLATION CS is added.
2
SHRLEVEL CHANGE ISOLATION UR is added.
3
SHRLEVEL REFERENCE is added.
blank
The SHRLEVEL option is not added. The Db2 default for this utility option is used.
Default:
blank
UTIL_UNLOAD_SHRLEVEL_CHANGE_REGISTER
Specifies whether, when ISOLATION UR and SHRLEVEL CHANGE behaviors are in effect, pages that are read by the UNLOAD utility in a data sharing environment are registered with the coupling facility.
Values:
YES (or Y)
Pages are registered.
NO (or N)
Pages are not registered.
Default:
blank
UTIL_UNLOAD_SKIP_LOCKED_DATA
Specifies the SKIP LOCKED DATA option for generated UNLOAD utility statements. SKIP LOCKED DATA specifies that the UNLOAD utility is to skip rows on which incompatible locks are held by other transactions.
Values:
Start of changeYES or YEnd of change
The SKIP LOCKED DATA option is added.
Start of changeNO or NEnd of change
The SKIP LOCKED DATA option is not added.
Default:
NO
UTIL_UNLOAD_SPANNED
Specifies the SPANNED value that is passed to the generated UNLOAD utility statements. SPANNED indicates whether records are to be unloaded into a VBS data set in spanned record format.
Values:
Start of changeYES or YEnd of change
SPANNED is added.
Start of changeNO or NEnd of change
SPANNED is not added.
Default:
No