Yup.. Open iSeries Navigator. Go to Management Central. Select "Monitors" and then "Message" IBM has thoughtfully provided an example of a message monitor. You can create your own. Right-click on the sample and select "New based on". Give your new monitor a name and description. Set up the monitoring specifics through the "properties". The built-in help is pretty good on this. In general - You can monitor for specific CPF messsages or general thing like any Inquiry message. You set up a "trigger" value - and an optional OS/400 command that will be used when that trigger value has been reached. You can also set up a reset command. You select a collection interval. You can also specify that this monitor only runs at specific times or days. If you have multiple systems you can select the system or systems to monitor. We set up our own simple email messaging system and a QSYSOPR monitor - and the trigger command calls our system to send out an alert email. A few caveats - The trigger command should be a command, not a program call. ( It can be a user-created command that exectues a program. ) Navigator provides paramater values you can pass to the command - you'll have

Yup.. Open iSeries Navigator. Go to Management Central. Select "Monitors" and then "Message" IBM has thoughtfully provided an example of a message monitor. You can create your own. Right-click on the sample and select "New based on". Give your new monitor a name and description. Set up the monitoring specifics through the "properties". The built-in help is pretty good on this. In general - You can monitor for specific CPF messsages or general thing like any Inquiry message. You set up a "trigger" value - and an optional OS/400 command that will be used when that trigger value has been reached. You can also set up a reset command. You select a collection interval. You can also specify that this monitor only runs at specific times or days. If you have multiple systems you can select the system or systems to monitor. We set up our own simple email messaging system and a QSYSOPR monitor - and the trigger command calls our system to send out an alert email. A few caveats - The trigger command should be a command, not a program call. ( It can be a user-created command that exectues a program. ) Navigator provides paramater values you can pass to the command - you'll have