|
I just wanted to clarify a few things, since I started this thread. All I really wanted to be able to do was to do a MONMSG on a RUNJVA command to know when my Java class wasn't able to successfully do what I wanted it do. Before I went ahead and wrote all the programs, I just wanted to test that you could make RUNJVA send the escape message. So to test this, I used SBMJOB on a RUNJVA command of a class that was just setting System.exit(1). Normally, when the command you run on a SBMJOB ends with a *ESCAPE message, the job ends abnormally, this is because "normally" *ESCAPE messages have a severity that is greater than zero. Mandy has shown that you can in fact do a MONMSG and catch the error, and others have capably explained the various reasons why the SBMJOB ends normally. Thanks to all. It looks like I should be able to do what I want. Mark +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
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.