|
We ran into an issue where a variable, defined as *CHAR with a length of 5000, but either initialized or data moved to this field exceeded 5000 characters, caused a subsequent command to fail because of length limitation issue, CPD0183. How can this happen? Is this a bug? How can a field have more data than it was defined for.
We saw the same results if the data was defined in an RPGLE program, passed it the CL.
DCL VAR(&M) TYPE(*CHAR) LEN(5000)
SWPUSRPRF USRPRF(CPATEXT) CMD(SNDDST TYPE(*LMSG) +
TOINTNET((psteinmetz@xxxxxxxxxx)) +
DSTD(TEST) LONGMSG(&M))
Message ID . . . . . . : CPD0183 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 05/02/13 Time sent . . . . . . : 09:22:03
Message . . . . : Embedded command SNDDST too long.
Cause . . . . . : The length specified for the embedded command exceeds the
defined length. Command length is 5001, but the maximum length for the
embedded command string is 5000.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.