|
>-also, where can i find out about the >errors i get on the DISPLAY ALL MESSAGES >and ADDITIONAL MESSAGE INFORMATION screens? Check the job log of the job. In this case, I assume you are running the program interactively (as opposed to doing a SBMJOB and running it in batch.) When you get a "white message," put the cursor on it and press F1/Help. You will be given the second level help (Additional Message Information) display. This tends to give somewhat more detailed information about the message, but wait: there's more! Most things that produce error messages will produce 2 kinds: diagnostic and escape. The escape message tells the program that it has received an error and it should take care of it. The diagnostic message(s) indicate the details about why an error occurred. To see these diagnostic messages, you need to look into the job log. If you're at the second level help display, press F10 to see the job log. You should be able to see the CALL command, followed by the diagnostic messages, followed by the escape message. Put the cursor on the diagnostic message of your choice and press F1/Help for more info about that error. I think you'll find the diagnostic messages more useful than the more generic escape message. Buck Calabro CommSoft, Albany, NY mailto:mcalabro@commsoft.net * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. 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-2025 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.