|
From: | Patrick |
Subject: | Re: [open-cobol-list] Help understanding this behaviour |
Date: | Sun, 01 Sep 2013 20:53:22 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130809 Thunderbird/17.0.8 |
Hi Charles
Thanks for answering my post ! So I see were you are going with this, 17 bytes expected, 4 sent but why would the calling procedure tack on 13 bytes of junk? The calling procedure does not have knowledge of what is expected to be received, wouldn't it just send what is enclosed in the quotes? I actually just changed it to X(50) and the whole string "why is this string showing up later" gets sent along with the value enclosed in quotes. At the end of the day, if I have to send only values defined in working storage, it's not a big deal, it's just that I don't really get the logic behind this. Thanks for helping me to narrow the problem down to the calling side, I thought it was on the receiving end and thanks again for posting-Patrick On 09/01/2013 08:36 PM, Charles Anthony wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |