How do I create a global monitor message in a script and what types of messages can I monitor for?
When you put the command MONMSG at the beginning of a script—before any comments or declare statements (DCL) and without specifying a message ID—it acts as a global monitor message. This means the script will continue processing every command—even if an earlier step ended in error. If you have a multi-step process where a report relies on the successful completion of an execute statement to build a work file, you shouldn’t use a global MONMSG. Use the global MONMSG command only to monitor for escape messages.