|
Hello all, I don't generally like my interface programs to monitor files or data areas to determine when to shut themselves down; I prefer to have them capable of determining when the operator has issued ENDJOB, ENDSBS, or PWRDWNSYS. This prevents constant needless I/O to some other control structure. I'm trying to find a way to gracefully end one of my Java classes through the ENDJOB system command, in an equivalent fashion to the RPG SHUTDN op-code. Does anyone have a method they would recommend? I'm toying with Thread.isInterrupted(), but I don't want to have to check. I prefer, if possible, to just catch an InterruptedException or some similar mechanism because the thread is usually in an indefinite wait on a data queue (-1 timeout). At this point, I've just experimented with ending the job *CNTRLD from an external (interactive) job and for some reason an exception never gets issued. Any ideas would be greatly appreciated. If I can get this thing working the way I'd like, we'll have a lot better chance at getting our shop migrated more towards the Java world. Thanks, == Kristofor Jacobson Casino Applications Manager Mandalay Resort Group __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.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.