# ACI RPC bridge : varaible length structure **URL:** \ **Category:** Forum\ **Tags:** Mainframe-Integration, EntireX\ **Created:** [August 24, 2006, 5:10pm UTC](https://techcommunity.softwareag.com/t/aci-rpc-bridge-varaible-length-structure/59691 "2006-08-24T17:10:38Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jose\_de\_vogelaere](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jose\_de\_vogelaere](https://techcommunity.softwareag.com/u/jose_de_vogelaere)\ **Post date:** [August 24, 2006, 5:10pm UTC](https://techcommunity.softwareag.com/t/aci-rpc-bridge-varaible-length-structure/59691/1 "2006-08-24T17:10:38Z")
Suppose you have an ACI server. It receives a fixed length structure but sends a variable length return message composed of a fixed part with a variable length part containing a variable length array. sample return message 1 F\_field1 (A10) 1 F\_field2 (A20) 1 F\_returned\_rows (A3) 1 rows (1:999) 2 V\_field1 (A10) 2 V\_field2 (A20) F\_returned\_rows contains the actual number of rows returned and the ACI returned\_length field is 33+x\*30 depending on the number of occurences. Can we map this via the RPC ACI bridge ? ---
**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:** [August 30, 2006, 5:56pm UTC](https://techcommunity.softwareag.com/t/aci-rpc-bridge-varaible-length-structure/59691/2 "2006-08-30T17:56:59Z")
Hi Jos ---
**Author:** ![jose\_de\_vogelaere](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jose\_de\_vogelaere](https://techcommunity.softwareag.com/u/jose_de_vogelaere)\ **Post date:** [August 30, 2006, 11:28pm UTC](https://techcommunity.softwareag.com/t/aci-rpc-bridge-varaible-length-structure/59691/3 "2006-08-30T23:28:23Z")
The bridge works with a property file. we could add some customization properties. Some example: We could have a simple property like Default\_values\_if\_too\_short\_reply\_message. Then the bridge could accept if the aci server sends a too short message and assign default values to the fields of the return RPC message. Defaults would be blanks for string, 0 for numerics, etc, etc. We could even try more complex properties like: occurences\_table(1)=field(3). meaning the number of occurences of the first table is available as content of field 3. ---
**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:39pm UTC](https://techcommunity.softwareag.com/t/aci-rpc-bridge-varaible-length-structure/59691/4 "2021-04-02T14:39:59Z")