|
<Previous Thread> I'm not trying to be a wise guy, but... you do put the cursor on the error message and hit F1 don't you? And display the job log and put the cursor on the messages and hit F1 again? In fact, everywhere you have a question, you hit F1 to see if there's more info available right there? Sorry if this answer is stupid, but I've forgotten to check the plug on the toaster too many times. ----------------------------------------- <Response> Hi, Yes, but, it's good to ask. I have met programmers that are unaware of this simple function. In some partial listings of error messages I have seen, they briefly explain WHY a certain error message would occur. This is helpful when the only Message description is "communications error" and the only helpful system advice is "to fix problem, change program". Thanks, Jeff Burcher AS/400 Programmer GMA/CBCC (336) 378-6300 x3207 fax: (336) 378-6266 jburcher@cbcolcntr.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.