Maximum-LOB-bytes-per-row - Teradata Tools and Utilities

Teradata® Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

Product
Teradata Tools and Utilities
Release Number
16.20
Published
September 2019
Language
English (United States)
Last Update
2019-10-12
dita:mapPath
dsu1527114222346.ditamap
dita:ditavalPath
dsu1527114222346.ditaval
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

Maximum-LOB-bytes-per-row is an eight-byte unsigned integer that specifies the maximum total size of all Large-objects, in bytes, selected from a row in one request for which Teradata Database is permitted to return data inline, overriding a DBCAREA Return-objects-as option to defer data by returning a locator. Whether Teradata Database supports this feature can be ascertained using the DBCHQE Integrated-LOB query QERILSU value. The Maximum-LOB-bytes-per-row value does not include the length of the standard 8-byte Database prefixes for LOB datatypes: only the actual total amount of data should be included.

Maximum-LOB-bytes-per-row exists only when DBCHINI had been called for a DBCAREA with Total-length set to at least 1024 (that is, the returned DBCAREA Level value is at least 2). For a smaller DBCAREA, Maximum-LOB-bytes-per-field is taken to be zero.

Language Maximum-LOB-bytes-per-row
COBOL LOB-ROW-LIMIT
C, C++ lobRowLimit
PL/I LOB_Row_Limit
IBM Assembler DBRIMLBR
Routine Action for Maximum LOB Bytes
DBCHINI writes
DBCHCL reads (IRQ;IWPF)
Maximum-LOB-bytes-per-row is used by... To...
applications read

If Maximum-LOB-bytes-per-row is zero, no additional limit is placed on the length of the row. The limit will instead be the limit of a LOB Field (if specified), message size, or other Database limit.

If Maximum-LOB-bytes-per-row exceeds a database server limit, an error will be issued by the server.

If both Maximum-LOB-bytes-per-row and Maximum-LOB-bytes-per-field are zero, the specified DBCAREA Return-objects-as option will determine how Large-objects are returned.