× 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.



We converted our system to V5R4 last night. Today, I am seeing problems
where the CALLPRC is used in CLLE programs. I am passing a character
string into an SQLRPGLE module. Using debug, the character string is
intact until it gets passed into the module. Here is the code.

             PGM        PARM(&PARM)

             DCL        VAR(&PARM) TYPE(*CHAR) LEN(22)

             CALLPRC    PRC(AA0130) PARM(&PARM)

             ENDPGM

Here is the debug eval results for the field when the program gets to the
CALLPRC statement.

&PARM = '01V000000100AA0125    '

The data gets corruptted when passed into the SQLRPGLE module.

This situation only applies to CLLE program compiled since installing
V5R4. We also compile to previous release of V5R2.

Thanks in advance for assistance.

Nick W. Mart


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-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.