Default language.

Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI LOBMaster for Db2 13.1.

+LOBMISSING(action,message)

The +LOBMISSING(action,message) parameter specifies what to do if 

BMC AMI Reorg

 finds a row in the base table space whose corresponding row in the LOB auxiliary table space is missing.


Important

(PTF BQU2620 applied) If BMC AMI LOBMaster REPORTONLY detects missing LOBs, it will end with:

  • Return code 4 if you have configured or specified +LOBMISSING(IGNORE) or +LOBMISSING(ERASE)
  • Return code 8 if you have configured or specified +LOBMISSING(ABEND)


LOBMISSING.png

BMC AMI Reorg considers a LOB missing only if the base row has a version number in the LOB field that indicates that there should be a corresponding LOB row in the auxiliary table space.

The following table lists the types of missing LOBs:

Type

Description

1

The LOB exists in the LOB index, but does not exist in the LOB table space.

2

The LOB does not exist in the LOB index, but does exist in the LOB table space.

3

The LOB is referenced by a row in the base table space, but does not exist in the LOB table space.

4

The LOB is referenced by a row in the base table space and exists in the LOB table space, but does not exist in the LOB index.

Note the following information about each type of missing LOBs:

  • BMC AMI Reorg detects types 1, 2, and 3 after read tasks have completed for the LOB index and LOB table space.
  • BMC AMI Reorg detects type 4 while reading the base table space.
  • Types 2 and 4 can be corrected by specifying +LOBMISSING(IGNORE) to fix the LOB index.
  • Types 1 and 3 are likely to cause Db2 SQL fetch to fail with an abend.

action

ABEND or A

(default) This value tells BMC AMI Reorg to abend the reorganization.

ERASE or E

This value tells BMC AMI Reorg to delete the LOB in error, if possible, and update the base table space row in the LOB column to NULL. Note the following specific actions based on the type of missing LOB:

  • Types 1 and 3—ignores this value
  • Type 2 and 4—corrects the index

IGNORE, IGN, or I

This value tells BMC AMI Reorg to ignore the error, leave the data as it was (if possible), and complete the reorganization. For missing LOB types 1 and 3, BMC AMI Reorg abends if you specify IGNORE.

Warning

For certain types of LOB errors, IGNORE can produce unpredictable results later in the reorganization (for example, when writing the LOB). Therefore, BMC strongly recommends that you use +LOBMISSING(ABEND, MSG) instead of IGNORE.

message

MESSAGE, MSG, or M

(default) This value tells BMC AMI Reorg to print up to 50 error messages to SYSERROR, followed by messages for the total missing LOB counts. For a sample report, see Messages-to-the-SYSERROR-DD.

NOMESSAGE, NOMSG, or NOM

This value tells BMC AMI Reorg not to write error messages to SYSERROR.

Example

In the following example, if BMC AMI Reorg encounters missing LOBs, the reorganization abends, and an error message is written to SYSERROR:

+LOBMISSING(ABEND,MSG)

Important

For the rules that apply to parameter syntax, see Parameter syntax rules.

Related topics

Command and syntax reference

DD-statements-for-BMC-AMI-LOBMaster

BMC-AMI-LOBMaster-parameters-RRGPARMS-DD

Reporting-for-BMC-AMI-LOBMaster

Working-with-infrastructure

Running-BMC-AMI-LOBMaster

LOBORPHANS-action-message


 

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