LSTRLOB parameter: Difference between revisions
mNo edit summary |
(Automatically generated page update) |
||
Line 11: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Sirius Mods</var> Version 7.7 | <dd><var class="product">[[Sirius Mods]]</var> Version 7.7 | ||
</dl> | </dl> | ||
==Description== | ==Description== |
Revision as of 20:06, 19 April 2013
Treat LOBs as Longstrings
Summary
- Default value
- 1
- Parameter type
- System
- Where set
- System manager
- Related products
- All
- Introduced
- Sirius Mods Version 7.7
Description
When LSTRLOB=1, User Language programs running in Model 204 version V7R2 or later can use normal field reference syntax for Lob fields. Otherwise (LSTRLOB=0), access to Lob fields must use the Buffer syntax.
The default value of LSTRLOB is 1. LSTRLOB has no effect for Model 204 version V7R1.
The "normal field reference syntax" applies to all uses of a BLOB or CLOB field name except for the Note statement.
The types of allowed "normal field references" are shown in the following table, which assumes that field LOB
has the BLOB or CLOB attribute:
Type of reference | Examples |
---|---|
Used in expression |
%s = LOB %t = LOB:substring(%pos, %len) %xmNode:addElement('info', LOB) |
Print statement |
print 'Value is:' and LOB |
Field updates |
%s1 = 'x':left(3000, pad='x') add LOB = %s2 Note that the normal field reference syntax in the Store Record and Add statements does not have a provision for the Reserve clause which is available on the Buffer syntax. This is not an issue for a change LOB to %s3 Note that the only type of Change statement allowed for a field with the MINLOBE attribute is this form, using the normal field reference syntax. |