Re: CLOB fields -- MIDRANGE-L

Subject: Re: CLOB fields
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Fri, 5 Jun 2026 14:15:46 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Jun 5, 2026, at 2:18 AM, Daniel Gross <daniel@xxxxxxxx> wrote:

If you want the content in RPG your best bet is to use a variable of SQLTYPE(CLOB:<size>). This results in a special data structure with a _LEN and _DATA subfield, that you can use from RPG. And the contents of your CLOB are fully copied into memory.

FWIW: I submitted an idea to allow the data and length subfields to be accessed more idiotically.

Instead of ‘clobfield_data’ and ‘clobfield_len’, the subfields would be qualified, clobfield.data & clobfield.len.

https://ideas.ibm.com/ideas/IBMI-I-4759

david

Follow-Ups:

Re: CLOB fields , Jon Paris

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.