Author |
Message
|
tdwells |
Posted: Wed Aug 06, 2003 5:36 am Post subject: Workflow Variable length String Element |
|
|
Apprentice
Joined: 30 Oct 2002 Posts: 42
|
Does anyone know the maximum length that data can be when an element is defined as a variable length string? _________________ IBM Certified Specialist - MQSeries |
|
Back to top |
|
 |
jmac |
Posted: Wed Aug 06, 2003 5:43 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
It would be the maximum size of the container, whcih I think is now 4M... Of course then it would be the only memeber in the container... _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
tdwells |
Posted: Wed Aug 06, 2003 6:14 am Post subject: |
|
|
Apprentice
Joined: 30 Oct 2002 Posts: 42
|
Thanks JMac.
Originally, I designed my container with an array-based data structure since I had certain fields that could be repeated up to 999 times.
However, workflow runtime would complain that the mapping was longer than the allowed maximum of 8516 when I would try to set the array size to 20 or more array rows (There's approximately 40 elements within the repeating data structure) plus about 30 other elements defined in 2 other non-repeating data structures. Therefore, I was thinking of just combining this repeating information into 1 string prior to imputting into Workflow as an XML message. Then that 1 string would just be input into a non-repeating variable length string element.
Any other suggestions or cautions? _________________ IBM Certified Specialist - MQSeries |
|
Back to top |
|
 |
jmac |
Posted: Wed Aug 06, 2003 6:38 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Well the array of 999 hit up against the other limit, which says no more than 512 members in a container.
Programming Guide wrote: |
A data structure is uniquely identified by its name and contains an ordered list of data members. At Runtime, it can become a stream of 4 MB passed between the client and the server.
A data structure can have up to 512 user-defined data members. A data
member that represents an array of data members counts with as many data members as it has elements.
|
I am not sure I understand the error you received relating to 8516??? Sounds like maybe you need to open a PMR _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
TJW |
Posted: Thu Aug 07, 2003 12:47 am Post subject: |
|
|
Novice
Joined: 11 Dec 2002 Posts: 16 Location: UK
|
The '8516' error can occur during translation of the fdl, it looks something like this ...
FMC26503E Data connector mapping between 'STEP1' and 'STEP2' with size of 10740 bytes is longer than the allowed maximum of 8516 bytes.
It occurs when too many data mappings are defined for an activity.
NB: When an imported fdl is translated by Workflow it creates a mapping for each element, so what looks like a single mapping of a data structure in an FDL can result in hundreds of element mappings when it is translated! |
|
Back to top |
|
 |
amittalekar |
Posted: Thu Aug 07, 2003 6:10 am Post subject: |
|
|
 Disciple
Joined: 03 Apr 2002 Posts: 166 Location: VA, USA
|
just a suggestion.......
It is not a good idea to have so many elements in data structure.... u may face lot of performance problems because of this. .... think of putting this large data somewhere else and use pointers to this data in WF if possible. |
|
Back to top |
|
 |
|