# Conversion error on server

**URL:** <https://techcommunity.softwareag.com/t/conversion-error-on-server/90750>\
**Category:** Forum\
**Tags:** Mainframe-Integration, EntireX\
**Created:** [July 22, 2009, 4:24am UTC](https://techcommunity.softwareag.com/t/conversion-error-on-server/90750 "2009-07-22T04:24:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JHCloete](https://avatars.discourse-cdn.com/v4/letter/j/0ea827/32.png) [@JHCloete](https://techcommunity.softwareag.com/u/JHCloete)\
**Post date:** [July 22, 2009, 4:24am UTC](https://techcommunity.softwareag.com/t/conversion-error-on-server/90750/1 "2009-07-22T04:24:58Z")

</div>

Dear forum,  
I currently have an occurence/array of 260 on a group level field using ACI.

When I try the same occurence/array size using RPC I get “10146974: xxxxxxxxx 9999 NAT6974 Conversion error on Server, reason 4 ,000”.  
When I change the size to 235 occurences then I do not get the error. Anything bigger produces the error.

My question is, under RPC is this the maximum size(235) or is this a bug, or is there a parameter to change in the attribute file to get more occurences?

Best regards  
Hennie

---

<div class="post-metadata">

**Author:** ![anon66457657](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@anon66457657](https://techcommunity.softwareag.com/u/anon66457657)\
**Post date:** [July 22, 2009, 11:43am UTC](https://techcommunity.softwareag.com/t/conversion-error-on-server/90750/2 "2009-07-22T11:43:47Z")

</div>

Dear Hennie,

please increase the MAXBUFF value on the Natural RPC server side.

With RPC632 which is delivered with NAT425 all buffers are dynamically increased on demand.

Best regards,  
Wolfgang

---

<div class="post-metadata">

**Author:** ![anon66457657](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@anon66457657](https://techcommunity.softwareag.com/u/anon66457657)\
**Post date:** [July 22, 2009, 11:49am UTC](https://techcommunity.softwareag.com/t/conversion-error-on-server/90750/3 "2009-07-22T11:49:08Z")

</div>

Dear Hennie,

please increase the MAXBUFF value on the Natural RPC server side.

With RPC632 which is delivered with NAT425 all buffers are dynamically increased on demand.

Best regards,  
Wolfgang

---

<div class="post-metadata">

**Author:** ![Douglas\_Kelly](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/douglas_kelly/32/102_2.png) [@Douglas\_Kelly](https://techcommunity.softwareag.com/u/Douglas_Kelly)\
**Post date:** [July 22, 2009, 11:32pm UTC](https://techcommunity.softwareag.com/t/conversion-error-on-server/90750/4 "2009-07-22T23:32:59Z")

</div>

Other sizes to check as you go:

- RPCSIZE \> MAXBUFF (minimum of MAXBUFF + 4, but more is usually needed. With a large array, I’d probably use MAXBUFF + 256)
- MAXBUFF \< MAXMSG (MAXMSG is the EntireX Broker Attribute, set on the mainframe Broker server side)

RPC will require a larger buffer as it carries not only the payload that you had in the ACI call, but also a “format buffer” and other information that describes the payload down to the field level.

---

<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, 2:57pm UTC](https://techcommunity.softwareag.com/t/conversion-error-on-server/90750/5 "2021-04-02T14:57:17Z")

</div>