|
On 03/03/2006, at 12:38 PM, Mike Pantzopoulos - (H/O) wrote:
Unfortunately, I'm the person responsible!The declared length is 20. It's varying so I presume it's really 22. The passed in parameter is actually defined as 20.
Yes.
I'm presuming it's something I've done with the way I've written the CALLPRC command in the CL.Or have I just done something stupid?
Yes.
Any clues would be gratefully accepted.
CL doesn't have any concept of *VARYING character strings. You'll have to build a proper string yourself. A *VARYING character string is prefixed with a 2-byte length thus you'll have to set the length into those bytes before you call the procedure. Declare the field as 22 bytes and use %BIN to set the length in the first two bytes.
I question why this field is *VARYING. It's only 20 bytes. Just make it fixed length and trim if needed.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
