Re: RPGLE based stored procedure with CLOB parameter

[Charles Wilt <charles.wilt@xxxxxxxxx>]

So increase the size...
For supported versions of the OS

The maximum length for a fixed-length character field is 16773104.
> The maximum length for a variable-length character field is 16773100.


https://www.ibm.com/docs/en/i/7.4?topic=appendixes-appendix-rpg-iv-restrictions

HTH,
Charles


On Tue, Oct 8, 2024 at 11:09 AM Brian Garland via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> Background:
> Our system uses several SQL stored procedures that use an RPGLE service
> program procedures which take a large VARCHAR as their parameter.  The
> scenario has come up where the max VARCHAR (32739) is not enough so I was
> hoping to use a CLOB.
>
> Problem:
> If I define a RPGLE procedure using SQLTYPE(CLOB:2000000) it doesn't
> compile because the precompile converts it to a DS with OVERLAY
> 008800     DCL-PI *N IND;
>
> 009000 //*        JSONPARM SQLTYPE(CLOB:2000000);
>
> 009000          JSONPARM CHAR(2000004) CCSID(*HEX);
>            //SQL
> 009000           JSONPARM_LEN UNS(10) OVERLAY(JSONPARM);
>             //SQL
> ======>                               aaaaaaa
>
> *RNF3748 20 a      009000  Keyword is not allowed for a parameter
> definition; keyword is ignored.
>
> 009000           JSONPARM_DATA CHAR(2000000) OVERLAY(JSONPARM:5)
> CCSID(*JOBRUNMIX);    //SQL
> ======>                                      aaaaaaa
>
> *RNF3748 20 a      009000  Keyword is not allowed for a parameter
> definition; keyword is ignored.
>
> 009100     END-PI;
>
>
> I was hoping to do this in the same style of our current process (one long
> string) to keep things similar.
>
> Is there any way to use a CLOB parameter in an SQL stored procedure that
> uses an RPGLE service program procedure.
>
>
> Brian
>
> --
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or company to whom they are
> addressed.
> Do not disclose, distribute, or copy this email to others outside your
> company. If you have received this email in error, please notify the
> sender
> immediately and delete this email from your system.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.