If you also use the -unbuflog parameter when you start your batch, then messages are written to the log as they arise rather than paged. With an appropriate text file browser, you can then periodically open your log to check for messages. Note that most browsers will lock the file, and this is to be avoided. However, you can also copy the log and read the copy.
All of this is a little clumsy, but other solutions are possible using additional statements in your program to pop up windows in your operating system when errors are detected. This however is a reasonably complex piece of work, and since I work on the basis that an error in a log means all after the error is tainted, I will usually set the session option to ErrorAbend so that the session stops when an error occurs rather than have some hours of run time to produce a flawed output.
Kind regards
David
