Important We are integrating BMC AMI LOBMaster technology into the BMC AMI Reorg product and discontinuing BMC AMI LOBMaster as a separate product. For the latest integrated documentation, see BMC AMI Reorg for Db2 13.1.

BMC AMI LOBMaster syntax

This topic describes SYSIN syntax for BMC AMI Reorg as it applies to BMC AMI LOBMaster.


Related topics

BMC-AMI-LOBMaster-command-and-syntax-reference

Getting-started-with-BMC-AMI-LOBMaster

Large-object-LOB-components 

Reporting-for-BMC-AMI-LOBMaster

Working-with-infrastructure

Running-BMC-AMI-LOBMaster

REORG TABLESPACE

REORG TABLESPACE syntax applies to LOB reorganizations.

REORG_TABLESPACE_syntax.png

AUX

AUX tells BMC AMI LOBMaster whether to process both the base table space and any LOB auxiliary table spaces at the same time:

  • YES (the default) processes both the base table space and any LOB auxiliary table spaces at the same time. Effectively, specifying AUX YES with REORG TABLESPACE initiates BMC AMI LOBMaster.The following considerations apply to AUX YES:
    • If you also specify REBALANCE on your REORG command, the utility invokes DSNUTILB.
    • If a pending DDL change exists to drop a LOB column, BMC AMI LOBMaster changes the AUX value to NO. You can specify AUX (or AUX YES) after the change is materialized.
  • NO (or if AUX is omitted) processes only the base table space.

Additional options

The following keywords provide specific functionality when processing objects with LOBs:

REPORTONLY

REPORTONLY tells BMC AMI Reorg to perform the following actions without reorganizing, thereby producing DASD savings:

  • Analyze LOB size
  • Write LOB size reports to LOBREPRT
  • Write check errors to SYSERROR

Using REPORTONLY issues one of the following return codes, based on the +LOBMISSING or +LOBORPHANS value: 

  • 0 means LOBMaster did not find any errors
  • 4 means LOBMaster found errors, and +LOBMISSING or +LOBORPHANS specified IGNORE or ERASE.
  • 8 means LOBMaster found errors, and +LOBMISSING or +LOBORPHANS specified ABEND.

DISCARD

DISCARD tells BMC AMI Reorg to discard rows as part of the reorganization. This option functions somewhat differently when AUX is specified on a table space with LOBs:

  • BMC AMI Reorg ignores any DISCARDDN specification.
  • BMC AMI Reorg always dynamically allocates the discard files in variable-blocked spanned (VBS) record format. For partitioned table spaces, a separate discard file is allocated for each partition that contains discards. This spanned discard file is compatible with the IBM Db2 LOAD utility in Db2 10 and later.
  • You must include an XULDDYNM-unload-data-set-and-discards-automation-control-point or specify the OUTPUT command, providing a data set name for the discard file. This name must be unique for each partition.
  • BMC AMI Reorg dynamically allocates the SYSPUNCH file (which contains a generated LOAD statement). A separate file is allocated for each partition that contains discards.
  • The XULDDYNM-unload-data-set-and-discards-automation-control-point or OUTPUT command must provide a unique data set name for the SYSPUNCH file for each partition.XULDDYNM has a variable type that indicates whether the file being allocated is for a discard file or SYSPUNCH file.
  • The generated LOAD statement specifies the SPANNED keyword, enabling its use with the Db2 LOAD utility in Db2 10 and later.
  • The unload file contains all LOB data for discarded base table space rows.

Note: If you use both DISCARD and REPORTONLY in the REORG statement, BMC AMI Reorg writes to the discard file without discarding the rows. You can use this combination of options to selectively unload data from a table that contains LOB columns

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*