×
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.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Birgitta Hauser
Sent: Wednesday, May 05, 2010 1:41 PM
To: 'RPG programming on the IBM i / System i'
Subject: AW: Weird Embedded SQL Problem: getting x'20' in result variable
It seems your variable was padded with double byte blanks x'0020'.
When defining your variable with varying length (as you've already done),
these blanks will be ignored
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Schmidt, Mihael
Gesendet: Wednesday, 05. May 2010 11:08
An: RPG programming on the IBM i / System i
Betreff: Weird Embedded SQL Problem: getting x'20' in result variable
Hi,
I am having a really weird embedded sql problem. I am just retrieving a
value from a database field, nothing special. The database field is defined
VARCHAR(32000). The value in the field is about 200 characters long. The
receiving variable is defined 32000A.
Most of the time the variable is filled correctly and is padded with spaces
(x'40'). But some times the variable is padded with x'20' instead of x'40'
and I got no clue why. The retrieved value though is correct. Only the
padded space is wrong.
This mailing list archive is Copyright 1997-2024 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.