Structured data transfer (was: JT400 components)

On 9/12/2011 10:09 AM, Joe Pluta wrote:

It depends on how I'm doing the impedance matching. If I send or
receive all the detail at once, a data queue is nice. I have other
situations where I send/receive the detail one record at a time (first I
send the header, then each detail). In that case, I use two data DS's,
but the control DS tells me which one actually has data. It isn't
perfect, but it avoids an extra queue. Of course, the additional queue
could be either a feature or a bug depending on your design requirements.

In my case, I am sending all the data at once (usually for validation or a batch transaction), so the data queue technique works well.

I basically generate a unique key and send the data to the queue ... then call the program, passing the key as one of the parameters (perhaps in a structure).

The data is processed by the host program, and then a new key is generated the results send back to the same data queue with the new key. The host program returns the generated key back to the java code which reads the data queue with the generated key to get the results.

If I was only processing a single detail record at a time, I would probably pass the header & detail at one time as you describe.

david