|
<Mark> Wouldn't something like a *DTAQ or possibly even something "heavier" like MQSeries be a better choice than a *USRSPC? The *USRSPC is a great way to pass the data efficiently, but it seems like it forces you to handle all of the "queuing" aspects that would be needed to deal with high-volume and that you get for "free" by using a queueing delivery system. </Mark> I will take a look into MQSeries. I have to distribute this to around 20 - 30 iSeries machines so cost may put that idea in the grave. I have actually already built the dynamic call functionality that I described, so I will probably just go that route. It isn't much, but it is exactly what I need. <Mark> Also, have you considered driving it more from Java? In other words let it parse the XML and make all of the decisions and just call the appropriate RPG programs directly to process the transactions? </Mark> I will be calling the RPG program directly and I will tell it which User Space to look for the data in. I am guessing you are saying to just pass the data as a parm to the RPG program?? I have thought of this, but there are going to be many times where my data could exceed 65,535 bytes (i.e. large PO) and for sure I would hit up against the 7 parm max of PCML. The User Space is nice because there is only ever one version of the data in memory or on disk. If I sent it the other way I am not so sure that would be the case (I will have to look into PCML a little more to verify this). Thanks for your comments, Aaron Bartell
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.