× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

The SQL pre-processor doesn't support RPG constants...


On Tue, Nov 30, 2021 at 12:47 AM Åke Olsson <konsult@xxxxxxxxxxxxxxx> wrote:

I noticed something weird when testing an SQL program I am writing. The
program parses message queues in search of escape messages.

The message data is then received in a character variable for later

But if I define the receiving variable like this:

dcl-c Used_Ccsid 278;

dcl-s Messtxt char(100) ccsid(Used_Ccsid);

The SQL fetch fails with SQLSTATUS 57017 “Character conversion between
CCSID 1200 and CCSID 65535 not valid)

Whereas if I define the “Messtxt” variable like this

dcl-s Messtxt char(100) Ccsid(278);

It all works fine

Normally defining various features of variables using constants for say
number of digits, sizes or similar works perfectly fine.

This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 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.