I'm not using z/OS Batch Runtime rather it's a plain vanilla batch job using JZOS to run Java code. My reasons for not using a transaction manager are as follows: - The process is pretty simple and does not need all the features they offer. - I hoped that I would be able to use RRS to coordinate unit of recovery between the two RM's. Isn't that what RRS is for ? - The process was implemented is WAS on z in the official project ( my experiment is just an experiment ) and the results were not exactly thrilling. The amount of cpu that implementation consumed actually killed the project. I don't know if it was due to WAS or the application code as I don't know much about either and the experts were at loss to explain it. Now the question is if the use of RRS is in some way restricted for us outsiders although the manuals don't describe it like that. If it is not restricted then I'd like to know how to do it in my batch process. After all aprt from this one glitch it's working fine and using a lot less resources.
Mohammad On Fri, 4 Apr 2014 14:10:26 +0800, Timothy Sipples <[email protected]> wrote: >A threshold question: Why are you reluctant to take advantage of a >transaction manager? That's what transaction managers are designed to do, >along with several other things. > >I think you're referring to the z/OS Batch Runtime which then invokes JZOS, >by the way. My recollection is that the z/OS Batch Runtime in z/OS 2.1 >introduced resource coordination between DB2 and VSAM, but multiple >resources beyond that pair are out of coordination scope/RRS. Transaction >managers, e.g. CICS Transaction Server, IMS Transaction Manager, and >WebSphere Application Server for z/OS (to pick three notable examples) can >all span MQ and DB2 and other resource managers with RRS. > >-------------------------------------------------------------------------------------------------------- >Timothy Sipples >VCT Architect Executive (Based in Singapore) >E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
