|
Brad, The biggest difference between the two would be the extra overhead of a job vs a thread. You can reduce that overhead some with prestart jobs. The biggest concern with multi-thread jobs is that a lot of legacy (including system) code does not behave well in a multi-threaded environment. David Morris >>> brad@bvstools.com 02/25/02 10:42AM >>> Just thinking outload here. Let's assume I have an appliation that I want to run many times simultaniously. Assuming I'm running the aplicate on the 400, what would be "better". 1 - Running the application in multiple jobs (ie submitting the job x times into QSYSNOMAX or something similar) 2 - Running many instances of the apllication using Java threads? I'm guessing it really won't make much of a difference unless job resource allocation comes into play. Bradley V. Stone BVS.Tools www.bvstools.com
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.
midrange.com
