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.

+LOBERRORS(action,message)

The +LOBERRORS(action,message) parameter specifies what to do if BMC AMI Reorg encounters an integrity error while processing a table space that has an associated LOB.

Related topics

Command and syntax reference

BMC-AMI-LOBMaster-DD-statements

BMC-AMI-LOBMaster-parameters-RRGPARMS-DD

Reporting-for-BMC-AMI-LOBMaster

Working-with-infrastructure

Running-BMC-AMI-LOBMaster

LOBERRORS.png

For more information about the types of integrity errors that BMC AMI Reorg might encounter, see Detecting and controlling errors.

Important

In many cases, these errors will cause Db2 to abend while reading the LOB. For example, during an SQL fetch of the data, Db2 might fail with an 04E abend.

action

ABEND or A

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

ERASE or E

This value is not currently used.

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.

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 LOB error 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 there are errors in the structure, the reorganization abends and an error message is written to SYSERROR.

+LOBERRORS(ABEND,MSG)

Important

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


 

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