Re: How do I clip a vary length field?

I'm not sure I understand the question as posed.

If you want to limit Upper to 1024 characters then define it that way e.g.

Dcl-S Upper Varchar(1024);

Then the truncation takes place on assignment.

The problem I have is why you are not just assigning EZDQLSTL directly to upper. Why bother with XSql1024 ? Which you don't seem to be setting correctly anyway as you are mapping the count portion over the first 2 characters of EZDQLSTL which I'm pretty sure is not what you want.

Is EZDQLSTL even a varchar? I suspect IBM define it as Char * - which does not mean varchar - it means variable in length - not the same thing.

P.S. If you ever do need to get the address of the data portion of a varchar then use %Addr( fieldName : *Data ) - not the + 2 method which will fail for large fields.

On Dec 9, 2019, at 10:02 AM, C Holko <christopherholko@xxxxxxxxx> wrote:

So, I have this
XSql1024 S 9216 Varying
Based(SqlPtr)

Upper S Like(XSQL1024)

and later some code does
SqlPtr = %addr(EZDQLSTL) + 2
Upper = XSQL1024

The EZ* fields are from QSYSINC/QRPGLESRC EZDAEP coming in the exit
QIBM_QZDA_SQL2

I need to clip XSQL1024 so it will always fit in Upper. I am getting SQL
strings in excess of 9k.

What are my options?
--
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@xxxxxxxxxxxx for any subscription related questions.

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