# Msg truncated to fit receive-buffer

**URL:** <https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511>\
**Category:** Forum\
**Tags:** Mainframe-Integration, EntireX\
**Created:** [February 11, 2015, 3:26am UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511 "2015-02-11T03:26:44Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Brooks](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/chris_brooks/32/516_2.png) [@Chris\_Brooks](https://techcommunity.softwareag.com/u/Chris_Brooks)\
**Post date:** [February 11, 2015, 3:26am UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511/1 "2015-02-11T03:26:44Z")

</div>

Hi all,

We are having problems getting a webservice to behave when converting between the code pages ibm-1047\_P100-1995 and UTF-8.

The RPC call is initiated by the mainframe and calls to a Unix box which then responds. So far, everything is working perfectly up to the point where the response is passed back to the mainframe broker.

The Broker SYSOUT shows:

> [@](#):
>
> W00/REQUEST 2015-02-10 11:03:27.472 ETBD0282 SPFX Values:  
> Prefix = 800109240000045A0000002400000000000000000000052303000000000000  
> 0000000000  
> Unique-ID = 313546656231302D3130353830342D3030303031462D303030303034  
> Key string: ,BID=mvs:18028,F=SEND,UID=ONEWORLD\_TEST,CID=100000001F00000D,S  
> L=1078,LS=UTF8,API=9,XRL=0,ANODE=oneworld-test-wl4,ATYPE=Java,AVERS=8.1.3.  
> 00,ANAME=XML RPC Server,ETXL=256,RPCLIB=CORCODES,RPCPGM=ZPARTY-S.  
> SeqID = 60  
> W00/PRNTTRAP 2015-02-10 11:03:27.474 ETBD0286 Diagnostic Values:  
> TRAP6 Fields Before:  
> Input fields: in length 1078, out length 968, in buf 45E75028  
> Output fields: returned length 0, required length 0, out buf 12FA4030  
> Routine: SAGTCHA, Method: ICU, Trace: 3 Option: 8  
> Sender CodePage UTF8  
> Receiver CodePage ibm-1047\_P100-1995  
> Broker CodePage ibm-1047\_P100-1995,swaplfnl  
> W00/USREXIT 2015-02-10 11:03:27.474 ETBD0298 User Exit Diagnostic Values:  
> In Fields: Sender=UTF8, Receiver=ibm-1047\_P100-1995  
> Broker=ibm-1047\_P100-1995,swaplfnl, Options=8, Trace level=3  
> W00/PRNTTRAP 2015-02-10 11:03:27.474 ETBD0286 Diagnostic Values:  
> TRAP6 Fields After:  
> Input fields: in length 1078, out length 968, in buf 45E75028  
> Output fields: returned length 0, required length 1078, out buf 12FA4030  
> Routine: SAGTCHA, Method: ICU, Trace: 3 Option: 8  
> Sender CodePage UTF8  
> Receiver CodePage ibm-1047\_P100-1995  
> Broker CodePage ibm-1047\_P100-1995,swaplfnl  
> W00/TRANEND 2015-02-10 11:03:27.475 ETBD0286 Diagnostic Values:  
> Conversion Trace Area (rc=4):  
> ucnv\_fromUChars:E15  
> W00/RESPONSE 2015-02-10 11:03:27.475 ETBD0282 SPFX Values:  
> Prefix = 8001092400000024000000005CC1D5E2000000000000014E03000000000000  
> 000000004E  
> Unique-ID = 313546656231302D3130353830342D3030303031462D303030303034  
> Reply Strg: CID=100000001F00000D,EC=00000000,SEQID=60,TXT=Successful respo  
> nse.  
> W00/RESPONSE 2015-02-10 11:03:27.475 ETBD0282 SPFX Values:  
> Prefix = 2201051C0000001C000000005CC1D5E2000000000000008801000000  
> Unique-ID = 0008E2DE28180000CE7C08B345C96C0500000001CE7C08B345C8B385  
> Reply Strg: CID=100000001F00000D,EC=00200094,RETL=00001078,TXT=API: Msg tr  
> uncated to fit receive-buffer,UOWST=RECV\_NONE.  
> SeqID = 59

It seems to be an issue during the code page conversion.

The IDL is:

> [@](#):
>
> 1 ZPARTY-INOUT /\* Inout  
> 2 IPA-CUSTOMER-ID (A13)  
> \*  
> 1 ZPARTY-OUT /\* Out
> 
> - \*\*\* TN-Name-and-Address \*\*\*  
> 2 ACN-ARBN-NO (A9)
> - \*\*\* CDM-Attorney \*\*\*  
> 2 ATTORNEY-CODE (N6)  
> 2 AGENCY-CODE (A2)  
> 2 STATUS (A1)
> - \*\*\* Both Views \*\*\*  
> 2 PERSON-TYPE (A1)  
> 2 NAME-PREFIX (A60)  
> 2 NAME-FIXED (A60)  
> 2 NAME-REST (A60/1:4)  
> 2 ADDRESS-VALUE  
> 3 ADDRESS-LINE (A40/1:4)  
> 3 SUBURB (A30)  
> 3 STATE-CODE (A3)  
> 3 POSTCODE (N4)  
> 3 REDEFINE POSTCODE  
> 4 POSTCODE-A (A4)  
> 2 COUNTRY-CODE (A2)  
> 2 COUNTRY-NAME (A60)
> - 2 CUSTOMER-FOUND (L) /\* Out
> -

I wonder if the logical parameter (CUSTOMER-FOUND) is causing issues as we have many other web services working fine but none of them have a logical parameter in the response to the mainframe.

We’re running EntireX 8.1.3 and Natural 4.2.7 sp14.

Any ideas?

Thanks,  
Chris

---

<div class="post-metadata">

**Author:** ![Rolf\_Bahlke](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rolf_bahlke/32/109_2.png) [@Rolf\_Bahlke](https://techcommunity.softwareag.com/u/Rolf_Bahlke)\
**Post date:** [February 11, 2015, 9:26am UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511/2 "2015-02-11T09:26:00Z")

</div>

Hi Chris,

you cannot use UTF-8 with SAGTCHA & RPC.

So either do not use UTF-8 in the XML RPC Server (this is the recommendation) or change the conversion setting in the Broker to SAGTRPC.

---

<div class="post-metadata">

**Author:** ![Rolf\_Bahlke](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rolf_bahlke/32/109_2.png) [@Rolf\_Bahlke](https://techcommunity.softwareag.com/u/Rolf_Bahlke)\
**Post date:** [February 11, 2015, 12:18pm UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511/3 "2015-02-11T12:18:31Z")

</div>

My recommendation.

- do not change the setting of CONVERSION in the Broker attribute file
- in the entirex.xmlserver.properties file set “entirex.server.codepage==ISO8859-1”

---

<div class="post-metadata">

**Author:** ![Chris\_Brooks](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/chris_brooks/32/516_2.png) [@Chris\_Brooks](https://techcommunity.softwareag.com/u/Chris_Brooks)\
**Post date:** [February 12, 2015, 12:04am UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511/4 "2015-02-12T00:04:26Z")

</div>

Hi Rolf,

Thanks for your replies. Can I confirm that the double equals sign is a typo?  
We’ll try it and see if it fixes our error.

Regards,  
Chris

---

<div class="post-metadata">

**Author:** ![Chris\_Brooks](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/chris_brooks/32/516_2.png) [@Chris\_Brooks](https://techcommunity.softwareag.com/u/Chris_Brooks)\
**Post date:** [February 12, 2015, 5:09am UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511/5 "2015-02-12T05:09:46Z")

</div>

We made the change to the RPC server config code page as shown above.

We’re not getting any Natural errors and we see LS=ISO-8859-1 instead of UTF-8 now but we still see the 00200094 Msg truncated to fit receive-buffer error in the Broker trace as below:

> [@](#):
>
> W00/REQUEST 2015-02-12 14:17:53.108 ETBD0282 SPFX Values:  
> Prefix = 80010924000002440000002400000000000000000000032203000000000000  
> 0000000000  
> Unique-ID = 313546656231322D3130323430332D3030303032332D303030303138  
> Key string: ,BID=mvs:18025,F=SEND,UID=xmluser,CID=NONE,SC=RPC,SN=NATRPCD1,  
> SV=CALLNAT,W=60S,SL=544,RL=9788,LS=ISO8859\_1,API=9,XRL=0,ANODE=chocs-poc-w  
> l2,ATYPE=Java,AVERS=8.1.3.00,ANAME=Java Runtime,ETXL=256,RPCLIB=TMNEW,RPCP  
> GM=TM-GN1-N.  
> SeqID = 323  
> W00/RESPONSE 2015-02-12 14:17:53.110 ETBD0282 SPFX Values:  
> Prefix = 2201051C0000023C0000001C5CC1D5E200000000000002D701000000  
> Unique-ID = 0008E2DE28180000CE7E89640596290500000001CE7E89640595A805  
> Reply Strg: CID=1000000023000019,CST=NONE,CUID=xmluser  
> ,EC=00000000,RETL=00000544,TXT=Successful response  
> ,UOWST=RECV\_NONE.  
> SeqID = 320  
> W00/REQUEST 2015-02-12 14:17:53.293 ETBD0282 SPFX Values:  
> Prefix = 2201051C0001D1AE0000001C00000000000000000001D23901000000  
> Unique-ID = 0008E2DE28180000CE7E89640596290500000001CE7E89640595A805  
> Key string: BID=ETB333,F=SEND,UID=NATRPCD,CID=1000000023000019,SC=RPC,SN=N  
> ATRPCD1,SV=CALLNAT,W=NO,SL=119186,API=8,EL=0,RPCLIB=MQSERVER,RPCPGM=TM-GN1  
> -N.  
> SeqID = 324  
> W00/RESPONSE 2015-02-12 14:17:53.306 ETBD0282 SPFX Values:  
> Prefix = 2201051C0000001C000000005CC1D5E2000000000000006A01000000  
> Unique-ID = 0008E2DE28180000CE7E89640596290500000001CE7E89640595A805  
> Reply Strg: CID=1000000023000019,EC=00000000,TXT=Successful response  
> .  
> SeqID = 324  
> W00/RESPONSE 2015-02-12 14:17:53.306 ETBD0282 SPFX Values:  
> Prefix = 8001092400000024000000005CC1D5E2000000000000016F03000000000000  
> 000000006F  
> Unique-ID = 313546656231322D3130323430332D3030303032332D303030303138  
> Reply Strg: CID=1000000023000019,EC=00200094,RETL=0000119186,SEQID=323,UOW  
> ST=RECV\_NONE,TXT=API: Msg truncated to fit receive-buffer.

Is there any way for us to be able to see the payload? Perhaps that would help us to understand what the RPC Server is trying to push into the Broker and diagnose the problem.

---

<div class="post-metadata">

**Author:** ![Rolf\_Bahlke](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rolf_bahlke/32/109_2.png) [@Rolf\_Bahlke](https://techcommunity.softwareag.com/u/Rolf_Bahlke)\
**Post date:** [February 12, 2015, 8:41am UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511/6 "2015-02-12T08:41:40Z")

</div>

Do you see this error in the Broker trace only, or do you also get an error in thr RPC client?

Please send the complete Broker trace to support, the interesting stuff is not in the part you posted here …

---

<div class="post-metadata">

**Author:** ![Rolf\_Bahlke](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rolf_bahlke/32/109_2.png) [@Rolf\_Bahlke](https://techcommunity.softwareag.com/u/Rolf_Bahlke)\
**Post date:** [February 12, 2015, 9:29am UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511/7 "2015-02-12T09:29:35Z")

</div>

> [@Chris Brooks](#):
>
> Can I confirm that the double equals sign is a typo?

Of course it is a typo, sorry for the confusion.

---

<div class="post-metadata">

**Author:** ![Rolf\_Bahlke](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rolf_bahlke/32/109_2.png) [@Rolf\_Bahlke](https://techcommunity.softwareag.com/u/Rolf_Bahlke)\
**Post date:** [February 12, 2015, 10:26am UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511/8 "2015-02-12T10:26:28Z")

</div>

This is a completely different scenario.  
There is a Java or XML/SOAP RPC client which sends a request to a Natural RPC Server RPC/NATRPCD1/CALLNAT, library TMNEW, program TM-GN1-N with a receive length of 9788 bytes.  
The RPC Server seems to change the library to MQSERVER and returns 119186 bytes.

The consequence is the “Msg truncated to fit receive-buffer” error on the client side. However, the RPC client should reread the message with the correct length and continue without an error. So in this case the error in the Broker log can be ignored.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:32pm UTC](https://techcommunity.softwareag.com/t/msg-truncated-to-fit-receive-buffer/180511/9 "2021-04-02T15:32:51Z")

</div>


