Re: SQL column size in CLLE

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Jim

How about wrapping those columns in a CAST?

*Regards*

*Vern Hamberg*

IBM Champion 2025 <cid:part1.iEeWSUfp.vxFqQoqf@centurylink.net> CAAC 
(COMMON Americas Advisory Council) IBM Influencer 2023

On 5/28/2025 1:19 PM, Jim Oberholtzer wrote:
> I am running this SQL in a CLLE program:
>
>   Runsql ('CREATE TABLE QTEMP/LISTJRN AS (
>               SELECT JOURNAL_RECEIVER_LIBRARY as RCVLIB
>                     ,JOURNAL_RECEIVER_NAME    as RCVNAM
>                     ,DETACH_TIMESTAMP         as TIMESTMP
>        FROM QSYS2.JOURNAL_RECEIVER_INFO
>        WHERE DETACH_TIMESTAMP IS NOT NULL
>         AND SUBSTR(JOURNAL_RECEIVER_LIBRARY, 1,1) <> ''Q''
>         AND DETACH_TIMESTAMP < CURRENT_TIMESTAMP - 14 DAYS
>      ORDER BY DETACH_TIMESTAMP)
>      WITH DATA')
>        COMMIT(*NONE)
>
> In SQL runscrips, the SQL works great, until I go to use the columns RCVLIB and RCVNAM.  The SQL produces a file with varchar output which the CLLE does not like.
>
> How to I put a size on the two columns (ideally Char 10) so the CLLE compiler won’t complain?
> --
> Jim Oberholtzer
> Agile Technology Architects